Database Info

[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.

[Q] Flashed the LPX13D image and now my recovery is gone.

Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?

Try to flash cwm and tell me what happens

Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.

deleted

Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l

Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.

Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.

Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.

Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?

Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.

Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

Huawei Mate 9 command not allowed but the bootloader is unlock

Hey guys i got a new problem with my phone. I did a factory reset and later i unlocked the bootlader again but when i tried to do something with adb said ''Command not allowed'' later when i tried to install twrp said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 471859200 bytes
sending 'recovery' (8728 KB)...
OKAY [ 0.252s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.266s

Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo

ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I'm loving you so much right now

ante0 said:
Are you on Oreo?
Edit: seeing your thread below this one you are.
Oreo uses RECOVERY_RAMDISK instead of RECOVERY.
So you'd flash with fastboot flash recovery_ramdisk recovery.img
Make sure you're flashing a recovery for Oreo
Click to expand...
Click to collapse
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo

CommunalH said:
I flashed with it but when i opened the recovery mode he opened erecovery from huawei and i flashed twrp for oreo
Click to expand...
Click to collapse
Could you send me the recovery you're flashing?

ante0 said:
Could you send me the recovery you're flashing?
Click to expand...
Click to collapse
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3

CommunalH said:
When i tried to flash to oreo i downloaded a file named Hwota8, in there were the twrp named TWRP8_3.0.3
Click to expand...
Click to collapse
Good, that's the correct one
Can you boot to system?

ante0 said:
Good, that's the correct one
Can you boot to system?
Click to expand...
Click to collapse
I don't hace OS right now, options neither

CommunalH said:
I don't hace OS right now, options neither
Click to expand...
Click to collapse
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.

ante0 said:
What is your model of mate 9? (LxxCxxxBxxx)
I thought you should try to flash ramdisk and kernel as well, in case KERNEL partition is broken too it would probably go to erecovery (erecovery uses its own kernel.)
If you are on AL00 or C636 you can use dload right away. If not we'll have to find another way.
Click to expand...
Click to collapse
I don't know here to find my build number without OS, i know it's MHA-L09B

Question [RESOLVED] Cannot flash recovery - Partition/Volume full

So, I upgraded from MIUI 13 Stable to MIUI 14 Weekly today (clean flash via fastboot). What I hadn't realized is that my TWRP was still on A12, so TWRP couldn't read internal storage.
But when I tried to flash the A13 TWRP via Fastboot, I get this error:
Code:
Warning: skip copying recovery image avb footer (recovery partition size: 104857600, recovery image size: 201326592).
Sending 'recovery' (196608 KB) OKAY [ 6.370s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
So, somehow, my recovery partition is way too small (or it is just full? But I already erased the old TWRP, so currently I have no recovery)
And the only way I can boot into TWRP is to use the fastboot boot command to temporarily boot into it.
Is there a way to deal with this without doing a wipe?
EDIT: My dumbass was trying to flash the Boot version of TWRP instead of the Rec version

TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.

NOSS8 said:
TWRP
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Click to expand...
Click to collapse
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.

wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
Which img?

NOSS8 said:
Which img?
Click to expand...
Click to collapse
skkk's A13 TWRP image

wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Btw the error message I get after trying to 'flash current TWRP' is this:
Code:
cd /tmp/abrec/ && /system//bin/magiskboot repack -n /dev/block/bootdevice/by-name/recovey_a /tmp/abrec/rec_a.img process ended with ERROR: 1
Error repacking image.

wizpizz said:
Thanks for the reply, but I don't think the issue is related to fastboot since I can't flash the image in TWRP either.
Click to expand...
Click to collapse
And if I try to flash it via 'Install', I get:
Code:
size of image larger than target device

wizpizz said:
skkk's A13 TWRP image
Click to expand...
Click to collapse
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?

NOSS8 said:
Installing Twrp and rooting are two different things.
No need for Twrp to root.
Is it weekly stock rom or Xiaomi Eu rom?
Click to expand...
Click to collapse
I am such a moron lmao. I was trying to flash the Boot version of TWRP instead of the Rec version... Just flashed the Rec version and it works now. You made me check back on the TWRP thread, so thanks I guess ahah