Hi,
I had my kindle rooted and a few weeks back the OS got updated automatically to a new version and my Home screen went black and I was unable to change the wallpaper. So I ran Stunts Wallpaper Fix but something must have gone wrong and I am now stuck in the:
Kindle Fire System Recovery
Your kindle doesn't seem to be able to boot.
Resetting your device to Factory defaults may
help you to fix this issue.
The choices I have are:
Reboot your kindle
Reset to Factory Defaults
Choosing any of the two options eventually leads back to the above. So I purchased the fastboot cable but that apparently does not help either, as soon as I plug it into the kindle it will go back to the Kindle Fire System Recovery screen. I have ADB installed on my PC, however when starting the Kindle, my PC only recognizes the driver for about 2 seconds and displays it as "Jem-PVT-Prod-04" in the Device Drivers then that disappears as well.
I read many, many threads on this forum but don't seem to find anyone with this particular problem. Help very much appreciated.
Where did you get your factory cable?
I got it from the "EARLYBIRD SAVINGS 3ft USB to Micro USB Factory Cable for Amazon Kindle Fire Motorola Xoom/Phones" from Amazon.
eandjon said:
I got it from the "EARLYBIRD SAVINGS 3ft USB to Micro USB Factory Cable for Amazon Kindle Fire Motorola Xoom/Phones" from Amazon.
Click to expand...
Click to collapse
And before plugging it in, did you make sure your device was completely powered down (held the power button for 10-15 seconds)?
Yes, absolutely. Tried it several times always returning to the System Recovery Screen.
eandjon said:
Yes, absolutely. Tried it several times always returning to the System Recovery Screen.
Click to expand...
Click to collapse
You may have a bad factory cable, or the "factory cable" you have is not a factory programming cable.
If you can install the driver in my signature on the jem device before it disappears, then you should be able to use the fastboot command like this and not have to use a factory cable:
fastboot -i 0x1949 getvar product
Run that command and after it says waiting for device, plug your kindle in while powered off, it should go into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I followed your instructions and it seems to be working.
I am now receiving after rebooting the Kindle a dark screen saying "fastboot mode" in yellow.
In order to not screw things up again, what would be the best way forward?
I would suggest using kindle fire first aide and reflashing the stock system partition.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I followed the steps mentioned for the Kindle First Aide and did a complete restore. My Kindle is now up and running!
Thank you sir for your excellent advice!
On another note if you try my wallpaper fix again, if it has some kinda error and bricks again, could u report the error to me? I always try to make it as safe as possible, and would like to know why my safeties didn't help in your case. Who knows, it might actually work this time since your os is closer to stock than before possibly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I installed your wallpaper fix and it worked without any issues at all. Thank you!
My kindle fire hd 8.9" rooted is doing the same
stunts513 said:
If you can install the driver in my signature on the jem device before it disappears, then you should be able to use the fastboot command like this and not have to use a factory cable:
fastboot -i 0x1949 getvar product
Run that command and after it says waiting for device, plug your kindle in while powered off, it should go into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My kindle is stuck in the exact same loop. What do you mean by 'install the driver...on the jem device'? ...I'm pretty green
Basically it means open the device manager on your PC, and plug you kindle in while its off, if it is indeed an 8.9" model, after it powers on you should see a device pop up briefly in the device manager called jem something, if it instead makes the noise like something connected an you don't see a jem device popup, then you probably have the drivers installed already. If you see the device pop up then quickly right click it and hit update drivers and point it to where you extracted my drivers and let them install. After that you should be able to use the fastboot command I mentioned to get I to fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It says "Windows encountered a problem...The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
Sent from my SGH-T999 using xda app-developers app
You must be on windows 8, you need to disable driver signature enforcement. Google it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
It's rebooting now...fingers crossed!!!
IT WORKS!!!
Thank you so much Stunts!!! I'm now trying to do your programming, and I'm having a bit of a problem. The dos is telling me 'Could Not Find ...system32\framework-res.apk.orig doing prelim check...' followed by 'Your system partition is too low...' what am I doing wrong?
OK well the cannot find time isn't an error, its just extra output that I haven't disabled, that file it can't find is basically the cleanup process running to delete any files from a previous attempt, and if they aren't there you see that error. As for the disk space error, you should check your system partition to see how much space it has left on it, you will need around 40mb to use the wallpaper fix. You can attempt to disable the check if you are sure you have enough space, but if it doesn't have enough space you will end up with a softbrick'd device stuck in a boot loop until it has its system partition reflashed. Try either over adb shell or in a mobile terminal running "df /system" and tell me how much space it has free.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Try either over adb shell or in a mobile terminal running "df /system" and tell me how much space it has free.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app[/QUOTE]
Ok, recap...system is still rooted. I did a full system reboot, and the only other os that I had was go launcher. To try and get the script to run, I deleted Go launcher, along with widget picker, and live wallpaper. I tried to run "df/system" through COMMAND under administrator, and I tried the same command on my kindle through a terminal emulator and it said "not recognized" on pc, and "not found" on kindle. I'm sorry if this is annoying, and I appreciate the help.
---------- Post added at 05:32 AM ---------- Previous post was at 04:55 AM ----------
n/m, just found the df. on system it says 37M. What can I do for the other 3M?
---------- Post added at 05:49 AM ---------- Previous post was at 05:32 AM ----------
Ok...I realized I was asking stupid questions that I should resolve myself. For nOObs (like me) I went to this http://forum.xda-developers.com/showthread.php?t=619153 to get help with the adb shell. In doing so I was able to find my available space. I typed the command "df" and it showed all my available and used storage. I then went in to X-plore (root file management app) where I was able to change my user status to SU and go in to the systems folder and remove apps that were invaluable. Thanks for all the help stunts, if it wasn't weird I would send you some Christmas cookies lol.
Related
Hello-
Quick background. I have a Kindle Fire with the CM9-Reloaded ROM installed. All was going well for a few weeks until my Kindle stopped connecting to the internet. I figured it was just a bug and wanted to reinstall the ROM or choose a different one.
I have FFF v1.4 (with the blue logo) installed. When I get to the screen that allows me to choose "Normal Boot", "Recovery", or "Reset Boot Mode" I choose the "Recovery" to go into TWRP; however, this doesn't happen. It puts me back into a loop to the same screen to choose again. I can do this over and over again and I'm still not able to get into recovery to get to TWRP.
I decided to see if I could use the Kindle Fire Utility to get to TWPR that way. Before everyone asks, my drivers are all updated and functioning properly. I uninstalled and reinstalled just to double check. When the Kindle is plugged in, I can go to the device manager and see my Kindle there. The problem is that KFU says I'm offline and I can get to any of the menus. When I plug in my Kindle I do get the little "bong" that tells me my computer recognized it.
Also, went to my laptop and downloaded the KFU and installed everything. Same result as with my desktop.
What else can I try? I have a factory cable, but I really don't know much about how to use it. I simply followed step by step instructions to root this when I originally got it. Any suggestions? I'd really just like to put this Kindle back to stock, re-root, and try it all over again to eliminate any potential issues in the future. Thanks in advance for your help.
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
same boat
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Dasanko said:
Does "adb reboot recovery" not work from within the ROM either? You can try to reflash TWRP from fastboot, if you're feeling brave enough. Double check the hash first, though.
Click to expand...
Click to collapse
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
jeffjoleen said:
No, adb reboot recovery doesn't work. How would I reflash TWRP from fastboot? I'm definitely a rookie at cmd work.
Click to expand...
Click to collapse
By it not working, do you mean that it reboots normally?
"fastboot getvar product" to get the KF to stick with fastboot mode when it's loading the bootloader.
"fastboot flash recovery twrp.img" very important to double check the file hash to make sure it's not corrupt.
"fastboot reboot" only in case it doesn't automatically reboot on its own.
EDIT: Keep in mind fastboot mode uses a different set of drivers, so you may have to install those as well (included in KFU, along the ADB ones).
---------- Post added at 06:57 PM ---------- Previous post was at 06:49 PM ----------
Justugh said:
hello all
i am in need of dire help working on sister's inlaw kindle fire
i got the KFU newest one and verified the kindle was the newest version software
i started the KFU i must of missed a step and the kindle fire is locked on loadscreen (kindle fire) a soft brick i got the program that u say try and the system will not be found by it
i have removed and reinstalled the Adb rebooted my system and hard reboot kindle........the computer sees the kindle but not as kindle..........in device manger it shows up under the ADB section not the portable..........i only see the ADB there is no kindle hardware tab in windows explorer it is not listed
but it is listed in devices and printers under unspecified with the name kindle in there........... i can not access any info in the tab it list the name as kindle the rest are blank
please help i have no idea what to do on this one.........it is locked on the screen and i can not get the system to fully talk with each other to correct it using the methods u have posted
**note i went to a 2nd computer that has never had kindle or any ADB or any other program dealing with this the system is giving the same results as stated above the system sees it but does not know what it is ...thought it might be a overlapping driver issue on my computer
side note i am kind of poor and really do not have 200 bucks to buy a new one for her i have a week to fix with out getting caught help please
Click to expand...
Click to collapse
Please don't hijack other people's threads, start your own here on Q&A. Otherwise, handling with two completely different issues in the same place gets awfully confusing. Also, read this: http://forum.xda-developers.com/showthread.php?t=1552547
My kindle fire is stuck in a boot loop (i think) it just keeps saying "Kindle Fire" then restarts then says the same thing and does this for ever in this state the computer doesnt find the device. I have a fastboot cable and it does put the device in to fastboot. Then I switch the fastboot cable with a regular kindle cable then it finds the device as otter2-prod-04. This all happened when I was trying to put twrp on it. And I think I rooted it.
If it shows up now as otter on your PC you just need to use fastboot to reflash the system image. If you are have an exclamation mark in the device manager you need to install the adb drivers for it when its in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for the reply but another problem that i forgot to mention is that neither adb nor fastboot find the device.
Check the device manager for an an exclamation mark then also, what fastboot command are you running? If you don't run the command with -i 0x1949 it won't detect it. So for a test try running "fastboot -i 0x1949 getvar product".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
when I run that command it only says <waiting for device>. And also in device manager it has a exclamation mark.
Then u need to tell it to install the adb drivers for the device with the exclamation mark. That would be the reason the fastboot command isn't working. If u have rooted it then you should have the appropriate drivers laying around somewhere for adb mode. If not send either rpost back or pm me, and I will link u to my drivers I customized for kindles, though I am unaware if they will work with kf2 as is because I don't have its pid, only the vid may be the same, if that's the case I can always fix it and reupload it.
Sent from my Amazon Kindle Fire HD using xda app-developers app
bootloop
stunts513 said:
Then u need to tell it to install the adb drivers for the device with the exclamation mark. That would be the reason the fastboot command isn't working. If u have rooted it then you should have the appropriate drivers laying around somewhere for adb mode. If not send either rpost back or pm me, and I will link u to my drivers I customized for kindles, though I am unaware if they will work with kf2 as is because I don't have its pid, only the vid may be the same, if that's the case I can always fix it and reupload it.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
I also have a kindle fire second generation. But it's in a different bootloop, with the first bright white and orange kindle logo repeating every 10 seconds or so. Nothing else. No adb, no fastboot. Not recognized by the computer at all! Could you please help?
Sounds like you will need a fastboot cable to attempt fixing that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jarjacksn said:
I also have a kindle fire second generation. But it's in a different bootloop, with the first bright white and orange kindle logo repeating every 10 seconds or so. Nothing else. No adb, no fastboot. Not recognized by the computer at all! Could you please help?
Click to expand...
Click to collapse
You need to get a fastboot cord. There is some great info here http://forum.xda-developers.com/showthread.php?t=2271909
Hello all
I realize the one post below me is almost the exact same problem, but I am stuck. I just got my kindle hd 89 and I already have a red screen. Every option I try to use to get fastboot does not work, whether I'm using cmd and typing in the command, using KFFA, or KFHD 2.1. I think I ended up with a red screen by using FireFlash but without checking the right options. If it matters, I started with 8.4.6. I really want to unred-screen this, so any help would be appreciated! Thanks.
hi beatmastermcfly,
I guess this will be a driver problem, for me win 7 64bit it works perfectly.
Have you ever tried KFHD_SRTv1.3-8.1.2 to start on another PC? Did you run it as an Admin?
You get a red screen when you try to SRT to enter fastboot?
mfg
JPL
GermanJPL said:
hi beatmastermcfly,
I guess this will be a driver problem, for me win 7 64bit it works perfectly.
Have you ever tried KFHD_SRTv1.3-8.1.2 to start on another PC? Did you run it as an Admin?
You get a red screen when you try to SRT to enter fastboot?
mfg
JPL
Click to expand...
Click to collapse
I used KFHD_SRTv2.1- 8.1.4 and I am going to try KFHD_SRTv2.0- 8.1.3 , but the link to KFHD_SRTv1.3-8.1.2 in this thread appears to be dead. Anyone have a mirror?
And yes, the issue I'm having with KFFA, the SRT, and even when I am just trying to boot into fastboot via cmd, is that it says "waiting for device" and then when I plug it in it says "KindleFire" (in orange) for a second or two before switching over to the red screen.
I was able to do fastboot before the red screen showed up, so I doubt it has anything to do with drivers.
hi beatmastermcfly,
I asked because I recently in a German Help - Forum have 3 different PC's tried it with a user (always bare OS with identical increments). Only after 1 week it has then eventually folded.
the Pc's have not accepted the Fastboot.exe for any reason.
mfg
GermanJPL
GermanJPL said:
hi beatmastermcfly,
I asked because I recently in a German Help - Forum have 3 different PC's tried it with a user (always bare OS with identical increments). Only after 1 week it has then eventually folded.
the Pc's have not accepted the Fastboot.exe for any reason.
mfg
GermanJPL
Click to expand...
Click to collapse
I do not understand what you are saying.
I will say that when I plug the Kindle in, my laptop makes the "device connected" noise followed quickly by the "device disconnected" noise and it even shows up in the device manager for the split second before it turns red.
What exactly is the device that shows up in the device manager call itself before it disappears? And does it have a yellow triangle on it?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
What exactly is the device that shows up in the device manager call itself before it disappears? And does it have a yellow triangle on it?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
At first it showed up under "portable devices" as an "unknown device" and I managed to uninstall the drivers in the hopes of re-installing them, and then the next time it showed up under "portable devices" as "jem-004..." etc. or whatever the code name for this type of kindle is. I think it just shows up as the category "other devices" now, but I do not have the kindle handy.
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Your drivers just saved my life dude. Thank you so much. Gotta figure out the next step now.
stunts513 said:
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
oh but seriously dude running CM10.1 now and could not be happier thank you so much.
Your solution to fastboot and redscreen issue
Hey beatmastermcfly,
I'm having the same issue you had with the red screen and fastboot not working.
Are you able to walk me through the solution you had with the the drivers that were recommended?
Did you end up using Ubuntu, or did you figure out how to do it in windows 7?
cheers
Hello I am very sorry to ask for help, I have this same problem and can help stunts513 beatmastermcfly, my kindle has a red screen and make everything after root, and the worst part is that my laptop recognizes it as unknown device which driver you downloaded work for you
:crying:
Dead Kindle Fire HD 8.9
Okay, due to my own errors while using fastboot on my KF, it no longer does *anything* when I try to turn it on. I can't reenter fastboot, since ADB no longer recognizes the device (which of course, it can't, since the device doesn't start). I mean, it does *nothing* (although the hardware is in great shape).
Am I, as I suspect, just dead in the water here? I have the recovery files, but without ADB or fastboot, I no longer have a way to load them.
Should I just start using the KF as a doorstop now? Or is there some obscure solution to this mess?
rogerlig
Someone correct me but figuring concludes that the red screen is because amazon blocks tablet when it comes to a stolen board or losses , my I get a tablet I did not say much , so that the repaired but through the serial number of a personal contact amazon and they said it was lost and I imagine blocked the operating system so I could not use the tablet
Please Help!
Meeperman said:
Hey beatmastermcfly,
I'm having the same issue you had with the red screen and fastboot not working.
Are you able to walk me through the solution you had with the the drivers that were recommended?
Did you end up using Ubuntu, or did you figure out how to do it in windows 7?
cheers
Click to expand...
Click to collapse
Did you ever find a solution? Thanks!
On a win7 x64 box you need adb (there is a quick version) installed. The kfhd drivers. USC disabled. AND MOST IMPORTANTLY YOU MUST RUN ADB FROM A COMMAND PROMPT ORIGINATED FROM THE ADB FOLDER. (shift+right click and select "run command prompt from here)
Did you ever get your kfhd 8.9" to work. Everything youve said so far is the exact replica of my kindle. I know its like 7 years later but this is still a problem for people
Juhpan said:
Did you ever get your kfhd 8.9" to work. Everything youve said so far is the exact replica of my kindle. I know its like 7 years later but this is still a problem for people
Click to expand...
Click to collapse
this is a COPY/PASTE of my own post. the files i specify are the exact names, just search this section of X-DA for them. SEE BELOW.
i had the same problem with the "red screen of death" as well. i found that if i installed the "Minimal ADB and Fastboot" and / OR (i did the minimal first.... ) KFHD_SRTv1.3.5 and RUN THE APP FIRST, then when it says "waiting for device" you then plug in the ALREADY OFF tablet it then WORKS!! says "fastboot mode" on the tablet. and it is listed in device manager also.
i got BOTH apps here at this board in this section.
WARNING: i run windows XP with all updates as of 10-31-2017 (pm me for info, 2 lines of text!! ) . NEWER windows versions have "permission issues". fixes are posted in multiple topics here in the Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 section. READ THEM!!
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.
My thread title pretty much explains what happened after I tried uninstalling some pre-installed apps (using Clean Master) in my Kindle Fire HD 8.9.
My question to XDA kindle owners... is the potential fix for my device just a 10 dollar factory cable away? Can my device be restored in factory setting once I get in to fastboot and find the Android equivalent of Windows system restore?
Sidenote:
1) 2 days ago I succeeded rooting my Kindle Fire HD 8.9 with no issues. In that same day I installed setCPU to keep my device running at 1.5 Ghz. I admit... the only crazy thing I did with my device was attempting to uninstall pre-installed applications that came with my Kindle.
2) my desktop computer knows the Kindle Fire HD 8.9 is being connected to USB... but a few seconds later it refuses.
Fastboot cables don't work on 8.9" models, you need to install the drivers when the device briefly is detected with the ones in my signature if it doesn't have them installed already. If/when they are installed you just need to so only turn the kindle off and unplug the cable and run "fastboot -i 0x1949 getvar product" and when it says waiting for device plug the kindle in, it should then go into fastboot. From there you can restore it with kffa.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Fastboot cables don't work on 8.9" models, you need to install the drivers when the device briefly is detected with the ones in my signature if it doesn't have them installed already. If/when they are installed you just need to so only turn the kindle off and unplug the cable and run "fastboot -i 0x1949 getvar product" and when it says waiting for device plug the kindle in, it should then go into fastboot. From there you can restore it with kffa.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Have you or any XDA-ers out there seen this kind of dilemma My desktop PC is having?
Jem-PVT-Prod-04 appears briefly, then disappears.
Here is a snapshot of my desktop.
Here is what I see in 0-3 seconds
i.imgur.com/xKUCDu0h.jpg (copy-paste this link to address bar)
Here is what I see after 3 seconds
i.imgur.com/2lzDMjmh.jpg
i.imgur.com/Lj16wo9h.jpg
*** NOTE: this site is not allowing me to host pictures of my desktop... so i removed the http part ***
That's what it is supposed to do on the 8.9” model, you have to try to install the driver while it briefly appears. If you can't kffa might have something that will help, if not you can always do this from a Ubuntu live CD, which is easy because the drivers are built in, only thing you have to do is install the fastboot command from the repos, but that's easy as long as you use the 13.10 live CD.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Fastboot cables don't work on 8.9" models, you need to install the drivers when the device briefly is detected with the ones in my signature if it doesn't have them installed already. If/when they are installed you just need to so only turn the kindle off and unplug the cable and run "fastboot -i 0x1949 getvar product" and when it says waiting for device plug the kindle in, it should then go into fastboot. From there you can restore it with kffa.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
stunts513 said:
That's what it is supposed to do on the 8.9” model, you have to try to install the driver while it briefly appears. If you can't kffa might have something that will help, if not you can always do this from a Ubuntu live CD, which is easy because the drivers are built in, only thing you have to do is install the fastboot command from the repos, but that's easy as long as you use the 13.10 live CD.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Here was my attempt to install drivers in your signature
(bolded & underlined (text) links below are snapshots of my desktop)
attempt:highfive:
i.imgur.com/FiUHnUxh.png
result
i.imgur.com/6D91yFZh.png
Ah that's cause your on windows 8, you have to disable windows driver signature enforcement, look it up on Google, then try again. Also no offense but could you just tell me what the error is next time, I use the xda app on my kindle for the most part and I can't select those as links without opening it to my browser then copying and pasting it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
another brick in the wall said:
Here was my attempt to install drivers in your signature
(bolded & underlined (text) links below are snapshots of my desktop)
attempt:highfive:
i.imgur.com/FiUHnUxh.png
result
i.imgur.com/6D91yFZh.png
Click to expand...
Click to collapse
You need to disable the signature enforcement that both Windows 7 X64 and Windows 8 users have to deal with. This post covers it better than I can type it. http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
My status so far...
1. Install stunt513's driver with windows driver signature disabled..... check
2. run fastboot in command prompt ..... check (but "fastboot mode" logo on the screen is just there... not moving)
3. run KFFA 4.1.100 (RunMe.bat) ..... check
4. attempted to run 1. Device Diagnostics (Safe) >>> 1. Ready to Test ADB Communication
result...
* daemon not running. starting it now on port 5037
* daemon started successfully
No changes happening and kindle fire is still in "fastboot mode" logo.
I'm not sure if I should take the next step in attempting to restore the kindle fire (option 4 in KFFA 4.1.100) because I might hardware brick it for real this time.
When using kffa I believed there is a option or question it asks you about putting it into fastboot mode for you or something, you need to tell it not to because it sounds like its just hanging on a adb command that cant execute because its in fastboot mode already.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
also, i was just reading some instructions in the KFFA thread
http://forum.xda-developers.com/showthread.php?t=2096888
here's one of the instructions...
Kindle Fire First Aide Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat. Temporary disable the Android SDK.
The bolded red text above..... are you guys sure it's not a misplaced instruction? In my mind it sounds kinda totally off topic (or it should have been step 5... or something)
I having ever used it before, I assumed as long as you had java installed it was pretty straight forward as running the run me.bat as admin, I would assume the stuff in red means if have the android SDK to take it out of your paths temporarily.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I having ever used it before, I assumed as long as you had java installed it was pretty straight forward as running the run me.bat as admin, I would assume the stuff in red means if have the android SDK to take it out of your paths temporarily.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
i'm back on track with this device..... completely restored and rooted.
thanks stunts & linear!:highfive:
You're welcome.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
stunts513 said:
Fastboot cables don't work on 8.9" models, you need to install the drivers when the device briefly is detected with the ones in my signature if it doesn't have them installed already. If/when they are installed you just need to so only turn the kindle off and unplug the cable and run "fastboot -i 0x1949 getvar product" and when it says waiting for device plug the kindle in, it should then go into fastboot. From there you can restore it with kffa.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I get the following error trying to install your driver: "The INF file you selected does not support this method of installation."
I'm on a Win7 32-bit system. After downloading your zip, I extracted the files to their own directory and right-click the android-usb.inf file, which gives the above error. Can you point me to a solution? Thanks.
You are supposed to open the device manager, find the device with a triangle next to it, usually will say jem unless its not an 8.9" device, then it would say something like otter2, or Tate, right click it and hit update driver and point it to where you extracted it, then it should install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You are supposed to open the device manager, find the device with a triangle next to it, usually will say jem unless its not an 8.9" device, then it would say something like otter2, or Tate, right click it and hit update driver and point it to where you extracted it, then it should install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It shows as jem, but on power-up it appears so briefly that I cannot install the driver for it. From power-on to device appearing to disappearing takes 1-2 seconds.
Yea you have to be fast, this is why I stick to Linux... Kffa might have a driver install option that installs to the driver cache on windows so it would auto install the driver when detected, at least after you hit skip obtaining from Microsoft update. Not sure about that though as I have never used kffa.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Success
another brick in the wall said:
also, i was just reading some instructions in the KFFA thread
http://forum.xda-developers.com/showthread.php?t=2096888
here's one of the instructions...
Kindle Fire First Aide Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat. Temporary disable the Android SDK.
The bolded red text above..... are you guys sure it's not a misplaced instruction? In my mind it sounds kinda totally off topic (or it should have been step 5... or something)
Click to expand...
Click to collapse
Did you fix it yet? I have the same problem.