How to backup stock recovery before flashing TWRP? - Xiaomi Poco X3 NFC Questions & Answers

Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.

lebigmac said:
Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.
Click to expand...
Click to collapse
I have had the same issues with that TWRP from mauronofrio and our stock ramdisk image. However, using Orangefox or the latest 3.5.0 TWRP which can be found in the Index for our device (everything can be found there lol) solved that issue, also, you don't need to backup the recovery partition, because the stock can be easily found and flashed the same.

Thanks but that still doesn't explain why the command fastboot boot twrp.img doesn't work on the Xiaomi Poco X3 NFC with unlocked bootloader.
EDIT:
Ok good news. I've actually managed to boot into the TWRP before flashing it.
As soon as it's done uploading the recovery to the phone you must unplug the USB cable. The timing is very important.
Good luck!

lebigmac said:
This appears to be a more widespread issue than I had originally thought:
Fastboot boot <boot.img> doesn't work but flash does
Hi there ! I compiled a kernel for my DB410. I am trying to boot it using $ fastboot boot boot.img Following the instructions that can be found here: https://builds.96boards.org/releases/dragonboard410c/linaro/debian/17.06.1/ Unfortunately, the device doesn’t boot. It starts the booting...
discuss.96boards.org
fastboot boot TWRP.img Not working
I'm trying to just boot the TWRP image for my OnePlus 5t to then install a custom ROM. So I typed fastboot boot "C:\Users\Elias\Downloads\twrp-3.3.1-0-dumpling.img" and it seemed to work and I got ...
android.stackexchange.com
https://www.reddit.com/r/LineageOS/comments/arakiy
After Android Q upgrade fastboot boot doesn't work on guacamole · Issue #1530 · TeamWin/Team-Win-Recovery-Project
I am running an official build of TWRP, downloaded from https://twrp.me/Devices/ I am running the latest version of TWRP I have read the FAQ (https://twrp.me/FAQ/) I have searched for my issue and ...
github.com
Can't boot TWRP image using fastboot boot
I'm trying to root my Moto Z3 Play. I'm on Windows 10, I have already unlocked the bootloader, however, I can't boot the twrp.img. I got the twrp.img from here https://twrp.me/motorola/motorolamoto...
stackoverflow.com
Click to expand...
Click to collapse
try latest OFOX or TWRP (OFOX image needs to be extracted from zip file), I'm really interested if some of these will boot via "fastboot boot recovery.img", thanks

lebigmac said:
Hi. How can I backup the stock recovery on my Xiaomi Poco X3 NFC before flashing the TWRP?
I tried executing following code while the phone is in fastboot mode but it never actually boots the custom recovery. It get's stuck at the poco boot logo. Yes my phone has unlocked bootloader.
Code:
fastboot boot TWRP.img
In terminal I get this output:
Code:
[email protected]:/# fastboot boot twrp_3.4.0-15_mauronofrio.img
downloading 'boot.img'...
OKAY [ 3.080s]
booting...
OKAY [ 5.088s]
finished. total time: 8.168s
Does anybody know why this command is not working? Thanks.
Click to expand...
Click to collapse
You don't need to backup the sock recovery.
Everything you need to do is download the stock rom and extract recovery.

@jeryll thanks for chiming in. All of these TWRP images will boot via "fastboot boot recovery.img" on our device.
It's important to unplug the USB cable at the right moment as soon as it's done uploading. Good luck!

Related

