Advice to update Pie MIUI 10.2.2.0 PDTMIXM - Xiaomi Mi 8 Lite Questions & Answers

Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite

orozcore said:
Hey guys I wanna know about the Pie update I have mi Mi 8 Lite and as soon as i power up and conect to a wifi and update to 10.2.2.0 ODTMIXM was available so i updated and no problem i unlocked the bootloader (15 days wait time, sad) and flash twrp no root because is magisk and i can't hide root (even with magisk default hide root) for a bank app so is not rooted but since five days I was notified about and update to Pie miui 10.2.2.0PDTMIXM stable (persistent notification) but here are some questions:
* the twrp will cause a problem if I download this update and the updater applies or I have to remove twrp (I'll make a twrp backup just in case I don't have the original img file)
* I've read there no version of twrp for Pie and the version for 8.1 is not ideal. (correct me if i'm wrong)
* I might not need root, no problem the miui have some tweaks and I'm getting used to miui. (I had a Moto X Play with root and xposed and some modules)
* Is the first stable version, should I wait for a next Pie version with bugs solved.?
* I'm knew to miui less than a month with my Mi 8 Lite
Click to expand...
Click to collapse
There's a TWRP for pie

mr_reaper said:
There's a TWRP for pie
Click to expand...
Click to collapse
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)

orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Which TWRP version u running?

mr_reaper said:
Which TWRP version u running?
Click to expand...
Click to collapse
sorry for the late reply the version i'm using is recovery-TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150

orozcore said:
So your suggest is that I download the Pie update and let updater installs it and reflash twrp (is it the same version?)
Click to expand...
Click to collapse
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46

MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go. Mind you that version 1003 is older that the one you need. Due to bad naming scheme, the latest you want is 0212. (12 February 2019).
https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
Click to expand...
Click to collapse
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
EDIT: Also, the stock Pie release is good. I am currently on Pixel Experience but may switch back to stock rooted at some point. Until Xiaomi releases the Pie kernel sources, no custom ROM is going to be perfect.

lexridge said:
You might want to go with TWRP 0121 (also Pie compatible) instead, as someone reported in another thread having problems doing a restore with 0212 and nobody has yet verified if 0212 can actually do a successful restore. We are still a fairly small group here.
Click to expand...
Click to collapse
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
MetallicGR said:
Yes. Update, boot in fastboot, connect to your PC, flash TWRP and youre good to go.
Click to expand...
Click to collapse
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.

chan200606 said:
Has anyone reported a successful restore with *any* version of TWRP on the Mi8 Lite? I have only seen the unsuccessful one you mentioned, and another one who couldn't restore with either 0121 or 0212. I have not tried it myself, and believe that most people are using TWRP only to flash magisk or custom roms so far.
---------- Post added at 02:39 AM ---------- Previous post was at 02:22 AM ----------
The default settings in TWRP is to automatically restart the phone after an ota. As the ota overwrites the recovery with the stock version, we would normally need to reflash TWRP.
However the wzsx TWRP allows you to disable this automatic reboot in its settings. This should mean that we can reflash TWRP (and magisk if used) immediately after flashing the ota while still within TWRP, before restarting to the new system, thus avoiding the need for fastboot/PC.
This is just my theory - I haven't tried it myself as I haven't decided to do the pie ota yet.
Click to expand...
Click to collapse
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.

i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs

lexridge said:
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?

Not many people will shutdown their phones to test the restore guys. It's difficult, but we have to wait for someone to try this with the latest version of twrp. Nothing dusturbing here in my opinion. We will thank whoever tries this first that's for sure.

chan200606 said:
Why wouldn't you just flash the IMG file to the recovery partition under TWRP?
Click to expand...
Click to collapse
Interesting. I did not know you can flash img files directly with TWRP. Haha. Color me stupid!! How does TWRP know which partition to write the .img to? Does it give you a choice?

Yes it does. Choose recovery.

