Restore Stock Recovery - Amazon Fire 7 5th Gen (Ford) - Fire Q&A, Help & Troubleshooting

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

Related

[Q] Signature failed in restore recovery

hi, i had the frf91 vodafone version on my nexus one. i thougth to install the frg83d posted here with rom manager. Everything went fine but the installation didn't restore the recovery and if i try to flash it with fastboot:
C:\android\tools>fastboot devices
HT05EP800252 fastboot
C:\android\tools>fastboot flash recovery recovery.img
sending 'recovery' (2294 KB)... OKAY [ 0.344s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.734s
am i doing something wrong?
is it because i'm rooted? i rooted my N1 without unlocking the bootloader.
Thanks
I dont think you can use fastboot to flash the recovery image without unlocking, you need to install the appropriate binary (/system/bin/flash_image) and call it from a shell on your phone (using a desktop is ok)
see http://forum.xda-developers.com/showthread.php?t=687280
http://www.droidforums.net/forum/dr...covery-framework-res-apk-custom-boot-ani.html
I would also say you lost root when updating your ROM. Also, you can't fastboot flash unofficial files without unlocking the bootloader.
Root, and flash through adb or ROM Manager, etc
Sent from my Nexus One using XDA App

[Q] Can't Flash ClockWorkMod Recovery

I have a Streak 7 (unlocked WiFi + 3G/4G) with Stock Honeycomb. I previously Rooted it and had CWM Recovery installed (not sure which version, but I think it was 5.something). Somehow, I seem to have reverted to the stock recovery. I don't know how this happened, but I noticed it first when I tried to make a backup last week. I have tried several times to flash CWM recovery (both versions 5.0.2.7 and 5.0.2.8) but I keep getting the stock recovery when I boot to recovery. Otherwise, everything seems to operate normally.
I use fastboot to flash recovery and get the following:
C:\Android ADB Streak\Streak\Win32>fastboot flash recovery recovery.img
sending 'recovery' (4402 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 1.355s]
finished. total time: 1.863s
On the Streak screen, I see:
Starting Fastboot USB Download Protocol
Flashing StorMgr partition recovery
Read after write partition recovery
then I reboot the Streak:
C:\Android ADB Streak\Streak\Win32>fastboot reboot
rebooting...
finished. total time: 0.002s
But when I boot into recovery, I get the stock recovery. Am I doing something wrong?
wdwray said:
I have a Streak 7 (unlocked WiFi + 3G/4G) with Stock Honeycomb. I previously Rooted it and had CWM Recovery installed (not sure which version, but I think it was 5.something). Somehow, I seem to have reverted to the stock recovery. I don't know how this happened, but I noticed it first when I tried to make a backup last week. I have tried several times to flash CWM recovery (both versions 5.0.2.7 and 5.0.2.8) but I keep getting the stock recovery when I boot to recovery. Otherwise, everything seems to operate normally.
I use fastboot to flash recovery and get the following:
C:\Android ADB Streak\Streak\Win32>fastboot flash recovery recovery.img
sending 'recovery' (4402 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 1.355s]
finished. total time: 1.863s
On the Streak screen, I see:
Starting Fastboot USB Download Protocol
Flashing StorMgr partition recovery
Read after write partition recovery
then I reboot the Streak:
C:\Android ADB Streak\Streak\Win32>fastboot reboot
rebooting...
finished. total time: 0.002s
But when I boot into recovery, I get the stock recovery. Am I doing something wrong?
Click to expand...
Click to collapse
You press/hold +Vol button, press/hold the power button till the menu comes up. You then select option #2 and press the power button. That will take into CWM.
Thanks. I feel like a clone:cyclops:; I forgot about selecting option 2. Although it would be helpful if each Android device didn't have a different way of getting to Recovery.
Thank you very much .... But when I select option 2 "install update .... " my device freeeze on boot !!!!!!!!!!
Can you give me a solution please .. thanks
kdultimate said:
Thank you very much .... But when I select option 2 "install update .... " my device freeeze on boot !!!!!!!!!!
Can you give me a solution please .. thanks
Click to expand...
Click to collapse
You've flashed the CWM via Fastboot and your trying to boot into it now?
I would make sure you are at least 60% charge first.
Yes .... Exactly i flashed cwm via fastboot ... Writing recovery ok ... But when i tried to enter " the device freeze on install update package and i cannot make anything... Thanks
kdultimate said:
Yes .... Exactly i flashed cwm via fastboot ... Writing recovery ok ... But when i tried to enter " the device freeze on install update package and i cannot make anything... Thanks
Click to expand...
Click to collapse
There are a few different CWM versions, so it's possible that you used a version not compatiable with your ROM.
The same was happening to my streak but i installed version 3.0.x.x and it worked with that one
Sent from my LG-P999 using xda app-developers app

[Q] soft bricked verizon non-dev moto x

I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2635366
slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
Are you still able to enter the Bootloader menu?
jpd_ said:
Are you still able to enter the Bootloader menu?
Click to expand...
Click to collapse
yes, I just cant boot into recovery or android.
slappydj1 said:
yes, I just cant boot into recovery or android.
Click to expand...
Click to collapse
Go ahead and flash the stock recovery img then follow the instructions from here:
http://forum.xda-developers.com/showthread.php?t=2639102
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Very helpful link here as well on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=2603358
If you made a back up through TWRP, you can try restoring your phone from there too.
jpd_ said:
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Click to expand...
Click to collapse
The Verizon OTA is out. That is what got him in the situation he is in.
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
They generally seem to show up 1 week to 1 month from when the OTA is released.
slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.
Cozume said:
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.
Click to expand...
Click to collapse
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
slappydj1 said:
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?
Cozume said:
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?
Click to expand...
Click to collapse
I tried to boot into recovery using the fastboot menu on the phone.
slappydj1 said:
I tried to boot into recovery using the fastboot menu on the phone.
Click to expand...
Click to collapse
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?
Cozume said:
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?
Click to expand...
Click to collapse
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
slappydj1 said:
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
Click to expand...
Click to collapse
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.
Cozume said:
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.
Click to expand...
Click to collapse
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
slappydj1 said:
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?
Cozume said:
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?
Click to expand...
Click to collapse
So Ill have to wait until the factory image is released?
slappydj1 said:
So Ill have to wait until the factory image is released?
Click to expand...
Click to collapse
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.
Cozume said:
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.
Click to expand...
Click to collapse
I was going to do a factory reset using fastboot, and I flashed the gpt.bin. after that I could not flash anything. Later I learned that wasnt the factory image but the OTA update, so I realized I messed up then.

Fastboot failed

When I try:
fastboot boot recovery.img
I only get this and it wont boot into the Cyanogen Recovery :/
downloading 'boot.img'...
OKAY [ 0.217s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.221s
Any idea what I can do?
Check to see what Fire OS version you have. If it is 5.11 then booting a custom recovery will not work til a new custom boot.img can be created for it.
tuckerwagner said:
When I try:
fastboot boot recovery.img
I only get this and it wont boot into the Cyanogen Recovery :/
downloading 'boot.img'...
OKAY [ 0.217s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.221s
Any idea what I can do?
Click to expand...
Click to collapse
As far as I know you can only do temporary recovery boots (either twerp or Cyanogen) using a PC to push the recovery image and then boot it.
Code:
adb reboot bootloader
fastboot TWRP_Fire_2.8.7.0.img
Is what works for me.
same problem. Any way to downgrade?
skola28 said:
same problem. Any way to downgrade?
Click to expand...
Click to collapse
Same here... Bought two, got one to work and I think my girlfriend let the other update and now I am getting the "FAILED (remote: unknown command)" on the other.....
Ugh, time to look at Amazon's return policy?
skola28 said:
same problem. Any way to downgrade?
Click to expand...
Click to collapse
If on 5.1.1, at this time,
cannot root
cannot boot custom recovery
cannot downgrade
once a the update.zip is captured, maybe a new twrp can be built
RW2112 said:
Check to see what Fire OS version you have. If it is 5.11 then booting a custom recovery will not work til a new custom boot.img can be created for it.
Click to expand...
Click to collapse
Turns out it is 5.1.1. I guess I will wait for a new boot.IMG unless there is a way to downgrade. Thanks for your help!

I think I soft bricked my phone. flashing "no command"

I've got a moto x '14 verizon XT1096. Tried to use fastboot to load twrp to eventually get to install Cm13. However, it threw this message:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.006s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.024s
Dumbass me thought it would be a good idea to unplug the device and simply try again. Well, what a bad decision. The phone now flashes the "no command" robot on it's back. yes, flashes. i can get back to fastboot, but after this i'm not sure what to do.
Thanks in advance. I'm fairly new at this, be easy on me.
Try this. This is my mini guide I wrote in another thread.
Well, at first I tried to flash twrp through fastboot but the original recovery override the twrp recovery.
So, what I did, instead of flashing, I just temporary booted into twrp.
adb reboot bootloader
fastboot boot twrp.img (and not fastboot flash recovery twrp.img)
Then phone booted into twrp, I flash supersu 2.46.
Then I easily downloaded twrp manager from google play and installed twrp recovery to my xt1096.
Have fun
Use this https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse

Categories

Resources