Database Develop

Can't Flash Recovery

I'm on the T-Mobile variant and have followed the steps on the motorola website to unlock the bootloader. When I boot into fastboot, it says the device is unlocked with at status code 3. When I run 'fastboot flash recovery recovery.img' everything seems to run fine:
fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.930s​When I try to reboot into recovery mode it just shows me the warning that my bootloader is unlocked, then boots as normal. I don't know what to do. I've tried both the twrp and cwm recovery images. Any help?

what recovery did you flash?

waiflih said:
what recovery did you flash?
Click to expand...
Click to collapse
I've tried both the twrp and cwm recoveries that are available in the android development section.

You are replacing recovery.img with the actual file name right?
Sent from my Moto X.

mentose457 said:
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
Click to expand...
Click to collapse
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.

elijahah said:
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
Click to expand...
Click to collapse
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app

jayboyyyy said:
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
I'm already on 4.2.2. I'm guessing you mean to undo the recent OTA? How would I do that without a custom recovery or root?

Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X

flashallthetime said:
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
Click to expand...
Click to collapse
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.

elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.

elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7

mentose457 said:
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
Click to expand...
Click to collapse
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
phositadc said:
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
Click to expand...
Click to collapse
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.

elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7

elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Thanks for all your help though guys.
Click to expand...
Click to collapse
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.

mentose457 said:
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
Click to expand...
Click to collapse
I get this:
fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.071s​

Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.

elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
Excellent. Glad you got it working.

elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
PS you had recovery the first time you hit the up volume and it sent you to a screen that said "no command" from that screen if you press the up volume and power button together it sends you to the recovery screen. It may be down volume and power together to get passed that "no command" screen but its one of the two. I saw people having that same problem in the forum about maintaining root through the OTA.

phositadc said:
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
Click to expand...
Click to collapse
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.

leonardoafa said:
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
Click to expand...
Click to collapse
Will charge up a bit over 50% and see. I still get permission denied. Plus when I try to get into recovery, I can't. The Motorola log shows up for a while, then restarts and boots normally into Android.

[Q] TWRP fastboot boot problem

I have a VZW dev edition with unlocked bootloader and running 4.4.2. I would like to boot (not flash) into TWRP to install SuperSU so that I can keep the stock recovery installed, but I get this error in both mfastboot and the regular fastboot:
C:\platform-tools>fastboot boot twrp-2.6.3.1-ghost-4.4.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.953s
I'm running windows 8.1 and the unlocking process went without a problem.
It also doesn't work if I try: fastboot boot recovery twrp-2.6.3.1-ghost-4.4.img
Any ideas?
Thanks

Aeroman787 said:
I have a VZW dev edition with unlocked bootloader and running 4.4.2. I would like to boot (not flash) into TWRP to install SuperSU so that I can keep the stock recovery installed, but I get this error in both mfastboot and the regular fastboot:
C:\platform-tools>fastboot boot twrp-2.6.3.1-ghost-4.4.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.953s
I'm running windows 8.1 and the unlocking process went without a problem.
It also doesn't work if I try: fastboot boot recovery twrp-2.6.3.1-ghost-4.4.img
Any ideas?
Thanks
Click to expand...
Click to collapse
your trying this the hard way. power down phone
hold volume - and power till you get into the bootloader and then hit volume - till you highlight recovery then hit volume + and presto your in recovery.
enjoy

Aeroman787 said:
I have a VZW dev edition with unlocked bootloader and running 4.4.2. I would like to boot (not flash) into TWRP to install SuperSU so that I can keep the stock recovery installed, but I get this error in both mfastboot and the regular fastboot:
C:\platform-tools>fastboot boot twrp-2.6.3.1-ghost-4.4.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.953s
I'm running windows 8.1 and the unlocking process went without a problem.
It also doesn't work if I try: fastboot boot recovery twrp-2.6.3.1-ghost-4.4.img
Any ideas?
Thanks
Click to expand...
Click to collapse
Just flash TWRP, and you install root and SU and you're done. then reinstall stock recovery, seems like the simplest way to do it if what you tried is failing. Just don't forget you're rooted in case OTA comes your way.

The Moto X doesn't support booting just the recovery image like a Nexus device, unfortunately. All the posts I've read have indicated as such, yet to see anyone having successfully done so.
I'd do the same if I had a dev edition. I still don't understand why it doesn't support something so simple which should be available to any unlocked bootloader.

opps i did not understand what you was asking there is a simple way to do this.
Install TWRP with the mfastboot command then install SuperSU
then get the stock recovery img from the correct SBF zip and flash it also with the mfastboot command.
and presto root with stock recovery.

[Q] can't erase/flash custom recovery

I have non-dev Verizon Moto X 4.4.2 unlocked using the chinese method.
I'm in fastboot right now and it says "Device is UNLOCKED. Status Code: 3" if that means anything.
Every time I tried to flash TWRP and I reboot to recovery...it's still the stock android recovery.
I also tried to erase the stock recovery but i get this message:
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.094s
My motox is unlocked..so why doesn't it say permission denied and why can't i flash a custom recovery??
please help.
I'm not root btw.

Did you go into TWRP after flashing it?

You have to boot straight to recovery or it gets written over by the stock recovery

bigv5150 said:
You have to boot straight to recovery or it gets written over by the stock recovery
Click to expand...
Click to collapse
i thought i did but it boot straight into the OS instead of recovery...let me try again...
*edit*
ok wow i guess i didn't do it when i thought i did but i'm in TWRP now.
Thank you guys!

