This will only work with system versions 5.0.X , will not work with Fire tablets on System version 5.1.1or higher
Required
PC/Mac/Linux although I will only cover PC
Can ADB/Fastboot be used on Linux and Mac?
You will need a way to copy Stock Firmware file to a SD Card
You will need a few files
Drivers
Stock Firmware
update-kindle-37.5.2.2_user_522054520.bin.zip - AFH -
Custom recovery I used Twrp
UPDATE-SuperSU-v2.46.zip if you want to root
Open Gapps zip if you want Google Services (I suggest ARM/5.1/pico)
Instructions
Install Drivers
Change Stock Firmware file extension from .bin to .zip
Copy Stock firmware to sd card
Insert SD Card in the KFFOWI/Ford
Boot to Fastboot Mode
Boot Custom Recovery
In Custom Recovery, Install Firmware.zip, SuperSU.zip, GApps.zip
Reboot
I covered most of these steps in
2015 Fire: Booting TWRP, Rooting, Installing Gapps with Video
Tomsgt Video also covers most of this using Amazon-Fire-5th-Gen-SuperTool.zip in
How to install CM12.1 rom on the Amazon Fire 5th gen
Note: I have tested this method by
Installing CM12.1, Booting cm12.1, Factory Reset in twrp, Rebooted, Installed Stock Firmware (nothing extra), Booted Stock Rom. It is possible that this method does not restore everything or reflash all partitions, but everything appears to work correctly.
Alt method: using Stock Recovery
If you do not have a way to get the Firmware file to the SD Card
try [HOWTO] How to restore firmware on your device + Amazon Firmware by Awesomeslayerg
[Video]How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tabletor
If you have a pc but not a sd card reader, you can try
adb sideload with
Cyanogen Recovery (2015-11-04) by ggow
If you don't have a pc, you can try
[Guide][Script]Fire Mobile Boot Helper - Boot imgs without your PC using android! by Harry44
Error: E: Cannot restore System -- mounted read only
If you see this trying to restore a nandroid backup, I just install the official firmware (plus SuperSu and GApps) then just restore the data from the back up
sd_shadow said:
Error: E: Cannot restore System -- mounted read only
If you see this trying to restore a nandroid backup, I just install the official firmware (plus SuperSu and GApps) then just restore the data from the back up
Click to expand...
Click to collapse
awesome write up buddy love it. you are all over this device thats for sure
Can I perform a full, stock recovery on 5.1.1?
I lost some stock Amazon apps (launcher, Amazon Video) during Root using AutoRootScriptFirev4.12.
I have used ADB to restore the 5.1.1 Update but it returns still missing the apps deleted during Root and no Launcher.
Both factory reset & sideloading the 5.1.1 Bin restore my tablet still with missing components.
Is 5.1.1. only an update and not the full restore?
ArmandSalmon said:
Can I perform a full, stock recovery on 5.1.1?
I lost some stock Amazon apps (launcher, Amazon Video) during Root using AutoRootScriptFirev4.12.
I have used ADB to restore the 5.1.1 Update but it returns still missing the apps deleted during Root and no Launcher.
Both factory reset & sideloading the 5.1.1 Bin restore my tablet still with missing components.
Is 5.1.1. only an update and not the full restore?
Click to expand...
Click to collapse
I think there isn't any way on 5.1.1 bud
Sent from my KFFOWI using Tapatalk
plase hlep me dump backup emmc
i need dump 1G or 4G, please root and dump file,
adb shell su -c " dd if=/dev/block/mmcblk0 of=/sdcard/fire.img bs=1024 count=4194304"
Please have a few questions please, I hope not bother anyone
sd_shadow said:
Error: E: Cannot restore System -- mounted read only
If you see this trying to restore a nandroid backup, I just install the official firmware (plus SuperSu and GApps) then just restore the data from the back up
Click to expand...
Click to collapse
hi Please have a few questions please, I hope not bother anyone, I have two kindles 5th gen 5.1.1 full root, block OTA upgrade and install nova all with supetool then I try to install CM12 With flash fire apk but i got stuck in CyanogenMod logo, my pc recognizes mtp as fire and adb and fastboot working perfect but I can not boot intro stock recovery in any way, when I try to enter to stock recovery fire gets stuck in (amazon logo) forever and when I type (adb devices) adb show fire as fastboot device, I do not understand, is there any way to fix this?
jonathanjr321 said:
hi Please have a few questions please, I hope not bother anyone, I have two kindles 5th gen 5.1.1 full root, block OTA upgrade and install nova all with supetool then I try to install CM12 With flash fire apk but i got stuck in CyanogenMod logo, my pc recognizes mtp as fire and adb and fastboot working perfect but I can not boot intro stock recovery in any way, when I try to enter to stock recovery fire gets stuck in (amazon logo) forever and when I type (adb devices) adb show fire as fastboot device, I do not understand, is there any way to fix this?
Click to expand...
Click to collapse
did you try
fastboot.exe oem reboot-recovery
Sent from my Motorola XT1060 using XDA Labs
Yep keep stuck in (amazon logo forever) and when i tipe adb devices keep showing fire as fastboot devices, I read all your recommendations all very good to be honest with u and thanks to u and root jonky have two fires 5.0.1 With CM12 working well,thanks u all!!!
jonathanjr321 said:
Yep keep stuck in (amazon logo forever) and when i tipe adb devices keep showing fire as fastboot devices, I read all your recommendations all very good to be honest with u and thanks to u and root jonky have two fires 5.0.1 With CM12 working well,thanks u all!!!
Click to expand...
Click to collapse
if you can't get to recovery, there is no known fix
Sent from my Motorola XT1060 using XDA Labs
THANKS
sd_shadow said:
if you can't get to recovery, there is no known fix
Sent from my Motorola XT1060 using XDA Labs
Click to expand...
Click to collapse
is ok, thanks to u guys I know u all working hard here that helped me to get a lot experience
I tried to install TWRP. It won't boot into TWRP. Nor will it boot into stock recovery. All I am able to do is get it to FASTBOOT mode. I current'y have Slim rom on it. It stopped loading as well. It just sits there with the Slim logo rotating. Any help will be great.
musiqlives said:
I tried to install TWRP. It won't boot into TWRP. Nor will it boot into stock recovery. All I am able to do is get it to FASTBOOT mode. I current'y have Slim rom on it. It stopped loading as well. It just sits there with the Slim logo rotating. Any help will be great.
Click to expand...
Click to collapse
if it won't boot to stock recovery, there is no fixing
I installed the OS from Amazon OS 5.1.2 to Android 5.1.1. (Lollipop). It worked a few days and started intermittently working sensor and I decided to reinstall another Android 5.1.1. After reinstalling the tablet does not turn on. Then I went in fastboot and through ADB installed Amazon OS 5.1.1.
The result: the tablet when turn on does not show screen AMAZON, that is does not react to pressing the power button. When connected to the computer constantly appears and disappears "PreLoader USB VCOM Port".
Tell me, please, how can I restore the tablet after that?
[email protected] said:
I installed the OS from Amazon OS 5.1.2 to Android 5.1.1. (Lollipop). It worked a few days and started intermittently working sensor and I decided to reinstall another Android 5.1.1. After reinstalling the tablet does not turn on. Then I went in fastboot and through ADB installed Amazon OS 5.1.1.
The result: the tablet when turn on does not show screen AMAZON, that is does not react to pressing the power button. When connected to the computer constantly appears and disappears "PreLoader USB VCOM Port".
Tell me, please, how can I restore the tablet after that?
Click to expand...
Click to collapse
i have the same problem. So far the only fix is to order a used motherboard on the web and hope it isn't bricked. Amazon should really release a program to return the device to stock from the PreLoader USB-MTP mode.
There is this thread for the possible solution:
https://forum.xda-developers.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747/
goldenpipes said:
Amazon should really release a program to return the device to stock from the PreLoader USB-MTP mode.
Click to expand...
Click to collapse
Amazon has a generous 'no questions asked' exchange policy during the warranty period which runs 90 days to 2 years depending on model and region. Device is not intended for enthusiasts as evidenced by aggressive lockdowns. Why would any company in their right mind release such a tool given the target audience?
Bricked my tablet but I'm able to boot into fastboot mode
Hello,
I have just softbricked my tablet because the wrong OpenGapps were flashing.
The problem is I can't start a custom recovery because the boot loader is too new
And I can't access my stock recovery because I've tried flashing TWRP from it in the past.
What can I do now? As I said earlier, I can access the device using Fastboot commands, but I don't know how to get at least one ADB interface working on the tablet so that I can upload the stock image to the device.
Thanks for any help!
TheGoliath said:
Hi,
I just softbricked my tablet 'cause of flashing wrong gapps?
The problem is, that I can't boot into a custom recovery (bootloader to new)
And I can't access my stock recovery because I tried to flash TWRP over it in the past.
So what can I do now? As I said, I'm able to access the device with fastboot commands but I don't know, how to get at least a adb interface running on the tablet so I can sideload the stock image.
Many thanks for any help!
Click to expand...
Click to collapse
You will not be able to reload stock FireOS from fastboot as the necessary commands have been disabled by Amazon. Pretty much game over if you can not access stock recovery and bootloader version is >5.0.x.
Can you describe "softbricked" symptoms in more detail? At what point during boot process does device hang/loop?
Davey126 said:
You will not be able to reload stock FireOS from fastboot as the necessary commands have been disabled by Amazon. Pretty much game over if you can not access stock recovery and bootloader version is >5.0.x.
Can you describe "softbricked" symptoms in more detail? At what point during boot process does device hang/loop?
Click to expand...
Click to collapse
OK. So I wanted to install the new Fire Nexus Rom and I may have installed the wrong package or something, but the symptoms are the following:
When I press the power switch, it turns on. Then the Amazon logo appears and after about 10 seconds the screen goes black again. The whole thing then repeats itself in a boot loop
i flashed stock update-kindle-37.5.2.2_user_522054520.
following a link in the forums
had to do it for pokemon
can i just flash any newer version as well this way or will ability to fastboot boot twrp then be gone?
thanks for any help
hello:
i think i have totally break my shield tv, just with one line!! fastboot oem lock!
before i have totaly functional shield tv with custom rom, beautiful kodi all channel, all game, all movie, all music..
last night i read a littler book and in one moment my tv stop, and i hard restart but all it's break kody and other apps android so i decided to fix that!
i try to change rom with system.img and vendor.img (oem unlock working great)
but when i try flash vendor.img doesn't work and android doesn't lunch so i remember i have the same problem before so i try "fastboot oem lock", it's work so i try after "fastboot oem unlock" doesn't work "my device cannot be unlock"...i try all things....i have not acces in twrp because i flash recovery with official rom (it's work) but i have black screen for recovery....
and for android, i have just logo nvidia!!!
what's **** with google tv...
If you have fastboot working, you can boot TWRP by putting your Shield in bootloader mode:
Power off the Shield
Plug the microUSB cable into the Shield and your computer
Hold the Shield's power button until the bootloader menu appears
Then go to the directory where your TWRP image is stored, open a command prompt and enter "fastboot boot twrp-20160222-UNOFFICIAL-foster for M.img". The exact command will depend on the name of your TWRP image, of course. If all of this works, then you should be able to flash the stock ROM or a custom ROM.
Shield has Android TV 2017
I am following this process and the shield is not working.
—–
fastboot oem unlock
twrp boot (fail)
Infinite reboot
(controller a,b key pushing
power cable in)
hw mode bootloader connect to pc
(pc recovery img “fastboot-all.bat” Execution)
error devices not connect after install 2 things finished
—
shield tv Does not wake from sleep mode
pc to connect (pc devices manager display others-apx)
hw mode is not working
How can I recover it?
If your shield TV doesn't boot correctly, fastboot-all.bat won't work because you need to have adb working.
You should indeed rather follow the instructions given on Nvidia website, i.e. for Shield TV 2015 16GB with Marshmallow or newer installed:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Before that, be sure you use a good quality USB OTG cable.
Sounds like you can't boot into fastboot or bootloader mode.
If you can't, it means that you are hard bricked.
If you already had latest Nvidia experience version 5.1, there was no need to reflash the whole recovery image, PLUS you don't mention what recovery image you flashed.
To sum up your error was eather a bad usb cable (this a very known issue now, shield is picky) AND/OR wrong blob (which is the bootloader and it comes in all nvidia recovery image packages) flash.
What makes the device brick is a corrupted bootloader.
If bad USB and fail while flashing blob (which again is the bootloader), it gets corrupted.
If wrong blob flash (by using one that is not for you device model OR when attempting to downgrade to MM or lower bootloader), it gets corrupted.
Moral of the story:
Never mess with the bootloader a.k.a blob if you dont know what you're doing.
I know there are many hard bricked users around so better start reading. Take your time and make sure you understand all the instructions and also the pros and cons of the restore/unbrick method.
NOTE: just so you know next time for Shield TV 2017 , when you unlock bootloader and flash TWRP recovery or custom firmware you must root, because root with SuperSU disables some checks Nvidia run at boot. If you don't root, then your Shield will be stuck at boot.
- Sent from my Tapatalk Hub -
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
Hello. I have a Fire HD 8 which was rooted and I tried flashing twrp recovery onto it so to make the long story short the recovery (volume down + power) is stuck in a gray amazon logo screen and in normal mode it's a loop of the orange fire screen. Also I've installed all the drivers in my pc and have adb installed as well as the Kindle FIre Unbrick Utility which says there is no device.
carlm3 said:
Hello. I have a Fire HD 8 which was rooted and I tried flashing twrp recovery onto it so to make the long story short the recovery (volume down + power) is stuck in a gray amazon logo screen and in normal mode it's a loop of the orange fire screen. Also I've installed all the drivers in my pc and have adb installed as well as the Kindle FIre Unbrick Utility which says there is no device.
Click to expand...
Click to collapse
Any Hope to fixing this Fire HD 8? or do I have to trash it? Thank you.
carlm3 said:
Hello. I have a Fire HD 8 which was rooted and I tried flashing twrp recovery onto it so to make the long story short the recovery (volume down + power) is stuck in a gray amazon logo screen and in normal mode it's a loop of the orange fire screen. Also I've installed all the drivers in my pc and have adb installed as well as the Kindle FIre Unbrick Utility which says there is no device.
Click to expand...
Click to collapse
carlm3 said:
Any Hope to fixing this Fire HD 8? or do I have to trash it? Thank you.
Click to expand...
Click to collapse
Sounds like you wiped your recovery, as booting to the orange logo usually means a soft brick (which is fixable via flashing firmware in recovery).
In this case, with no recovery, it'll be a bit more tricky, as you'll likely need to take the device apart. Try following the method below:
https://forum.xda-developers.com/showpost.php?p=80287339&postcount=154
You'll also end up with TWRP if you follow the above method.
Note: It may be possible to flash a stock recovery image in Fastboot, but I am not sure?
Kctucka said:
Sounds like you wiped your recovery, as booting to the orange logo usually means a soft brick (which is fixable via flashing firmware in recovery).
In this case, with no recovery, it'll be a bit more tricky, as you'll likely need to take the device apart. Try following the method below:
https://forum.xda-developers.com/showpost.php?p=80287339&postcount=154
You'll also end up with TWRP if you follow the above method.
Note: It may be possible to flash a stock recovery image in Fastboot, but I am not sure?
Click to expand...
Click to collapse
Correct my recovery is gone. Is there any way I could recover using software without opening the device?
For example for Samsung devices there is a Odin Flashing Software. But is there any amazon flashing software that I could reload everything including recovery? Thanks for your answer also
carlm3 said:
Correct my recovery is gone. Is there any way I could recover using software without opening the device?
For example for Samsung devices there is a Odin Flashing Software. But is there any amazon flashing software that I could reload everything including recovery? Thanks for your answer also
Click to expand...
Click to collapse
I don't believe there is any recovery software for these.
Opening the device shouldn't be too bad, and is probably your best bet.
The other option is to try and flash a recovery image via Fastboot. That's how I'd do it on other devices, but i'm not sure how it'll work on the Fire without hacked fastboot. See attached zip I took from the Unlock thread. One of the files in there is the recovery image.
Kctucka said:
I don't believe there is any recovery software for these.
Opening the device shouldn't be too bad, and is probably your best bet.
The other option is to try and flash a recovery image via Fastboot. That's how I'd do it on other devices, but i'm not sure how it'll work on the Fire without hacked fastboot. See attached zip I took from the Unlock thread. One of the files in there is the recovery image.
Click to expand...
Click to collapse
Thanks, I'll try. If it helps, here is a picture which could explain the issue a little better.
Picture of Fire Tablet Errors on PC
Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!
Hello, I have exactly the same issue.
I would be really grateful if someone could help us.
i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv
Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(
what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea
Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.
i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC