i live in australia, and got a kindle fire for my b'day, and wanted to access the features that arnt allowed outside the US. my first search i came across rooting it, and it seemed straight forward, the instructions, which was for kindle fire utility. i installed the drivers, then did run.bat, that worked and detected the kindle. then it said to go to bootmode menu, then install permanent root with superuser. it lasted about 2 seconds then it rebooted the kindle. thats it. unless i misread something. it looked exactly the same as before, i didnt know what to expect, but some hint that something had changed, so i figured it didnt work. then i saw the bootmode menu, and selected normal, and that just reset it, then chose fastboot, not knowing what it did. so i tried that. now my kindle isnt detected by the pc at all, it just says kindlefire on the screen, and the power light is orange.
most of the fixes i have come across all start with "we assume you have this or this installed on the kindle, and that it is detected in some way by the computer". but it isnt being detected at all. i saw the fireusb thing, with ubuntu, i attempted that, but it didnt seem to recognise the fk file, which was only 9mb, it was the only file the instructions said to take, and that its supposed to unpack to more tools to manage it and get it to register that the device is plugged in.
then the only thing else i could try was opening the back of it, and doing the shorting out thing, then plugging it in, but KFU didnt detect it and not sure what else to try. i am a complete noob at this i know, so i dont know where to go from here.
edit: turns out the kindle doesnt like being detected in 3.0 usb, or usb hubs. so if you are trying to get it to detect, use the ones in the back of the pc lol... soo much wasted time on this over such a simple thing, but im glad it was a simple mistake, and not a major problem. though now i have the issue of having small sratched and stuff on the side when i opened the case, but oh well, learn from my mistakes!
have you tryed holding the power button for like 20 seconds and completely powering it off then powering it back on? Chances are your stuck in fastboot many people lately have had this happen so your not alone. Some say to power it off have the kindle fire utility window open plug your kindle in it should power back on then recheck status. Look in device manager and see how it appears there windows is terrible with drivers when this happens it will try to install what it thinks best even if the device is unknown rendering adb useless until the driver is reinstalled correctly. Most the time this is not enough to set the bootmode back to normal because it cannot detect your device correctly. http://forum.xda-developers.com/showthread.php?t=1670405 this may help but its not the only thing that can be done. If some of the files actually did get pushed to your device such as fff the bootmode can be changed via the bootloader. Try the power down thing see what you get and post back.
---------- Post added at 01:03 AM ---------- Previous post was at 12:12 AM ----------
also look at this thread http://forum.xda-developers.com/showthread.php?t=1670300
Another thing simply just rooting your device does not change how it appears its not until you install twrp and fff that it changes there are simple ways to do that first we need to get your boot mode corrected and ensure you are rooted then the rest can get sorted out. Check how your device is listed in device manager first.
sorry for the delay. spent all day just trying to install ubuntu, then connecting to the internet wirelessly, seems to have a lot of issues. anyway, in the end i got it all set up, followed that guide, then ran firekit, but still not detected. in windows and ubuntu, when its plugged in by usb, nothing at all shows up in device manager, or lsusb. ive tried doing the short trick, then plugging it in, still doesnt get detected. and honestly i think when i thought i rooted it, i may have misclicked and instead of selecting instant permanent root or whatever that command was, i just did a normal boot, so im pretty sure i selected fastboot for a stock kindle. i know the usb cord works cause i use it for my phone.
adb devices doesnt detect it either. i got all the doesnloads from the link you posted, would they all be up to date? also the adb_usb.ini file, had to get online, but not sure if that matters.
In Linux, type
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
...and make sure you have the following:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Reboot to save any changes you've made and check "lsusb" again.
i added both those rules, one of which was already in there, but it still isnt being detected. typing lsusb, then up and enter repeatedly as i plug it in doesnt show any changes at all, its not being detected.
While unplugged, type
Code:
udevadm monitor --environment
Plug it back in and see if you get a result.
sadly not. tried plugging other things in, they all appeared, also my phone with the same cord. but nothing at all when i tried the kindle, with it powered off when plugging it in, and with the shorting out thing, nothing at all. i dont understand how booting in fastboot by accident, with a stock kindle, could make it not be detected at all, ive read people causing worse things getting it to at least be picked up. im pretty sure thats all i did, i cant think of how i could of done anything worse.
That's interesting...I'm having the same problem with mine but I was led to believe it was my VM causing the problem.
So, just to make sure...
Are you using a VM Linux install or USB or other?
Have you tried multiple usb ports?
Do you have FireFireFire installed and if so, what version are you using? (If you're not sure, what does your boot logo look like?)
What Linux distro/version are you using?
this is the first time ive ventured outside windows, so not sure what you mean by vm, but i installed ubuntu with a disc, to a second hard drive that i had in my comp.
and nope, dont have firefirefire installed, im pretty sure its just a stock kindle still, just stuck in fastboot by mistake, and not being detected by any usb port.
also, would a factory cable work? if its makes it boot differently, you would think it would? i really suck at making things, but http://forum.xda-developers.com/showpost.php?p=23049902&postcount=254 is selling them. sure it would probably take 2 -3 weeks, but if it works then thats better then not using it forever lol. and if i get it fixed before it even arrives, well, cant complain about that.
A factory cable will only help if you can get Linux to detect your device. Considering you can't get Linux to detect any USB event when plugging your Kindle in, it most likely points to a problem with your Linux install.
It would be very helpful to know what version of Ubuntu you are using.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
though there is a few updates in theupdate manager. but last time i installed them, it completely disabled my wireless adapter and ened up reinstalling ubuntu to get it to work again cause i couldnt figure out how to get it detected again. but redownloading it all now to see if its any different. i hope it is just a problem with the install, at least thats something i can work on.
at soupmagnets suggestion, i made a liveUSB, which i had tried to do earlier, but didnt succeed, where as now it does work, im pretty sure i have the drivers now installed, but not sure where to go from here, with it still not being detected at all.
haaa... im an idiot. just putting that out there. ok, so i got the kindle detected. turns out it was the usb ports. one was usb 3.0, and the others were in a hub, which apparently the kindle doesnt like. i got frustrated and plugged it into the back of the pc, and it is now unknown device in device manager. thinking i should go back into ubuntu, see if its also detected there, and go from there
oh yeah the usb is a problem and use 2.0 and go back to ubuntu you will see its detected in a couple hours Im gonna retest soups script for udev rules but I think you will have success now
---------- Post added at 11:20 PM ---------- Previous post was at 11:16 PM ----------
in fact I think using 3.0 usb is quite dangerous
i didnt go back to ubuntu, i just used KFU again, and just tried doing normal boot. and it worked. its back up and working. ill try rooting it again now, being more careful this time, sorry for the waste of time, but thanks to soupmagnet for helping. now that its back to stock, i do stil lwant to root it, and now with ubuntu installed, what is the best noob friendly guide to use to just get the basic things up and running.
yayyy Im glad you got it goin check allow installation from unknown sources under device and install twrp first then fff bootloader no need to root flash a rom and gapps once your familiar all roms are rooted
You can select these options in kfu watch the dialogue on the screen you can see the files downloading and getting pushed to your kindle just make sure your connected to the net I suggest running one of the options without your device plugged in first do a reboot on your computer plug your kindle in check for adb online boot status normal and go for it
---------- Post added at 11:38 PM ---------- Previous post was at 11:23 PM ----------
or go this route http://forum.xda-developers.com/showthread.php?p=24129239
Related
A few of you know me already from my thread where I asked a million questions before attempting to install a custom ROM on my new KF. Well, it still went completely south somehow, so here I am.
So, I'm stuck with the stock Kindle Fire logo on the screen, and and can't get it to go anywhere.
Here's what I did:
Downloaded KFU, installed the drivers, plugged in the Kindle,and ran KFU. ADB status online, boot status 4000.....so everything seemed good, from what I've learned. Also looked in Device manager, and it showed up as Android phone, or whatever it's supposed to say. I figure I'm good to go.
My plan is to install TWRP,FFF, and root it, then boot into TWRP, and flash the ROM. The first thing I did(and it seems wrong now) was try to install FFF, instead of TWRP. I think that's the wrong order, but not totally sure if it matters, but it's my assumption that it does.
So, as soon as I sent the command, for some reason, my computer got this blue screen with some message that I didn't have time to read, because it restarted right after. It still said everything looked good, so I tried again to install FFF. I think the "crash" was just coincidental, because it didn't act like that the second time, but whatever.
Anyway.......said it was installing FFF, and then it went to <waiting for device>
I figured ...ok...need to wait.
After about 10 minutes of waiting, I held the power button down until it turned off, then turned it back on, because someone said that's what you should do if this happens. Well, essentially.....since then, I've not seen anything but the Kindle Fire logo on the screen, and it feels like I've tried everything. A forum member spent some time on the phone with me, and we tried everything he knew.....no luck.
At one point, someone told me to uninstall the drivers and reinstall them, which I did, but upon reinstalling them, nothing changed, and the computer no longer even recognizes it being plugged in as a USB device, the drivers don't show now in device manager, even though I told KFU to reinstall them. To me that's weird, and seems like a major problem, because the computer isn't "seeing" the device, but that's mu humble opinion. I'm at a total loss, and would sure appreciate some help bringing this thing back.
Thanks....immensely, in advance!
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
If nothing you do results in any change, it's time to give up on Windows and create a Linux LiveUSB. Linux is extremely stable and pretty easy to set up and send adb/fastboot commands with. If you do decide to take that route, Ubuntu is pretty much the standard and version10.4 generally works better than later versions.
soupmagnet said:
Make sure you reboot your computer. Also if you can, switch USB ports. Pay attention to your device manager when doing so. Trying on a different computer can also be helpful.
Click to expand...
Click to collapse
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
soulweeper51 said:
I rebooted, switched ports, and it didn't seem to change. The computer didn't even recognize it being plugged in. I just plugged in a flash drive, just for fun, and got the message that USB device was detected, so it's not the computer....to me anyway. Also tried plugging the Kindle into my wife's older Dell, and it gave me a message that a USB device connected to the computer wasn't working properly.
Click to expand...
Click to collapse
Use the KFU on the laptop to install the drivers and see if that makes a difference.
soupmagnet said:
Use the KFU on the laptop to install the drivers and see if that makes a difference.
Click to expand...
Click to collapse
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
soulweeper51 said:
The older Dell is a desktop, is that what you meant? Just try installing drivers via KFU from there?
Click to expand...
Click to collapse
Yeah, that's what I meant.
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
kinfauns said:
Why Windows fails to install/load the drivers for fastboot is really a mystery to me. It obviously has the adb part of it working or you wouldn't be in fastboot in the first place.
You need to provide details on exactly what's going on when Windows attempts to load drivers.
Turn up the sound volume on your computer. With the device connected to your PC, turn it (the Kindle Fire) off and back on. When the device puts itself into fastboot, Windows will provide a series of two tones.
low->high means it's connecting
high->low means it's disconnecting.
If you get the low->high tones without the high->low tones following them up, you should be seeing SOMETHING change in the device manager. Don't gloss over the details with "Android phone whatever" but report what you see. The device drivers post in the beginner's guide has details on what should appear in the device manager.
EDIT: Also do this...
http://support.microsoft.com/kb/315539
Even with the device disconnected, you should see 4 devices under "Android Phone" if you've managed to get those device drivers installed from KFU.
Click to expand...
Click to collapse
I just did exactly what you said......plugged it in, turned it off. Turned volume all the way up, turned it on....no sound of any kind.
The weird part is when I first installed the drivers, I checked it by plugging the device in, and had adb status online, staus 4000, plus I went to the device manager, and I remember two things that said android phone. One said android phone, and the other said android something or other. And, it was seeing the device and everything seemed hunky dory, and I guess at that time it was???
I did uninstall and reinstall the drivers via KFU, and it says it's installing them, but never again have I seen anything in device manger that says Android anything. That is just wrong to me.
Personally I think you're spinning your wheels with Windows and causing yourself more headache than needed.
Create a bootable Linux LiveUSB on a thumb drive with Ubuntu 10.4 and get Android-SDK installed on it.
[Edit:]fixed spell check fail
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first.
Click to expand...
Click to collapse
Trust me.....I realized not too long after that I had done the wrong order. I even had a note to myself right here that said:
TWRP
FFF
Root
For the life of me, I don't know why I did FFF first.
All the questions I asked, and as anal retentive as I am, I totally screwed that part up, which may be the entire problem. Trust me.......I'm pissed.
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
kinfauns said:
I'm starting to think you've killed your bootloader or got a bad flash when your machine crashed. This is why I suggested you flash your recovery first, because you can still fix that through the bootloader if a recovery flash goes wrong.
In any case, I think soupmagnet is right... FireKit is probably the next thing you should try if Windows won't even recognize the device being there. If on top of that, I'm right about your bootloader, you're going to have to crack your case open and put it into USB boot mode because Firekit won't be able to fix that on its own.
Click to expand...
Click to collapse
Can I ask what Firekit is?
Firekit is a tool used to fix major problems easily. I would use it as a last resort because there isn't a command for just installing TWRP without the bootloader.. Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
soupmagnet said:
You should at the very least, set up the Android-SDK on your LinuxUSB and check to see if it's just a driver issue you're dealing with. Linux handles the drivers for Android devices much better, and in most cases, easier than with Windows.
Click to expand...
Click to collapse
I'll just be honest and tell you that I have no idea what you're talking about. I don't mean that in a bad way.......I'm not some computer whiz that speaks the same language as a lot of you. Right now I wish I had left the freakin thing alone with Go Launcher Ex and called it a day. I'm really pissed off right now....that's not your fault.
I don't suppose that Factory Cable will do anything for this situation, correct? The guy said he will send it ASAP FWIW.
Had to ask.
soupmagnet said:
Get your Android-SDK installed and I'll help you with the drivers and platform-tools install.
Click to expand...
Click to collapse
Can you kindly tell me how I get to the point you're speaking of?
Sorry....this stuff is foreign language to me.
Do I have to install ubuntu on my computer?
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
soupmagnet said:
Take a breath...relax. We'll walk you through it.
Get a thumb drive w/approximately 1Gb of storage and create a bootable LiveUSB.
Click to expand...
Click to collapse
Should I trust this method?
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
I know NOTHING about this.
EDIT: Never mind.......that's another OS......damnit!
Can't I just play dumb, and send it back? I hate to say that, but.....
I guess this is it
http://www.linuxliveusb.com/en/download
^See.......trying as hard as I can to keep a good attitude.
That will work. Download Ubuntu 10.4
Alright folks, I would like to start off with a little introduction:
I'm extremely new to the rooting scene, i've been jailbreaking iphones and ipods since day one. That being said, I probably should have spent more time researching this technique before I went through with it.
Fast forward to today:
I tried rooting my device awhile back, wasn't a 100% successful and I really didn't have the time to work it out. I did have FFF installed and the next window (which i'm not exactly sure what it's called, which allowed me to boot in various moods and such)
Earlier today I got stuck in a boot loop, where my kindle would turn off as soon as i restarted it, and after i selected normal boot mode. I decided it would be a good idea to try a different boot option, so i tried the FF boot, which completely ruined my day.
My current situation is as follows:
I'm currently stuck on the first FFF screen (yellow triangle, with the green light on), i can do nothing else from that screen except hard (cold) reboots. When i plug my kindle in (Mac, windows 7, windows XP), the device is not recognized and i get zero response. I've tried a decent amount of suggestions on this forum, including Kindle fire unbrick (Which can somehow see that there adb is installed, but the bootmode is unknown)
Help out of this current situation would be wonderful. I'm really in a jam here.
Sounds like you are stuck in fastboot and you might have a dead battery too.
You should read this...
http://forum.xda-developers.com/showthread.php?t=1552547
1st post for background information, 2nd post for making sure your device drivers are loading/working, and the 3rd post for fastboot and adb commands. You'll probably need to use fastboot to change the bootmode back to normal.
This one...
http://forum.xda-developers.com/showthread.php?t=1623244
address dead battery problems. You might be affect this by this one as well.
Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?
B4CKlash said:
Thanks for the reply,
I read pieces of the first one before I posted on this thread. The KF was 100% charged and i only used it for about 15mins before the whole crashing problem occurred, so i highly doubt it's a low battery issue.
The screen that i'm stuck on is actually the recovery screen. After reading the article in it's entirety, i'm still not exactly sure what to do. My problem is that i cannot get my kindle fire to be recognized as any type of USB device on any type of computer. Wouldn't that issue need to be addressed before i can go about doing anything else? Or will drivers see what my computer think is not there?
Click to expand...
Click to collapse
What do you mean by recovery screen? Because your first post said FFF and that's your bootloader. If the yellow triangle boot logo comes up and that's all that the display does (doesn't go black and redisplay the boot logo), then it's in fastboot mode. Windows should give you an indication that it's connecting with a series of 2 connection beeps (low->high tone) without a following set of disconnect beeps (high->low tone). The device manager will show something new in the list (this is covered in post #2 in the first URL I pasted for you).
Yes, you need to get something to get recognized by your computer then you need to install the proper drivers for it. Look at post #2 again, and see if you can figure out what device is appearing in the list and get the drivers loaded for it. If you get absolutely nothing, there's something wrong with the bootloader, your USB cable, USB port, or computer in general and it's a bigger problem.
If nothing happens on your computer, find another one and hook it up there. You might also look at this...
http://forum.xda-developers.com/showthread.php?t=1430038
and see if Linux can help you.
I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?
B4CKlash said:
I'm sorry, I was mistaken. I am stuck in Fastboot mode, The one with the yellow triangle. I get zero indication from Windows device manager list, or beeps (same on my mac). I have tried 3 different cables, so i highly doubt that's the problem either.
My next step is the linux distro, which i will get back to you with when I get everything installed. My only concern is that the linux distribution isn't going to recognize the USB either (seeing as 2 other operating systems haven't) and that there's something inherently wrong with my kindle. In which case i'm ****ed? or is there any chance that amazon will take it back?
Click to expand...
Click to collapse
Windows will be the only one that of the three that will beep at you. There's a better chance of you getting something done with Linux, but it's starting to sound like a bootloader problem to me. There's another user with a similar problem to yours and he's basically where you are now. Both of you might have to open up the case and get it to USB boot mode where you can upload a bootloader to it through USB. Try Firekit and see if it gets anywhere.
So, Ive been searching for over 6 hours now and I really cant seem to root my kindle fire. I tried basically everything, and when things went wrong, I just deleted the files and started again. On my last try, I was able to fastboot it (at least I think so). When I ran KFU, ADB was online and Boot: 4002.
When I tried to root it always got stuck trying to find twrd.img. Then I tried option number 4, Installing Clockwork Recovery (because option number 3 was a dead end) and twrd.img was installed. But everytime something seemed to go right, the process wouldnt finish, it would just be <waiting for device>. I thought my problems would be over, so I tried to root it again. Now whenever I turn on the device, KFU is unable to locate my kindle, and it doenst appear on the device managing tab either. Even using the kindleunbrick.bat that worked for me the last times, it just gets stuck at <waiting for device>. ADB is offline and Boot: Unknown for now.
I really need to root my kindle because I dont live in America, so I dont have access to most stuff. I already changed the language when installing the driver, however, everytime I hooked my kindle up, a windows message would pop out saying that there was a problem with the driver, but when I went to device managing tab and tried to uptade the driver to "user\.android" it always came back as updated.
I am really noob at this, but I have read all the guides I found and something always went wrong. I hope someone can help me with this, please.
Thanks
Is your kindle turning on? If I could suggest you should put off anymore attempts to root your device till you know precisely what your doing and why. My biggest guess right now is your drivers are the greatest pitfall. You seriously don't want anything going wrong with them in the process of sending recoveries boot loaders or rooting you will end up with a really fancy paperweight. Privy to to attempting anymore you need to know that your drivers are functioning 100%.The fact that you pushed cwmr to your device after twrp should hurt a thing hopefully one should overwrite the other if all goes well . Since rooting is the primary goal go with that until you have verified root then recovery and bootloader can be done easily later with safer methods. Hold off awhile as long as your device will boot until you have found the knowledge and support to make it happen right. Start here http://forum.xda-developers.com/showthread.php?t=1552547 then go here http://forum.xda-developers.com/showthread.php?t=1638452 plan to use this method to root http://forum.xda-developers.com/showthread.php?t=1568340 ask a lot of questions don't be hasty or you will spend a lot of time trying to fix it instead of enjoying it.
As I said, I read all those guides already. I can use my kindle normally, but when I connect it to my computer, it is unrecognized. I tried every method I found to root, even though I just wanted to watch stuff and download a few games for my spare time(my intention was to watch stuff from premium features, but Im not really sure if root will allow me to do that from a foreign country*, so Im a little hesitant to extend premium).
I guess I wont try anything else for now because my main goal was reading, and this I can still do, but I am puzzled with the fact that I was unable to root it. Ill try to understand a bit more (hopefully with some tips). Thanks
*Geographical restrictions
OK well youve read the guides but in what you say it appears you are doing some of the wrong things why would you unbrick if your not bricked? Your drivers are your only issue as of this point but your methods are pushing you close to bricking your kindle. I would like to see you succeed in rooting your device and avoid bricking it.
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
When your around we can try to get your drivers working
It would be nice to know what os your running on your computer. If you are on windows 7 use system restore to roll your computer back to a date before you started messing with the drivers or anything. Once it completes plug your kindle into your computer check to see if you can access the SD card contents and if it appears as a kindle in your device manager. Important now if all is good unplug your kindle and run the .bat file that comes with kfu. Then plug your kindle in let windows install the driver. Open up kfu find the tools folder shift plus right click select open command window here. Then type adb devices if its followed by a string of numbers this shows your kindle connected via adb . At this point you should obtain some help from some of the pros here at xda at fastboot and adb commands to safely root your kindle. If you decline and still wish to use kfu then only select install permenant root. If at any point in this process it fails and you loose adb connection do not unplug your kindle run the driver file again then recheck device status with kfu I believe its option 0 to see if your back online again. Pay attention to the dialogue that takes place in the kfu window you see verbatim that says failed or permission denied then quit after that. One important thing is you need to allow installation from unknown sources in the kindle settings on the kindle under device or it won't push the required files anyway.Wait to install twrp and fff until later there are easier safer methods. If your kindle hangs for a long time at the kindle fire logo select boot mode normal in kfu before unplugging. If at anytime kfu states waiting for device do not unplug it rather power it completely off then power it back on while connected .
---------- Post added at 01:53 AM ---------- Previous post was at 01:32 AM ----------
Just a side note I have rooted 4 different times with kfu without a single failure or mishap including the ones you are experiencing. I'm inclined to feel that relates mostly to your computer and drivers which makes kfu an unsafe approach for you I'm not responsible If you brick it!!!
I unbricked my device before I even came here, I tried an youtube tutorial and then it got stuck on the kindle fire logo, but after I unbricked it, it was fine. I know that something is going wrong, but Im following step-by-step the guides (at least I think so). As I said, everything was going correctly, ADB was online, Boot:4002, but when I tried to root it would be on an endless search for the file twrp.img, and after I succesfully downloaded it (I guess), my computer is unable to find my Kindle.
I run Windows 7, but it isnt properly activated (my room mate threw out the serial code), I dont know if this would interfeer in any way. When I conect the kindle, it appears to be in USB mode and says that I can transfer files, but my computer wont even find it. Ill try to restore my computer now and then Ill come back.
I know that doing this is my responsibility, but not being able to download apps is pretty annoying, so I have to keep trying.
If you can get adb status online then, why don't you install TWRP manually? Or use the "smirkit"?
Once you get recovery installed, you're set.
Also, be sure to "disconnect" from USB storage mode before trying to use adb commands or they won't work.
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Shift+right click your KFU "tools" folder and select "Open command window here"
From there, enter:
Code:
adb devices
If the output is something like:
Code:
List of devices connected
123456789ABCDEF
then you can install TWRP
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
If the output is:
Code:
List of devices connected
(null)
then you need to reinstall your drivers
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Thank everyone that helped me, I managed it!
Actually I was doing everything right, but I guess the problem was my computer, because when my girlfriend came over I tried connecting it to her netbook and it recognized my kindle. I just downloaded the kfu, installed drivers, reconected kindle and let it update, ran KFU and selected option 2. All done now
I have no idea why this didnt work before, but at least now I can really enjoy my kindle.
Thanks again!
saybhausd said:
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Click to expand...
Click to collapse
Not system recovery bud system restore two different things go to accessories system tools system restore choose a date chose to restore to that point. System recovery is way way different. Glad you got it going
I was given a "bricked" kindle to take a look at last week. Here is the story I was given.
User installed a custom rom, but it was for a lower version (didnt fully understand this)
Afterwards it locks on the kindle fire logo during boot.
User made a factory cable to restore the unit, and now anytime ANY usb is plugged into the device it shuts off immediately.
I tried opening the device and shorting the required pins, but plugging in the usb doesnt do anything. It appears to be charged, but I have no way of knowing.
It doesnt show as anything in device manager (it looks to be fully off)
Pressing the power button still gets it to start and hang at the kindle logo.
My guess is the factory cable was made incorrectly and shorted the usb board but I figured I would see what others thought.
Thanks
Any opinions?
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
narume said:
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
Click to expand...
Click to collapse
Thanks for the thought, but nothing shows in device manager. I believe this is due to the kindle shutting off the second you plug any usb into it.
bump?
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Thepooch said:
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Click to expand...
Click to collapse
I'll definitely try the factory cable again (the user tried this, but who knows)
But as far as the device not being recognized... Like I said, the second you plug it into usb (either computer, or power plug) it shuts off.
Its not that I get a windows notification for "not recognized" windows doesnt see it period.
it should not turn your device off it should appear stuck at the logo like I said sounds like a bad build guess you misunderstood
---------- Post added at 06:45 PM ---------- Previous post was at 06:38 PM ----------
only use a 2.0 usb port and try it from the device in an off position
I know this has been covered thoroughly in this forum multiple times, and I have really tried to read as many threads as possible before asking.
I rooted my device months ago and finally got a Nexus 7 and want to give my KF to my kids but wanted it stock first. I must have done something in TWRP that removed my bootloader.
I have tried the unbrick tool, I ordered a factory cable from Skorpn (awesome work btw) and by using KFU, my PC can finally see my Kindle.
The problem I'm having is that none of the commands are working and it looks like the bootloader is either bad or completely gone.
It used to turn on and the logo stayed bright. After I used the factory cable it now turns on, blinks, and goes dim.
All the drivers loaded correctly and KFU see's it online.
When I try to reinstall TWRP through KFU it downloads, but is stuck at waiting for device.
***********************************************
* Activating Fastboot (4002) *
***********************************************
2433 KB/s (510876 bytes in 0.205s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
After reading further, I think I formatted too much and wiped the SD card partition. It doesn't seem like there is a bootloader at all.
Did I miss something in all the reading?
Thanks.
So after doing even further reading I found
http://forum.xda-developers.com/showthread.php?t=1638452
I connected the factory cable and the logo is now staying brightly lit, so I assume it's in FB Mode.
I downloaded TWRP based on the link and FFF, but now I don't know what to do with them.
I went to ADB's site and installed SDK, but I'm not sure how to get the cmd portion to sideload TWRP and then FFF.
I'm doing my best to following along in the instructions and went to the ADB site and installed SDK.
I saved it to my C drive but when I try to do the following, along with "adb devices,
c:\Android\android-sdk-windows>
I get:
'adb' is not recognized as an internal or external command,
operable program or batch file.
Update:
NVM, I had it in the wrong directory.
Once I got that figured out, I did an "adb devices" and no devices came back. Of course I have the factory cable connected and I'm not sure if that matters.
Update:
Ok, now I used a standard USB and it sees my device, but now the logo went back to going dim after reboot.
So it looks like my problem is fairly common, however forum searches don't seem to be helping.
It looks like I wiped too much in TWRP.
Now that I finally figured out ADB, I'm confused about the factory cable.
When it's connected ADB does not see my device but the logo is lit bright yellow. When I use a standard cable ADB sees the device but the turns on and goes dim but the logo is still there.
I've downloaded the ZIP files for TWP and FFF, but I can't seem to figure out how to side load them no matter what I do.
I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.
Copcheck said:
I'm about to give up on this.
I decided to go the Soupkit rout and installed ubuntu 11.10 and got my PC to boot to USB.
I followed all the directions but my device is always offline. The only thing I can think of is that the 3rd step says to reboot, when I reboot Soupkit is gone and I have to download it again. When I download it, I save it, drag it to the desktop and extract it there and then run in terminal, use option 1 and then option 2.
I realize forums contain a ton of duplicate posts but I really tried to research and follow all the guides before posting.
Does anyone have any advice?
Update:
Realized I forgot to add persistence to the LiveUSB drive. I'm going to try again.
Click to expand...
Click to collapse
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.
leroy329 said:
Let me know if this soup kit route works. we have the exact same problem going on here... ill live install ubuntu as well, Ill try my hand here shortly, and give you feedback on my testing.
Click to expand...
Click to collapse
No luck with adding persistence.
I get everything to to boot in Linux, followed all the instructions, but Soupkit still does not see my Kindle.
I've tried my factory cable and a regular cable. No luck
Some has changed though because now my Kindle logo light is solid bright whereas before it would blink and dim.
Good luck to you!
Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.
Copcheck said:
Well I've had a great dialogue with myself, but I fixed it by accident.
You guys do awesome work and I know its frustrating when people ask repeat questions. I thought I had truly given it my best shot before asking, but in the end it was an accident that seem to have fixed it, that and Skorpns factory cable LOL.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
KFU said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
Plugged in a standard USB
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Can anyone shed light on why KFU said offline but it still took a root?
Also, regarding the factory cable, I read a ton of material on when to use it and why, but not really how. What I mean is when to plug in and when to revert to the standard cable. If I missed that, my apologies.
Click to expand...
Click to collapse
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
When I unplugged the factory cable from the PC and the KF, I could have done 1 of 2 things. Powercycle the KF and hold the power button down to get into TWRP or use a regular USB to side load a ROM and then load it.
Good luck to you, I hope you get it figured out.
Remi85 said:
wow im def. gonna try this seeing how we have similar issues with my kindle fire being recognized with a reg usb and online in kfu but with a boot status of unknown and then not seeing it and status being offline when i plus in the factory cable. also with the regular cables it boots to the cm10 boot logo and then with the factory cable it stays at the kindlefire orange and white cable. only thing im confused on is where you say you
"I then unplugged my factory cable from both the PC and KF and booted the KF into recovery"
how did you reboot to recovery? or this was automatic after option 2? thanks and its awesome you were pretty much able to figure this out on your own. i feel i wont have the same luck
Click to expand...
Click to collapse
If you're getting the Kindle Fire orange and white, you haven't installed the new bootloader. Rerun KFU with the Kindle in Fastboot (using Cable) and select install FireFireFire. This will give you the bootloader to reboot to recovery.
Edit: You might as well reinstall TWRP while you're at it, just to be safe.