lexridge said:
It is disturbing nobody has yet tested a TWRP restore. I would try it myself, but right now I cannot afford any long term downtime, as my mom is having health issues and I cannot take the chance of missing a call in case of emergency. .
Regarding flashing TWRP after update.... I certainly agree with your theory...and this could be done in either of two ways:
Method One, backup the Recovery only within TWRP. You MUST do this before taking the update!!! This lets you simply restore your existing recovery after the update. Not tested, but should work just fine assuming TWRP can indeed successfully restore (unknown).
Method Two, my personal favorite, which is what I did, was build an updated flashable .zip file of TWRP from the 1003 zip file (the only version I could find as a flashable .zip.) Just zip edit the BlaBlaBla_1003.zip file, replacing the 1003.img with the newer version 0121.img or 0212.img (after adding new .img file, delete old 1003.img file from the zip). You must also edit the /META-INF/com/google/android/update.binary (not really a binary, but actually text) to reflect the new .img filename within the zip. Update/Save zip file with new changes. Rename zip to new version name then check it to make sure your changes remained intact. Copy to phone storage. It will flash fine. Already tested. I can provide the 0121 zip file if needed, or create a 0212 flashable TWRP version as well if somebody wants it.
Click to expand...
Click to collapse
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.

MetallicGR said:
Yes it does. Choose recovery.
Click to expand...
Click to collapse
good to know you can flash a img within twpr so i'll try when I update

mr_reaper said:
i havent tried cause im still waiting on bootloader to be unlocked when i check earlier i had 124 hrs
Click to expand...
Click to collapse
Yes is bad to wait so much time and there's nothing you can do I read about the version of the unlocker but with no luck. So I finally have unlocked bootloader.

Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
If you didn´t read before a member linked to you In the post #6 both TWRP versions.
About your steps:
- No need to backup previous TWRP, just flash the new image and reboot to recovery again.
- If you already have Magisk no need to flash it again so you won´t lose root status nor any data/settings of the rom.
If you want to unroot the 0212 has this option in advanced menu.

orozcore said:
I haven't noticed the restore of twpr backups failed, I only did the backup.
Can you share the flash file or the img of 0212 or 0121?
So to be clear.
* Make twrp backup
* donwload the update
* let it update and hope no lost of data
* wait to boot and enter fastboot and flash img 0212 or 0121
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
I hope no mess with my phone.
Click to expand...
Click to collapse
You should probably update your TWRP first and foremost, otherwise no access to data after you flash the update.. You will also need the Magisk Manager as an apk somewhere on your microSD card. I edited your to-do list:
* Download Magisk Manager and store on your microSD card.
* Flash new TWRP (0212 or 0121).
* Make a full twrp backup and do a recovery only backup as well
* download the update
* let it update and hope no lost of data
* Reflash img or TWRP Recovery backup 0212 or 0121
* Reboot recovery, check that you can decrypt data
* flash magisk and try to test my bank apps that detect root, i couldn't hide root with magisk for these apps. (i don't need magisk so much)
* After first boot, manually install your saved Magisk Manager app from microSD card. Run it. Check if all is good.
Do you use Titanium Backup? If so, make a full TB before doing any of this.
---------- Post added at 01:04 AM ---------- Previous post was at 12:42 AM ----------
SubwayChamp said:
Actually v0212 is restoring, I restored data from Arrow to Havoc and no problem with that.
Just all the recoveries and roms are acting weird, I´m not sure if it´s only my device; any AOSP rom is showing bootanimation at first reboot, recovery not responding touch but then press pwr button and after that screen works normally, at time to bootup for first time screen appears totally black then press pwr to screen off and pwr to wake up and now screen is working again, luckily at second reboot all this is normalize.
---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------
Click to expand...
Click to collapse
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!

lexridge said:
Good to know that it is working for you. I will try a restore over the weekend myself, as I plan on getting rid of PE ROM. Not very happy with it, and the dev is not responding to anyone at all. I will probably just go back to stock PIE with alternate launcher.
Regarding your odd problems, I am not having any of your mentioned issues at all. My reboot times are very speedy and recovery touch has always worked from the start. I have only flashed one 3rd party ROM so far. Pixel Experience. It is actually a pretty good ROM, but the camera(s) are a bit flaky. I need my camera to work 100%. I did just install the MiX Cam, which so far is working really well. I have more testing to do before I make a decision. It seems camera apps work great for a few days, then suddenly start crashing. Ugh!
Click to expand...
Click to collapse
I never saw before this kind of weird behaviour btw is working generally speaking fine.
I´m not a fan of camera but the stock is so far better, I noticed that HavocOs rom has the feature to enable camera2 api and EIS, maybe you might try it. Regarding to use a custom launcher on stock miui rom there´s Poco launcher that keeps the same system icons than theme chosen and is very fast.

