Can anyone tell the methoad with explanation to how to flash any rom.. It will be a great help
1st, my suggestion for you ( or any other without any knowledge about custom things ) to stay with the stocks. When you at least, know the basic of every related things, then u can start to steps into the custom world. ( no offense, my friend, its for your own goods.
2nd, as per your request, I'll list below the basic process ( from the very beginning, so that u can have the big picture ) to have custom ROM on your device.
+ First, most important, and a MUST step for everyone or any devices, is to UNLOCK the BOOTLOADER. Before the bootloader is unlocked, you will not be able to have any further actions with your device but to use it as it is. For Xiaomeme devices, you will need a Mi Account, bond it with your device ( at Dev Options ) , then download Mi Unlock, and wait for the set time of Xiaomeme ( normally, its 7 days now ). After 7 days, you can use Mi Unlock to unlock your device's bootloader ( all your data will be wiped ) . Now, u done the 1st step.
+ Second, you will need to find for your device a Custom Recovery, it's not only help you to simply the ROM flashing process, but also many other tasks that u will have to do. Besides, it's name is Recovery also for a reason. If anything goes wrong during the "playing time" you can always boot into recovery and restore the latest known good backup that u did before to bring your device back to normal state. Now there's few options for Custom recovery and luckily, there's always be one suit for you device ( not like before, TWRP is the only one and if ur device is not supported yet, then...............) In case ur device is Redmi Note 10, you can try TWRP unofficial build of Nerbessky, it's kind of fully functions for normal needs of most users.
+ 3rd, find and download a ROM build for your device, then follow the ROM's manual to flash the ROM into the device. Each ROM will have it's own method of flashing, so remember to always read the ROM's manual before trying.
So, here's the basic process of how to have a custom rom on a devices, hope it'll help!
Bro can you tell the steps I written below is accurate or not
- Format Data
- Wipe Dalvik / Cache/ System / data
- reboot to recovery
- Flash latest global firmware
- Flash rom zip
- Flash disable force encryption
- format data
- Install Magisk
- Reboot to recovery
- Flash twrp
- Reboot to recovery
- Reboot to system
Jaydeep_kumar said:
Bro can you tell the steps I written below is accurate or not
- Format Data
- Wipe Dalvik / Cache/ System / data
- reboot to recovery
- Flash latest global firmware
- Flash rom zip
- Flash disable force encryption
- format data
- Install Magisk
- Reboot to recovery
- Flash twrp
- Reboot to recovery
- Reboot to system
Click to expand...
Click to collapse
No they are not, at least for RN10. follow what @LinhBT said.
MNQuaser said:
No they are not, at least for RN10. follow what @LinhBT said.
Click to expand...
Click to collapse
Bro can you please send here how to?? Pls
Jaydeep_kumar said:
Bro can you please send here how to?? Pls
Click to expand...
Click to collapse
@LinhBT did a great job explaining. let me simplify.
- unlock bootloader. the process will automatically factory reset your device, so backup before doing this
- flash custom recocary via fastboot
- wipe everything
- flash desired rom and optimally gapps for some roms.
- reboot and enjoy
different roms might require additional steps. but these are the basics.
Related
I used to flash new ROM's on my old Galaxy S2 and there was never a issue of bootloader thing and same goes for old Xiaomi phones like redmi 1s.
But recently When xiaomi started locking bootloader , even after unlocking bootloader ,In most of ROM threads there is warning to delete the bootloader file from MIUI recovery ROM and then flash the ROM through recovery as it'll relock the bootloader.
Why does this happen so ?
1) What is the difference between official and unofficial unlocked bootloader ?
2) How much difference does one make if we want to flash all type of ROM's including MIUI , CM ,RR etc ?
3) Is there any way in which bootloader once unlocked , we don't have to worry about getting it relocked by flashing other ROM's like exactly what happens in most other android smartphones after unlocking their bootloader ?
Please clear the above doubts as it's becoming very confusing and irritating on flashing the ROM and what points needed to be kept in mind to avoid bricking the RN3.
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
lack of good/complete tutorials
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
timberwolf60 said:
Read this thread, my phone was officially unlocked the bootloader and used alka twrp to flash official rom with the ease. No need to do anything, just flashed it, superSU and exposed. Rebooted my phone, done. Only failed on incremental ota update, rebooted phone and received a second ota full rom and always success.
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
That is a lot of If else there
Why we can't just flash any rom after unlocking bootloader officially and always have to fear about bootloader relock again?
If i am not mistaken this situation is in Xiaomi phones right ?
Dust2Dust said:
I believe flashing has always been a tricky job, more or less. The fact of the matter is that (for our device) I see very little complete tutorials in ROM threads, they all focus on the last bit of flashing. Some hazards are being mentioned and in the best case scenario you get a link to a vague solution (cross other forums and boards), never a full tutorial in the starting topic or the second post however. Back in the days you would see full explanations in every ROM thread, first posts were even being reserved for that. Nowadays users are being supposed to know it al which most do not.
Besides from the complete guides I also noticed that whenever something is explained, the explanations themselves are poor in terms of language (grammar as well as vocabulary) causing even more problems for newbies to fully understand what they are up to.
I am ne to the Xiaomi community but I am absolutely not new to flashing, cooking etc. (started back in the days with iPAQ's and so on) but I also had a though time to end up where I am now with a official unlocked phone that is rooted, has a custom recovery and a Xiaomi.eu ROM. MY journey was a long one but I must conclude that none of the steps were a real hazard, but combining everything in a workflow in correct order was a pain in the back.
First thing that came to me was the idea of writing down my experiences in the form of a FULL tutorial, which I might do when I find the time. I am pretty sure this will help many fellow flashers, newbies and pro's, to establish what most of us did.
These were just my two cents.
P.S. One more thing I noticed is that there are a lot of unfinished projects, they do the job that they were needed for, but they do nothing else.
e.g. Why are there so many custom recoveries, are there no developers anymore that can combine them all to one-fits-all ?
Click to expand...
Click to collapse
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Xiaomi.eu weekly rom was cooked from cn dev rom, removed Chinese apps and put in Google apps and more European languages. Those who wish to flash it must officially unlocked bootloader.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
and What's the difference between officially and unofficially unlocked bootloader ? i have unofficially now , should i officially unlock it ? if it makes flashing procedure easy ?
akhil17kr said:
Yes right , but i think Xiaomi is the culprit here for every complicated procedure here.
What's the difference between officially and unofficially unlocked bootloader ? and how's Xiamio.eu ROM is different from global stable ROM ?
Click to expand...
Click to collapse
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Dust2Dust said:
Couple of examples: Xiaomi.eu gives me different locales and languages. It also sets default GPS location to Europe instead of Asia which provides a faster GPS fix. It is however behind in development so it doesn't have MIUI 8 yet.
As for the bootloader unlock: I have not looked into that since there is no need. If you follow all the steps in correct order and with correct ROM's official unlocking cannot go wrong. The culprit however is the complete chaos (now I said it) in instructions and tutorials. So I have not looked into the unofficial bootloader unlocking.
Click to expand...
Click to collapse
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
I did the same steps above after flashing resurrection remix with cm13 radio,after restoration of miui from twrp Alka backup my fingerprint sensor stopped working bcos the firmware didn't restore and I unchecked that partition so what i did was again.
1) go back to twrp Alka
2) flash the full MIUI 8 rom .zip and rebooted
3) then the fingerprint started working .
So Alka twrp has a bug in Restoration of firmware partition .so be careful and have a full twrp Alka backup and then flash cm13 and firmware
akhil17kr said:
do you mind reading this question and clarify the steps , asked in Official CM13 thread. Nobody answered there:-
"Hey , I've unlocked RN3 bootloader unofficialy and currently on MIUI stable version with root and TWRP recovery.
I want to taste official CM13 but no plans to use it , just test it. After using it for day or 2 , i want to switch back to my MIUI ROM.
What should be the ideal steps through which i can avoid all these hassles of Bootloader relock stuff.
Can't we just normally go back to MIUI ROM by restroing using TWRP backup ?
Here's what i'll do , please correct the steps:-
1) Flash TWRP alka version and make complete backup of current MIUI ROM.
2) Wipe system ,data, cache,dalvik cache.
3 First flash CM-fIrmware file,then CM13 ROM , then gapps.
4) Reboot and use CM for 2-3 days.
Now to go back to the MIUI ROM backup:-
1) Reboot to alka recovery.
2) Wipe system ,data, cache,dalvik cache.
3) restore the MIUI Nandroid backup (Deselect firmware file.)
4) Reboot
DONE ! Back to MIUI.
If my steps are right ?
Please guide on the same. "
Click to expand...
Click to collapse
They look more or less correct, I choose not to go the CM way (yet) since there are still some flaws that I can't live with.
I would try to go to official unlock, whatever it takes. It just looks more solid & safe from what I have been reading so far.
Also I would choose to use an other Recovery:
Official TWRP with F2FS Support
• Based on official TWRP 3.0.2-2 & updated CyanogenMod source
• Adds Support For F2FS based file systems.
• Used for flashing official CyanogenMod 13 based ROMs.
• Users with official unlocked bootloader will have to flash Universal Boot Img Patcher (UBP) after flashing MIUI Recovery ROM Zip.
• Users with unofficial unlocked bootloader should strictly not use this TWRP for flashing MIUI Recovery ROM Zip.
That seems optimized for CM the most.
II should tell you that I received the phone two days ago and I am also still catching up on reading.
Add on, taken from the above link:
In case of unofficial unlock:
4. Flashing Official CM13 ROM
• Flash F2FS TWRP & Backup Current ROM.
• Select /data & /cache Partitions & Select Change File System
• Select F2FS & Swipe To Change
• Reboot to Recovery & Factory Reset
• Reboot to Recovery & Flash CM13 Firmware
• Reboot to Recovery & Flash CM13 Zip
• Flash Appropriate GApps Version Zip & Reboot to System
• To Return Back To Any ROM After Flashing CM13, Flash Safe TWRP v2 & Proceed.
Heya,
This is my first time attemtping unlocking/twrping/flashing custom rom on any device, so I'm aware that I'm complete newbie in this.
I was following the guide on the miui/mipad 4 forum
I have succesfully unlocked the bootloader.
I have succesfully installed TWRP.
But I'm stuck after the next step the guide said to flash an included noverity zip file. I did that, hit clear cache/dalvik and rebooted device (no other option to exit that menu). Now I'm stuck on booting screen - small MI logo in middle and three small blinking dots at the bottom...
What do I do? Is this the popupar bootloop? Do I reflash fastboot miui rom? Help...
Just flash any custome rom available. Xiaomi.eu, moke.v.v.
•Stock Miui will not boot after flash any custome recovery. Sorry, my English not good enough.
KimUyLong said:
Just flash any custome rom available. Xiaomi.eu, moke.v.v.
•Stock Miui will not boot after flash any custome recovery. Sorry, my English not good enough.
Click to expand...
Click to collapse
That's why I present the ONLY WORKING CUSTOM RECOVERY, but since some users decided to hijack my thread with pointless rant about no clear instruction to fastboot it + some broken TWRP link, yeah, enjoy your NOT WORKING stock MIUI...
It just need a basic fastboot flash command (already included in the OP), follow the instruction to get root (no flash needed, it got Magisk 17.1 already & WORKING PROPERLY via Advanced menu)...
Xposed need to wipe /data to disable encryption.
https://forum.xda-developers.com/mi-pad-4/how-to/recovery-twrp-t3851971
PLoK said:
Heya,
This is my first time attemtping unlocking/twrping/flashing custom rom on any device, so I'm aware that I'm complete newbie in this.
I was following the guide on the miui/mipad 4 forum
I have succesfully unlocked the bootloader.
I have succesfully installed TWRP.
But I'm stuck after the next step the guide said to flash an included noverity zip file. I did that, hit clear cache/dalvik and rebooted device (no other option to exit that menu). Now I'm stuck on booting screen - small MI logo in middle and three small blinking dots at the bottom...
What do I do? Is this the popupar bootloop? Do I reflash fastboot miui rom? Help...
Click to expand...
Click to collapse
head to my thread, forget those noverity bullsh!t...
you only need to flash the LR.Team's TWRP and do the Magisk install (root) via Advanced menu then you'll be happy, trust me.
for now: reflash original stock ROM, flash TWRP, do the root via Advanced menu, reboot to system & you'll see...
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
nasos_Gr said:
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Click to expand...
Click to collapse
Miui decided to use MODIFIED VENDOR IMAGE hence POCO F1 gets a modified vendor image for Android Pie-based Project Treble GSIs
what was the impact?
custom roms couldn't be flashed (booted) if you don't flash the modified vendor image from twrp
even today when most of the roms have their own vendor you still need to flash the vendor+firmware (atleast)
Developer Akhil Narang started collecting all releases at
https://mirror.akhilnarang.me/MIUI/beryllium/
currently I am using 9.6.27-9.0 which is working best for me, 10.3.6 image made my batter drainage high (atleast i noticed)
I am on HAVOC2.8 and this is how i did it
1. flashed TWRP 3.3.1 unofficial (download it from HERE ) ref Reference - as official twrp has TOUCH driver issues. this one worked with me very well
2. I wiped /data, /system then
3. flashed VENDOR.zip from HERE
4. FLASHED CUSTOM ROM (i use HAVOC2.8)
5. FLASHED DFE HERE - REFERENCE
6. FLASHED GOOGLE APPS ( GAPPS.ORG) ( ARM64>9.0MicroPackage)
7. Flash Kernel ( OPTIONAL- havoc uses shadow kernel , i feel optimus drunk kernel is better, battery and 4g connectivity) even Franco Kernel is very good
8. FLASHING MAGISK19.3
9. when i was on havoc2.7, by using MIGRATE, it made flashable zip of my APPS+DATA, stored in internalStorage, and now I will FLASH that file., Mine size goes to 2gb you can get it from HERE
10. WIPE CACHE/DELVIK
11. REBOOT
fire reboot may go in to bootloop and then second reboot may take a while and finally you should see Pixel Setup asking google accounts and info etc
-----------------------
extraa
once after you finish setup! don't RESTORE APPS from PLAYSTORE, (download only license apk, in my case I have purchases many apps from playstore and saperate license info is always appear in intial setup! SELECT THOSE ONLY)
ONCE playstore is DONE downloading all your selected (fewer) apps, and MAGISK ROOT is working...... put device on AIRPLANE MODE
FROM DROP DOWN Notification panel, CLICK MIGRATE, and it will prompt you what do you wana restore from your previouce ROM to newly flashed HAVOC ..APPS+SETTINGS+PERMISSION+DATA etc - migrate restoration may take upto 30 mins,
once done, uninstall from system and reboot device!
REMEMBER I DONOT RECOMEND MIGRATE TRICK FOR WHATSAPP, it doesn't work properly and NOTIFICATION ISSUES with BLANK DP observed by me whenever I forcely re-instated whatsapp by migrate!
Martensite said:
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
Click to expand...
Click to collapse
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
nasos_Gr said:
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
Click to expand...
Click to collapse
Flashing custom roms will not wipe anything, so the vendor is still there. And firmwares too.
Hello
I am trying to update for a while now, but I just cannot get it installed.
I already have TRWP 3.3.0.0 running on a rooted Pocophone F1.
I am still kind of newbie using LOS, sorry. Some stuff I still don't understand even though spending lots of time reading and googling and reading...
What I do:
I start TRWP and wipe: WIPE ADVANCE Dalvik,Cache,System,Data
I install in the following order:
beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware
lineage-16.0-20191003-nightly-beryllium-signed
Disable_Dm-Verity_ForceEncrypt_02.04.2019
Magisk-v19.4
open_gapps-arm64-9.0-mini-20191003
then I reboot, stare a while on the working LOS-installing-log and...
boot to TRWP
I am experiencing problems while installation for some time, so I already tried:
- wiping dalvik after each zip during installation
- Magisk-v19.3
- leave out open-gapps
- beryllium-9.6.27-9.0-vendor-firmware
- lineage-16.0-20190807-nightly-beryllium-signed
- lineage-16.0-20190929-nightly-beryllium-signed
Where do I find information on which corresponding vendor/firmware to be used for LOS16?
Looking at the screen while installation of lineage-16.0-20191003-nightly-beryllium-signed, I read: "... Target: ...V10.2.3.0.PEJMIXM..."
So I guess I should flash that mentioned vendor/firmware version for that mentioned LOS version, but I just don't know where to download that vendor/firmware. It is not available on the server of akhilnarang...
Maybe I'm wrong and there might be another problem, I just do not know what to do.
Best regards
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Prior to now, I had a 6 month old LOS working up to now.
My last attempt:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
says: "If you plan to install custom kernels, flash the zip AFTER installing Magisk".
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Zackptg5 says:"If you're not encrypted: flash all of your stuff, then FLASH THIS ZIP LAST"
I use the most recent DFE Disable_Dm-Verity_ForceEncrypt_10.01.2019 from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page64
most actual vendor/firmware i find here: https://xiaomifirmwareupdater.com/firmware/beryllium/
is: fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
I have not found a trustworthy source for the very new 10.3.8.0, but this should not be an issue...
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
I am really pissed off at this point.
I can still enter TRWP 3.3.0.0 by pressing ON+VOLUP
I don't know any further.
So then, my new order is:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- Magisk-v19.4
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
Done that and REBOOT SYSTEM and....
Pocophone boots into FASTBOOT...
Why you didn't follow my instructions? clearly you dont understand ...
Oh...
I read your reply again, so is it correct you want me to:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT to RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
? ok in this order?
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Andi900rr said:
Sorry, found another mistake in my last description, now I tried:
WIPE ADVANCE Dalvik,Cache,System,Data,internal
INSTALL in the following order:
- fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- open_gapps-arm64-9.0-mini-20191003
- Disable_Dm-Verity_ForceEncrypt_10.01.2019
then
WIPE Dalvik and REBOOT SYSTEM
-> after REBOOT SYSTEM, Poco F1 instantly starts into FASTBOOT. I then press ON+VOLUP to enter RECOVERY and then
INSTALL
- Magisk-v19.4
then
REBOOT system
-> still, Poco F1 instantly starts into FASTBOOT again.
That is where I am stuck now.
Click to expand...
Click to collapse
install a global rom via twrp the latest one with 10.3.8.0 recovery flashable
go to twrp
flash the miui stable ..and then flash magisk 19.3 ..format data then reboot ... and then follow the steps i already given..
watch this for your reference https://www.google.com/url?sa=t&sou...BMAF6BAgFEAk&usg=AOvVaw09B7QXYvADkv7ZyNQtvH1K
Ok, will do that next day, thank you for your help and patience!!
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Andi900rr said:
In Recovery, I cannot "Swipe to unlock" anymore...
The touchscreen is not working. I had that issue several times in the past already. Rebooting to Recovery sometimes helps, but not now.
Click to expand...
Click to collapse
ok so its time to flash rom via fastboot ..just download the latest stable 10.3.8 fastboot rom after you install back up everthing first before flashing so you can restore if anything happens..back up only Boot , Recovery , System image , Vendor image , Efs and your good to go.. watch these and download are already included in this video https://www.google.com/url?sa=t&sou...BMAJ6BAgFEA4&usg=AOvVaw2naYU5q2jUaE5qUeskrBed[/url]
Before anything else ..use the twrp 3.2.3.0 recovery
Man, flash MIUI 10.3.8.0 on fastboot. ONLY MIUI. then boot... if it boot, tell us
Success flashing:
miui_POCOF1Global_V10.3.8.0.
recovery-20181211
Magisk-v19.3
rebootet to recovery, now into TWRP 3.2.3-0
I still wonder what was the problem and what was the solution...
Maybe formatting data was the solution?
From here, I backed up:
Boot
Recovery
System.image
Vendor.image
Efs
Backup created successfully; also copied to PC.
I wonder when installing LOS again from here on, if I should...
- update to TWRP 3.3.0-0
- update to Magisk-v19.4
or not.
bamz1117 said:
what rom your using before you installed los?
Clean flash would be needed ..you should wipe internal too to get it working , dont forget to remove all you password , fingerprint and face unlock.
Boot to recovery wipe system/dalvik/data/cache/internal before doing this you need to do a nandrioid back up..
do this:
download the lastest vendor:
beryllium-V10.3.8.0.PEJMIXM-9.0-vendor-firmware
next the LOS rom:
lineage-16.0-20191003-nightly-beryllium-signed
open_gapps-arm64-9.0-mini-20191003
and then
download the latest DFE version 19.3:
you can download it in telegram pocof1 group chat
and then wipe dalvik cache after that reboot system
first boot reboot to twrp recovery and the flash magisk v19.3 the reboot system....
i hope this method will help you..goodluck!!!
Click to expand...
Click to collapse
you can download it in telegram pocof1 group chat
Click to expand...
Click to collapse
please guide me to the group
****
I did the exact order bamz1117 wrote:
flashed:
-beryllium-V10.3.7.0.PEJMIXM
-lineage-16.0-20191003-nightly-beryllium-signed
-open_gapps-arm64-9.0-mini-20191003
-DFE 19.3
wipe dalvik
reboot system
and back into FASTBOOT...
Seems I am back where a was coming from? I am confused.
I have the suspicion that one of my zips is corrupted/defective/unproper version, but I have no idea which one.
When I flash
- beryllium-V10.3.6.0.PEJMIXM
- lineage-16.0-20191003-nightly-beryllium-signed
- Disable_Dm-Verity_ForceEncrypt_02.04.2019
wipe dalvik
reboot
- Magisk-v19.3
at least I see the LOS install logo working for quite a long time, but after that it reboots to TWRP recovery.
I noticed the following things:
concerning FW/vendor:
- beryllium-V10.3.6.0.PEJMIXM
I downloaded from https://mirror.akhilnarang.me/MIUI/beryllium/
is 451MB in size
- the newer ones:
fw_beryllium_miui_POCOF1Global_V10.2.3.0.PEJMIXM_a0319918c1_9.0
fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIXM_aa86bd1d08_9.0
are 91 MB each, I downloaded from https://xiaomifirmwareupdater.com/firmware/beryllium/
are those files fake?
Where to download V10.3.8.0 from a trustworthy source?
Would someone please explain me the proper order for a clean re-install (while rooted and TWRP recovery already installed) AND explain the reason behind that particular order?
My current understanding, which might be wrong:
1. Firmware/vendor first (obvioulsy this is giving hardware support to the operating system like with a PC), then
2. Lineage OS (this is the operating system) and
3. openGapps third (this modifies the operating system and includes google apps)
4. DFE (a kind of a script? which modifies the operating system by disabling verity/encryption/quota when setting the filename of the zip accordingly)
5. Magisk (offers services in order to hide rooting etc. to prevent apps with higher security e.g. online banking to detect security nonconformity and thus stop working)
Please correct me where and why I am wrong in that order - I want to understand it.
Thank you.
I dont know why but I lost TWRP meanwhile.
My Pocophone only starts into fastboot mode, I cannot invoke TWRP Recovery anymore.
I tried to flash the latest stock rom with "Tool all in one", which tells me bootloader is still unlocked.
But when I try to flash, a command window opens and closes immediately and nothing happens.
I try to run "Tool all in one" as admin, but it does not start.
I dont know what to do.
Was able to flash twrp 3.3.0-0 via fastboot... If I enter Recovery, it shows twrp 3.2.3-0 .... idk,wtf
I am able to restore Miui10 from backup! It runs!
But flashing vendor/LOS/DFE/Magisk is not working! WTF! No idea why.
Still have THE SAME fastboot-loop issue after flashing vendor/LOS/DFE/Magisk I STARTED WITH the first post.
Unofficial TWRP has been released, it is tested, can be used can be touched
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Your PC already installed adb&fastboot driver
-If you cannot enter the cycle boot, please refer to: https://forum.xda-developers.com/re...access-redmi-9-mediatek-t4149531（-vbmeta.img）
How to:
STEP 1
- Backup Always Recommended
-Turn off the phone-then press the volume down button + power on button to enter fastboot
-Then plug in the data cable (provided that your phone is correctly installed with the adb driver) and run the redmi9 one-key flashing tool
-Wait for the phone to enter recovery and you're done
note:
My device China version redmin9
Download （Download link may require vpn）：new
TWRP-3.4.2BREDMI9.rar - 蓝奏云
文件大小：31.8 M|
wwa.lanzous.com
lkj00 said:
Unofficial TWRP has been released, it is tested, can be used can be touched
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Your PC already installed adb&fastboot driver
-If you cannot enter the cycle boot, please refer to: https://forum.xda-developers.com/re...access-redmi-9-mediatek-t4149531（-vbmeta.img）
How to:
STEP 1
- Backup Always Recommended
-Turn off the phone-then press the volume down button + power on button to enter fastboot
-Then plug in the data cable (provided that your phone is correctly installed with the adb driver) and run the redmi9 one-key flashing tool
-Wait for the phone to enter recovery and you're done
note:
My device China version redmin9
Download （Download link may require vpn）：
https://wwa.lanzous.com/iXvkCgnha5g
Click to expand...
Click to collapse
Is your device boot successfully without any problem
I think it is not safe to flash this recovery in global version ROM...
lkj00 said:
Unofficial TWRP has been released, it is tested, can be used can be touched
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Your PC already installed adb&fastboot driver
-If you cannot enter the cycle boot, please refer to: https://forum.xda-developers.com/re...access-redmi-9-mediatek-t4149531（-vbmeta.img）
How to:
STEP 1
- Backup Always Recommended
-Turn off the phone-then press the volume down button + power on button to enter fastboot
-Then plug in the data cable (provided that your phone is correctly installed with the adb driver) and run the redmi9 one-key flashing tool
-Wait for the phone to enter recovery and you're done
note:
My device China version redmin9
Download （Download link may require vpn）：
https://wwa.lanzous.com/iXvkCgnha5g
Click to expand...
Click to collapse
Thanks for sharing. This may be better than the other one from unofficialtwrp. Forks by wzsx150 are usually good from my past experience. Anyone successfully installed?
Shas45558 said:
Is your device boot successfully without any problem
I think it is not safe to flash this recovery in global version ROM...
Click to expand...
Click to collapse
My device has been tested without problems
lkj00 said:
Unofficial TWRP has been released, it is tested, can be used can be touched
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Your PC already installed adb&fastboot driver
-If you cannot enter the cycle boot, please refer to: https://forum.xda-developers.com/re...access-redmi-9-mediatek-t4149531（-vbmeta.img）
How to:
STEP 1
- Backup Always Recommended
-Turn off the phone-then press the volume down button + power on button to enter fastboot
-Then plug in the data cable (provided that your phone is correctly installed with the adb driver) and run the redmi9 one-key flashing tool
-Wait for the phone to enter recovery and you're done
note:
My device China version redmin9
Download （Download link may require vpn）：
https://wwa.lanzous.com/iXvkCgnha5g
Click to expand...
Click to collapse
lkj00 said:
My device has been tested without problems
Click to expand...
Click to collapse
Great.....you should try gsi on your device....
Sounds good and regards to the developer, But I recommend that to wait until the TWRP be tested well and release the first update vesion .
for me I will keep waiting for the official TWRP, no need to rush there is no any custom rom
Well it works for me. I use the redmi 9 nfc 3/32 lancelot.
Thread Title Edited to: Redmi 9 unofficial TWRP (Sep,2020)
Funk Wizard said:
Thread Title Edited to: Redmi 9 unofficial TWRP (Sep,2020)
Click to expand...
Click to collapse
Thanks for quick respond.
I just want to know can this be used to flash full magisk? I am in indian rom. Will there be brick issue or something?
Colossus96 said:
I just want to know can this be used to flash full magisk? I am in indian rom. Will there be brick issue or something?
Click to expand...
Click to collapse
I guess you can test it yourself. Quite easy to fix things if it doesn't boot the TWRP. You'll simply flash the original recovery.img from the current MIUI full ROM installed on your phone to erase the TWRP without even erasing userdata. My bootloader is currently locked so can't test it now. About bricks, as you know this is an MTK so you have to be extremely careful.
The advantage with TWRP is you can mod the system so long as you enable write access to that partition. Flashing Magisk modules also works better via the recovery.
Last thing, I think the only way you can get root on MIUI is through the patched boot method. Flashing the Magisk installer zip in TWRP just doesn't do.
Abdullah.Csit said:
Sounds good and regards to the developer, But I recommend that to wait until the TWRP be tested well and release the first update vesion .
for me I will keep waiting for the official TWRP, no need to rush there is no any custom rom
Click to expand...
Click to collapse
I also wait for offical..i root my device and use mod...
I do not want to take risk because of mtk prossessor...
I did
nielsync said:
Thanks for sharing. This may be better than the other one from unofficialtwrp. Forks by wzsx150 are usually good from my past experience. Anyone successfully installed?
Click to expand...
Click to collapse
I did installed it into my Redmi 9 4/64 Indonesia version... So far no problem at all
---------- Post added at 12:57 AM ---------- Previous post was at 12:50 AM ----------
lkj00 said:
Unofficial TWRP has been released, it is tested, can be used can be touched
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Your PC already installed adb&fastboot driver
-If you cannot enter the cycle boot, please refer to: https://forum.xda-developers.com/re...access-redmi-9-mediatek-t4149531（-vbmeta.img）
How to:
STEP 1
- Backup Always Recommended
-Turn off the phone-then press the volume down button + power on button to enter fastboot
-Then plug in the data cable (provided that your phone is correctly installed with the adb driver) and run the redmi9 one-key flashing tool
-Wait for the phone to enter recovery and you're done
note:
My device China version redmin9
Download （Download link may require vpn）：
https://wwa.lanzous.com/iXvkCgnha5g
Click to expand...
Click to collapse
Hi sir, i have tested this twrp, and its stable enough.. but i wanna ask u for helping us make a stable/official one based on PBRP (Pitch Black Recovery Project). Can u help us with this??
My telegram : @afdy_y
lkj00 said:
Unofficial TWRP has been released, it is tested, can be used can be touched
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Your PC already installed adb&fastboot driver
-If you cannot enter the cycle boot, please refer to: https://forum.xda-developers.com/re...access-redmi-9-mediatek-t4149531（-vbmeta.img）
How to:
STEP 1
- Backup Always Recommended
-Turn off the phone-then press the volume down button + power on button to enter fastboot
-Then plug in the data cable (provided that your phone is correctly installed with the adb driver) and run the redmi9 one-key flashing tool
-Wait for the phone to enter recovery and you're done
note:
My device China version redmin9
Download （Download link may require vpn）：
https://wwa.lanzous.com/iXvkCgnha5g
Click to expand...
Click to collapse
What is redmi 9 one key flashing tool? How can i find it?
Shas45558 said:
What is redmi 9 one key flashing tool? How can i find it?
Click to expand...
Click to collapse
It means the flashing program in the zip. You can just flash the img file via fastboot command. I tried, it works.
Copy the .img file to your fastboot folder & flash .
Almost brick my device.....
Today I installed this in my redmi 9....
I was surprised when I see that my device is is boot into this recovery....
I am very happy but my happiness gone after a few minutes.....
When I boot into system I cannot boot into recovery.....
So I format all user data and chach....
But same thing happen To me....
I flash this recovery again with fastboot mode.. then I can boot into recovery...
I think it could be happen because my phone is encrypted... So I force dencrypted my device....
When I want to boot into system. I fail to boot no system and no recovery...
I think it is over but luckily I able to boot into fastboot mood ..then I flash boot and recovery....
I realise that there is no need to flash this recovery... Because you can root your phone without recovery....
If you try to flash GSI ROM... It will not happen because it does not support GSI ROM
There is no option to erase system and vendor separately.....
So who want to flash GSI via this recovery, I suggest you do not flash it because we do not need it this time....
I am not sure it may be happen only with me. Feel free to share your experience...
Shas45558 said:
Today I installed this in my redmi 9....
I was surprised when I see that my device is is boot into this recovery....
I am very happy but my happiness gone after a few minutes.....
When I boot into system I cannot boot into recovery.....
So I format all user data and chach....
But same thing happen To me....
I flash this recovery again with fastboot mode.. then I can boot into recovery...
I think it could be happen because my phone is encrypted... So I force dencrypted my device....
When I want to boot into system. I fail to boot no system and no recovery...
I think it is over but luckily I able to boot into fastboot mood ..then I flash boot and recovery....
I realise that there is no need to flash this recovery... Because you can root your phone without recovery....
If you try to flash GSI ROM... It will not happen because it does not support GSI ROM
There is no option to erase system and vendor separately.....
So who want to flash GSI via this recovery, I suggest you do not flash it because we do not need it this time....
I am not sure it may be happen only with me. Feel free to share your experience...
Click to expand...
Click to collapse
This recovry is only to flash magisk for now. Flashing ROMs not supported yet. Don't try to flash rom with this.
That's mean this recovery is not helpful.....
Because we root our devices without any recovery....
Colossus96 said:
This recovry is only to flash magisk for now. Flashing ROMs not supported yet. Don't try to flash rom with this.
Click to expand...
Click to collapse
So it's just for the developers ( As first step to deal with this awful Mediatek ). We will look forward and hopping to get lucky as redmi note 8,8pro.
Abdullah.Csit said:
So it's just for the developers ( As first step to deal with this awful Mediatek ). We will look forward and hopping to get lucky as redmi note 8,8pro.
Click to expand...
Click to collapse
In order to get that lucky we will need source code. Without source code nothing can be done properly.