You probably hit the power button instead of volume+ the first time around.

[Q] Fastboot flash error - FAILED (remote: unknown command)

Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.

same here

Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825

neverdies said:
Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Click to expand...
Click to collapse
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP

jmang98 said:
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP
Click to expand...
Click to collapse
what steps have you done so far?
ie: unlock/root/flash recovery?

itsJohnuno said:
what steps have you done so far?
ie: unlock/root/flash recovery?
Click to expand...
Click to collapse
Same problem....

Did anyone who was having this problem end up finding a fix?

This is a problem I have too, need a fix.

Still need a solution. Is this due to lollipop? Cuz back then I was able to unlock the bootloader. LG L90 D415

BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
D405_v20a_patched_aboot??
http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
EDIT:
Did you flash D405_v20a_patched_aboot if not, you need to flash D405_v20a_patched_aboot

i also have same poblem d415

me too...same problem D415 tmobile version

Does anyone with this problem have an lg d-415 and android with root? Because I think these commands in a terminal emulator or in an adb shell will fix fastboot:
Code:
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Or if that doesn't work try this >> https://forum.xda-developers.com/lg...ick-hard-bricked-l90-variants-t3173429/page24
I think this problem is caused by people not unlocking the bootloader.

Same error on LG D415
BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.

aixhinnn said:
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.
Click to expand...
Click to collapse
How did you enable fastboot, what commands did you run?

0000.0000.00 said:
How did you enable fastboot, what commands did you run?
Click to expand...
Click to collapse
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.

aixhinnn said:
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.
Click to expand...
Click to collapse
Did you try volume down+ power to factory reset and see if that fixes it?

im having this problem too, but on an lg v10 tmobile

17mm said:
im having this problem too, but on an lg v10 tmobile
Click to expand...
Click to collapse
This problem is strange and I'm not sure if it has a solution.

0000.0000.00 said:
This problem is strange and I'm not sure if it has a solution.
Click to expand...
Click to collapse
what i did was get lg bridge and mobile support, let if flash the most current update then used this method to root on the latest 30c update https://forum.xda-developers.com/tm...901-nougat-t3773942/post76711778#post76711778
twrp flashed fine, magisk installed flawlessly, now rooted on latest official update with all kinds of goodies to play with :good:
oh and with magisk you pass safetynet aswell so all good.

Restore Stock Recovery - Amazon Fire 7 5th Gen (Ford)

IF YOU PLAN ON INSTALLING ANY CUSTOM ROM CHECK THAT YOUR RECOVERY IS ACCESSABLE!!!
If you have lost access to your stock recovery on your Amazon Fire 7 5th Gen (Ford) for whatever reason I would highly recommend restoring your recovery before doing any further customization to your device. Without recovery you have absolutely nothing to fall back on if your device becomes inoperable. If you have tried flashing any type of custom recovery directly to your device its more then likely you have lost access to your stock recovery. Hopefully youv made it to this thread before it was too late and luckily its a pretty simple process to restore your access.
Before we begin you must have a working OS for this process to work. If your device will not successfully boot then you can not complete the steps necessary to restore access to your recovery.
First lets
• Download Fire 7 Stock Recovery Image https://app.box.com/s/tjju5dptvsmsfjienf37siip8j6ch7wo
• Download and install the Flashfire App http://download.chainfire.eu/950/FlashFire/FlashFire-v0.30-20160331135212.apk
Next we'll
• Open the Flashfire App and allow it root access
• Press the red "+" button and select "Flash Firmware Package"
• Browse to the folder containing the Fire 7 Stock Recovery Image you previously downloaded and select it then press the "√" in the upper right corner
• Change Reboot option from "Normal" to "Recovery"
• Press the "FLASH" then "OK"
• Flashfire will reboot into recovery when its complete (Usually only takes a couple mins but its possible it may run for more)
It is also possible to restore access to recovery using Flashify
• Download and install Flashify
http://www.apkmirror.com/apk/christian-gollner/flashify/
• Press "Select Recovery Image" then choose file
• Browse to the Fire 7 Stock Recovery Image you downloaded earlier, select it and choose "Yup"
• Once complete reboot to recovery to confirm
That's it now you're back in action!!!

Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs

sd_shadow said:
Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Thought about that this morning as well. If no one else confirms before I get off work here shortly I will try then. (Especially like to see someone with a hard brick attempt it) In theory it seems it should work since the image seems to carry the signature from Amazon. Well at least that's what I picked up from researching for a fix to restore access to recovery on two of my fires.

Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
Click to expand...
Click to collapse
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse

knicknut said:
Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs

sd_shadow said:
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse

knicknut said:
used ?
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse
yes, my bad
Sent from my XT1080 using XDA Labs

Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?

vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
Unfortunately I don't believe so. We need a key to unlock the actual ability to flash via Fastboot. As far as I know at least

vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
I suspect that capability is coming (foundation is in v0.32) but probably not for this device due to fastboot restrictions I posed by Amazon.

Sorry cross posted removed

Robin Son said:
stuck with 5.1 will not boot to stock recovery
was going to try using fastboot with 5.3.1 stock img.file but can't find one
TGT123 super tool will reboot my A-fire but will not install stock recovery
O yeah and i lost root and no playstore
Anyone had this problem and fixed???
Click to expand...
Click to collapse
Please don't cross post. Answered here: http://forum.xda-developers.com/ama...stom-rom-fireos-5-3-1-0-t3418541/post70006008