Database Users

[Q][SOLVED]Getting Recovery to work with 4.1.2 Android and 3.41 Bootloader?

I don't know if I'm the only one or just a among a group of unlucky few but I managed to update to 4.1.2 no problems. Was able to restore root, no problems. It flashed the new bootloader 3.41 but now I can not get into Clockworkmod recovery. I tried installed it through rom manager and I tried flashing it through fastboot commands. I even tried the regular and the touch recovery. Is there a work around to this? Are these recoveries not compatible with the new bootloader? I suppose I can flash the old 3.34 bootloader and try again but does anyone actually know the deal here? Please help me out.
EDIT:
Thanks to SilverPosition and his post here . He has provided us with a link to a working CWM Touch Recovery. I've also been told that TWRP 2.3.1.1 found here also works with the 3.41 bootloader.
Thank you everyone for figuring this out

Update:
The only solution I found so far was to reflash the 3.34 bootloader in fastboot mode and then reflash my CWM recovery. Then I was able to get into recovery. What I don't understand is that many have been able to get the 3.41 bootloader flashed and then still have no trouble getting into recovery. So what am I missing? I installed the 3.41 bootloader 2 ways just to test. 1, with fastboot commands with the .img and the other in CWM with the .raw file. Both worked just fine updating the bootloader to 3.41 but no matter what recovery is then broken. Anyone got any input?

tucstwo said:
I don't know if I'm the only one or just a among a group of unlucky few but I managed to update to 4.1.2 no problems. Was able to restore root, no problems. It flashed the new bootloader 3.41 but now I can not get into Clockworkmod recovery. I tried installed it through rom manager and I tried flashing it through fastboot commands. I even tried the regular and the touch recovery. Is there a work around to this? Are these recoveries not compatible with the new bootloader? I suppose I can flash the old 3.34 bootloader and try again but does anyone actually know the deal here? Please help me out.
Click to expand...
Click to collapse
I have the same issue. I've tried every thing I can think of (except flashing the old bootloader) and nothing seems to work. Can't get into custom recovery (CWM, Goo Manager, TWRP, QuickBoot, ROM Manager), you name it I think I've tried it. I tried to flash CWM 6.0.X.X (can't remember exactly which one) thru the Toolkit but that didn't work either.

i used "fastboot boot recoveryimage.img" to get into cwm-recovery temporarily...

jpcalhoun said:
I have the same issue. I've tried every thing I can think of (except flashing the old bootloader) and nothing seems to work. Can't get into custom recovery (CWM, Goo Manager, TWRP, QuickBoot, ROM Manager), you name it I think I've tried it. I tried to flash CWM 6.0.X.X (can't remember exactly which one) thru the Toolkit but that didn't work either.
Click to expand...
Click to collapse
CWM will work with 3.34. I can't get it to work no way no how on 3.41.

tucstwo said:
CWM will work with 3.34. I can't get it to work no way no how on 3.41.
Click to expand...
Click to collapse
Cannot get TWRP to work with 3.41 either - works nicely with 3.34.
Is it possible to flash just the important stuff of 4.12 and leave out the bootloader (i.e., keep bootloader 3.34)?

Android 4.1.2
Bootloader 3.41
TWRP 2.3.0.0
I got it to work by erasing the stock recovery then flashing TWRP.
fastboot erase recovery
fastboot flash recovery
I also noticed if you do not erase the stock recovery prior to flashing the custom recovery, it creates a "recovery-from-boot.p" file in the system directory. This file causes your custom recovery to be overwritten with the stock recovery during boot up. You will need to rename or delete this file then flash your custom recovery again to make it stick.

docfreed said:
Cannot get TWRP to work with 3.41 either - works nicely with 3.34.
Is it possible to flash just the important stuff of 4.12 and leave out the bootloader (i.e., keep bootloader 3.34)?
Click to expand...
Click to collapse
What I did was flashed the entire 4.1.2 and then flashed the 3.34 bootloader and my old CWM recovery back in if you choose to go that route. Its a lot easier to replace what doesnt work rather than pick and choose what you're gonna flash