[Q] Can't boot into TWRP after updating to 4.4.3

Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything.
Any help is appreciated.
Click to expand...
Click to collapse
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
dottat said:
Why not just flash that recovery and then boot to it from the menu? Or you use flashify from within the Rom and change recoveries on the fly?
Click to expand...
Click to collapse
Worked like a charm. Thanks!
maaavy said:
Before I updated to 4.4.3 I was able to boot into TWRP by using the fastboot commands:
fastboot boot twrp.img
It would automatically reboot the phone into TWRP where I could flash SuperSU yet retain stock recovery.
Now when I attempt to do the very same thing on 4.4.3 I get:
downloading 'boot.img'...
OKAY [ 1.320s]
booting...
OKAY [ 0.402s]
finished. total time: 1.722s
The phone reboots but instead of rebooting into TWRP it just reboots the entire system.
I'm using stock everything, S-off and Unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
Brain fart on my part. Such an obvious mistake. Thanks!
santod040 said:
I know you got this resolved, but for future reference, your command should be: fastboot flash recovery nameofrecovery.img
You flashed the recovery as if it were a boot.img, which it's not.
Click to expand...
Click to collapse
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
cntryby429 said:
I wanted to follow up on this. I've used his idea in the past on another htc device. I'd "fastboot boot <recovery>.img" and I could flash whole ROMs without touching the existing recovery. As soon as you reboot the old recovery is still there. His command wasn't an incorrect syntax for flashing a boot.img it was temporarily booting into a recovery. Is there any reason this wouldn't work nowadays?
Click to expand...
Click to collapse
Yeah I know that was possible in the past, to flash a rom using a recovery one time, without overwriting the current one.
As I've never seen any real need or purpose to doing that, I've never done it that way.
I do know that the other command is what should be used to actually overwrite and flash a new recovery for further use.
So I can't really answer as to whether that method still works or not.
Didn't sound like it did for him though.

Unable to boot into recovery but able to boot system

