Please help me!
I rooted my girlfriend's Kindle a few days ago in order to install the Google Play store. Managed that just fine and installed a few apps. I then decided it would be a good idea to change the launcher and get shot of the carousel. I tried the next Launcher 3D and followed an online guide to install it. On rebooting the Kindle I got a constant pop up advising Next Launcher 3D had stopped working. It popped up continually every 1/2 second or so and I couldn't get rid of it,
Again I had a look online and found a guide to removing it using command prompt script via ADB. I went through the instructions correctly but it kept telling me the app didn't exist. Using the dir command showed the app though. Confused I tried again a couple of times. I then got a pop up on the device telling me another app.....something relating to Swype had stopped working. The Kindle rebooted itself and presented a screen with a red triangle and 'Kindle Fire System Recovery' giving me the options to either reboot or reset to factory defaults. I tried both of these options (perhaps foolishly) and had no success.
I was given some further advice from a very helpful poster on here to get KFFAide v100 and enter some fastboot commands. On entering the command 'fastboot -i 0x1949 getvar product', the script shows 'waiting for device'. Powering on the device at that point does nothing more than booting to the same screen with the red triangle. Windows does not acknowledge that the device is connected at all.
It would seem I was hasty in rooting the device. Having rooted several other Android devices I was clearly overconfident in my ability and now find myself at a loss. Is there any way at all for me to recover the device at this point? Or should I now file this under 'very expensive experience and education'?
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi Stunts513. Thank you for your reply. Have tried what you said above and Windows (8) just doesn't detect that the device has been connected. No pop up from system tray, nothing in file explorer and nothing, not even for a second in device manager.
Am at a loss for the moment. Will have to get hold of an Ubuntu CD and try that way. Am just praying it detects the Kindle. Didn't on my girlfriends laptop nor my PC so am mildly panicked just now.
OK, so I went through Linux Mint and installed the SoupKit and tried it that way. Same result. The device just isn't detected at all. Really starting to fear the worst here. The fact it's still powering on should give me some faith but i've tried all I can think of and everything advised and cannot proceed past this point.
Does anyone have any last gasp possibilities for me? Borderline desperate here now.... will try anything at this point.
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Did exactly that. Brought up the virtual terminal. Nothing.
Have tried everything now I think. Used different PCs. Different cables. Different OS. Tried bypassing getvar and just trying a manual command "fastboot -i 0x1949 flash recovery recovery.img". Nothing is getting any response from this device other than booting to the recovery screen.
Suspect I may be out of luck.
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah it is most definitely an 8.9 model. Am not sure what I have done to it but it is not being detected by any OS whatsoever. Have bitten the bullet and bought the Mrs a replacement. Expensive error on my part.
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many apologies for the delay. i managed to get the Kindle up and running following your advice coupled with that on another thread. Although it wouldn't detect in either Windows 8 or Ubuntu, it did so on Windows XP. Don't imagine you can begin to explain that one any better than I can as it's entirely illogical......but there you go. From there it detected as a JEM device and I was able to run KFFA and do a complete restore.
I now have it the way I intended to have it in the first place. Changing the launcher was fruitless as I couldn't get the wallpaper fix to work but am fine with that. had a look at customising the icons on the carousel but boy does that look like more trouble than it's worth!! Lol.
I wont pretend I was going to send my Kindle off to you guys. In truth I would have sold it to recoup some of my losses and raise funds towards the replacement. I will however be making a donation to the team very shortly as a token of my appreciation.
Thank you very much for all your help. it is greatly appreciated.
Hi All,
I'm looking to purchase a 8.9" Fire HD that will only power on to the kindle fire screen.
I've rooted other KFs in the past and have a fastboot cable.
Would it be worth the risk to take a chance that I can salvage this Fire?
thanks
Well I thought I'd throw some output here for you, on the 8.9" models you don't use a fastboot cable to fix it, usually they are fixable just by letting it install the fastboot driver when it briefly pops up on the computer, then running "fastboot -i 0x1949 getvar product" and then plugging the device in while its off. I have seen a few damaged bootloaders out there, but I doubt that would be the case, you just have to have patience when trying to fix it. If the fastboot drivers aren't wanting to install you can just boot the latest Ubuntu live distro and install the fastboot command from the repos and it will work automatically without the driver problems. Sorry this is more of a tutorial than an answer but it kinda goes into play of what you were asking.
All in all I say go for it if it's for a decent price.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I have the Kindle 8.9 HD with the front-facing camera. I tried to flash CM 11, but now it's stuck at the bootscreen. It has the orange and white boot screen and a second later, a pixelated white bar pops up on the left, then it stays frozen until I shut it down. Windows doesn't seem to detect it at all, and I can't seem to get fastboot mode except for in Ubuntu using Soupkit. However, even if I do manage to get it into fastboot on Soupkit, SK says the device is offline afterwards even though the tablet displays fastboot on the screen.
It should be said and might be obvious, I'm not entirely sure what I'm doing. I spent a great deal of time reading into how to troubleshoot it myself. I do have previous experience with flashing roms on my Android phone, but that's about it.
Once it is in fastboot, reboot into windows and use kindle fire first aid. As I recall soupkit wasn't meant for 2nd gen kindles, only the kf1, but I could be mistaken, I use Ubuntu and know what I'm doing so I don't use these kinda things. Windows should detect the device as a jem device, so download drivers in my signature, extract them somewhere and in the device manager right click the jem device, hit update drivers, and point it to where you extracted mine. Once that is done kindle fire first aid should be able to reflash it.
Kffa: http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Once it is in fastboot, reboot into windows and use kindle fire first aid. As I recall soupkit wasn't meant for 2nd gen kindles, only the kf1, but I could be mistaken, I use Ubuntu and know what I'm doing so I don't use these kinda things. Windows should detect the device as a jem device, so download drivers in my signature, extract them somewhere and in the device manager right click the jem device, hit update drivers, and point it to where you extracted mine. Once that is done kindle fire first aid should be able to reflash it.
Kffa: http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Just like that. It's working! Didn't realize SK wasn't for 8.9, so when it didn't work, I stopped and just assumed it was fastboot on the tablet that wasn't working. I guess thinking it was hard-bricked might have been a bit dramatic.
Thanks, man! You're a lifesaver. You know your ****.
So I managed to brick my rooted Kindle Fire 2nd Generation after trying to install a rom with TWRP app. Anyways, I have a fastboot cable, and the correct drivers and Android SDK, but when I plug in my cable, turn off the device (holding button for 20 seconds), then turn back on, it still goes to red screen immediately after the brief kindle fire logo, exactly the same without fastboot cable. What am I dong wrong?
Would really appreciate any help .
-Thanks,
Jacoobyman
You sure the fastboot cable works? If it does I would keep the device manager open and see if it is briefly being recognized as a adb device or not. If it briefly detects it then I would attempt a "fastboot -i 0x1949 getvar product", then plug the kindle into fastboot cable while off and see if that works, and yes I know that is typically meant for a 8.9" model but if its a weird circumstance then it couldn't hurt to try.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You sure the fastboot cable works? If it does I would keep the device manager open and see if it is briefly being recognized as a adb device or not. If it briefly detects it then I would attempt a "fastboot -i 0x1949 getvar product", then plug the kindle into fastboot cable while off and see if that works, and yes I know that is typically meant for a 8.9" model but if its a weird circumstance then it couldn't hurt to try.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
No it does not detect it at all in device manager. not even briefly. :/
That sounds bad, I don't trust windows too much for debugging but I'm guessing Linux would say the same thing, what were you trying to flash that caused this?
Sent from my Amazon Kindle Fire HD using Tapatalk
[HELP] Unbricking Kindle Fire HD7" with Fastboot Cable; pc won't recognize Kindle
Lemme start from the beginning. (I've made numerous threads before I had a fastboot and commentors kept asking questions that I've answered in the post so I'm gonna try to be detailed as possible)
Before I had a fastboot cable
I flashed a ROM onto my Kindle Fire (Cyanogen 13). Didn't like it so I thought a recover to factory settings would work. It didn't and it got stuck on the TWRP screen. Stuck on TWRP meaning that it's literally stuck on the blue TWRP screen. It doesn't get to the main menu or anything. I scoured the internet for solutions and some (which didn't mention a special cable) I tried but it ultimately failed because the program (can't list every single one but one I do remember is Kindle Fire Unbrick Utility), could NOT find my Kindle Fire. Also, Kindle Fire could not be found under "this PC" but when I plugged it in, it made the ding sound and could be found under ""Device Managers". I started reading steps about using a fastboot cable and was led to believe if you use one, your PC should recognize Kindle, therefor programs to unbrick should find the Kindle.
Got my fastboot cable today
I ordered one from Amazon and when I plug my Kindle in with cable, it turns on saying "fastboot kindle fire". I was excited to get this fixed finally. I followed a YouTube video's instruction (of a channel that I can count on) Tekify's Unbrick Kindle Fire. I did all the installing ADB drivers and what not but once I plugged the Kindle in and then opened the Unbrick program (this one Unbrick Utility). I pressed "1" on my keyboard to wipe everything on device. But once I pressed enter it sat on <waiting for device>. I checked under Device Managers and under Other Devices, Tate was there. But I couldn't find the Kindle under "This PC" still.
I've already researched this specific issue and people said to go to Tate's properties and update driver software. Then browse your PC for the Kindle under "This PC" but can't because Kindle doesn't show up under there. I know this is a Bible's worth of words but I really want to get this tablet FIXED!
CrustyLube said:
Lemme start from the beginning. (I've made numerous threads before I had a fastboot and commentors kept asking questions that I've answered in the post so I'm gonna try to be detailed as possible)
Before I had a fastboot cable
I flashed a ROM onto my Kindle Fire (Cyanogen 13). Didn't like it so I thought a recover to factory settings would work. It didn't and it got stuck on the TWRP screen. Stuck on TWRP meaning that it's literally stuck on the blue TWRP screen. It doesn't get to the main menu or anything. I scoured the internet for solutions and some (which didn't mention a special cable) I tried but it ultimately failed because the program (can't list every single one but one I do remember is Kindle Fire Unbrick Utility), could NOT find my Kindle Fire. Also, Kindle Fire could not be found under "this PC" but when I plugged it in, it made the ding sound and could be found under ""Device Managers". I started reading steps about using a fastboot cable and was led to believe if you use one, your PC should recognize Kindle, therefor programs to unbrick should find the Kindle.
Got my fastboot cable today
I ordered one from Amazon and when I plug my Kindle in with cable, it turns on saying "fastboot kindle fire". I was excited to get this fixed finally. I followed a YouTube video's instruction (of a channel that I can count on) Tekify's Unbrick Kindle Fire. I did all the installing ADB drivers and what not but once I plugged the Kindle in and then opened the Unbrick program (this one Unbrick Utility). I pressed "1" on my keyboard to wipe everything on device. But once I pressed enter it sat on <waiting for device>. I checked under Device Managers and under Other Devices, Tate was there. But I couldn't find the Kindle under "This PC" still.
I've already researched this specific issue and people said to go to Tate's properties and update driver software. Then browse your PC for the Kindle under "This PC" but can't because Kindle doesn't show up under there. I know this is a Bible's worth of words but I really want to get this tablet FIXED!
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 XT1096 using XDA Labs