tucstwo said:
What I did was flashed the entire 4.1.2 and then flashed the 3.34 bootloader and my old CWM recovery back in if you choose to go that route. Its a lot easier to replace what doesnt work rather than pick and choose what you're gonna flash
Click to expand...
Click to collapse
Thanks - yes, of course you're right. Are you able to repeatedly boot into CWM, make backups, etc... I hate to redo my whole setup again but I also believe that there's an issue with the 3.41 bootloader.
Did you flash the bootloader and CWM with fastboot?

docfreed said:
Thanks - yes, of course you're right. Are you able to repeatedly boot into CWM, make backups, etc... I hate to redo my whole setup again but I also believe that there's an issue with the 3.41 bootloader.
Did you flash the bootloader and CWM with fastboot?
Click to expand...
Click to collapse
Use the bootloaders provided in this thread : http://forum.xda-developers.com/showthread.php?t=1929270
There's 2 threads floating around but 1 of them provides to bootloaders in flashable format and the one I gave you in image format for fastboot flashing.
What I did was downloaded the OTA zip from here: http://forum.xda-developers.com/showthread.php?p=32672323
Downloaded Voodoo OTA Rootkeeper from the play store. Backed up my su binary and root access with that app.
Then I ran the ota zip in CWM.
I rebooted. went into Voodoo OTA and restored root access
I used root explorer and deleted /system/recovery-from-boot.p and /system/etc/install-recovery.sh this way it wouldnt keep attempting to flash the stock recovery on boot.
Rebooted into fastboot mode and fastboot flashed the 3.34 bootloader
rebooted the bootloader
then fastboot flashed cwm touch.
then rebotoed and everything works fine.
Only issue is im on the 3.34 bootloader and not the 3.41 one and just want to know WHY?! lol

tucstwo said:
Use the bootloaders provided in this thread : http://forum.xda-developers.com/showthread.php?t=1929270
There's 2 threads floating around but 1 of them provides to bootloaders in flashable format and the one I gave you in image format for fastboot flashing.
What I did was downloaded the OTA zip from here: http://forum.xda-developers.com/showthread.php?p=32672323
Downloaded Voodoo OTA Rootkeeper from the play store. Backed up my su binary and root access with that app.
Then I ran the ota zip in CWM.
I rebooted. went into Voodoo OTA and restored root access
I used root explorer and deleted /system/recovery-from-boot.p and /system/etc/install-recovery.sh this way it wouldnt keep attempting to flash the stock recovery on boot.
Rebooted into fastboot mode and fastboot flashed the 3.34 bootloader
rebooted the bootloader
then fastboot flashed cwm touch.
then rebotoed and everything works fine.
Only issue is im on the 3.34 bootloader and not the 3.41 one and just want to know WHY?! lol
Click to expand...
Click to collapse
Thanks - I'll try this tonight and let you know - I'd also like to know why there's so much issue with 3.41 but I'll be happy if I can update.

janedoesmith said:
Android 4.1.2
Bootloader 3.41
TWRP 2.3.0.0
I got it to work by erasing the stock recovery then flashing TWRP.
fastboot erase recovery
fastboot flash recovery
I also noticed if you do not erase the stock recovery prior to flashing the custom recovery, it creates a "recovery-from-boot.p" file in the system directory. This file causes your custom recovery to be overwritten with the stock recovery during boot up. You will need to rename or delete this file then flash your custom recovery again to make it stick.
Click to expand...
Click to collapse
I removed the "recovery-from-boot.p" file, and erased the stock recovery, then flashed Clockwork Recovery, but still can't boot into Clockwork recovery. It just displays "boot downloaded image" on the top, then after a few seconds, it boots into android os...

I don't know about CWM but I got it to work with TWRP.

janedoesmith said:
Android 4.1.2
Bootloader 3.41
TWRP 2.3.0.0
I got it to work by erasing the stock recovery then flashing TWRP.
fastboot erase recovery
fastboot flash recovery
I also noticed if you do not erase the stock recovery prior to flashing the custom recovery, it creates a "recovery-from-boot.p" file in the system directory. This file causes your custom recovery to be overwritten with the stock recovery during boot up. You will need to rename or delete this file then flash your custom recovery again to make it stick.
Click to expand...
Click to collapse
janedoesmith said:
I don't know about CWM but I got it to work with TWRP.
Click to expand...
Click to collapse
I tried exactly this
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-3.41
fastboot reboot-bootloader
fastboot erase recovery
fastboot flash recovery twrp2.2.2.1
fastboot reboot-bootloader
Then into recovery...nothing. Back to the google screen. That's it.

