Related
Total n00b here. I think I may have really messed up my Kindle fire.
I have searched high and low for a solution but unfortunately I fail to understand some jargon, so Im stuck. Some of you may shake your heads in disgust for being forced to associate yourself with someone of my idiocy and may say it serves me right. All the same, Im desperate for help here, so anything you can do to help me out would make me infinitely grateful.
I have been researching for weeks now on rooting my Kindle fire which I recieved as a birthday gift at the end of April so I could tap into its full potential. I was running the most recent firmware (6.3.1) and finally decided to downloaded the Kindle Fire Utility 0.9.6 to my PC and pull the trigger on Rooting it. I had some initial driver issues, but eventually got the KFU to show an ABD status of "Online" with a Boot Status of "4000". I had read in a few places that it was a good idea to make a recovery before doing anything else, so without giving it much thought I typed 3 (Install Latest TWRP Recovery) and hit enter. The KFU displayed the screen "waiting for device" and the KF went to the boot logo screen, which is where it has stayed ever since. It never occurred to me that I should first "ROOT" my kindle, and I dont know if this is directly responsible for my current situation or not.
Ive attempted to follow various suggested methods of recovery (power off Kindle, and powering it back on after restarting my computer and initiating Bootmode command 1 <4000>normal and command 3 <5001>recovery (in separate instances) and uninstalling/reinstalling drivers.) but now every error that can occur does. At this point Im ready to throw in the towel and Id be happy to just get my Kindle back to its factory settings but I dont know how I can do that.
I have come across various threads that appear to address just my problem by downloading the original Kindle firmware update from Amazon, renaming it "update.zip" and "flashing it to the sd card", but I have no idea what that means or how to do it. PLEASE HELP!!!!
(after my first misadventure there is now a "recovery" folder in the directory where I unzipped the KFU. Im inclined to think this might help, but I dont know how or what to do with it.)
Thanks in advance for anyone patient enough to respond to this.
Ok, so after further researching this problem, I have taken note that many users have successfully, installed a TWRP recovery without Rooting their Kindle Fire, (at least that is how I understand it). Evidently its not uncommon for a failure to occur during the process of any one of the optional commands given in the KFU, almost always causing this "boot logo error" or similar mishap.
That being said, I have attempted every other form of recovery mentioned on this and other forums, including Kindle Fire Unbrick Utility, with no success. The underlying problem being, that anything I am attempting to correct through the computer never reaches my Kindle. My PC acknowledges that there is something plugged into the USB port by sounding an alert tone, but it sounds different, like theres some kind of error, and the "USB error" icon appears on the right hand side of the "Start bar" (I normally use a Mac, so Im no hip to all the PC lingo) When I click it I get one of two messages no matter which port the device is plugged into: either the Kindle is labeled as an "Unknown Device" and that drivers could not be located, or that my device could perform "faster" if I moved it to a "high speed" USB port (all of the ports on my computer are listed under High Speed). When checking the device utilities folder, previously the driver was consistently called "Android ABD Interface" with a yellow error sign. Upon "updating driver" I would get the error code 10, "this device cannot start". Now however, no driver is displayed whatsoever for my Kindle, android or otherwise...
Ive read that in some cases, allowing the battery to completely drain then plugging in and booting it back up will cause a Kindle in this state to "default to its factory settings", so this will be my last ditch effort to salvage my Kindle before I resign myself to returning it to Amazon in hopes that it will still be covered under warranty. I guess Im just not cut out for this sneeky stuff. The retarded thing is, the only reason I wanted to Root my Kindle fire in the first place was to personalize the backgrounds...
what happened is your stuck in fastboot and your windows drivers are all buggered up. I can tell you what I would do?
---------- Post added at 10:34 PM ---------- Previous post was at 10:32 PM ----------
unplug your kindle from your computer and use system restore to roll your computer back to when your drivers were good not to be confused with system recovery if your with me so far?
---------- Post added at 10:36 PM ---------- Previous post was at 10:34 PM ----------
its very likey that adb will not detect your kindle it cannot while its in fastboot
But first try this shift plus right click on the tools folder in kindle fire utility select open command window here power your kindle off and enter the command
Fastboot getvar product (hit enter)
Plugg your kindle in it will power on in fastboot
If you get the response product: kindle then we can move on.
I think so, though I dont know how to perform a "system restore"... If it was a Mac id simply jump into the Time Machine and roll back the clock a few hours, but I dont even back up my PC cuz I use it for nothing but the occasional game and PC exclusive stuff like "this"...
if you get the response product: kindle
Type fastboot oem idme bootmode 4000 (hit enter)
fastboot reboot (hit enter)
The problem really isn't that you've done anything wrong. For some reason when the device switches from normal boot (4000) to fastboot (4002), Windows fails to recognize it as being in fastboot mode. The typical fix is to reinstall the drivers. Unfortunately, it isn't always as easy as it sounds. Sometimes it works and sometimes you'll end up bald from pulling your hair out over it, and I have yet to see a definitive solution to this problem. So, as of now, success is really just hit and miss.
There are, however a few tutorials to give you a decent foundation to work from.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
YouTube is likely to have a few thousand videos on the topic as well.
If all else fails, you can always set up a Linux LiveUSB and issue adb/fastboot commands from there, but I would consider that a last resort, unless you are already familiar with Linux.
yes and what soupmagnet said to
Ok Pooch, so while you telling me what I should be doing, I decided to be proactive and figured out how to perform a system restore and rolled my computer back to this morning before I started any of this messy business. Hopefully this will not complicate the process youve now begun directing me through...
just unistall the drivers that came up when you plugged your kindle in unplugg your kindle reinstall the drivers and maybe youll get lucky
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
the drivers could be a fight but hey its windows
Thepooch said:
just unistall the drivers that came up when you plugged your kindle in unplugg your kindle reinstall the drivers and maybe youll get lucky
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
the drivers could be a fight but hey its windows
Click to expand...
Click to collapse
Soooooo, I didnt get lucky...
To your point Soup Magnet, Ive probably watched most of the tutorials you mention on You Tube and read every forum thread on the subject within the past 6 hours... It sounds so simple! But im tired.
Ill try the command prompts you suggested earlier and see if I get any luck there, after that i'm done, at least for tonight.
Thanks for your help guys!
dont give up its fixable your just in the wrong bootmode
Thepooch said:
Fastboot getvar product (hit enter)
Plugg your kindle in it will power on in fastboot
Click to expand...
Click to collapse
..."< waiting for device >"
It was worth a shot. Thanks again.
was it powered off before you plugged it in after it said waiting for device?
---------- Post added at 11:41 PM ---------- Previous post was at 11:31 PM ----------
Then next time try
fastboot -i 0x1949 getvar product (hit enter plug in your powered off device)
fastboot -i 0x1949 oem idme bootmode 4000 (hit enter)
fastboot -i 0x1949 reboot(hit enter)
Thepooch said:
was it powered off before you plugged it in after it said waiting for device?
Click to expand...
Click to collapse
Correct. I powered off the Kindle and disconnected it. Then I entered the command and hit enter and connected the powered off device. The Boot screen came back on, but that where it stays, and 15 min later its still "waiting for device".
Ill revisit this in the morning when my head is clearer. If you come up with any bright ideas in the mean time, Ill be happy to try them out!
indeed good luck rest should help xda isnt going anywhere
Sorry typo above is fixed
Thepooch said:
was it powered off before you plugged it in after it said waiting for device?
---------- Post added at 11:41 PM ---------- Previous post was at 11:31 PM ----------
Then next time try
fastboot -i 0x1949 getvar product (hit enter plug in your powered off device)
fastboot -i 0x1949 oem idme bootmode 4000 (hit enter)
fastboot -i 0x1949 reboot(hit enter)
Click to expand...
Click to collapse
nope
nope
nope
I know all the commands are good, its just not communicating to the Kindle...
Figured Id give it one more go before I hit the sack. I know this is gonna keep me awake anyway...
http://forum.xda-developers.com/showthread.php?t=1660636
pugsley42 said:
[UPDATE 2] - Steps I took to (finally) get mine working
Note: If your device is recognized in Device Manager as something *other* than "Unknown Device* (such as "kindle" or "Android ADB Interface"), skip to step 3.
1. Turn off the device.
2. Plug the device into USB to your computer. This should turn the device on.
3. Delete the ".android" folder from your Windows profile. This is very important. If you just uninstall the device and driver, Windows will still use this to reinstall the device. You want to start as fresh as possible to eliminate complications from previous attempts.
4. Uninstall it from Device Manager. Make certain to check the box to uninstall the driver as well.
5. Start a new scan for hardware changes in the Device Manager.
6. As mine was stuck in fastboot mode, it recognized the device as "kindle" (lower-case "k")
7. Run the "install_driver.bat" from the Kindle Fire Utility.
8. After driver install, run the Kindle Fire Utility.
9. ADB status will say "offline", that's fine.
10. Choose option 1 to go into the Bootmode Menu.
11. Choose option 1 to boot into Normal Mode.
12. It will be stuck at <waiting for device>.
13. Turn off the device, keeping it plugged into the PC. *very important* This step was one among others that made THE difference for me.
14. Turn on the device. *Hopefully*, you should immediately see the utility spit out some text and your device should reboot.
15. Boots up!! (well, mine did, and I had almost give up hope were it not for my pride and stubbornness).
Click to expand...
Click to collapse
Looked promising and I almost got excited about it... until step 14, when after turning on the device after turning it off (while still plugged in)no new text was spit out in the utility and my Kindle refused to reboot...
What might be happening is that every time I plug in/ turn on from off while plugged it, windows attempts to install the driver software automatically, which may be causing the mix up at the device utility stage. Like Pugsley, after deleting the .android folder from my profile and uninstalling the ADB interface/driver, then running hardware change scan, my device is recognized as "kindle", but after turning off the device and turning it back on at the "waiting for device" screen, the device is automatically updated as Android ADB interface with errors again. Is there a way to temporarily block this auto-install? That might work...
josepho1997 said:
Plug it in and tell me what it says on your computer. If it says Kindle or Android Composite Device then you should be good. If it doesn't, do a hard reset and try again. Same thing happened to me and the KFU drivers wouldn't work for me, so I downloaded a new driver. I will post a new reply with he drivers. But first if you get Android Phone or something else under Android Composite device, then uninstall it. Then go to disk drives(i think that's what its called)
and find your kindle and uninstall. Then reopen device manager. Find Kindle with an ! and open it up. Now open of the Kindle Fire Drivers folder I gave you(unzip first) and click on install.bat
Click to expand...
Click to collapse
In Device Manager, when I plug in my Kindle it shows up as "kindle" in all lower case letters and the generic device icon has a yellow "!" attached to it. If I uninstall it an then "check for hardware changes" it just pops right back up.
Is "disk drives" separate from the Device Manager utility? I did a search for it at the start screen and came up with nothing... If you send me those drivers you were talking about Ill give that a try. Thanks.
Grrr! So I downloaded the driver.zip file you posted up (thank you) and double clicked the "install" file within the unzipped folder. It appears to have installed, but now every time I plug in the Kindle it goes to "unknown device", not showing up as "kindle" anymore, and no sign of "android" anything in the device manager. I haven't been doing anything differently, same USB port as before, etc. I did shut down my computer for a few hours and booted it back up just before downloading the zip file though. Must have started the whole cycle over again. I've got to go back through earlier posts and find out how I got past this issue.
I think I know what you're asking me to do, it will just take a little bit of patience on my part to get it going. Ill post my results when I do. Thanks again!
My Kindle Fire is currently stuck at the stock boot logo (it just says kindle fire: kindle in white, fire in orange).
When I plug it into my PC, KFU says it is online, but the boot status is unknown.
I have tried every option in the KFU, the Unbrick tool, and the Firekit. The constant error message is "/system/bin/sh no such file or directory"
Using adb through the terminal, I can push things to the Fire, and I can reboot it, but I get the same /system/bin/sh error that appears when using those other tools.
Please correct me if I am wrong, but I think I need a factory cable to solve this problem. I do not have the knowledge or the tools to create one. I found a link many places in the forums, but the store those links point to is out of stock. Where do you suggest I buy a factory cable?
Also, would it be possible to use adb to push "sh" to the device so I can use adb shell?
Yes your right when you get that error good chance you need a factory cable found here http://forum.xda-developers.com/showthread.php?t=1392693 but it may just be a matter of getting your bootmode reset do you have a bootloader installed for instance yellow triangle or white kindle with blue fire?
---------- Post added at 12:35 AM ---------- Previous post was at 12:29 AM ----------
What were you doing or rather what did you do that caused it to stick and do you not have access to recovery?
---------- Post added at 12:40 AM ---------- Previous post was at 12:35 AM ----------
Pm sent
Thepooch said:
Yes your right when you get that error good chance you need a factory cable found here http://forum.xda-developers.com/showthread.php?t=1392693 but it may just be a matter of getting your bootmode reset do you have a bootloader installed for instance yellow triangle or white kindle with blue fire?
---------- Post added at 12:35 AM ---------- Previous post was at 12:29 AM ----------
What were you doing or rather what did you do that caused it to stick and do you not have access to recovery?
Click to expand...
Click to collapse
I was trying to flash it back to stock. As far as I can tell, the bootloader and recovery are stock (when I turn it on, it shows the stock kindle fire in white and orange), it just won't get past that Kindle Fire logo.
Gregsaw said:
I was trying to flash it back to stock. As far as I can tell, the bootloader and recovery are stock (when I turn it on, it shows the stock kindle fire in white and orange), it just won't get past that Kindle Fire logo.
Click to expand...
Click to collapse
Yeah you always wanna do a full wipe when returning to stock the problem is how its attempting to restore your data that has it stuck
---------- Post added at 12:52 AM ---------- Previous post was at 12:48 AM ----------
So now you need to fastboot flash twrp.img and fff.bin to it to fix it
---------- Post added at 01:01 AM ---------- Previous post was at 12:52 AM ----------
at any rate iI pm`d you with an offer to help
look
look
Real Newbie with the same problem
I was trying to use KFU for the first time last night and as it could see my KF OK I went ahead to my cost...
ADB Status - ONLINE
Boot Status - 4000
So I selected option 1 - Install Permanent Boot with Superuser and off it went.
twrp.ing missing so will download v2.2.2.1
100% OK
fff.bin is missing so will download v1.4a.bin
100% OK
(The I got a Notice that Fastboot uses a different device than ADB, if you see Kindle or Amazon reinstall drivers) (but I did not see either in Device Manager, just ADB)
Installing FFF...
<waiting for device>
(I have a screen shot of everything KFU reported)
I left it for about an hour but that's as far as it got.
On the KF it just has the 2 words Kindle Fire (White/Orange) and won't go any further
It will turn off an on, but won't go past this inital screen and is now OFFLINE to KFU
It is detected as a USB device if I unplug it from my PC and then plug it in again and will switch on from off when I plug it in, but still won't go past the "Kindle Fire" startup screen ???
I realise now that I should have done a lot more research before attempting this as I haven't a clue what I've done.
I have ordered a breakout board from Amazon.co.uk as I'm guessing I've bricked it and need to short Pins 1 & 4 ???
But before I make another mistake I though it best I appeal to you for any help
What's that expression "A little knowledge is a dangerous thing"
KFU = 0.96, Win 7 Pro 64bit, KF 1st Gen, very early US model
Regards, Dave.
Dave before you go to far try a Soupkit setup on ubuntu 12.04 or linux mint mate 13 http://forum.xda-developers.com/showthread.php?t=1850038 see if it doesn`t detect the device. If you have no animation at the startup screen your just stuck in fastboot and its just a matter of resetting the bootmode to normal. If it is stuck in fastboot Soupkit utility will reset it.
Thepooch said:
Dave before you go to far try a Soupkit setup on ubuntu 12.04 or linux mint mate 13 http://forum.xda-developers.com/showthread.php?t=1850038 see if it doesn`t detect the device. If you have no animation at the startup screen your just stuck in fastboot and its just a matter of resetting the bootmode to normal. If it is stuck in fastboot Soupkit utility will reset it.
Click to expand...
Click to collapse
Thanks, I will give it a try, I have downloaded Soupkit, ubuntu 12.04 and linux mint mate 13 now looking for a pendrive I can stick linux or ubuntu on...
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
OK, I found a spare 32GB Pen Drive and appear to have successfully installed ubuntu 12.04 on it and booted into it OK. Tonight I will try and workout how to install SoupKit...
Hopefully I will be able to change the boot mode back to Normal.
On a different topic...
I inadvertantly had my iPhone pluged into my PC and I noticed that I could see all the folders inside it when in ubuntu 12.04, I have an old version of an IPA file that I would like to install on my iPhone as the current version in the Apps store won't work, is there a simple way to accomplish my task from ubuntu 12.04 ???
Dave
Thepooch said:
Yeah you always wanna do a full wipe when returning to stock the problem is how its attempting to restore your data that has it stuck
---------- Post added at 12:52 AM ---------- Previous post was at 12:48 AM ----------
So now you need to fastboot flash twrp.img and fff.bin to it to fix it
---------- Post added at 01:01 AM ---------- Previous post was at 12:52 AM ----------
at any rate iI pm`d you with an offer to help
Click to expand...
Click to collapse
I have the same issue. I only get the white kondle with blue fire logo. I cannot reset to the defaut factory software
Brand new kindle, just opened out of the box.
Wanted to root it, and not it's stuck on the logo screen of Kindle Fire with no animation.
It's not getting recognized by my computer, so I can't use any of the programs to try and fix it. What do i do?
have it working, but now another problem appeared. When it's connected to my computer, and recognized by adb, the bootstatus is unknown. what can i do to fix that?
I had the same problem, either get a factory cable or use the pin short trick to getinto fastboot and flash the firefirefire 1.4 bootloader within twrp
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
bearbrain said:
Brand new kindle, just opened out of the box.
Wanted to root it, and not it's stuck on the logo screen of Kindle Fire with no animation.
It's not getting recognized by my computer, so I can't use any of the programs to try and fix it. What do i do?
Click to expand...
Click to collapse
Its just your drivers pm sent
---------- Post added at 04:23 PM ---------- Previous post was at 04:07 PM ----------
read your private message or not simply leave your device connect power offf and power on your drivers should reinstall then rerun kfu and check your status also make sure you have allow installation from unknown sources checked between each reboot for sending twrp and fff if it sits waiting for device simply hold the power button down and power back on kfu will finally decide to send twrp and fff when it sorts its stupid drivers out.
Hi, I'm Aareon. I've read in multiple places that 6.3.3 can be downgraded to 6.3.2, but I've read elsewhere that 6.3.3 doesn't work with KFU (Kindle Fire Utility). From experience, I've noticed that KFU 0.9.6 doesn't work with the Boot Status of 6.3.3. It is imperative that Boot Status displays correctly in-order for the rest of the software to function appropriately.
I guess my ultimate question is; 'Am I wasting my time?'
Please, legitimate answers preferably with explanation, of some sort.
P.S. I've seen the 6.3.3 pre-rooted update, but that requires TWRP, which I've explained my plight above.
@sd_shadow
Aareon said:
Hi, I'm Aareon. I've read in multiple places that 6.3.3 can be downgraded to 6.3.2,
Click to expand...
Click to collapse
yes it can be downgraded but once connected to wifi, 6.3.3 will be downloaded, and an attempt to auto install will be made, at least once a day.
but I've read elsewhere that 6.3.3 doesn't work with KFU (Kindle Fire Utility). From experience, I've noticed that KFU 0.9.6 doesn't work with the Boot Status of 6.3.3. It is imperative that Boot Status displays correctly in-order for the rest of the software to function appropriately.
Click to expand...
Click to collapse
reported boot status is just for reference, and does not directly affect the options available, nor does it mean options will or will not work.
I guess my ultimate question is; 'Am I wasting my time?'
Click to expand...
Click to collapse
If 6.3.3 is installed and you do not have a fastboot cable, Yes you are wasting your time.
Please, legitimate answers preferably with explanation, of some sort.
P.S. I've seen the 6.3.3 pre-rooted update, but that requires TWRP, which I've explained my plight above.
@sd_shadow
Click to expand...
Click to collapse
more details and my Video posted here [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
---------- Post added at 06:36 PM ---------- Previous post was at 06:30 PM ----------
I've requested that this be moved to Amazon Kindle Fire Q and A
---------- Post added at 06:52 PM ---------- Previous post was at 06:36 PM ----------
moved: thanks @Naddict
Fastoot
sd_shadow said:
yes it can be downgraded but once connected to wifi, 6.3.3 will be downloaded, and an attempt to auto install will be made, at least once a day.
reported boot status is just for reference, and does not directly affect the options available, nor does it mean options will or will not work.
If 6.3.3 is installed and you do not have a fastboot cable, Yes you are wasting your time.
more details and my Video posted here [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only
---------- Post added at 06:36 PM ---------- Previous post was at 06:30 PM ----------
I've requested that this be moved to Amazon Kindle Fire Q and A
---------- Post added at 06:52 PM ---------- Previous post was at 06:36 PM ----------
moved: thanks @Naddict
Click to expand...
Click to collapse
Yes, I do in-fact have a fastboot cable. It came with my mail delivery purchase of N2Aos. My next question is, I don't understand why, when I tell KFU to send my Kindle into Normal mode, it says 'waiting on device' forever. Also, if I try installing TWRP after I think I've gotten myself into fastboot, it says 'can't write to bp1, panic'. This goes for every time I've tried. Have I missed a step in your tutorial, or what?
I wouldn't use KFU, just the ade/fastboot.exe files from KFU
did you watch my video?
If using KFU, try power off kindle, connect fastboot cable, to both kindle/pc, wait a sec, start KFU, select install TWRP (not root)
Aareon said:
Yes, I do in-fact have a fastboot cable. It came with my mail delivery purchase of N2Aos. My next question is, I don't understand why, when I tell KFU to send my Kindle into Normal mode, it says 'waiting on device' forever. Also, if I try installing TWRP after I think I've gotten myself into fastboot, it says 'can't write to bp1, panic'. This goes for every time I've tried. Have I missed a step in your tutorial, or what?
Click to expand...
Click to collapse
Bp1, panic is because of how KFU is trying to set the boot,ode which is no longer possible on 6.3.3 if you are using your so called fastboot cable correctly it will work. I say so called because there are alot of fakes and knockoffs out there that simply do not work. In order to get a real fastboot cable to work power off the device hook one end to the pc 2.0 usb port only then plug to the device it will go straight to fastboot. If that fails shift plus right click on the tools folder in KFU and select open command window here. In terminal type
Code:
fastboot getvar product
then insert the cable to a powered off device. If again it fails then in the terminal type
Code:
fastboot -i 0x1949 getvar product
and insert cable to powered off device. All these attempts and still nothing question the validity of your cable and get one that works from here http://forum.xda-developers.com/showthread.php?t=1392693 post#9.
Fastboot
Thepooch said:
Bp1, panic is because of how KFU is trying to set the boot,ode which is no longer possible on 6.3.3 if you are using your so called fastboot cable correctly it will work. I say so called because there are alot of fakes and knockoffs out there that simply do not work. In order to get a real fastboot cable to work power off the device hook one end to the pc 2.0 usb port only then plug to the device it will go straight to fastboot. If that fails shift plus right click on the tools folder in KFU and select open command window here. In terminal type
Code:
fastboot getvar product
then insert the cable to a powered off device. If again it fails then in the terminal type
Code:
fastboot -i 0x1949 getvar product
and insert cable to powered off device. All these attempts and still nothing question the validity of your cable and get one that works from here http://forum.xda-developers.com/showthread.php?t=1392693 post#9.
Click to expand...
Click to collapse
I got my fastboot cable from buying N2Aos off of Amazon. I know that it is legit because others have done the same and have had no problems.
I appreciate your help and will try these things. Thanks
Aareon said:
I got my fastboot cable from buying N2Aos off of Amazon. I know that it is legit because others have done the same and have had no problems.
I appreciate your help and will try these things. Thanks
Click to expand...
Click to collapse
If you say so doesn`t mean that it`s legit for your device so run through the steps I pointed out and test it.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
If your using KFU 0.9.6 that`s outdated as well http://forum.xda-developers.com/showthread.php?t=2192818 0.9.9 is actually more up to date.
Fastboot
Thepooch said:
If you say so doesn`t mean that it`s legit for your device so run through the steps I pointed out and test it.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
If your using KFU 0.9.6 that`s outdated as well http://forum.xda-developers.com/showthread.php?t=2192818 0.9.9 is actually more up to date.
Click to expand...
Click to collapse
Is there a way to test, besides using the kindle, whether a fastboot cable works or not?
Is this what you bought? N2Aos(TM) - Convert your Kindle Fire into a Jelly Bean 4.2.2 Android Tablet (Includes USB Cable)
If so, that is not a Fastboot cable
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
just a standard usb data cable.
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
if it is a Fastboot cable, when you power off, connect fastboot cable to Kindle then PC, Kindle will start to boot, and stop at Kindle Fire Boot Logo (except it actually fastboot mode). and stay there.
Drivers on the pc will not matter at this point, because it the power to 5th pin that causes it to boot to fastboot mode.
sd_shadow said:
Is this what you bought? N2Aos(TM) - Convert your Kindle Fire into a Jelly Bean 4.2.2 Android Tablet (Includes USB Cable)
If so, that is not a Fastboot cable
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
just a standard usb data cable.
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
if it is a Fastboot cable, when you power off, connect fastboot cable to Kindle then PC, Kindle will start to boot, and stop at Kindle Fire Boot Logo (except it actually fastboot mode). and stay there.
Drivers on the pc will not matter at this point, because it the power to 5th pin that causes it to boot to fastboot mode.
Click to expand...
Click to collapse
How do you know it is a standard usb cable. On the package it said fastboot cable included.
Is this correct? Without USB plugged, during boot, my Kindle loads the 'kindle fire' splash. It then sticks there for about 2-3 seconds, then it dims. 2-3 seconds later, the screen flashes, and again 2-3 seconds later it flashes again. 2-3 seconds later the 'shine marquee' proceeds. About 60 seconds later the unlock screen shows up. For some reason, even after plugging in my 'fastboot cable' it does the same. But I noticed that the first time the screen flashes, some small white text pops-up quickly and then disappears on the right side of the screen.
Aareon said:
Is this correct? Without USB plugged, during boot, my Kindle loads the 'kindle fire' splash. It then sticks there for about 2-3 seconds, then it dims. 2-3 seconds later, the screen flashes, and again 2-3 seconds later it flashes again. 2-3 seconds later the 'shine marquee' proceeds. About 60 seconds later the unlock screen shows up. For some reason, even after plugging in my 'fastboot cable' it does the same. But I noticed that the first time the screen flashes, some small white text pops-up quickly and then disappears on the right side of the screen.
Click to expand...
Click to collapse
No, that is not correct. If it is a fastboot cable, kindle will not boot to stock rom.
sd_shadow said:
No, that is not correct. If it is a fastboot cable, kindle will not boot to stock rom.
Click to expand...
Click to collapse
You're right. I'm getting a refund for my N2Aos as we speak. Buying a fastboot cable.
http://forum.xda-developers.com/showthread.php?t=2814955
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Sent from my DROIDX using Tapatalk
Hey Guys -
So I'm starting to get a little desperate. I had Lineage 14.1 with Gapps 7.1 on a kindle fire hd 8.9. Was having some trouble with google play games and couldn't get an apk to actually download, so I did what any moron would do and decided I would try to go back to stock OS and start over. Went into TWRP, flashed my recovery images, but forgot to wipe before I rebooted.
So now I have no recovery and no fastboot (possibly???). When I uninstall ALL the drivers, I can get the computer to recognize the device for only a second or two, but in that two seconds, the device manager collapses and doesn't repopulate until after the device is no longer recognized - I'm running windows 10. Under hiddden devices it shows up as a JEM-PVT-Prod-04, but it shows with a question mark. I can access fastboot commands, but "fastboot -i 0x1949 getvar product" only shows it as waiting for device. I'm currently stuck because it will boot to the orange and white kindle fire logo, blink, then display the same logo but with this grey line running down the side.
Does anyone have any idea as to how I can at least get fastboot going? I can take it from there, but it appears that I can't do much of anything because I can't even access it from the device manager. I'm thinking about running linux or trying it on a mac to see if the device manager has the same issue with populating.
Thanks
YES, i can help.
you need EITHER:
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA
OR
Minimal ADB and Fastboot (a few megs) from here @ X-DA
launch the app, and when it says "waiting on device" plug the usb cable into the ALREADY OFF tablet.
this is the only way i could get fastboot to work (and be "installed" in windows) on my 32 gig model. i have the "red screen of death" and these 2 apps are the only ones i could get to work. i WANT to try "kindle fire first aid" but ALL the links here for that app are DEAD.
Did you ever get your kindle working again and if so please could you share how you did it I have the very same problem. any help you might have so far?
Thanks so much. Robert
Yes I found the secret steps contact me if you still need it
My reply is correct.
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA WILL fix you.
rmontgo3Denver said:
Yes I found the secret steps contact me if you still need it
Click to expand...
Click to collapse
can you help me?
---------- Post added at 06:36 PM ---------- Previous post was at 06:23 PM ----------
compjan said:
My reply is correct.
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA WILL fix you.
Click to expand...
Click to collapse
Where to find this file? cant find any links
ichwill said:
can you help me?
---------- Post added at 06:36 PM ---------- Previous post was at 06:23 PM ----------
Where to find this file? cant find any links
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2011126
A simple search for KFHD would have answered your question.
I ended up using linux FWUL cause the driver support in windows is ****. I tried KFHD-SRT and flashed the boot system and recovery manually but my device may not work as it red screened and kept entering fast boot.
Care to share this secret? Mine boots then goes to red screen, will not get to fastboot.