I have successfully rooted my smaller Kindle Fire HD. I tried to root my 8.9 Fire HD and now I'm stuck with what I think is brick.
I started off with this link.
http://rootkindlefire.com/kindle-fi...t-kindle-fire-hd-8-9-into-pure-android-tablet.
I worked great until I got to step 20 when the device rebooted and it ran super slow and the display was not right a visible line running through the display. No apps showed up and command took more than 20 seconds to register. Unable to fixed it at this point I did a factory reset and all was good. No line through the UI and response time was back to normal. I tried couple of more times to root it and each time was meet with the same result. I left it lay for a while but took it back up again after doing some more research. I finally settled on this root solution and it worked.
http://wiki.cyanogenmod.org/w/Install_CM_for_jem
It worked and I was able to boot into TWRP and check its various settings then a problem occurred when I tried to move files to the device. I got message unable to mount cache. After some poking around I notice the internal storage at 0. No space for to move any files from my computer to the device. Try as I might I wasn't able to copy anything to the device. So one final time I attempted to do a factory reset and this is where things went to hell. The device rebooted but I got neither the standard Orange fire logo or the blue TWRP loading Fire Logo, all I got was a truly black screen like all the pixels where dead and no back light. The Kindle no longer shows up as a Kindle in my Device manager and its name is actually something cryptic like 'Kolwr29'. I am able to assign it the Andriod ABA Device but it cycles in/out of the device manager like its being connected and disconnected from my laptop. I've read most of the links listed as suggested on this forum but the device doesn't respond to any Fastboot commands and any command I give continually says 'waiting for device.' I've tried to do this on both my laptop and desktop but the device exhibits the same behavior. I also in desperation ordered a Fastboot cable even though I was fairly certain from what I read that it wouldn't work my Fire 8.9. Nothing same problem.
I'm at lost. The device will not respond to any commands and think I truly have a brick on my hands. I'm at the point where I'm just going to pay to replace it than wash my hands of trying to root it. We'll just live with the crappy apps from the amazon store. Any help you guys can give me would be greatly appreciated.
I've read the following posts and gone through all the steps in them but to no avail.
http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1850192&page=2
http://forum.xda-developers.com/showthread.php?t=2010353
http://androidcowboy.com/2014/01/root-kindle-fire-hdx-8-9/
Related
Okay, I just got my kindle fire (replacement; broke the screen on my other) and I rooted it perfectly and everything was working fine until an hour ago when Amazon sent an update to my Kindle 8.9, and when I checked it said my system was 8.4.3 so I rerooted the device which worked perfectly and installed adw launcher but none of my backgrounds would work nor show up. (I did all of this using Kindle Fire First Aide 64).
I then went to the option that said fix a broken installation because I installed holo launcher after that and it did the same thing no backgrounds were working and on that one the menu buttons were missing. The fix a broken installation changed permissions for all of my apps and then it asked was I using a kindle fire 2 and I have NO IDEA what a kindle fire 2 is, so I googled it and couldn't find a clear answer to whether my device was or wasn't one, I saw some yes's and some no's so I clicked yes. My device then rebooted and the kindle fire logo came up but then it disappeared for like a second and then it flipped upside down. I got to my lock screen and had to unlock the screen but I had to use the opposite direction to get to my unlock button (i.e unlock icon was on the right and cam on left but had to swipe left like I was opening cam in order to unlock my screen).
I saw something at the bottom that said safe mode so I googled what that was and on the amazon help page people said to power down the kindle while holding the volume down and power button. I tried that method 3 times, and it didn't work. I tried the hold the power down for 20 sec thing (i actually did it for 20 secs one time and then again for a full minute) none of that worked either. My computer doesn't recognize the kindle, so no adb. I also tried going to my sdk folder where fastboot was located and opening the command prop and trying to enter fastboot that way while the kindle was powered down. NONE of those options have worked. Could someone PLEASE help me??
UPDATE:
I fixed the upside down kindle issue (don't remember how, it was yesterday and i'm very forgetful ) The kindle started working fine, but the background was black and in my quest to fix the background (tried fff, kfu, soupkit, etc) and NONE of them have been working for me. I have literally been trying to fix this issue since yesterday around this time (2pm here) and I can't seem to fix it. When I plug my device into the computer it DOES power on the device and recognizes it as other jem-pvt-prod-04 but then that stays for like 2 secs and disappears. When I try to use the fastboot commands it just says waiting for device forever and nothing happens. I've also tried right clicking the jem, etc in device manager and installing google drivers but they won't install. I'm REALLY stuck here and would appreciate if someone could help me. I have tried calling someone on here and have been leaving messages for 2 days now but I guess they're really busy so if ANYONE has any idea PLEASE PLEASE help me.
I have linux on my computer (wmware), and i'm running windows 8 as well if that helps anyone.
post can be closed, issue fixed after 2 more hours of playing around with my kindle.
I have tried to refrain from asking but I have read many posts and am not really clear on my issue. Several weeks ago my wife was using the her kindle mainly just for books and laid it down to charge. The next morning she turned it on a the message "your kindle fire has detected a problem, please press the power button to restore your device to factory settings. Due to her books being on the amazon servers this was no big deal, pressed the button and it went through the motions and said it was sucessfully completed. Reboots and back to the same message, again and again and again. I come to this site read how to download KFU to help get me out of this loop. Installed the drivers per instructions opened ADB and saw were the kindle is in the device manager but shows as online boot status unknown. Uninstalled reinstalled to no avail. Took it to a local shop to see if the could get it to work. They were able to get TWRP loaded but could not get a clean install loaded, it always failed. I picked it up still had TWRP on it to try it myself. I was able to get the update.zip file where it needed to be, installed, failed, rebooted and now I am back where I started with the "your kindle has detected a problem". I tried to re-install TWRP but ADB continues to say it is online boot status uknown. I have rebooted the device serveral times as well as computer and noticed that for a moment it will reflect the online boot status 4000. If you have a cat like reflex you might be able to do something but I guess I am a little slow. I know it is not a driver issue as when it had TWRP on it it would reflect correctly and could communicate. So at this point I am a little lost, in fact for as much time as I have spent on this I probably could have bought a new one. Are there any instructions out there that I may be missing on how to deal with this or is it pretty much dead. If I could get it connected I do think it could be fixed.
Soupkit?
jwhite0514 said:
I have tried to refrain from asking but I have read many posts and am not really clear on my issue. Several weeks ago my wife was using the her kindle mainly just for books and laid it down to charge. The next morning she turned it on a the message "your kindle fire has detected a problem, please press the power button to restore your device to factory settings. Due to her books being on the amazon servers this was no big deal, pressed the button and it went through the motions and said it was sucessfully completed. Reboots and back to the same message, again and again and again. I come to this site read how to download KFU to help get me out of this loop. Installed the drivers per instructions opened ADB and saw were the kindle is in the device manager but shows as online boot status unknown. Uninstalled reinstalled to no avail. Took it to a local shop to see if the could get it to work. They were able to get TWRP loaded but could not get a clean install loaded, it always failed. I picked it up still had TWRP on it to try it myself. I was able to get the update.zip file where it needed to be, installed, failed, rebooted and now I am back where I started with the "your kindle has detected a problem". I tried to re-install TWRP but ADB continues to say it is online boot status uknown. I have rebooted the device serveral times as well as computer and noticed that for a moment it will reflect the online boot status 4000. If you have a cat like reflex you might be able to do something but I guess I am a little slow. I know it is not a driver issue as when it had TWRP on it it would reflect correctly and could communicate. So at this point I am a little lost, in fact for as much time as I have spent on this I probably could have bought a new one. Are there any instructions out there that I may be missing on how to deal with this or is it pretty much dead. If I could get it connected I do think it could be fixed.
Click to expand...
Click to collapse
I saw your post and saw the soupkit thread and thought you should head over there for more info: http://forum.xda-developers.com/showthread.php?t=1850038
Hey guys, before I begin, yes i read the '[HOW-TO] Before asking for troubleshooting help...' page as well as the '[GUIDE] Kindle Fire For Beginners' page, and am still in need of a bit of assistance due to my hilariously lacking knowledge of the workings of electronic equipment. :silly:
I just dug my kindle fire out of my dresser drawer where it has been sitting due to being 'bricked' for quite some time (stuck at the boot logo - white kindle text and orange fire text shimmering on a pure black background - holds a charge but is indefinitely at this screen). It is completely stock, having not downloaded or installed any ROMs or any other software, and initially began experiencing this problem the morning after running it out of battery while downloading a few books and games one night. I promptly plugged it in, went to bed, and woke up to it in this state that next morning.
I have tried downloading Kindle Fire Unbrick V1.1 by ZombiePiratez and running that to fix it, but it does not recognize my kindle fire. So, i downloaded Eclipse ADT with Android SDK for windows and followed some instructions i found for getting it to recognize my kindle as "Android Composite ADB Interface" in hopes that then the unbricking tool would recognize it and work its magic for me. But it didnt. I imagine this is because the process that I followed is flawed.
My question is, if i were to buy a "factory cable" would I be able to unbrick my kindle fire without having to do any of this command promp shamanism thats clearly over my head? Kinfauns states in his guide that "With a factory cable, unbricking just comes down to "plug it in and flash new stuff" in almost every bricking situation." But what does 'flash new stuff' mean; should I have picked that up from the guide as well? Or could I just use the factory cable in conjunction with ZombiePiratez unbricking tool to get back to the factory settings?
Thanks in advance for any pointers
See my How to flash twrp and firefirefire with a Fastboot cable
http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
Sent from my XT862 using Tapatalk
Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:
noobSaurus said:
Hey @sd_shadow !
Thanks for the link to that, the videos you've created make it possible for even someone with my level of tech knowledge to work through this problem. Immensely better than trying to follow a written guide
Anyway, I finally got my fastboot cable and followed the steps in your videos to the tee, however I'm still encountering one small problem. When I get to the point where I'm installing update-kindle-prerooted.6.3.3.v1.zip in TWRP by swiping across the screen, it runs until it gets to the line thanking paulobrien and two others but then promptly freezes (or so i assume since it doesnt continue on and the loading bar halts in its tracks). I decided after a few tries to just hold the power button to get it to shut off and then booted the kindle in normal boot mode - and it worked! - despite not being able to complete the process as shown in your video. But this concerns me, as I do not have any of the additional apps shown in your video (not that this truly matters to me) and under settings -> device it shows that I am running version 6.3.1_user_#####. So I have two questions:
1) Did the fff and twrp processes work, but the 6.3.3 update fail thus enabling me to use my kindle as a v6.3.1 device again?
2) Will it harm my device in any way (e.g. re-bricking) if I just call it good and use it as it is now?
Thanks for all the help so far :highfive:
Click to expand...
Click to collapse
1 yes installing TWRP and FFF reset boot, and allowed 6.3.1 to boot normally
2. the only problem should be that, when connected to wifi, update will redownload and try again once a day or so
Kindle will reboot to TWRP, but update should fail, if that does not bother you it is fine
3. what twrp version did you install? says in twrp if you are not sure
I installed TWRP v2.7.1.0-blaze because that is what you used in the video, even though i had read that 2.2.2.1 may be preferable for stock unrooted kindle fires. I did this so that I could follow your video exactly without having to change any steps except for switching otter to blaze in the cmd promt code I inputted.
Also, as I write this, Ive realized that I still may have made a mistake and installed one of the alternate test files for the 6.3.3 prerooted update and not the complete file itself, so ill get back with that info.
Yeah, i installed the alternate test file the first time :silly:
Went back through and followed your instructions to the 'tee' again and its up and running.
I do have one more question though; when I am using the device I dont get very far before selecting an application or making another command causes the screen to go black, only displaying the time and settings option at the top and the home button, back button, search button, etc at the bottom - none of which respond when selected. This happens with both the go launcher and the kindle launcher, and each time the only way I can stop it is resetting the device... Any suggestions to counteract this?
Before I begin, trust me when I say I have scurried through dozens of Google results, forums, blogs, YouTube videos, FAQ's and other things trying to find out how to unbrick this thing. I have a Kindle Fire first gen which I rooted using Kindle Fire Utility through superuser 3 days ago. All was well, as I had google play and an innovative new launcher. After downloading a few apps, I thought that I had finally made the Kindle the fully-functional Android tablet I had desired. However, after a few hours of seamless use, the Kindle decided to freeze on me. Holding the power button still brought up the "Do you wish to power down your Kindle?" notification, and I shut it down, planning on restarting it. However, when I turned it back on, it would not get past the animated Kindle Fire logo. The weird part was, I could still hear notification tones. I was using my phone to DM on Twitter, and when I would get a message back, I could hear the twitter notification on my Kindle. (No, I was not mistaking it for the phone). After a while, I could hear that sound it makes when the battery was about to die. I plugged it in, and after two hours I unplugged it, held the power button to shut it down, and started searching google for answers. I was advised to use the Kindle Fire Utility to launch it in fastboot mode, which only restars the Kindle with no success. I have tried all options on the KF utility, even Permaroot. If I install TWRP recovery, it gets stuck on waiting for device. On most options, it gets stuck on waiting for device. (I have tried all the unplugging, unpowering options I saw). The computer makes a sound when the KF is plugged in, but it doesn't come up on the devices with removeable storage tab. I have all drivers installed, it is ADB enabled through the device manager, I have the Java Developer Kit, as well as Android SDK. The only thing I can get any utility to do (I have tried many such as Kindle Brick, SuperOneClick,etc) is restart the Kindle as if I did it myself. It still makes all the notification tones I mentioned earlier. One thing I have noticed, though, is that when the Kindle is 10 seconds from dying, the Unlock Screen will appear with no response. I have tried several times to let it get to that point, then quickly plug it in, but no sucess. It just restarts on the same boot screen. I have no idea what to do. I'm not a developer by any means, but I'm good with following directions I'm given to mess with computers and such. I don't have much knowledge of the command prompt, either. I just made this post as a last resort. Someone please help. (Running Windows 10 techncinal preview on a Windows 8, 64-bit laptop if that helps)
Do you know which system version?
Kindle Fire Utility doesn't root the latest system version.
Guessing that you rooted older version, then Kindle downloaded and installed newer system version, it would not ask for permission.
New system version may not have installed correctly.
If system was updated, Kindle lost root.
When powered off, connect to wall charger, does it charge?
Couple of options
See if you can force fastboot mode with adb commands
Or buy a fastboot cable
Then flash fff and twrp so you can reinstall stock rom
See
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
Sent from my XT912 using Tapatalk
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
horgenblorg said:
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
Click to expand...
Click to collapse
this is only for kindle fire 1 (2011)
there is a separate section for your device see
Fire Index: Which Amazon (Kindle) Fire Do I have?
for correct forum link
Sent from my XT1254 using XDA Labs