All I did was rename recovery-from-boot.p to recovery-from-book.bak, reinstalled TWRP from GooManager, and everything works just fine.
You have to disable/delete that file in /system or it will restore the stock recovery every time you reboot.

iElvis said:
All I did was rename recovery-from-boot.p to recovery-from-book.bak, reinstalled TWRP from GooManager, and everything works just fine.
You have to disable/delete that file in /system or it will restore the stock recovery every time you reboot.
Click to expand...
Click to collapse
Nah that's not it. Those files were the first thing I got rid of as soon as I restored root access, before I even bothered to access recovery. If u look a few posts up I told that other member how I installed stuff on my tablet and it included those steps.

tucstwo said:
Nah that's not it. Those files were the first thing I got rid of as soon as I restored root access, before I even bothered to access recovery. If u look a few posts up I told that other member how I installed stuff on my tablet and it included those steps.
Click to expand...
Click to collapse
Ah--I see that now. I'm not sure which bootloader I'm on, to be honest--I just took the OTA as-is.

I flashed my device with the JZO54K factory image. Then i flashed cwm 6.0.1.0 via fastboot. I can not boot recovery using any method (recovery via bootloader, adb, terminal, various apps) with the 3.41 bootloader. The only way I have been able to use recovery is to downgrade to the 3.34 bootloader from JRO03D.
Sent from my Nexus 7 using Tapatalk 2

I'm in the same ship. Only works using 3.34 bootloader.
Install the factory image or OTA, with 3.41 bootloader stop me from running cwm. Only solution is flash 3.34 bootloader image file to use it again.
Edit: C80 here.

+1, I'm on a C60 revision Nexus 7 and I spent hours trying to figure this out until I flashed back to 3.34 bootloader. Thanks for this!

Bootloop on OP2 after 3.1.0 OTA

