I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
ffalzone23 said:
I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB Download protocol
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000).
I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated.
As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
Click to expand...
Click to collapse
I don't know if this method will work on CM. You can give it a shot and report back.
1. Download the Asus firmware from Asus website and extract it once because there is anotherr zip in it.
2. Copy the second zip file to your root directory on your internal sd and reboot
3. If it works, you should see the notification on the lower right corner and click on it. You just follow the instruction to put your device back to the factory bootloader.
Before you use this method, you need to move all your stuff to your computer as a back up because it will wipe everything that you have on your device..
There is another method that you could try if it does not work.. Good luck..:fingers-crossed:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
ffalzone23 said:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification
What is this other method you speak of....
This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time.
On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
Click to expand...
Click to collapse
Did you unzip it once? You need to have a different firmware version than the one on your system... I will find the other method and link for you..
Thanks Man. I appreciate the help!
ffalzone23 said:
Thanks Man. I appreciate the help!
Click to expand...
Click to collapse
I am still looking for the link. I forgot what it is called... I will post the link here when I find it..
LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
ffalzone23 said:
LetMeKnow, Thanks for the update.
Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
Click to expand...
Click to collapse
By reading your post again, let me summarize it here. You know how to use fastboot, can't boot to your custom recovery (TWRP), want to flash stock recovery to fix your problem, and have try a few methods to put the stock back but it did not work. You still can get to your bootloader menu. Can you try to use this command to see if you can access to your custom recovery: fastboot boot-recovery
Good luck and get back to you on the link...
this is what came up in command prompt....
C:\android-sdk\platform-tools>fastboot boot-recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
ffalzone23 said:
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there.
C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img
sending 'recovery' (7746 KB)...
OKAY [ 3.606s]
writing 'recovery'...
OKAY [ 2.414s]
finished. total time: 6.022s
C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.548s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
Click to expand...
Click to collapse
I have not seen that before, so I don't know what to say...
When I did fastboot TWRP recovery, I used blob file instead of img file. Do you want to download the blob file and try again?
Edit: What version of TWRP did you fastboot? V2.6.3.0 is larger than our partition on the tf700. Therefore, you can not use it..
The .IMG was cwm recovery. I tried that after trying twrp most recent version. 2.6.3.1 I think.
Sent from my XT926 using xda app-developers app
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
If fastboot doesn't work for you but you have a rooted Android, you can try installing a recovery using the dd method:
Code:
cd wherever/you/downloaded/twrp
su
dd if=openrecovery-twrp-2.6.3.1-tf700t.blob of=/dev/block/mmcblk0p4
then reboot - the bootloader should flash your new recovery with a blue progress bar and reboot again. On the second reboot, hold down volume-down to get to the bootloader menu and try entering RCK again.
ffalzone23 said:
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts?
At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
Click to expand...
Click to collapse
You can try _that method. He always have good advices and know what he is talking about.....:good:
Good luck....
_that. What screen do I have my tablet on when I run the dd command prompt ?
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
ffalzone23 said:
_that. What screen do I have my tablet on when I run the dd command prompt ?
Click to expand...
Click to collapse
You mean the expected output? Something similar to:
Code:
15836+1 records in
15836+1 records out
8108136 bytes (8.1 MB) copied, 0.152395 s, 53.2 MB/s
(the above is from my PC - the TF700 is slower)
Or do you mean where you enter those commands? Either via your PC in an adb shell (in this case you must first transfer the file to the TF700 with adb push or other means), or directly on your tablet with a terminal app under Android (I recommend the one from jackpal, search the Play Store)
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
ffalzone23 said:
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
Click to expand...
Click to collapse
What is the response when you use power and volume down buttons?
It takes me into fastboot or boot loader screen w the rck, android cold boot, and wipe data icons
Yesterday I left my A510 in stand-by with its AOKP kitkat rom running (it runs smooth since many weeks).
This morning the tablet was bricked.
When I turn it on, it reports "boot failed" and starts the fastboot download protocol.
I cannot enter CWM recovery anymore.
I have tried to fastboot a CWM recovery with "fastboot boot recovery_nothrills.img" but it gets stuck; I tried to boot the stock recovery with "fastboot boot recovery_1_044_00.img" but it freezes.
I have tried to flash these recoveries with "fastboot flash recovery recovery_nothrills.img" but it fails:
Code:
# fastboot flash recovery recovery_nothrills.img
sending 'recovery' (5968 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.016s
I run these program as root under linux, therefore I thinks it's not a driver/permissions problem.
I have no idea of what else try.
Is there a recovery program as the one for the A500, running under XP?
Thanks.
Android developer tool
stragnagn said:
Yesterday I left my A510 in stand-by with its AOKP kitkat rom running (it runs smooth since many weeks).
This morning the tablet was bricked.
When I turn it on, it reports "boot failed" and starts the fastboot download protocol.
I cannot enter CWM recovery anymore.
I have tried to fastboot a CWM recovery with "fastboot boot recovery_nothrills.img" but it gets stuck; I tried to boot the stock recovery with "fastboot boot recovery_1_044_00.img" but it freezes.
I have tried to flash these recoveries with "fastboot flash recovery recovery_nothrills.img" but it fails:
Code:
# fastboot flash recovery recovery_nothrills.img
sending 'recovery' (5968 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.016s
I run these program as root under linux, therefore I thinks it's not a driver/permissions problem.
I have no idea of what else try.
Is there a recovery program as the one for the A500, running under XP?
Thanks.
Click to expand...
Click to collapse
Search for Android SDK developer tool there you will find the ADB and fastboot Command line tool.
In the forum you find Instructions you to flash back to stock.
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.
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
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!