Database Users

[D5803][Z3C][UB] Russel5's TWRP 3.1.1-0 FOTA Recovery MOD

Guys.
I made a bit modified version of @russel5 very nice work for our Z3C:
- A bit more colors, nice navbar buttons and new navbar background (fits to main screen background)
- More img flash options (be carefull with img flash because wrong flashes can brick you phone)
- More partition backup and restore options (boot is also included for sure - but not shown on the pic)
- New with 3.1.0-0: Additional partition for backup/restore: mmcblk1p2 ext4 mounted to /sd-ext - This is second partition on external SD Card, if available.
- New with 3.1.1-0: All above mentioned changes and official ones: https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Too beauty to keep it only for me
Requirements
Only for Unlocked Bootloader (UB)
New Bootloader needed: LA3.0_M_3
Information
Maybe NOT working with 7.x.x ROMs like (LineageOS/Carbon) - Only tested with MM and stock-like ROM (like SLiMM 3.8).
Please visit corresponing threads for help with TWRP and any 7.x.x ROM.
Installation - 2 Options:
a) Flashable zip via TWRP to update existing.
b) Extract twrp-3.x.x-0-z3c_Vxx.img from zip-file and flash via fastboot: fastboot flash recovery twrp-3.x.x-0-z3c_Vxx.img
Start FOTA Recovery:
Shut down phone completely - wait 5-10 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.
UPDATE 15.03.2017
New 3.1.0-0 from Russel5 - Big thx again to him! Say thanks to him - not me!
Thanks to @russel5 - This is his work:
https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113

@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?

doriandiaconu said:
@fluffi444 I flashed the recovery.img in fota with twrp and recovery is still 3.0.2. Any idea why?
Click to expand...
Click to collapse
Maybe i have an idea.... You know how to start FOTA Recovery correctly?
Shut down phone completely - wait 5 secs - Press Power and Vol Down until short vibration - release both keys and wait - done.
Looks like you still booting your system or kernel recovery....
Otherwise check your bootloader - must be LA3.0_M_3 (Service Menu - Service Info - Software Info - S1 Boot Version)

UPDATE 15.03.2017
New 3.1.0-0 from @russel5 - Big thx again to him! Say thanks to him - not me!

can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks

filou76 said:
can someone please explain/summarize for me the differences of twrp recoveries that we have on the z3c. if i got it right, there is (1) old bl recovery = kernel 'attached', (2) new bl recovery = seperated img from kernel and (3) fota recovery wich uses an unused partition of unlocked bl.
is that correct?
whats the advantage of fota? can every custom rom use all the different recoveries? can (2) + (3) be flashed both on the same device?
i am really confused wich version i wanna install and keep on my phone...
thanks
Click to expand...
Click to collapse
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!

fluffi444 said:
Yes - this all can be confusing!
I'm trying to be complete as I can be - I will mention only the last dev of the tools - Actually many more are involved and often it's an growing work of many - Especially No 1.
1) For LB - We have recovery (and root) for LB - Here the last (and best) rooting and TWRP method is the one from russel5:
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This installs recovery files to SYSTEM partition folder /system/etc/mm_twrp_recovery
This is file: recovery.twrp.cpio.lzma
2) Only UB - Recovery integrated in Kernel a) and b)
a) Rootkernel (tobias.waldvogel) https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
afaik this was one of the first tools which can integrated automaticly very resource-conserving recovery to kernel - Disadvantage: Hard to change TWRP if new version is out.
b) PoC TA Tool (munjeni) https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893
Great quite new tool which can also integrate TWRP (but here the complete fota recovery.img) to kernel: Advantage easy to change TWRP to new version, because full fota revovery.img is used
3) Only UB - Recovery to FOTA partition (now known as recovery partition) - newer bootloader needed
This is the recovery.img you can download from official TWRP page or from russel5 (img to be flashed via fastboot) or from this thread (flashable.zip).
Those recovery.img's are complete bootable images with zImage and ramdisk (TWRP is in ramdisk).
That all means that it's indeed possible to have THREE recvoerys running on one phone! But this is senseless of course !!!
Option 1 is only recomended if you are on LB! But works also for UB. But its away if you flash complete new ROM (as TWRP is on SYSTEM)
Option 2 is.... for what? Let me say: Only if you really need the function to reboot to recovery directly from system.
Option 3 is my favorite (but only for UB) - this is bootable no matter what you did to system or even with kernel!
It's on his own seperate partionen and save for unwanted modifications, wrong boot or system flashes, etc
Only (and actually not really an) disadvantage is that you have to start this from shutted down phone... Reboot to recovery is not working!
Click to expand...
Click to collapse
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.

filou76 said:
Wow, thanks a lot @fluffi444!! It's even more complicated than I thaught. WHAT A MESS! :silly:
Well I'am still on Concept Rom --> Bootloader LA3.0_L_Hero_16. I guess that one is close to LA3.0_M_3? Don't remember where I got my TWRP 3.0.0.0 version from, but i flashed it as recovery.img, so it should be fota-type, right? Actually I can reboot from system to recovery ...
I think I'll keep this one as is and see if I need a newer version one day, when i change system to any Nougat rom.
Click to expand...
Click to collapse
Yes - flashing by fastboot goes to FOTA/Recovery partition... Yes - keep it - I don't even know how Concept N or M will react...

Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.