Hello everyone.
I've recently got the notification from the updater saying that oxygen OS 3.1.0 was out and awaiting to be downloaded (was on 3.0.2).
Since I unlocked bootloader/installed twrp/installed supersu when I was on 2.1.0 I wanted to update using the same method that I had used to update it before: install full zip of 3.0.2, install zip 3.0.2->3.1.0, install supersu
Problem is after I've done this the phone was stuck into booting animation when booting into system.
And since I'm dumb and nervous I thought that wiping /system before the installation was the solution.
So once again, this time with also system wipe, full 3.0.2->ota update->install supersu
Now you already probably understood that not only the phone is booting forever, but also I lost access to twrp and only have fastboot showing up when trying to boot through power+vol up
What can I do? What did I do wrong?
Thanks for the attention
Edit: I can access recovery, had the wrong combo of buttons going (i was pressing power+vol up but it's power+vol down)
I repeat, TWRP is fully accessible
Edit 2: Since TWRP was fully accessible I reinstalled both full zip and 3.0.2->3.1.0 zip without supersu and it booted... What did I do wrong with supersu?

Depends on the SuperSU zip y supposed you need the one specific for oos3 beta or h2os
Sent from my ONE A2005 using Tapatalk

I fresh installed 3.1.0 but after booting up and flashing supersu v2.78 i get bootloop. Before it always worked so i think we need to wait for an updated version of supersu.
I boot in fastboot modes by volume up + power and then connect with pc en boot in recovery with fastboot command. 'fastboot boot recovery.img'

Burn2Hell said:
I fresh installed 3.1.0 but after booting up and flashing supersu v2.78 i get bootloop. Before it always worked so i think we need to wait for an updated version of supersu.
I boot in fastboot modes by volume up + power and then connect with pc en boot in recovery with fastboot command. 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Did you try flashing the modified SuperSu 2.78 zip?

I had the same problem until I flashed the SuperSu mentioned from Spannaa the post before.

It happened to me too and the fix is to flash the modified supersu.

Nimwe said:
Hello everyone.
I've recently got the notification from the updater saying that oxygen OS 3.1.0 was out and awaiting to be downloaded (was on 3.0.2).
Since I unlocked bootloader/installed twrp/installed supersu when I was on 2.1.0 I wanted to update using the same method that I had used to update it before: install full zip of 3.0.2, install zip 3.0.2->3.1.0, install supersu
Problem is after I've done this the phone was stuck into booting animation when booting into system.
And since I'm dumb and nervous I thought that wiping /system before the installation was the solution.
So once again, this time with also system wipe, full 3.0.2->ota update->install supersu
Now you already probably understood that not only the phone is booting forever, but also I lost access to twrp and only have fastboot showing up when trying to boot through power+vol up
What can I do? What did I do wrong?
Thanks for the attention
Edit: I can access recovery, had the wrong combo of buttons going (i was pressing power+vol up but it's power+vol down)
I repeat, TWRP is fully accessible
Edit 2: Since TWRP was fully accessible I reinstalled both full zip and 3.0.2->3.1.0 zip without supersu and it booted... What did I do wrong with supersu?
Click to expand...
Click to collapse
Can you please specify the brief step by step procedure of flashing 3.1.0 on 3.0.2 (Clean flash)!Please!
Sent from my ONE A2003 using Tapatalk

nitishgupta said:
Can you please specify the brief step by step procedure of flashing 3.1.0 on 3.0.2 (Clean flash)!Please!
Click to expand...
Click to collapse
Download the full OOS 3.1.0 zip from post #1 in the Oxygen mirrors thread and flash it via recovery.
If you want root, flash a SuperSU zip from the same post.

Soft bricked Zenfone 3 still have TWRP

I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.

Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.

android_101_ said:
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
Click to expand...
Click to collapse
I only have the Twrp recovery.

Canukboy said:
I only have the Twrp recovery.
Click to expand...
Click to collapse
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?

wang1chung said:
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
Click to expand...
Click to collapse
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.

Canukboy said:
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Click to expand...
Click to collapse
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.

Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Click to expand...
Click to collapse
Hy Wang.. I followed your guide - modified updater-script, but I can't install the stock rom .zip from TWRP.
It says "can't extract updater-binary", I tried few times thinking that the file is corrupt, but the result still same.
FYI, I use stock ROM "UL-ASUS_Z012D-WW-14.2020.1709.68-user.zip", and TWRP 3.1.1.
Please help me if you have experienced it before. Thanks

@rzahunn
I've never had that error before and you're on the latest version of TWRP so I'm going to guess it has to do with your modification of the updater script.
You edited updater-script not updater-binary, correct? There are two files with similar names

There's a detailed guide by @kyle_l88 on how to return to stock.
Here's the link: https://forum.xda-developers.com/zenfone-3/development/how-to-to-stock-rom-recovery-zenfone-3-t3666223
Do note that the original recovery link is dead. The updated link is: https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA

TWRP Bootloop
Sorry if my reply is irrelevant, but I need some helps.
I am also using Zenfone 3, but stuck in TWRP bootloop.
I cannot flash using fastboot (not detected on PC), reflashing ROM doesn't help either.
I've tried all the possible methods I found on Google, such as dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota method but still has no luck.
Restoring backup would end me in TWRP too.

@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.

wang1chung said:
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
Click to expand...
Click to collapse
I've managed to fix the bootloop after following the guide. I missed that somehow, thanks for pointing that to me.
I've thanked you (pressed the Thanks button).

dm verity
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
does it hangs on logo then start again? then reflashing the rom then flashing the dm verity zip again hope it works

[A2017G] Cant install superSu through twrp

I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?

Shakedbuk said:
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Click to expand...
Click to collapse
Update your twrp, there's no need to use that old version... my phone reboots when it wants when it has opd twrp versions
Download twrp 3.1.1-0
Put it on your phone, maybe via adb or through mtp if you have it
Go to Install -> hit the button on the right that says 'Install image'
Find the TWRP.img and install it, it will prompt you where to install it, put 'recovery'

Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.

Shakedbuk said:
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Click to expand...
Click to collapse
Don't use axon7tool for this... you already have TWRP, the only thing you have to use axon7tool for is to install twrp when you have the stock recovery. after you have twrp on the phone just try not to use the PC except for maybe miflash

I tried both of this options.
Flashing new version of twrp through the old twrp resulted in black screen when i try to get to recovery.
So I flashed the old twrp from the pc, tried to flash the new one using the same method but it the same as i flashed it through the old twrp. (which mean that when i get to the recovery i get black screen)
ATM the situation is the same, system wont boot stuck on zte logo, twrp is 3.0.2.2 (there is another method to flash newer twrp?)
There is another option?

After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?

Shakedbuk said:
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Click to expand...
Click to collapse
Wait, what did you do? Did you install everything again after wiping system?

Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.

Shakedbuk said:
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Click to expand...
Click to collapse
You installed SuperSU without a system, and the phone did not boot up? Amirite?

what i did was wipe system dalvik cache, cache, after that install bootstack and the system files, and after that the supersu.
before i wiped the system, when i tried to install the supersu the twrp collapsed, after that it installed it but did not helped to make the system boot.

After update to V11.0.4.0.QFJEUXM TWRP no longer available

Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!

Same thing happening to me, no matter what I do, stock recovery keeps overwriting TWRP

Oh dear, that doesn't sound good.
I hope there will be a solution to the problem soon.
I don't want to do without TWRP and root.
I wanted to try it according to these instructions "https://miui.blog/redmi-k20/twrp-mi-9t-redmi-k20-vbmeta-mauronofrio/". But don't trust me, I'm afraid that it won't work and I can start all over again.

Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.

The fact that twrp is lost when flashing official rom (even thought twrp itself) is normal. You just have to reboot into bootloader and flash twrp again and it will be back.
Your problem here is that you are using an old and unofficial twrp build, that has problems on newer roms. Flash official twrp and you'll be fine

houbaba said:
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
Click to expand...
Click to collapse
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop

hounter17 said:
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
Click to expand...
Click to collapse
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html

RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Oh sorry it works? I read somewhere that the original causes also bootloops :good:

Found something on a Russian website.
Обновление TWRP Recovery от LR.Team для устройств на Android 10
Does anyone dare to test this?
Here is the link to the TWRP for our Mi9t
> TWRP-3.3.1-1109-DX (полный комплект для установки) <
Check it out...

I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.

frank808 said:
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
Click to expand...
Click to collapse
Where did you get the twrp file from?

You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899

RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Ok, I am on global 11.0.4.0 (QFJMIXM) and I used this latest twrp-3.3.1-0-davinci.img and I can confirm its working without bootloop.

ShiningScias said:
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
Click to expand...
Click to collapse
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so

zgfg said:
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
Click to expand...
Click to collapse
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
A custom Recovery doesn't change Widevine level.
And TWRP is useful in case of bootloop (because of an installed Magisk module, by example) or if you want to easily reinstall Magisk after ROM update.

RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Micdu70 said:
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
Click to expand...
Click to collapse
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img

zgfg said:
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Yes, it should work.
But I prefer OrangeFox Recovery.

zgfg said:
so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Micdu70 said:
Yes, it should work.
But I prefer OrangeFox Recovery.
Click to expand...
Click to collapse
Something is fishy. IMO, if that official TWRP is really ok for 11.0.4.0, then it should correctly boot by:
fastboot boot twrp-3.3.1-0-davinci.img
But phone rebooted into the dark.
TG, I didn't really flash with, so by long pressing Pow it rebooted to system.
Tried again, no avail
Edit:
Tried the same fastboot boot with
twrp-3.3.1-12-davinci-mauronofrio.img and also OrangeFox-R10.1_1-Stable-davinci.img (obtained by unzipping OrangeFox), but it also reboots to dark and I have to long press Pow to reboot to system

frank808 said:
Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Click to expand...
Click to collapse
You can install twrp by All In One tool
You can find its thread here itself

I took the official TWRP. " Link "
Flashed in fastboat and then booted the phone with a key combination in TWRP.
With the Fastboot command it didn't work for me either, the cell phone remained black ...