Hi I wonder if anyone can help me. My tf700 is running Zombi-Pop 5.1.1-OMNI-DEODEX RC2 . I may have wrecked my recovery and boot-loader. My Infinity is unlocked and rooted and had TWRP 2..7.00 or roughly that. In preparation for installing KatKiss 6.0.1 . I updated TWRP to [RECOVERY] KANG TWRP TF700T [email protected] JAN 4 from within TWRP and it completed ok. When I went to reboot into recovery I got a unable to boot error boot-image is unreadable X000000 or something like that, But I am able to boot the system which seems to be working OK. Does anyone know if the is anyway for me to re-flash a working recovery or am I stuck without a recovery? If anyone can help me with this I would much appreciate it.
Cheers Al-Man
ps. I have read loads of posts but I am still unsure as to what is the best course of action. I don't want to make it totally useless.
Your bootloader is fine or you would not be able to boot Android.
Kang TWRP 2.8.x is fine for any current rom so that is not the problem either.
Did you let the tablet reboot after the recovery flash? Sounds to me as if that was when things went south.
So fastboot flash the recovery, then reboot to system once before you try to boot into recovery.
If you don't know how to fastboot flash it's high time you learned it.
http://forum.xda-developers.com/showthread.php?t=2688891
You could also use flashify or dd commands if you have root.
Sent from my KYOCERA-C6745 using Tapatalk
Tried Fastbbot still no joy
berndblb said:
Your bootloader is fine or you would not be able to boot Android.
Kang TWRP 2.8.x is fine for any current rom so that is not the problem either.
Did you let the tablet reboot after the recovery flash? Sounds to me as if that was when things went south.
So fastboot flash the recovery, then reboot to system once before you try to boot into recovery.
If you don't know how to fastboot flash it's high time you learned it.
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Thanks for your quick reply bernbib. I have tried to fastboot and load a new recovery image. I am able to see the device using the fastboot devices command. When I flash a new TWRP image it shows the following
twrp.img
sending 'recovery' (7038 KB)...
OKAY [ 2.801s]
writing 'recovery'...
OKAY [ 2.541s]
finished. total time: 5.343s
I then try fastboot reboot and all I get is
rebooting......
on the boot loader screen it reads just under the boot version
Starting Fastboot USB download protocol this is constantly showing every time I boot to the boot loader.
and then I reboot from the tablet and its back to square one .
Any Help with this problem would be most appreciated I can still boot to system but I am not able to access recovery.
Many Thanks. Alex
Can you reboot recovery from adb or shell?
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Can you reboot recovery from adb or shell?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Hi RealWelder Thanks for your quick reply No I'm afraid not.
Cheers. Alex
screenshot of boot screen
I just thought I would post a screen shot to see if anyone has any suggestions
View attachment 3863929
Any help with this would be much appreciated. :crying:
cheers Alex
Al-Man said:
I just thought I would post a screen shot to see if anyone has any suggestions
View attachment 3863929
Any help with this would be much appreciated. :crying:
cheers Alex
Click to expand...
Click to collapse
I have seen many cases of "unrecoverable bootloader error" but never that you could still boot into system with that error. So I have no idea what is going on for you, but the only method I know of to successfully recover from a unrecoverable bootloader error is to flash the Asus system blob in fastboot after fastboot erasing each major partition. We call it a buster99 and you'll find it here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Before you do that why don't you try to 'fastboot boot recovery twrp.img' instead of flashing it. You should still be able to use TWRP as usual, flash a rom with it etc. It just does not get installed on the tablet....
See if you can use the recovery that way...
berndblb said:
I have seen many cases of "unrecoverable bootloader error" but never that you could still boot into system with that error. So I have no idea what is going on for you, but the only method I know of to successfully recover from a unrecoverable bootloader error is to flash the Asus system blob in fastboot after fastboot erasing each major partition. We call it a buster99 and you'll find it here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Before you do that why don't you try to 'fastboot boot recovery twrp.img' instead of flashing it. You should still be able to use TWRP as usual, flash a rom with it etc. It just does not get installed on the tablet....
See if you can use the recovery that way...
Click to expand...
Click to collapse
Thanks. berndblb I tried to fastboot twrp from my PC (Ubuntu 14.04) but no joy got the following :crying:
[email protected]:~/Android$ fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Android$ fastboot boot twrp.img
creating boot image...
creating boot image - 7211008 bytes
downloading 'boot.img'...
OKAY [ 2.727s]
booting...
FAILED (remote: ()
finished. total time: 2.751s
[email protected]:~/Android$ sudo fastboot boot twrp.img
[sudo] password for alex:
creating boot image...
creating boot image - 7211008 bytes
downloading 'boot.img'...
OKAY [ 2.729s]
booting...
FAILED (remote: ()
finished. total time: 2.747s
Any other suggestions, I don't like the sound of Buster 99 also tablet is the wife's.
Cheers. Alex
Buster99 has been a tablet saver for many users.
But if you don't want to do the whole thing try to fastboot erase recovery, cache and misc, then flash TWRP again and see if you can boot it.
Sent from my Nexus 5X using Tapatalk
berndblb said:
Buster99 has been a tablet saver for many users.
But if you don't want to do the whole thing try to fastboot erase recovery, cache and misc, then flash TWRP again and see if you can boot it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks berndblb After erasing everthing 3 times I was finally able to flash a new TWRP image. Many Thanks again for all your help. Alex

Unable to install TWRP

Hey all, here's a list of steps i've done:
1. succesfully unlocked bootloader
2. downloaded the lateset 3.3.1.0 img and twrp zip (europe) from twrp.me.
3. entered fastboot and validated my oneplus listed under fasboot devices
4. opened powershell from img folder and ran: fastboot boot twrp-3.3.1-0-guacamoleb.img
Then, it looked like the img was installed:
downloading 'boot.img'...
OKAY [ 1.266s]
booting...
OKAY [ 0.129s]
finished. total time: 1.409s
however, i got stuck with fastboot logo in my OnePlus, and ater hard-reset i tried to enter twrp - but i got the default oneplus recovery instead.
never reached the step where i install the twrp zip.
can someone please help me understand what i got wrong?
segevngr said:
Hey all, here's a list of steps i've done:
1. succesfully unlocked bootloader
2. downloaded the lateset 3.3.1.0 img and twrp zip (europe) from twrp.me.
3. entered fastboot and validated my oneplus listed under fasboot devices
4. opened powershell from img folder and ran: fastboot boot twrp-3.3.1-0-guacamoleb.img
Then, it looked like the img was installed:
downloading 'boot.img'...
OKAY [ 1.266s]
booting...
OKAY [ 0.129s]
finished. total time: 1.409s
however, i got stuck with fastboot logo in my OnePlus, and ater hard-reset i tried to enter twrp - but i got the default oneplus recovery instead.
never reached the step where i install the twrp zip.
can someone please help me understand what i got wrong?
Click to expand...
Click to collapse
Please follow this guide and use unofficial recovery https://forum.xda-developers.com/on...tloader-flash-twrp-root-t3954559/post80015800

Pixel 3a - stuck on BootLoader with: error boot prepar

Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
DarthLuch said:
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
Click to expand...
Click to collapse
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
adm1jtg said:
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
Click to expand...
Click to collapse
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
DarthLuch said:
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
Click to expand...
Click to collapse
If 21 worked but 22 didn't... Going from my faltering memory that means your not on March security, your on feb or earlier. 22 only worked on March, i am running it myself.
I got stuck here, too... I used the flash tool (flash.android.com) and it put me back to stock after about a 20 minute progress bar crawl
I have the same problem can someone help me?
YYa solucionaste ?

realme 5i twrp command not working ( fastboot boot twrp.img )

i am trying to root realme 5i. i successfully unlock bootloader. fastboot flash recovery twrp.img working fine.
but when i try command fastboot boot twrp.img it shows
PS C:\Users\hpp\Desktop\adbfastboot> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.415s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
ad_nannnn said:
i am trying to root realme 5i. i successfully unlock bootloader. fastboot flash recovery twrp.img working fine.
but when i try command fastboot boot twrp.img it shows
PS C:\Users\hpp\Desktop\adbfastboot> fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.415s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
Click to expand...
Click to collapse
Also same problem ... But after use another twrp it's shown success .. but still no working ... In commed section it's saw successful ... But when boot on recovery mood my phone it's no working ..no recovery option
Yeah right me too
Somehow Wrong Command
ad_nannnn said:
...
But, when I try command fastboot boot twrp.img
...
FAILED (remote: unknown command)
finished. total time: 1.421s
please guide me how to install twpr on m phone . please help
Click to expand...
Click to collapse
After flashing a Custom Recovery, If you want to boot to recovery, the actual command through fastboot is
Code:
fastboot boot recovery
or also in the bootloader screen you can press vol+ button untill you see Recovery mode then hit Power button.
The most important point is After flashing a Custom Recovery you must flash the vbmeta with Verity command To make it permanent. Otherwise it'll just revert back to Stock Recovery. (This method only works in Color Os (ie., Android 9), for RealmeUI you need additional thing to do)
iamvijaypushparaj said:
After flashing a Custom Recovery, If you want to boot to recovery, the actual command through fastboot is
Code:
fastboot boot recovery
or also in the bootloader screen you can press vol+ button untill you see Recovery mode then hit Power button.
The most important point is After flashing a Custom Recovery you must flash the vbmeta with Verity command To make it permanent. Otherwise it'll just revert back to Stock Recovery. (This method only works in Color Os (ie., Android 9), for RealmeUI you need additional thing to do)
Click to expand...
Click to collapse
Where do we get this vbmeta from? I'm having the same problem, that after flashing twrp.img it just reboots back into fastboot mode. Is this because Secure Boot is enabled and does vbmeta disable that?
realme 5 tg
doveman said:
Where do we get this vbmeta from? I'm having the same problem, that after flashing twrp.img it just reboots back into fastboot mode. Is this because Secure Boot is enabled and does vbmeta disable that?
Click to expand...
Click to collapse
realme 5 telegram group
CjConvento said:
realme 5 telegram group
Click to expand...
Click to collapse
iamvijaypushparaj posted it here https://forum.xda-developers.com/showpost.php?p=83251175&postcount=16 but unfortunately it still just boots into fastboot whatever I try.
doveman said:
iamvijaypushparaj posted it here https://forum.xda-developers.com/showpost.php?p=83251175&postcount=16 but unfortunately it still just boots into fastboot whatever I try.
Click to expand...
Click to collapse
After flashing recovery via cmd, you will go back to fastboot on your screen. Navigate the volume buttons til it show Recovery mode on top of the screen. Then press power button and it will boot to recovery.
jokezerious said:
After flashing recovery via cmd, you will go back to fastboot on your screen. Navigate the volume buttons til it show Recovery mode on top of the screen. Then press power button and it will boot to recovery.
Click to expand...
Click to collapse
It turned out the problem was Orangefox. With TWRP it booted into Recovery fine when I selected that option but with Orangefox it would just reboot into fastboot. I'll try some different versions of Orangefox sometime but for now my biggest problem is that it's impossible to set a Lock Screen PIN/Password, let alone use FingerPrint. It seems unlocking the bootloader breaks the security settings.
whats orangefox ? did u found a fix !
I rooted 5i and no use your code. I follow this video
Some code:
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot devices
fastboot flash recovery REALME5i.img
fastboot flash vbmeta vbmeta.img
adb reboot recovery

Categories

Resources