Related

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
You're the man! Props for all the hard work you've put into this.
TY!!!!
Awesome. I might have to wait a bit to install but glad to see the Pixel getting twrp.
Sent from my Pixel XL using Tapatalk
Wow, and so it begins. Thanks!
Thank you!!
Nice!!! Awesome job @Dees_Troy
Sent from my Pixel XL using Tapatalk
I just installed the IMG w/out issue.
I can't find the zip in TWRP file manager to flash though.
Everything looks encrypted.
EDIT: It went through on the 4th try of flashing the IMG, now I can see my /sdcard and install the zip.
But somehow this killed my OS.
Just flashed the flash-all.bat after removing -w so it doesn't wipe.
Now I'll try TWRP install again.
EDIT 2: Okay, after restoring to stock, the TWRP install went fine.
Maybe it didn't like my elementalx kernel or the existing root. The OP did mention something about root conflicts, I guess it may prevent TWRP installs too? But now I have OS *and* TWRP.
And I'm getting "Unspecified Error" when trying to copy my EFS backup from /sdcard/twrp/backup to my local computer. I am able to copy other non-TWRP files though.
.
.
.
Does a full backup on Pixel include System Image and Vendor Image? I don't recall seeing these on other devices.
Or do I just back up boot, system and data like usual?
***Hey ya'll, don't forget to back up EFS at least once and copy it to your computers!
Yea! Worked perfect!!!
Would the flashable SuperSU v2.78 SR3 zip work?
Looked it up and because of conflicting init binaries between TWRP and the current root method, it just wouldn't work.
While we're still on or near the first page of the thread, I'd like to clarify the whole EFS backup thing.
It's completely unnecessary. You don't need to do it. But the option is there (so no one asks where it went!)
Both the modemst1 and modemst2 partitions are merely a caching area for your modem firmware. They do not contain sensitive data like IMEI, or anything important. You can wipe them and they will be regenerated from scratch! Have no fear, your IMEI cannot be destroyed through means of bad flashes!
The issue with these partitions however is that should they ever become corrupt, the modem firmware will panic and fail to load - this is why you see your IMEI missing in such a case. The modem firmware simply refused to load due to encountering corrupt data. By clearing your modemst partitions (writing zeros to them), your modem firmware would happily load and regenerate the partitions, bringing back full call support & a visible IMEI.
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Yep just want to let ya guys know might want return to stock before doing this. Besides that all good. Good job TWRP team! :good:
CZ Eddie said:
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Click to expand...
Click to collapse
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
FYI on OP - A SuperSU update will be required to allow TWRP and SuperSU to co-exist.
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
delete
CZ Eddie said:
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
Click to expand...
Click to collapse
Do we still flash root the same way after we install TWRP? Or is there an su zip to flash?
Hooray! Cheers!

Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s

Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.

[Guide] OTA updates on non-stock recovery (TWRP)

If you've flashed a non-stock recovery like TWRP*, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
* TWRP is now officially supported, make sure you flash that version if you're using an older, unofficial TWRP.
1. Obtain the ROM you want to install. Make sure the download is from miui.com if you want stock
Official site -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab. The website does not update links immediately after a ROM update is released, so you may have to do a bit of digging if you want a very recent update.
You can also check ROM links on third party sites like ezbox.idv.tw, again, make sure the actual download links are from miui.com and not somewhere else.
Latest EEA ROM(Android 10) as of 2020-10-24 -
V12.0.3.0.QFJEUXM
Nightly official LineageOS builds
2. Get into TWRP
Either run 'adb reboot recovery'
Or power phone off and boot into TWRP by holding PWR+VOL_UP during boot
3. Upload the ROM to the phone
Code:
adb push ~/Downloads/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B] /sdcard/
4. Flash the ROM via TWRP
5. Flash Magisk if you use it, because flashing the ROM deletes it.
6. Remove the update file:
Code:
adb shell rm /sdcard/[B]miui_DAVINCIEEAGlobal_V12.0.3.0.QFJEUXM_12b99693bc_10.0.zip[/B]
That's it! Reboot your phone into your new ROM!
Also check out my debloat list and my detailed phone settings.
Additional note - formatting /system will brick your phone and you'll have to recover using a fastboot ROM.
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Benfatica said:
Please can I get the 10.3.15 ota zip for the official recovery I cant get the update and my phone is now on 10.3.12 it always say no update available even though I have done the update before and returned to 10.3.12 but it does show it to me again and also my otg doesn't work . please help me
Click to expand...
Click to collapse
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Micdu70 said:
OTA zip is here => https://bigota.d.miui.com/V10.3.15....PFJEUXM-V10.3.15.0.PFJEUXM-14bc6a5788-9.0.zip
Click to expand...
Click to collapse
Thanks,I was able to get it over ota but it doesn't come now has xiaomi removed it or something
I also get this message if I try to download the latest package. Is something wrong with my phone
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
C0rn3j said:
It looks like the 10.3.15.0 update was pulled and 10.3.12.0 is now latest.
Click to expand...
Click to collapse
Ok thanks, but why though ??
My last update is 10.3.11.0 July security patch
C0rn3j said:
If you've flashed a non-stock recovery like TWRP, you can not use the OTA update feature. You need to flash the full ROM via TWRP.
So how to get around this when the updater is telling you there is an incremental update?
Simple, we tell the updater to download the full image instead, move the update from the original folder so MIUI won't attempt to upgrade from it on next reboot, boot into TWRP and flash the image there.
1. Settings -> About Phone -> System update -> three dots -> Download latest package
2. Get filename of the update:
3. You now have the filename of the update. I got miui_DAVINCIEEAGlobal_V10.3.15.0.PFJEUXM_b6738621e2_9.0.zip and will be using this name throughout the rest of this how-to, replace the examples accordingly based on what name you got.
4. (optional) Backup the latest ROM file to your PC:
5. Prevent MIUI from seeing the update file and trying to update from it on accident by moving the file a folder higher:
6. Power phone off
7. Boot into TWRP by holding PWR+VOL_UP during boot
8. Flash the ROM via TWRP
9. Flash Magisk if you use it, flashing the ROM deletes it.
10. Boot back into Android and remove the update file:
That's it!
You can also download the full ROM directly through miui.com, but keep in mind the website does not instantly update the link there after a ROM update is released.
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
In my case the ROM download through phone was corrupted and I had to edit the site URL from the filename I got to get a proper update file:
Click to expand...
Click to collapse
Redmi K20 Open Beta File Link?
Wrong thread.
Don't quote the OP, it clutters the thread.
For people who want the 10.3.15.0 update. I uploaded it to mega. Link is here:
https://mega.nz/#!pddQUaBL!s5En8LWaxWciUyNowU8_rYYMk2D48Dj8J7_PbJwv0kc
C0rn3j said:
...
https://en.miui.com/download-361.html#619 -> My phone is the EEA version, so I use the 'Mi 9T EEA' tab.
Page best viewed in Firefox, clicking on the lock icon -> Arrow icon in the security tab -> Disable protection, since Xiaomi can't even set their website up properly.
...
Click to expand...
Click to collapse
The most accurate, updated and actual site for Mi 9t/K20 (davinci) firmware/rom - https://mirom.ezbox.idv.tw/en/phone/davinci/
10.3.15 ota is back online, just received it
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
rastip said:
Hey @C0rn3j
I am on stock 10.3.12.0 PFJEUXM and TWRP 4PDA 3.3.1.-2 fix and Magisk.
My questions:
1. Is it worth the upgrade to MIUI 11 as it is still Android 9
2. If I flash it through TWRP, did you loose any dual app settings? (as I lost dual apps while backing up the phone with TWRP and Titanium backup)
3. as you said I have to flash the Magisk again, did you choose the latest or the same as was installed on the phone before the upgrade?
Thanks in advance for reply
Click to expand...
Click to collapse
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
rastip said:
I have Nova Launcher, do you use default or as well external one?
Do you think Nova will stay untouched with this upgrade?
Click to expand...
Click to collapse
Nothing will happen to it
If the Magisk have to be flashed again, does it mean all the hide settings which were there before has to be set again or stay there from the old version? I have few apps in Magisk hide root, so just wondering how this will be affected with rom update
A second question:
I am on 10.3.12.0 not upgraded yet to 10.3.15.0.
Can I upgrade straight to V11.0.2.0 or first to 10.3.15.0 and then to V11?
---------- Post added at 05:27 PM ---------- Previous post was at 05:09 PM ----------
C0rn3j said:
1. Security updates.
2. I don't use dual apps so I wouldn't know. AFAIK people had issues with using the backup/restore functionality of TWRP on that version. You should probably update it as I believe latest is -4
3. Latest.
Click to expand...
Click to collapse
While flashing did you untick Recovery in the TWRP as I believe the whole 2,2GB ZIP has recovery image and could be flashed and overwrite the TWRP?
Your guide not working, twrp failed to install the update "file corrupted".
I've downloaded the OTA package from "http://c.mi.com//miuidownload/detail?device=1700361" and twrp very happy to install this file, my Mi_9T at the latest update 11.
Unfortunately the archive downloaded through the Updater cannot be flashed as is through TWRP (message: file corrupted)
miui_RAPHAELEEAGlobal_V11.0.3.0.QFKEUXM_153f9511ae_10.0.zip

[Guide][Root] The easiest way to root without TWRP

Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed

[Guide][GSI][10.0] How to get Havoc OS 3.12 GSI running on Redmi 8A

Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global Rom but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx, due to support wifi 2.4 ghz only. (Because bluetooth interfering with wifi 2.4 Ghz and our device doesn't support 5ghz wifi)
Compare to MIUI, Havoc OS has somethings i like:
+ Faster download/upload speed: no delay with wifi bluetooth interference
+ Doesn't have bloatware, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk and root.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI and extract to get system
From Official Havoc OS here: https://sourceforge.net/projects/havoc-os/files/a64-ab/ (Newer Version)
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature. If it doesn't work, then try an alternative way:
Open /vendor/bin/init.qcom.post_boot.sh and add the string:
Code:
sendevent /dev/input/event2 0 1 5
then reboot
13) Enjoy Havoc OS. Install apps, configure settings...
How to Update
- Flash system image over, no wipe require. Just reboot.
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from https://vancedapp.com/; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
- To fix Recording, from Misc features -> Force Timestamp Source, choose Clock boottime
And that's all. Now enjoy!
I gifted my sister this phone so i don't have device to test anymore. Still, sometime i'll test if i can. The guide still works so enjoy flashing!!!
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
ways2 said:
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
Click to expand...
Click to collapse
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw module working, despite i don't active the xiaomi option in setting.
Ga_hap_la_chanh said:
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw working, despite i don't active the xiaomi option in setting.
Click to expand...
Click to collapse
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
ways2 said:
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
Click to expand...
Click to collapse
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Thank you sir
thanks a lot for this
can you tell me how to upgrade our 32bit os to 64bit
Ga_hap_la_chanh said:
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Click to expand...
Click to collapse
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
eddy law paul king said:
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
Click to expand...
Click to collapse
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
ways2 said:
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
Click to expand...
Click to collapse
i am very afraid that i brick my devise
so make a video
it is accurate and much helpful and easy to understand
i am waiting
Can I use the attached files for installing gsi in redmi 9 ?
vinith 32 said:
Can I use the attached files for installing gsi in redmi 9 ?
Click to expand...
Click to collapse
no
this is for 8 and 8a only
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
ways2 said:
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
Click to expand...
Click to collapse
I used TWRP then moved to Orange Fox. Everything working fine, may be your screen is different. In d2tw module, there's a file called readme.md: Manual usage : - enable $ set-dt2w 1 - disable $ set-dt2w 0
Just try it -))))))))
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
ItsmeTushar said:
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
Click to expand...
Click to collapse
Boot.img and vbmeta are done before flashing the gsi. I'd recommend reading this thread first for better understanding
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Zzzleepy said:
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
Click to expand...
Click to collapse
That was weird. In stock ROM, I can back up the /data/media just fine even when encrypted. But after having Havoc OS, I cannot do that anymore. Tried on both TWRP and OrangeFox. I can, with an unencrypted phone, but I do not feel comfortable without a lockscreen. Tried all things I have researched on that error. Not one worked. Might as well just stick to Titanium Backup for backups.
Overall, great GSI. Loading is faster than on stock (with the internet too)! Though, I have another issue with regards to the locking of apps, so that the app would not be cleared. Speaking of clearing apps, it is tiring to scroll left just to see the "Clear All" option in Recents. Autostart too.
I know you are not the developer, but just letting you know my concerns.
How to resize system partition for install gapps?
Soerex24 said:
How to resize system partition for install gapps?
Click to expand...
Click to collapse
Reboot to custom recovery > Menu > Manage Partitions > System > Resize or Repair

Categories

Resources