Related
I made some changes to the build.prop and rebooted, and now it gets stuck at the Kindle Fire boot animation. I can't get it to boot into safe mode either. Is there a way to unbrick or restore it without a factory cable? I can't get it to show up with adb.
If there's no way, I could probably make a factory cable, but it would be nice to fix it without having to do that.
FroyoShark said:
I made some changes to the build.prop and rebooted, and now it gets stuck at the Kindle Fire boot animation. I can't get it to boot into safe mode either. Is there a way to unbrick or restore it without a factory cable? I can't get it to show up with adb.
If there's no way, I could probably make a factory cable, but it would be nice to fix it without having to do that.
Click to expand...
Click to collapse
Yes there is a way to get the 8.9 into fastboot so you can restore it without a factory cable, as a factory cable does not work on this device.
Power down the device and unplug
Open a cmd prompt where you have access to the fastboot script from SDK
Enter this command (or any fastboot cmd as long as you include [-i 0x1949]:
Code:
fastboot -i 0x1949 getvar product
It will say "waiting for device"
Plug in the device and it will automatically boot into fastboot.
I have confirmed this works works when the device is in a loop and adb is not recognized. This does not work on the other models, a factory cable is required. Once in fastboot you can flash a backup image. I will be posting an update to the KFHD SRTool in the development section this morning to include 8.9" version
onemeila said:
Yes there is a way to get the 8.9 into fastboot so it can you can restore it without a factory cable.
Power down the device and unplug the device.
Open a cmd prompt where you have access to the fastboot script from SDK
Enter this command:
Code:
fastboot -i 0x1949 getvar product
Actually any fastboot command works
It will say "waiting for device"
Plug in the device and it will automatically boot into fastboot.
I have confirmed this works works when the device is in a loop and adb is not recognized. This does not work on the other models, a factory cable is required. Once in fastboot you can flash a backup image. I will be posting an update to the KFHD SRTool in the development section this morning to include 8.9" version
Click to expand...
Click to collapse
Tried that... The command you said just shows the help list, if I do a different fastboot command it says waiting for device and then the Kindle boots normally and gets stuck at boot animation like usual.
FroyoShark said:
Tried that... The command you said just shows the help list, if I do a different fastboot command it says waiting for device and then the Kindle boots normally and gets stuck at boot animation like usual.
Click to expand...
Click to collapse
Are you sure you typed that command correctly because the help menu comes up if a command is entered wrong, I just did it and it worked fine. When you enter a fastboot command for this device it has to have the- [-i 0x1949] after fastboot, that is a zero not an O. If that is not done it will boot normally
ie:
fastboot -i 0x1949 [command]
I've posted the update for the 8.9 restore tool in development section
It could be because I have an older version of fastboot. Any chance you could upload the newest version for me?
FroyoShark said:
It could be because I have an older version of fastboot. Any chance you could upload the newest version for me?
Click to expand...
Click to collapse
Here you go:
https://docs.google.com/folder/d/0B4lZEJI5lYeMdzJobG5jSk9QSEk/edit
If you need to restore the system image though, you should just download the KFHD_SRTool from development section for 8.9 and follow the instructions. It has fastboot included in the tool.
I've done the same thing with my kindle fire hd 7 (7.2.2 rooted, no TWRP), now its just stuck on the boot animation.
adb does not recognize the device. I tried using fastboot, (with the normal usb cable), it gets stuck with the '<waiting for device>' message.
The device manager does show the Kindle, but earlier it used to show 2 devices, a kindle and an adb composite
Were you ultimately able to solve this issue?
rogue07 said:
I've done the same thing with my kindle fire hd 7 (7.2.2 rooted, no TWRP), now its just stuck on the boot animation.
adb does not recognize the device. I tried using fastboot, (with the normal usb cable), it gets stuck with the '<waiting for device>' message.
The device manager does show the Kindle, but earlier it used to show 2 devices, a kindle and an adb composite
Were you ultimately able to solve this issue?
Click to expand...
Click to collapse
Turns out, it was a driver issue. Installed the proper Amazon driver, then it was detected by the adb. From there on, I was able to replace the bad build.prop with my backup
onemeila said:
Yes there is a way to get the 8.9 into fastboot so you can restore it without a factory cable, as a factory cable does not work on this device. <snip>
Click to expand...
Click to collapse
My Kindle Fire 8.9" SW v.8.1.4 is completely dark and unresponsive as the result of an unsuccessful attempt to root using KF utility 0.9.6. I suspect results would have been different if I'd had the sense to locate your tool and use it instead. Having downloaded KFHD for v8.1.4, I have tried to get the tool talking with the brick, and see only < waiting for device > eternally. I have charged overnight, held the power button down for >20 sec. to make sure the device was off, then bumped the power button. This should assure that the device is on, but in Amazon's wisdom there are no LEDs to confirm this. Do you have any suggestions for getting the device in a communicative state? I am perfectly willing to open the case. Please forgive the post if this is not the right thread for it, and point me to the right spot if you can.
Same problem: KF 8.9" completely dead
jimbobboy said:
My Kindle Fire 8.9" SW v.8.1.4 is completely dark and unresponsive as the result of an unsuccessful attempt to root using KF utility 0.9.6. .
Click to expand...
Click to collapse
I have exactly the same problem. This KFU-version seems to be a real KF 8.9"-killer.
My device does not respond to anything, regardless what I tried. Connecting to a PC does not trigger any response. The device is not recognized by the PC in any way. I believe that there is no USB-communication at all. I tried a factory-mode cable and this didn't work, too.
Any help would be appreciated, really!
Thanks and regards
Conny
onemeila said:
Yes there is a way to get the 8.9 into fastboot so you can restore it without a factory cable, as a factory cable does not work on this device.
Power down the device and unplug
Open a cmd prompt where you have access to the fastboot script from SDK
Enter this command (or any fastboot cmd as long as you include [-i 0x1949]:
Code:
fastboot -i 0x1949 getvar product
It will say "waiting for device"
Plug in the device and it will automatically boot into fastboot.
I have confirmed this works works when the device is in a loop and adb is not recognized. This does not work on the other models, a factory cable is required. Once in fastboot you can flash a backup image. I will be posting an update to the KFHD SRTool in the development section this morning to include 8.9" version
Click to expand...
Click to collapse
OMG, man. You just saved my ass. Thank you SO MUCH for that info. I threw a "thanks" your way for that one. If I had some ebay money in my paypal I would've even donated I'm so happy. Thanks again. you made my day!
jimbobboy said:
My Kindle Fire 8.9" SW v.8.1.4 is completely dark and unresponsive as the result of an unsuccessful attempt to root using KF utility 0.9.6. I suspect results would have been different if I'd had the sense to locate your tool and use it instead. Having downloaded KFHD for v8.1.4, I have tried to get the tool talking with the brick, and see only < waiting for device > eternally. I have charged overnight, held the power button down for >20 sec. to make sure the device was off, then bumped the power button. This should assure that the device is on, but in Amazon's wisdom there are no LEDs to confirm this. Do you have any suggestions for getting the device in a communicative state? I am perfectly willing to open the case. Please forgive the post if this is not the right thread for it, and point me to the right spot if you can.
Click to expand...
Click to collapse
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Another one bites the dust...but hopefully not
Hi guys,
I tried the KFFirstAide tool to root my Fire 8.9, but after it ran, it just wipes red and then goes to the fastboot screen after powering up. I've used the KFHD SRT tool to replaced the system.img file, but still the same thing happens. Is it possibly because I need to restore the boot.img and recovery.img (which KFFirstAide overwrites) as well? And if so, does someone have a clean copy of those that will work with 8.1.4? Thanks!
George
KFHD_SRT
anyone have a working link for KFHD_SRT? i can get into TWRP and into fastboot mode, but simply trying to boot results in a black screen after the blue kindlefire logo
Wait don't do it!
Slimepuppy said:
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Click to expand...
Click to collapse
I hope you didn't swap motherboards... Like user onemeila stated, you do not need a fastboot cable on the Kindle Fire HD 8.9. Just make sure that before you enter the command "fastboot -i 0x1949 getvar product" that your Kindle is off and plug into the factory cable. Enter the command and wait for the message <wating for device>. Then turn on your kindle and you should boot into fastboot mode. If you see the fastboot screen on your kindle and Jem-PVT-Prod-04 in the command terminal, there is hope. The only problem I encountered is after each command, sometime it won't respond. So you might have to do one command, let it finish it's process. If the next one doesn't work, turn off the kindle enter "fastboot -i 0x1949 getvar product" command. Turn on the kindle and proceed with the next command to restore your kindle.
The way the device is setup, it's very hard to completely ruin the device.
Also read this page for reference by hashcode http://forum.xda-developers.com/showthread.php?t=2128175 and make sure to thank him. He helped me get my device going no problem. The top and bottom of the page should apply to you. If you need additional help let me know.
Slimepuppy said:
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Click to expand...
Click to collapse
You are pretty much screwed. Sorry to tell you. You've flashed over the bootloader, the problem is with one that doesn't work. So your device won't even boot into fastboot no matter what you do. There was a way to do it on the original KF by removing the back and grounding the usb boot pad, then you could usbboot cmds to install the bootloader. But I'm not sure if it will work or ever been tested on this device. Good Luck, look on the bright side you can turn it into an extremely thin planter box, that still serves no purpose
well
I didnt read everything carefully but succeded in rooting my KHFD 8.9"
then i tried to install FFF using KFU and then it restarted and i couldnt power it on
well i have tried using FireKit .. but it says waiting for OMAP device..
then i wanted to do the shorting trick !!
i have searched for two days and couldnt find any where the how to USB shorting of KHFD 8.9
please help I am getting frustrated..
Sent from my GT-N7100 using xda app-developers app
In total desperation I had opened my KHFD 8.9
But sadly I couldnt do anything to unbrick it
If anybody knows about hardware I can share photos of hardware
And may someone can be able to tell how to unbrick it or do fastboot
Sent from my GT-N7100 using xda app-developers app
onemeila said:
You are pretty much screwed. Sorry to tell you. You've flashed over the bootloader, the problem is with one that doesn't work. So your device won't even boot into fastboot no matter what you do. There was a way to do it on the original KF by removing the back and grounding the usb boot pad, then you could usbboot cmds to install the bootloader. But I'm not sure if it will work or ever been tested on this device. Good Luck, look on the bright side you can turn it into an extremely thin planter box, that still serves no purpose
Click to expand...
Click to collapse
Thanks onemeila - confirmation is good. Unfortunately, this is not a tax deductible education expense... :laugh:
Thanks for your KFHD SRT, by the way - I'm using it nearly weekly.
Andy
Kindle turn of eterny
Slimepuppy said:
Add another brick to the pile. Fire HD 8.9. Already rooted, OTA defeated, and Google App'd, but wanted the security of FFF just in case. Planned to used KFU 0.9.6 to set fastboot and then push FFF 1.4a once in fastboot. Instead, used KFU 0.9.6 to automatically install FFF. It appeared that KFU pushed FFF and then sent a reboot. The machine never came back to life after that shutdown.
Attempting to get into fastboot results in eternally <waiting for device>
I removed the back - there are no obvious 'fastboot' pads on any of the boards as there is for the HD 7".
Does anyone think that a factory cable would get this thing's attention? edit...apparently not. http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9
edit 2...built a factory cable and tried fastboot, KFHD Recovery tool, KFFirstAide, KFU, and Linux Fire Kit. Nothing can see the device on the other end of the USB cable.
Well...there's always a 'motherboard' swap. Sigh.
Click to expand...
Click to collapse
I have the same usse and i don0t know what to do. I made my own factory usb but nothing happens. I don't find the way to fix it... some can help me?
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Nikaroo said:
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Click to expand...
Click to collapse
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
soupmagnet said:
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
Click to expand...
Click to collapse
Thanks for the pointer - I think it got me a tiny bit further. After finding the package and 'fixing' drivers - woo-hoo - my computer is saying that the device is working properly now, I can see it as 'Kindle Fire' in my device manager. However, it still is showing up as 'Tate-PVT-08' under Devices and Printers, and it cannot be found (isn't communicating) with ADB. I feel like I'm missing something so small to be able to move forward and reflash this thing - it's so incredibly frustrating to not be able to find it. :/
I also have tried editing the adb usb file to include the 0x1949, having gone through the adb kill/start-server commands several times, which hasn't changed anything. Is there anything I am missing to get windows and adb to communicate with it? Or is my only option at this point trying 'non-Windows based options'?
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Click to expand...
Click to collapse
Sooo, I feel even stupider now. I do have KFFA, so I tried to reflash the system image. It went through and gave me a success, although it did have an issue with erasing user data and cache. It said to disconnect from the computer/usb and power down, then restart. I did that and was super hopeful - it went through the boot screen a few more times than normal... but then BAM. Right back to the Kindle Fire System Recovery screen that it can't get past. Ugh. I must have really screwed something up on it.
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here. Going through that, I checked my hardware IDs, and one of the numbers are off, which according to the guide means that my Kindle isn't in fastboot mode (and this is while using the fastboot cable). If I use a regular USB cable, it doesn't show up at all anywhere. The more I research, the more confused I get. Everything seems geared towards fixing your device if it is stuck in a bootloop (mine goes through that and sticks at the recovery screen) or being able to get it into fastboot, which I cannot seem to do even with the cable. I guess I'm going to try to uninstall and reinstall the drivers for it again, but I'm starting to believe that whatever value I changed while in super user mode before my problems began are going to make it impossible to fix...
The hardware I'd should be 0x1949, and at this point I'm guessing maybe something is wrong with something in the data partition or you have a bad kernel. I don't know how to wipe the data partition from fastboot though. I don't know if kffa reflashes the boot partition, but you could always try that since a system reflash didn't work, or you could try reflashing the system image again, there's another tool in the android development section called kindle fire system restore tool, maybe it will work better for you. Here's the other tool: http://forum.xda-developers.com/showthread.php?t=1951254
Ignore the part about that adb command, that's only for of your kindle can actually boot up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Nikaroo said:
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here.
Click to expand...
Click to collapse
Be very careful of what guides you use around here. Some of them (fastboot guide in particular) are made with the original Kindle Fires in mind, and can lead you to do irreversible damage.
I'll try that in the morning... I spent most of my day at this and need a break! Thank you so much for trying to help me out. I really appreciate any and all pointers.
Hello. I am having trouble with my first gen Kindle Fire HD. About two weeks ago it flipped itself into Fastboot mode and has stubbornly refused to kick back out of it since then. I have researched and tried many methods, but I am not a hardcore tech guy.
Here are the details and what I have tried so far:
- This kindle had a stock operating system and was never rooted
- I have tried holding the power button down for 20 seconds (and longer)
- I installed Android studio and the Kindle fire drivers. Attempted to reboot it using the command line tools. System refuses to give its serial number when queried using Adb devices command even after using the android update/kill-server/start-server commands. Accepts the reboot command, but does not leave fastboot when it reboots.
- Bought a factory cable, tried the above method again. Did not work. Same results.
- Downloaded Qemuroot program. Program fails to execute properly every time.
- Tried the Kindle Fire HD restore tools. Computer sometimes claims it is pushing the files to the kindle, but then nothing changes. Tried all available options except wiping user data and cache.
- Tried uninstalling the Kindle drivers and reinstalling just to see if there was an error there. Didn't work, but my computer does identify it as a Kindle Fire instead of as a Tate-PVT-08
I am at the end of my technical skills and what I can learn via google and internet forums. Since it's not completely bricked, just stubbornly indifferent, I thought maybe the good folks here might have some more options for me to try.
Any advice or help will be most appreciated.
Thank you!
Bumping this because I still need help...
yeah got the same issue here as well
Po5tHuMaN said:
yeah got the same issue here as well
Click to expand...
Click to collapse
I was told today that it is completely bricked and that it is a manufacturing issue. Sadly, it is two years old, so I doubt Amazon will be very cooperative about fixing it.
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
do a "fastboot devices" to see if the device is detected by the PC in fastboot mode.
But the fact that Amazon recovery is gone, does not look good.
shabuboy said:
do a "fastboot devices" to see if the device is detected by the PC in fastboot mode.
But the fact that Amazon recovery is gone, does not look good.
Click to expand...
Click to collapse
Please don't cross-post; found this exact text in three different threads. My earlier response here. Others have basically said the same thing.
@Davey126
Hmm... Are you referring to my answer?
shabuboy said:
@Davey126
Hmm... Are you referring to my answer?
Click to expand...
Click to collapse
@shaduboy
No - your response was helpful and appreciated. Second time in as many days a post made from my mobile via the official XDA app has included the wrong quote. Likely a navigation error on my part as no one else is complaining. My apologies.
I'll stick to responding from other devices; old eyes aren't what they use to be.
Hi Guys
A friend has given me a table he "bricked" a few months ago. Its a fire 7. I got it to run an old Lineage ROM back in 2017. I think it was on 5.1.1 when I got it.
He tried to flash a different ROM using flashfire and it failed, he says it gave an error about storage space - I am assuming he didn't wipe first.
Now the tablet wont boot. It powers on, shows the amazon splash then reboots, over & over.
I can get to the Amazon recovery holding the vol down button and from there into fastboot - can I recover this unit? I'm wondering if I can use adb to go from fastboot to TWRP then flash a new ROM and it will boot again?
I know a bit but not much about adb etc. Can anyone point me in the right direction?
EDIT: While messing about I have tried the info in this thread: https://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
I can push the TWRP to the device with fastboot but it fails to boot it with error: (remote: unknown command)
I assume this means its on the locked 5.1.X bootloader and not 5.0.X
Any other options to flash a new bootable ROM to it from the Amazon recovery/fastboot?
Thanks.
cardyology said:
Hi Guys
A friend has given me a table he "bricked" a few months ago. Its a fire 7. I got it to run an old Lineage ROM back in 2017. I think it was on 5.1.1 when I got it.
He tried to flash a different ROM using flashfire and it failed, he says it gave an error about storage space - I am assuming he didn't wipe first.
Now the tablet wont boot. It powers on, shows the amazon splash then reboots, over & over.
I can get to the Amazon recovery holding the vol down button and from there into fastboot - can I recover this unit? I'm wondering if I can use adb to go from fastboot to TWRP then flash a new ROM and it will boot again?
I know a bit but not much about adb etc. Can anyone point me in the right direction?
EDIT: While messing about I have tried the info in this thread: https://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
I can push the TWRP to the device with fastboot but it fails to boot it with error: (remote: unknown command)
I assume this means its on the locked 5.1.X bootloader and not 5.0.X
Any other options to flash a new bootable ROM to it from the Amazon recovery/fastboot?
Thanks.
Click to expand...
Click to collapse
You'll need to reload FireOS and start over as if it were a new device. If you're certain of the bootloader build reinstall FireOS 5.3.1 to avoid a potential hard brick. You'll then need to root with KingRoot, migrate to SuperSU, find a working build of FlashFire and hope the same thing doesn't happen again. All while making sure the device doesn't take an OTA update from Amazon. In short, a royal PiTA.
Note: there is an evolving hardware hack that may prove easier once it is a bit more mature. Involves cracking open the case (very easy) and shunting a point on the mainboard to ground. At present the exploit needs to run from a Linux based host but I suspect a Windows varient will soon be available. You'll find several threads discussing current progress.
The easiest way to fix this now is to follow the instructions in this thread here. This is the second method mentioned in the above post. This will reinstall the bootloader files and give you a 5.01 bootloader, defeating anti-rollback protection in the process. Afterwards you can load TWRP from fastboot.
As you probably have a 5.1.1 preloader now you should not need to open the case to enter download mode, holding down the left volume button when plugging in the USB cable should be enough.
Davey126 said:
You'll need to reload FireOS and start over as if it were a new device. If you're certain of the bootloader build reinstall FireOS 5.3.1 to avoid a potential hard brick. You'll then need to root with KingRoot, migrate to SuperSU, find a working build of FlashFire and hope the same thing doesn't happen again. All while making sure the device doesn't take an OTA update from Amazon. In short, a royal PiTA.
Note: there is an evolving hardware hack that may prove easier once it is a bit more mature. Involves cracking open the case (very easy) and shunting a point on the mainboard to ground. At present the exploit needs to run from a Linux based host but I suspect a Windows varient will soon be available. You'll find several threads discussing current progress.
Click to expand...
Click to collapse
Thank you for this - I read the hardware hack but also the option to reload fire OS & considered this to be the best option but like a ****, I flashed the tablet with Fire 5.1.2 - I now have an unbootable device. Black screen.
Anything I can do from this point?
MontysEvilTwin said:
The easiest way to fix this now is to follow the instructions in this thread here. This is the second method mentioned in the above post. This will reinstall the bootloader files and give you a 5.01 bootloader, defeating anti-rollback protection in the process. Afterwards you can load TWRP from fastboot.
As you probably have a 5.1.1 preloader now you should not need to open the case to enter download mode, holding down the left volume button when plugging in the USB cable should be enough.
Click to expand...
Click to collapse
As mentioned above, I tried to use the Amazon bootloader to flash FireOS back to the device and start again with it - I flashed 5.1.2 like an idiot and the tablet is now "dead" - I cant seem to even power it on.
Would the method described here recover the brick I now have? : )
Thanks again for the replies guys ! I think I can do the hardware hack if it will help - nothing to lose at this stage really.
cardyology said:
Thank you for this - I read the hardware hack but also the option to reload fire OS & considered this to be the best option but like a ****, I flashed the tablet with Fire 5.1.2 - I now have an unbootable device. Black screen.
Anything I can do from this point?
Click to expand...
Click to collapse
Your device is recoverable - and you may not even have to crack the case. This is the thread you'll want to follow. Still no Windows support but the process as fairly easy once you get past the prerequisites.
cardyology said:
As mentioned above, I tried to use the Amazon bootloader to flash FireOS back to the device and start again with it - I flashed 5.1.2 like an idiot and the tablet is now "dead" - I cant seem to even power it on.
Would the method described here recover the brick I now have? : )
Thanks again for the replies guys ! I think I can do the hardware hack if it will help - nothing to lose at this stage really.
Click to expand...
Click to collapse
The hack I was talking about has evolved a bit now: see here. This will reset anti-rollback protection so should unbrick the tablet. You won't even have to open the case: start with the tablet off and hold down the left volume button and plug in the USB cable as described in the post. You will end up with TWRP installed on the device and fully unlocked fastboot.
MontysEvilTwin said:
The hack I was talking about has evolved a bit now: see here. This will reset anti-rollback protection so should unbrick the tablet. You won't even have to open the case: start with the tablet off and hold down the left volume button and plug in the USB cable as described in the post. You will end up with TWRP installed on the device and fully unlocked fastboot.
Click to expand...
Click to collapse
Nice, I will give that a try now.
Thanks.