Help! I successfully rooted my Kindle Fire HD 7" following your tutorial "[ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version", and then installed Google Plays etc. following "[ROOT][HOW TO] Install Google Play Store Noob (Simple) Version". I then got to the "[How to] Install Go Launcher EX and HD Noob (Simple) Version" tutorial, and everything went down hill from here.
After following the instructions of tutorial 3, and error message popped on my screen saying that "October has Stopped" and my device froze. I held down the power button, but my device wouldn't boot up - instead it went to a screen with a "Red Warning Triangle". I tried everything from this screen to reboot/reboot my device, all to no avail. Eventually the battery died.
I was able to my Kindle Charged again using the wall charger. However, when plugging into my computer via USB, it doesn't appear on my list of devices. Thus, tools such as KF First Aide are of no help; they cant't communicate with my device, and get stuck on the "<waiting for device>" message.
Any advice?
Can I fix this? How Is my Kindle Fird HD 7" dead forever?
dim_opoulos said:
Help! I successfully rooted my Kindle Fire HD 7" following your tutorial "[ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version", and then installed Google Plays etc. following "[ROOT][HOW TO] Install Google Play Store Noob (Simple) Version". I then got to the "[How to] Install Go Launcher EX and HD Noob (Simple) Version" tutorial, and everything went down hill from here.
After following the instructions of tutorial 3, and error message popped on my screen saying that "October has Stopped" and my device froze. I held down the power button, but my device wouldn't boot up - instead it went to a screen with a "Red Warning Triangle". I tried everything from this screen to reboot/reboot my device, all to no avail. Eventually the battery died.
I was able to my Kindle Charged again using the wall charger. However, when plugging into my computer via USB, it doesn't appear on my list of devices. Thus, tools such as KF First Aide are of no help; they cant't communicate with my device, and get stuck on the "<waiting for device>" message.
Any advice?
Can I fix this? How Is my Kindle Fird HD 7" dead forever?
Click to expand...
Click to collapse
Yes you can fix it,In Fact, You need to have done a lot worse than that to completely fry your kindle, Don't worry, But you will need a factory cable now, Do you have one?
If you don't you can either
A) Order one from SkOrPn
B)Make one yourself, It's easy if you know how to solder
Once you acquire i'll tell you how to completely restore your kindle!
Yes he is right. You can order a factory cable from prokennexusa by PM.
Sent from my KFTT using xda app-developers app
AmrBanawan said:
Yes you can fix it,In Fact, You need to have done a lot worse than that to completely fry your kindle, Don't worry, But you will need a factory cable now, Do you have one?
If you don't you can either
A) Order one from SkOrPn
B)Make one yourself, It's easy if you know how to solder
Once you acquire i'll tell you how to completely restore your kindle!
Click to expand...
Click to collapse
Thanks. I am ordering a factory cable asap. Once it arrives, however, what do I so then?
If u got any Samsung chargers laying around its very easy to make one without solder
Sent from my KFTT using xda premium
dim_opoulos said:
Thanks. I am ordering a factory cable asap. Once it arrives, however, what do I so then?
Click to expand...
Click to collapse
The simplest tool that can restore your kindle would be
KFHD System.img Restore Tool KFHD SRT
All you need to do is download this tool
KFHD_SRT_v1.2.3- 7.2.3
This is a large download, System images are ~600Mb
Originial Thread
http://forum.xda-developers.com/showthread.php?t=1951254
Open SR Tool.bat
choose option 1
Or option 2 if you would like to have Go launcher or Apex launcher installed along with it, And google play store!
The tool will send the system image to your kindle, This will take about 7 minutes
Next, you should choose option 3 to wipe cache and userdata, This is recommended but not required, You will lose any files you transferred to your kindle, You don't need to do this if you want to keep your files!
If you need help just ask
:good::good:Good Luck:good::good:
UPDATE
I wanted to update everyone on my situation. I followed the threads advice - and it worked!
Specifically:
1. I ordered a factory cable from SkOrPn - got it in 3 days after placing order (shibby!).
2. I charged my device by plugging it into wall charger.
3. I installed the Kindle Fire ADB drivers on my compter - directions and links can be found on the thread [ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version
4. I installed the toolbox KFHD_SRT_v1.2.3- 7.2.3 - from the thread KFHD System.img Restore Tool KFHD SRT
5. I plugged my device into PC USB port using the factory cable - it immediately went into fastboot.
6. I used KFHD_SRT_v1.2.3- 7.2.3 from my pc (SR Tool.bat), followed the instructions, and presto.
dim_opoulos said:
I wanted to update everyone on my situation. I followed the threads advice - and it worked!
Specifically:
1. I ordered a factory cable from SkOrPn - got it in 3 days after placing order (shibby!).
2. I charged my device by plugging it into wall charger.
3. I installed the Kindle Fire ADB drivers on my compter - directions and links can be found on the thread [ROOT][HOW TO] Root the Kindle Fire HD and 2 with Windows - Noob (Simple) Version
4. I installed the toolbox KFHD_SRT_v1.2.3- 7.2.3 - from the thread KFHD System.img Restore Tool KFHD SRT
5. I plugged my device into PC USB port using the factory cable - it immediately went into fastboot.
6. I used KFHD_SRT_v1.2.3- 7.2.3 from my pc (SR Tool.bat), followed the instructions, and presto.
Click to expand...
Click to collapse
How long did it take your kindle to charge? When I plug mine in the wall charger it only turns on for like 5 seconds and that's about it? Also did you use the factory cable to charge or the usb cable that came with the Kindle?
bricked .. red screen
I was able to root my KFHD7 with Root_with_Restore and then Qemu .. rooting seemed to work fine.
I then tried to use Fire Flash app to load Hashcode's freedom boot image and TWRP recovery image.. clicked the flash button, it rebooted to a red screen.
I made myself a fastboot cable, when I plug it in, I see the Fastboot logo on the kindle, but my PC never detects the device.
Not sure where to go from here.
I've downloaded and tried KF2_SRT tool and no go. Also downloaded and tried KFFirstAide .. same deal.
All tools stay on <waiting for device>
remove factory cable after it is in fastboot
compmd said:
I was able to root my KFHD7 with Root_with_Restore and then Qemu .. rooting seemed to work fine.
I then tried to use Fire Flash app to load Hashcode's freedom boot image and TWRP recovery image.. clicked the flash button, it rebooted to a red screen.
I made myself a fastboot cable, when I plug it in, I see the Fastboot logo on the kindle, but my PC never detects the device.
Not sure where to go from here.
I've downloaded and tried KF2_SRT tool and no go. Also downloaded and tried KFFirstAide .. same deal.
All tools stay on <waiting for device>
Click to expand...
Click to collapse
remove factory cable after it is in fastboot mode then plug normal usb cable in it then into pc.
My Kindle Fire is basically like this one mentioned above and I'm in fastboot with the factory cable, but i'm stuck with , <waiting for device> on the tool. It seems as though my drivers can't be installed. Any fix to this.
wj3pic said:
...It seems as though my drivers can't be installed...
Click to expand...
Click to collapse
Can you elaborate on this?
soupmagnet said:
Can you elaborate on this?
Click to expand...
Click to collapse
So, basically.
1) I rooted
2) got google play
3) tried to get twrp with fire flash, and this is where i screwed up
Insted of using hashcode's twrp img i used the actualy twrp (blaze) img. so im in this constant reboot loop thing.
So i got a factory cable and I am in flashboot. I got KFHD recovery tool 1.3.5 and when i click option 1, it says <waiting for device>.
I think this is due to the fact that my drivers are not installed correctly, so i tried to reinstall drivers but it just doesnt seem to be working. My thoughts are, If i can just get my computer to recognize the device we might be ok. but i cant seem to make it do that.
wj3pic said:
So, basically.
1) I rooted
2) got google play
3) tried to get twrp with fire flash, and this is where i screwed up
Insted of using hashcode's twrp img i used the actualy twrp (blaze) img. so im in this constant reboot loop thing.
So i got a factory cable and I am in flashboot. I got KFHD recovery tool 1.3.5 and when i click option 1, it says .
I think this is due to the fact that my drivers are not installed correctly, so i tried to reinstall drivers but it just doesnt seem to be working. My thoughts are, If i can just get my computer to recognize the device we might be ok. but i cant seem to make it do that.
Click to expand...
Click to collapse
Watch this video here to learn how to set up your drivers http://m.youtube.com/watch?v=oaNM-lt_aHw&desktop_uri=/watch?v=oaNM-lt_aHw
You're bootlooping and need to use Kindle Fire First Aide to get your KFHD back to normal. http://forum.xda-developers.com/showthread.php?t=2096888
I used KFFA to get back to 7.2.3 bootloader and used Hashcode's 7.2.3 bootimg and the 2.6.1 TWRP file he lists. This worked great using Fire flash.
Sent from my Amazon Kindle Fire HD using xda app-developers app
KFHD7 turns off after 5 seconds
So I've basically followed all steps here and in numerous other threads, but one problem still persists: the Kindle Fire HD 7 turns off after 5 seconds. If I press the power button, nothing happens. If I plug it into a charger, it'll turn on and display the "Kindle Fire" logo on the screen then turn off after 5 seconds. If I plug it into a USB port, it'll turn on and display the "Kindle Fire" logo on the screen then turn off after 5 seconds. If I plug in the factory cable, it'll turn on and display the "Kindle Fire" logo, then display the "Fastboot Kindle Fire" logo then turn off after 5 seconds. I've left the unit on the charger for hours on end, then attempt to turn it on using the power button or plugging in a normal or factory USB cable and it'll do the same thing, turn off after 5 seconds.
OK you may have a 50/50 shot if its doing this because of a bad boot loader, but it could make things worse and end up in a hard brick if it shuts off mid flash, but if it happened to be something wrong with the battery then you would risk this for nothing, but I'm more inclined to think its the bootloader since it doesn't warn u of a low battery. If the fastboot device needs its drivers still, try installing the ones in my signature in that small time frame. If u can manage that, get a copy of the boot loader for your device and check the md5sum of the file( very important) and make sure it matches. Once you have that setup, you need to flash the boot loader onto the device, so I would suggest putting the boot loader in the same folder as fastboot.exe and running "fastboot -i 0x1949 flash bootloader bootloaderfile.bin" and let it say waiting for device, then plug you fastboot cable in and see if it will successfully flash within 5 seconds. If things go south it will hard brick though from an incomplete flash so just warning you ahead of time its up to you.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello,
I have a Kindle Fire (2nd Gen) running on firmware 7.4.6, is there a tutorial on how I can root and run another OS
instead of the Kindle OS?
Use this to root it. http://forum.xda-developers.com/showthread.php?t=1886460
Use this to get 2nd boot loader + twrp installed: http://forum.xda-developers.com/showthread.php?t=2271909
Two important things you should note, one is put the ROM and its corresponding gapps on the kindle's sdcard ahead of time or you may suffer a boot loop and have to push the film manually into twrp. Second is when you open fireflash, make sure to check the first check box, it should have red warning text under it. If you don't check this box you will reboot to a red screen and it will require a fastboot cable to fix. BTW you might wanna fix the thread title since this is a kfhd not a first gen kf1. Only reason I can tell is because of the os version. Kf1's have a completely different method to root and flash since they don't have a high security processor that checks the boot loaders signature.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I had my Kindle 5gen, with CM12 and i wanted to install another rom. The problem was that, because of multiple thing, the recovery was set to amazons, lost the boot access and only could enter in recovery to adb or fastboot. The problem got even worst when i installed a Firmware "update-kindle-37.5.2.2_user_522053820" so it could boot as a fire.
Now it doesnt turn on. I connect it to the PC and i can hear it conecting and disconecting. In Device manager i can see it conecting as a Unknown device and then into MT65xx preloader. The thing is that all this happens fast so i cant do anything to stop it and i tried holding the Power bottom and the power and up bottom as well.
I really dont know what to do now. Search everywhere with no luck.
Tried Amazon Fire 5th gen super tool, tried soupkit with cygwin64 and kindle unbrickv01 and nothing...
Im desperated...
Imanol Garbar said:
I had my Kindle 5gen, with CM11 and i wanted to install another rom. The problem was that, because of multiple thing, the recovery was set to amazons, lost the boot access and only could enter in recovery to adb or fastboot. The problem got even worst when i installed a Firmware "update-kindle-37.5.2.2_user_522053820" so it could boot as a fire.
Now it doesnt turn on. I connect it to the PC and i can hear it conecting and disconecting. In Device manager i can see it conecting as a Unknown device and then into MT65xx preloader. The thing is that all this happens fast so i cant do anything to stop it and i tried holding the Power bottom and the power and up bottom as well.
I really dont know what to do now. Search everywhere with no luck.
Tried Amazon Fire 5th gen super tool, tried soupkit with cygwin64 and kindle unbrickv01 and nothing...
Im desperated...
Click to expand...
Click to collapse
Wrong forum; CM11 is not an option on this device (2015 5th Gen 7" non-HD) .
Davey126 said:
Wrong forum; CM11 is not an option on this device (2015 5th Gen 7" non-HD) .
Click to expand...
Click to collapse
yeah my bad, it was CM 12, anyway i had a CM something but now i have nothing.
Hmm, there is some of misinformation it seems... and sadly, not enough research was spent to see what you wanted to achieve it seems...
Fire 5th, cannot have the recovery such as TWRP or CWM installed. If you have 5.0.x you can tether of it, but it can't never be installed.
See Q5: http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441
If the stock Amazon recovery is gone, you have a bricked device.. If you have Amazon recovery, you can go back to stock (stay within the version you had, do not downgrade, or you will brick it), check the link above following Q5, there will be two unbrick methods at the bottom. Select the one based on your version 5.0 vs 5.1 or later.
What I did was flash recovery properly (after root, CWM) and accidentally hit reboot without an OS to boot to. Now it is stuck on the Kindle fire logo, but it only shows for a brief period of time (one second) then a black screen. What do I do now? Is it bricked? BTW, I was installing a unofficial version of Cyanogenmod 13 for "tate" and don't have a fastboot cable on hand, nor a soldering iron. :fingers-crossed:
Badcatalex said:
What I did was flash recovery properly (after root, CWM) and accidentally hit reboot without an OS to boot to. Now it is stuck on the Kindle fire logo, but it only shows for a brief period of time (one second) then a black screen. What do I do now? Is it bricked? BTW, I was installing a unofficial version of Cyanogenmod 13 for "tate" and don't have a fastboot cable on hand, nor a soldering iron. :fingers-crossed:
Click to expand...
Click to collapse
Fastboot is the answer.
Badcatalex said:
What I did was flash recovery properly (after root, CWM) and accidentally hit reboot without an OS to boot to. Now it is stuck on the Kindle fire logo, but it only shows for a brief period of time (one second) then a black screen. What do I do now? Is it bricked? BTW, I was installing a unofficial version of Cyanogenmod 13 for "tate" and don't have a fastboot cable on hand, nor a soldering iron. :fingers-crossed:
Click to expand...
Click to collapse
Uhhh... I hate to be the bearer of bad news, but I'm pretty sure the 2013 model without the camera is NOT the 'tate'. There are various warnings about this, including Cyanogen's own wiki:
Be sure you have a 2012 "Tate" device and not the 2013 Kindle Fire HD 7" "Soho" device. The 2013 model does NOT have a camera. And it currently has no exploit for loading a custom recovery. Using the Tate exploit files on a Soho device will end with an unrecoverable brick.
Click to expand...
Click to collapse
Sounds like you've discovered the unrecoverable brick they speak of, when doing exactly what they say not to do. Your model sounds like the Soho.
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.