johny.mnemonic said:
Did anyone tried to do backup/restore with this recovery?
I am using it since flashing to LineageOS 14.1 and did multiple backups. Tonight I broken my google account in the ROM, so I wanted to restore to last backup. I already tried four of my backups and all of them are bootlooping, so I am starting to suspect the recovery, as all of those backups were done from perfectly working system.
Click to expand...
Click to collapse
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.

fluffi444 said:
Yes - fully working here. Even Restore. But I still use 6.0.1.
But sometimes (not recovery version related) its not enough to restore only DATA or only SYSTEM.
It happens to me that only an complete restore of all saved partition did the trick...
But as I said that happens also with older recoverys or/and not modded.
Click to expand...
Click to collapse
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.

johny.mnemonic said:
Then it must be something either with my setup, or with 7.1.1 itself.
I tried everything: partial restore, full restore, new flash with recovering of data partition only... Everything was bootlooping.
I am not sure what finally worked, as I was trying it desperately for hours, but most probably the last mentioned thing without flashing Magisk.
Click to expand...
Click to collapse
Try twrp 3.0.2.0 or 3.0.3.0. Some said they have problems with 3.1.0.0 an LOS.

UPDATE 18.06.2017
New 3.1.1-0 from Russel5 - Modded by me. Thanks to Russel5 and TWRP-Team.

Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks

zeryors said:
Hi,
This recovery its amazing because i am trying to have a 6.0.1 With TWRP 3.x.x with Magisk, root and Xposed. At the moment when i ve Magisk and root, i miss Recovery by Magisk mod boot image.
Any idea why screen appear as out resolution or refresh. At least ... it seen enter on Recovery, BUT I CANT reset With Vol+, Vol-, Cam , Power...
at least i can connect by adb and restart.
¿Any idea?
Thanks
Click to expand...
Click to collapse
Hi, i know the sad answer... the problem its the screen, Original Screen (broken touch panel) show perfect Recovery but the "new" screen its the problem... its compatible but not 100% :_(
It´s curious a normal Recovery show OK but not FOTA

Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
TWRP is booting if I flash it to `boot` instead of `recovery`. I flashed CarbonROM this way but lost TWRP after that of course. I also tried [russel5's TWRP 3.1.1-0] which is not booting from `recovery/fota` either. However, an older TWRP version by Tomascus I found -> here <- is booting fine from `recovery/fota`.
Maybe this is bootloader related but I am not entirely sure. If so, how can I update the bootloader?
Sony Xperia Z3 Compact D5803
- Bootloader: 1286-7314_S1_Boot_MSM8974AC_LA3.0_52-2
- ROM: CARBON-CR-5.1-MOO-RELEASE-z3c-20170918-1012
TWRP's tried:
- Russel5's TWRP 3.1.1-0 FOTA Recovery MOD by fluffi444
- [D5803,z3c,aries]Twrp_3.1.1-0_img_for_unlocked_bootloader by russel5
- Tomascus TWRP 3.1.0-0

Andi- said:
Hi there,
booting this current version of TWRP from `recovery/fota` is not working for me. The device just reboots but should load TWRP. I flashed it via `fastboot flash recovery [twrp.img]` without any errors.
Click to expand...
Click to collapse
My MOD is technically the same as original one from Russel. So please ask in his thread (you did this already... btw: please do not post the same question in several threads)
I never tried 7.x.x-based ROMs. So I cannot say anything reladed to the compatibility I'm afraid. MM with stock-like ROM is working with 3.1.1.0 (from Russel).
I will make an note in OP...
And note this: https://forum.xda-developers.com/showpost.php?p=71882082&postcount=12

I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.

Piospi said:
I am trying to install a newer TWRP for Carbon Mod custom rom. I tried:
- install .img with TWRP in TWRP
- flashify
- official app TWRP from google play
- fastboot commands with "platform-tools"
Everywhere I get a message that everything went fine but in TWRP I still have the old version - 3.0.0.2 :/
I am asking for help because I have been fighting this from two days :/
I have Xperia Z3C with unlocked bootloader, stock prerooted firmware .291 + EliteKernel v3.
Click to expand...
Click to collapse
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.

casouzaj said:
To which partition have you installed the TWRP image file? Starting with your phone turned off, f it's been sent to the FOTAKernel partition, hold both the power and the volume down buttons until your phone vibrates (as if it was booting up normally), when you should release the power button. When the screen lights up, release the volume down button.
Otherwise, if you installed TWRP in the recovery partition, boot your phone up as usual. When you see the led lit up, press the volume button.
Click to expand...
Click to collapse
Thank you very much for the answer. Starting the phone with Power + VolUp does not do anything. The phone shows the Sony logo and the system starts.
I installed the IMG file in recovery / fota and the ZIP version doesn't ask for locations.

flashing roms with 4.4.x kernel without qpst

If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps

I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk

sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
You can request unlock .img again

The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.

ShaktiSW said:
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
Click to expand...
Click to collapse
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader

satyen_ said:
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
Click to expand...
Click to collapse
I never needed to. And AEX 6.0 run pretty much smooth without blue screen issue. I just followed the above mentioned procedures.

Deleted.

senthamizhan said:
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
Click to expand...
Click to collapse
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.

renatohm said:
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
Click to expand...
Click to collapse
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts

senthamizhan said:
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
Click to expand...
Click to collapse
Thanks for your kindness!
Alright then, I'm next on line to test! I'll just backup (it sucks...) then I'll flash!

Out of luck, flashing via Mi Tool now...

renatohm said:
Out of luck, flashing via Mi Tool now...
Click to expand...
Click to collapse
What happened

senthamizhan said:
What happened
Click to expand...
Click to collapse
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.

renatohm said:
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
Click to expand...
Click to collapse
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP

satyen_ said:
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
Click to expand...
Click to collapse
Yes, that's the reason I tried this in the first place, but it didn't work for me.
Qfil did work, and I'm now on Bootleggers.

sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
Bro,if u had used your email address try checking in your inbox again for image, just search bootloader .

I've changed my mail with a Gmail one and it work. Now I've my unl files
Inviato dal mio Z2 Plus utilizzando Tapatalk

flash vendor to factory ( if you already flashed factory to vendor ) "
explain this line

In these forums there was a file for updating baseband to 1.70. I flashed it promptly and my phone also went into soft brick. Because accidentally my bootloader got locked and got revised also. By using certain key combinations I succeeded in again unlocking my bootloader without formatting my inner storage . now I am able to flash 4.4 ROMs. Without going through all the hassles of backup, formatting and again flashing twrp.

Your guide didn't work for me (but step 2 using your file didn't lock my bootloader). It would be nice if you gave direct link to items in your steps (for i.e factory to vendor.zip, twrp...). I guess I'll try using qfil unless someone has some tips... BTW I can't find a good qfil guide for 4.4 kernel roms, could anyone give me a link to a helpful thread for it if I can't get it working using this method?

Status of TWRP with Android 10 on Mi 9T

Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!

Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^

Micdu70 said:
Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^
Click to expand...
Click to collapse
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!

Annie the Eagle said:
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!
Click to expand...
Click to collapse
You normally don't need to flash VBMeta file.
- Official TWRP => https://dl.twrp.me/davinci/
- Latest OrangeFox (actually "R10.1_1" because "R10.1_2" is a broken version) => https://files.orangefox.tech/OrangeFox-Stable/davinci/
EDIT: Flash "R10.1_1" version over bad "R10.1_2" version if you already downloaded/flashed via my previous MEGA link.

Annie the Eagle said:
Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!
Click to expand...
Click to collapse
Sorry but this is not teally true - or maybe it's the case for custom roms and/or custom twrps
Using (not alone, you can find several peopke reporting the same):
-QFJEUXM 11m0.4.0 (Global, Stable,v Android 10)
-Official TWRP 3.3.1-0-davinci
Just flash that twrp through fastboot, do not wipe or fornat anything (vbmeta, internal storage, whatever), you will not loose anything and everything will work
And the same holds if twrp is replaced by orangefox (since recently, using R10.1_2)
Eg, when booting to twrp, you will enter your pin/password you use in system for unlocking the screen - and twrp will recognize and work with your encrypted Internal memory (so again, without formatting data, wiping vbmeta or whatever)
However, if you want to use some custom roms whose installation requires to format or wipe something, and/ot to use some custom twrps, that's another story (but not a problem in miui or in the official twrp)

Install Magisk without permanent TWRP - is it possible?

I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402

cris2d2 said:
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
Click to expand...
Click to collapse
but what would that help you with? having the normal recovery?

mike500005 said:
but what would that help you with? having the normal recovery?
Click to expand...
Click to collapse
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
yes i understand but what would be the goal? what you dont like or are afraid that you dont want the recovery is it because OTA updates? or??? you can try to root it and then reflash the stock recovery.img and apply a patched boot image could work idnk cause i have already done a lot to get mine working with latest update and i don't really want to go threw all the backups again

cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
custom recovey doesn't replace rom

indeed what you descripe is the official and recommended root method. TWRP is just for nandroid backup (not really needed since Migrate Backup and Magisk Modules can flash straight from android without TWRP at all), therefore the Magisk.zip is just for traditional reasons. Many devices don't even have TWRP (or with no working encryption support)
Installation
The Magic Mask for Android
topjohnwu.github.io
We no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support
Click to expand...
Click to collapse

Guide to flash realmeUI 2.0 beta builds [Global Variant Only]

DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DO​The only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery

reserved

Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA

Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader

bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work

ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you

What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?

kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.

It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""

Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.

Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance

4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?

Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.

kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too

How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?

Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?

Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks

Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks

tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me

So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again