Hi! Yesterday I rooted my Kindle Fire HD 8.9 with no problems. The problems came after I installed TWRP before installing Cyanogenmod and GApps. Long story short, I got those on there eventually, and when I rebooted my Kindle, it showed the Cyanogenmod splashscreen/ animation, so I thought everything went well. After about, probably, 8 minutes it flashed the Android lock screen, but that's it. So I turned it off, then on again. Now, when I turn it on, first it shows the regular "Kindle Fire" logo with "Fire" being in orange, and then changing to blue, then it just loops showing the Cyanogenmod animation, then flashing the Android lock screen for a split second, then repeating that from the Cyanogenmod animation. I can't get into TWRP when I press the volume up key IMMEDIATELY after I turn the Kindle on. But, I can get it into Fastboot mode, except anytime I do a command, it'll either say "error: device not found", or something like, or it'll say "List of devices connected" followed by the serial number, and next to that "offline". If anyone could help me with this, it would be GREATLY appreciated.
Or, is there a way to completely reset it? At this point, I honestly don't care if I end up with the Amazon OS again, I just want my Kindle back
Anything? I just want to be able to use my Kindle again... At this point I'd rather it have a full factory reset, and just start fresh, as if none of this happened, and leave it that way... :crying:
Fleetwood Mac & Cheese said:
Hi! Yesterday I rooted my Kindle Fire HD 8.9 with no problems. The problems came after I installed TWRP before installing Cyanogenmod and GApps. Long story short, I got those on there eventually, and when I rebooted my Kindle, it showed the Cyanogenmod splashscreen/ animation, so I thought everything went well. After about, probably, 8 minutes it flashed the Android lock screen, but that's it. So I turned it off, then on again. Now, when I turn it on, first it shows the regular "Kindle Fire" logo with "Fire" being in orange, and then changing to blue, then it just loops showing the Cyanogenmod animation, then flashing the Android lock screen for a split second, then repeating that from the Cyanogenmod animation. I can't get into TWRP when I press the volume up key IMMEDIATELY after I turn the Kindle on. But, I can get it into Fastboot mode, except anytime I do a command, it'll either say "error: device not found", or something like, or it'll say "List of devices connected" followed by the serial number, and next to that "offline". If anyone could help me with this, it would be GREATLY appreciated.
Click to expand...
Click to collapse
Are you taking care to include the "-i 0x1949" parameter in your fastboot commands? That's one of the things I would think is preventing the kindle from being recognized. Also, try downloading and installing the Kindle ADB drivers.
monster1612 said:
Are you taking care to include the "-i 0x1949" parameter in your fastboot commands? That's one of the things I would think is preventing the kindle from being recognized. Also, try downloading and installing the Kindle ADB drivers.
Click to expand...
Click to collapse
Thank you! I eventually got it fixed. Now it's just looping the regular "Kindle Fire" logo in orange :/ but I'm working on getting it back to normal.
Related
I was following a youtube tutorial to rooting my Fire, when the damn thing got stuck in the boot loop. I have a factory cable, but I still can't seem to figure out how to fix it. When I go through ADB and type "adb devices" all it says is "Listing Devices" or something like that and nothing else comes up. It shows in the device manager as "Android ADB Device" and has the correct hardware IDs. I found somebody with a similar problem in this post http://forum.xda-developers.com/showthread.php?t=1660636 but I followed the steps to solve it exactly as he posted them and they all seemed to work, but at the end it never booted up, and just stayed at the Kindle Fire logo.
This is really getting frustrating because nothing I try seems to work. If you can, please show me toward the steps that I need to take to fix this. If you need any other information, just ask. I hope this doesn't have an obvious answer!
Is the logo blue or orange? Blue is fff and you can go to twrp and wipe everything, then mount and install a Eton. Otherwise you are in fast boot and you can flash a recovery and fff. You can pm me for Questions.
Devices:
Kindle Fire with AlienDroid primary and Modaco secondary
Hi all,
I have a Kindle Fire HD 7" which I rooted following directions here which went fine and I've been using the rooted kindle for a few weeks. Today when I turn my KFHD on it just sits at the logo screen (no animation or anything) and refuses to boot.
I've tried hard resetting it (holding power button for 30 seconds) which did not help. I found this thread which seems similar to my problem. I was able to add a new vendor ID to the drivers and get the KFHD to show up in device manager when plugged in. However, if I try to use the fastboot command to force it to reboot it sits at "< waiting for device >".
If I do an "adb devices" the KFHD shows up there but I'm unable to do "adb shell". For most adb commands I try it simply sits at < waiting for device >". I'm hoping this means that it's at worst only soft bricked. Interestingly "adb reboot" does work but it goes back to sitting at the logo after rebooting. Does anyone have any suggestions about what to try next?
Does anyone know if the KFHD has a recovery mode I can boot into? I read a few threads that say you can access a recovery/safe mode if you hold down the up-volume button when you power on (and another that says both up and down volume buttons) but I've had no luck with that. It doesn't seem to change anything.
A little more background:
What led to my problem was that I decided to experiment with BotBrew since I'm interested in trying to compile some Linux code to run on Android. The app installed fine and I was using my KFHD normally when all of a sudden I started to repeatedly get a force close messages on some apps (I remember correctly I believe it was the keyboard). Since the message kept popping up I shut down the KFHD and when I attempted to turn it on next this began.
you should post in the HD question thread, not here in the kf1.
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
My mistake, thought I was in the right forum, but I read the name wrong!
I apologize if this has been answered before, my kf is running jellybean 4.2.1, and now for some reason, when i boot it up, even after it has a complete charge, it boots to the splash screen and stays there. i plugged it into the computer, and when i open kfu(as an admin) it says
adb status: online
boot status: unknown
afterwards, i tried to boot it in normal via kfu, and it says "system cannot find the drive specified" then it goes on to say for 5 more times "system cannot find the path specified" be fore ending with "kindle has been told to reboot in normal mode", nothing happens on the kindle, and even at this very moment, is still stuck on the animated splash screen. the computer doesn't even recognize the kindle, and it was fine until now, what should be my next course of action? also, in order for me to charge the kf, i have to hold up the plug to the kindle with two stacked legos. could it be a faulty cable or input?
electricbrain876 said:
I apologize if this has been answered before, my kf is running jellybean 4.2.1, and now for some reason, when i boot it up, even after it has a complete charge, it boots to the splash screen and stays there. i plugged it into the computer, and when i open kfu(as an admin) it says
adb status: online
boot status: unknown
afterwards, i tried to boot it in normal via kfu, and it says "system cannot find the drive specified" then it goes on to say for 5 more times "system cannot find the path specified" be fore ending with "kindle has been told to reboot in normal mode", nothing happens on the kindle, and even at this very moment, is still stuck on the animated splash screen. the computer doesn't even recognize the kindle, and it was fine until now, what should be my next course of action? also, in order for me to charge the kf, i have to hold up the plug to the kindle with two stacked legos. could it be a faulty cable or input?
Click to expand...
Click to collapse
Try reflashing the rom using twrp as the os may be corrupted
Kfire21 said:
Try reflashing the rom using twrp as the os may be corrupted
Click to expand...
Click to collapse
Thank you, its working perfectly, although i should have made backups, im glad.
Well I have fooled around with this Kindle Fire for awhile and seem to be at a road block.
It is my wife's who stated she left it alone for a week or two, came back to turn it on and it locks up at the stock KF logo screen.
From what I have gathered that means the OS is toast.
Tried to get the KFU tool to work untill I found out that it needs to be forced into 'fastboot' to receive commands. So I built a debug cable and forced it. I then ran KFU to install twrp, said it installed and was rebooting. I had to force reboot the KF and then ran a KFU perm root script, rebooted.
Now I get to the white/blue kf logo and boot options for twrp, yet when it boots it hangs on the Teamwin logo screen.
Is this a boot loader malfunction that will require the shorting method to force USB rom loading? Or am I just missing something like a regular noob?
Thanks
TheInstinctz said:
Well I have fooled around with this Kindle Fire for awhile and seem to be at a road block.
It is my wife's who stated she left it alone for a week or two, came back to turn it on and it locks up at the stock KF logo screen.
From what I have gathered that means the OS is toast.
Tried to get the KFU tool to work untill I found out that it needs to be forced into 'fastboot' to receive commands. So I built a debug cable and forced it. I then ran KFU to install twrp, said it installed and was rebooting. I had to force reboot the KF and then ran a KFU perm root script, rebooted.
Now I get to the white/blue kf logo and boot options for twrp, yet when it boots it hangs on the Teamwin logo screen.
Is this a boot loader malfunction that will require the shorting method to force USB rom loading? Or am I just missing something like a regular noob?
Thanks
Click to expand...
Click to collapse
First off, have you considered installing TWRP manually? You may want to check the md5 of the recovery.img before installing though.
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
joeldf said:
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
Click to expand...
Click to collapse
When it's in fastboot mode, use fastboot commands, not adb
Sent from my sailfish using XDA Labs
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
joeldf said:
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
Click to expand...
Click to collapse
Did you watch my video?
Sent from my sailfish using XDA Labs
sd_shadow said:
Did you watch my video?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I watched several videos, and I think I started yours at one point, but between my 8 year old running around saying it's almost midnight (it was new years eve), and then trying to get him to go to bed, by the time I came back to this, I may have lost track of what I was watching.
Moral of the story, do this kind of thing without interruptions...
I did re-watch your video all the way through and I see that what happened was normal.
Still, there was that error trying to reset the bootmode (I didn't get what you got), otherwise, it still works and re-boots fine now. Even went into Recovery.
Next thing is trying out a new rom.
Thanks again.
MY DEVICE IS ALSO STUCK!!! After doing the fastboot reboot it gets stuck with the lifeless bootscreen and doesn't do anything from there, I've also tried to use the set boot mode but it hangs on waiting for device