Trying to root Kindle Fire, first try. - Kindle Fire Q&A, Help & Troubleshooting

So, I've found an array of guides both on and off the forums and I've followed a host of them. I am trying to obtain root and Superuser via Kindle Fire Utility. I've installed the drivers a number of ways including through the Android SDK, KFU and by unplugging and plugging it back in. Apparently the drivers are installed correctly because when I check in the device manager, the Kindle is listed as Android Phone and then under the dropdown as Android ADB Interface. However, no matter what I do, when I run the run.bat file in KFU the device is listed as offline and whenever I try to do the adb list the Kindle isn't showing up there either. I believe it is because I get a syntax error whenever I launch KFU before the actual KFU screen up saying that the location C:\User\.android doesn't exist. So, I'll list all the steps that I can remember I've done over the past 16 hours or so.
1) Downloaded the Android SDK and Java JDK (I think it's called...either way, I have updated JRE and DK)
2) Unplugged the Kindle Fire which is firmware 6.3.1 which was listed as Kindle in device manager and ran the install_drivers.bat file.
3) Confirmed via device manager that the fire is actually listed as Android ADB Interface
4) Did an adb kill
5) Deleted drivers once confirmed KFU couldn't find the device online
6) Reinstalled drivers via the KFU drivers folder
7) Repeated steps 3-5 then reinstalled the drivers via the Android SDK provided USB driver file
8) Repeated steps 3-5
And now I'm at a loss, I have no idea what else to do. I've rooted multiple phones as well as gotten homebrew running on Wii's and PSP's but this one is stumping me. Any advice or assistance would be greatly appreciated. Also, please don't kneejerk response and send me back to the thread explaining how to get the drivers running via KFU because I've done every step of that to no avail and I honestly believe the problem lies somewhere in the syntax error I get referring to the lack of a C:\User\.android folder.
Thanks in advance for your help

That's because your drivers are incorrect it should be android adb composite interface... sounds like your using xp and its the complete worst for driver installs...
my suggestion is this build your own little system with this http://forum.xda-developers.com/showthread.php?t=1850038 then do the task manually all you need to do is have twrp and fff the rest is entirely obsolete if you intend to just flash a rom anyway.. for the purposes of learning what to do and how to do it read these http://forum.xda-developers.com/showthread.php?t=1552547 http://forum.xda-developers.com/showthread.php?t=1638452 they will give you some needed insight.. jcase`s manual rooting tutorial can be found here but like i said flash a rom all roms are rooted http://forum.xda-developers.com/showthread.php?t=1568340

Thank you for the response, I am not using XP, I am using Windows 7 Home Premium.
I don't have Linux although I suppose I could use a USB drive or USB Hard drive to dual boot with Linux. Thanks again, I'll have to wait until my brother brings the Kindle back over to try this, until then I'll look over it all.

ok well usually running the install.bat for the drivers on windows 7 is enough but for some it isnt regardless drivers are you main issue and you certainly dont want to have any issues with them in the process it will only produce very bad results..
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
also your syntax error can be causing the issues as you say you need that .android folder to make it work...
post #2 has a ton of info on the driver thing http://forum.xda-developers.com/showthread.php?t=1552547

Related

[Q] USB ADB drivers do not install! Help please?

I am unable to get USB connection working with my phone for development purposes. I have turned on the USB debugging and connected the device with USB cable and it does detect file transfer capabilities, but I am unable to get the ADB connection working.
I am running Windows XP SP3
It says it has found a device 'Galaxy' but is unable to install drivers for it.
What I have tried:
sdk/extras/google/usb_driver directory
I tried installing PdaNetA302.exe
I tried installing Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
I selected 'install from specific location' -> choose a driver -> 'Android Phone' but it had none listed and the aforementioned driver directories did not work either when I selected them as 'Have Disk' options.
I also tried uninstalling all related devices and do the whole connecting thing again, but without success.
Help please?
SOLUTION
Apparently HTC drivers got in the way. After I removed all HTC drivers from my Windows XP, restarted and connected the device, the Samsung drivers kicked in and made it work.
To remove unused drivers from Windows XP you can follow this guide.
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
PdaNet
waylo said:
Thanks for posting your experience.
Another problem I found, was that there's a different SamsungDriver.exe floating around, 8341kb. DOES NOT complete the ADB drivers necessary.
After installing the v1.4.6 drivers mentioned above, golden!
---------- Post added at 11:47 AM ---------- Previous post was at 11:41 AM ----------
Spoke too soon.
ADB recognizes it when it's booted in ICS, but while in the bootloader, it's not picked up. Thus fastboot commands won't work!
Windows 7 gives me a Android 1.0 driver not installed error.
Anyone?
Click to expand...
Click to collapse
I had no end of problems getting adb and fastboot working for GN due to the usb driver problems.
After much Google-ing...
I installed PdaNet on my laptop and this installed all required drivers in the process of installing, you can then un-install PdaNet and the required drivers are still on your system.
I now have adb and fastboot working for both my Nexus One and Galaxy Nexus phones on my Windows 7 x64 laptop.
Hope this helps!
Thanks to XDA member el3ctrik for this tip!
Thanks, figured it out just after you posted. The PDANet drivers were the trick, in #3 below (don't need to actually run the installation in this case).
You'd think after 1.5 years of playing/hacking/unhacking/fixing and refixing the N1 I'd know how this is supposed to work.
A couple of comments, since some tutorials are based on older installations.
1. Installing android sdk. I went through a crapload of unnecessary trouble in trying to reinstall these, thinking that the usb drivers, adb, and fastboot needed to be updated. NO.
1a. In fact, in trying to reinstall the android sdk, you have to install the Java SDK. THEN, with the latest revision, R15, FASTBOOT IS MISSING! Need to pull that from a r13 zip.
2. You need the CORRECT samsung drivers. The ones mentioned above are the correct ones. I installed some limited half-ass versions which did not do the job.
3. You need FASTBOOT drivers. These were found from this post http://forum.xda-developers.com/showpost.php?p=9919944&postcount=1
which states:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
The #2 drivers let ADB see it when ICS is running, #3 (and probably #2 too) are needed while in fastboot. To get #3 installed, I had to go to device manager in Win7, hit update driver (next to the error exclamation mark device), and direct to these files.
That is all <whew!>
Glad you got it sorted out buddy, I was in exact same boat, years of Nexus One fastboot and adb use, but still had problems!
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Windows 7N USB driver issues
First post on this forum, so please bear with me.
I struggled for a few weeks trying to connect my new Samsung Galaxy Nexus (Rogers) to a 32-bit Windows 7 Ultimate N machine. The system wouldn't accept the drivers from Samsung - failed to recognize, driver software not successfully installed, etc. Tried all variety of proposed fixes, manually selecting the driver (have disk), downloading SDKs and ADB drivers.
Finally fixed it based on a very old suggestion from several years ago from an HTC user. The USB driver wasn't recognized in the absence of Windows Media Player being installed on the machine (a quirk of Ultimate N). Found the Patch from MS for WMP for 7 Ultimate N and the system immediately recognized and installed the Samsung driver and thus the Nexus is now connected.
Download my toolkit (ROM-Less), it will assist you in that manner!
It has easy instructions, and it will do most of the work itselff!
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
AMoosa said:
I am really struggling to install ADB drivers (for using within ICS). The GNex is in developer debug mode. When I plug in, Device Manager shows the Portable Device, but no other devices are shown. So in this case, i have nothing to right-click to manually install the drivers. There is nothing under Android, or adb, or anything like that. Hope someone can advise...
I got it to appear by changing to PTP mode in the USB Computer COnnection on the phone!! Success.
Click to expand...
Click to collapse
Check this, it has all neccesary info/drivers for your device, including fastboot drivers!
Beatsleigher root helper (My toolkit) check it out

Device not recognized on ADB?

I don't want to bother you with stupid threads and things like that, but I've used the search function on XDA and I'm still lost on this really small problem - my Kindle Fire is not being recognized anymore in ADB.
See, a long time ago (few weeks) I rooted my KF and installed Android Market, whatever. Never installed a recovery or custom ROM. Everything was ok until I tried to install TWRP using Kindle Fire Utility.
While trying to install, I got the famous "adbd cannot run as root in production builds". So I thought it was something with my drivers. Ok, then I installed the drivers that come with KFU - just to screw with everything. My Kindle Fire stopped being recognized by ADB.
I tried: (1) uninstall the drivers and install from KFU again. (2) uninstall the drivers and install the drivers I got from the video-tutorial (the famous one). (3) factory reset the kindle fire and do all the drivers install again. (4) hold the power button 900 seconds to reset the kindle fire and install the drivers again. (5) finally install the drivers on ANOTHER computer (running WinXP instead of Win7) and plug my factory reseted KF.
I gave up.
I don't know why my Kindle Fire isn't recognized by ADB on any computer at all. I thought it was my laptop, but then I tried the same steps I did at the first time using a Windows XP and no good. I don't know.
Can someone help me? Thanks a lot.
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
or you can try this solution:
http://forum.xda-developers.com/showthread.php?t=1430038
b63 said:
i think xp is the better decision for such things
you can try:
power down and disconnect kf
remove any old drivers: http://support.microsoft.com/kb/315539/en-us
remove anything with adb or kindle or unknown device
replug kf without powering it on (does it by itself)
install new drivers:
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
Click to expand...
Click to collapse
Tried that and didn't work.
I'm going to wait a little more before using Linux, I really wanted to do this using Windows only.
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
b63 said:
in what status is your kf now ?
normally booting ? - stuck at whatever ?
at xp now ?
checked the adb_usb.ini in your .android folder (in your personal folder) ? - should include 0x1949 and if you like 0x18D1 (i included it too)
to run kfu with 6.2.2 you need the patched version:http://forum.xda-developers.com/showthread.php?t=1458841
would put it to something like c:\kfu cause it don't like spaces in pathname
try running install_drivers.bat from kfu
Click to expand...
Click to collapse
Right now my KF is normally booting into stock ROM and stock everything.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Thanks for your support.
I have both computers at my disposal: Windows XP 32-bit and Windows 7 64-bit. I'm writing in my laptop which is the Win7.
Click to expand...
Click to collapse
xp will be the better choice cause you don't have to hassle with 32/64 bit drivers and the uac (user access control)
My adb_usb.ini has only 0x1949, I'll add 0x18D1 in another line (or should I use a blank space to separe them?).
Click to expand...
Click to collapse
add it in another line
Unfortunately I can't see the link you posted because XDA says I don't have privilegies to do so. My stock ROM is 6.2.2, but I think it as always been like that, and it worked using the normal way before. Can you mirror the post on your link somewhere else? I'd love to try the patched version.
Click to expand...
Click to collapse
seems that the patched version (the whole thread) is deleted - you will have to do it by yourself - take the original from the dev section and:
http://forum.xda-developers.com/showthread.php?t=1454913
The issue persists. I've seen that other people are having the same issue. The device got "unrooted" by unknown reasons and then it's invisible to any adb. As I'm writing to you right now, I'm trying the adb on my brother's Ubuntu. I've tried other solutions using linux but without success.
I'm running out of options here.
I'll admit that I haven't tested the last link you sent, but I can't see how that can change the way adb works on my device. Anyway I'll try that tomorrow.
in the meantime br3 is out - if you use kfu you will have to use an updated run.bat: http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
but you'r right - that will not change the communication
firekit http://forum.xda-developers.com/showthread.php?t=1430038
is worth a try cause linux don't use drivers to communicate
only needs some entries which are included in firekit
maybe try an other cable ?
really running out of ideas at this point ...
I got the same problem.
If you can fix it, please show me how, thank you.
c:\KindleADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
c:\KindleADB>
Just a quick idea. Have you tried the attach the kindle to a different USB port? I had the same issue until I used a different port. The front ports on my desktop are totally fubar, but the port where my mouse was worked when 4 out of 6 ports did not. This for me is probably a hardware problem, but it may help someone.
Sent from my Kindle Fire using Tapatalk
I am having the same exact problem as the OP and I truer everyway to root it and install the drivers but its still not recognized by adb
Its seems i should give up
Similar problem with cm9, and fixed
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Push push push it
tried all the steps. and still nothing. dont know what im doing wrong. starting to get pissed. any help would be great, thanks
Save my KF
sudogeek said:
I was using cm7 and all was well. I installed cm9 (the cm9_02_02 ROM) which supposedly had issues with SD card mounting and adb not working. (The SD problem is a regression which is fixed thusly.)
Initially, I got the "ADB server didn't ACK" message (I had recently updated the android sdk). To fix this, cd to the tools directory and
./android update usb
./android update adb
Then the server would start but wouldn't list the KF with "adb devices" command. I realized the second command had re-written the ~/adb_usb.ini. I added "0x1949" as the last line and bingo. adb does work on cm9_02_02.
YMMV, and this is on a Mac.
Click to expand...
Click to collapse
Could you help me to fix same problem with window. My PC alway, automatic recognize my KF as normal disk driver. I try to make a factory cab but not success .
Thanks.
Edit android-path.sh
1. On my Mac I opened System Profiler, then checked Hardware > USB > and 'MyDeviceName' (for me its: LePan Tablet PC)
2. Opened this file with a text editor: /Users/MyName/.android/android-path.sh
3. Added a new line in this file with the tablet Vendor Id, for example:
0x22a4
4. Executed: adb kill-server
5. Executed: adb start-server
6. Finally adb devices is showing:
List of devices attached
0163AE9D0801F02C0C280002 device
Bricked?
I think I'm having the same problem, or at least a very similar one.
Using windows XP. I got the drivers working, plugged my kindle into the Kindle Fire Utility, and ran option 2, which seemed like it was the option to create a backup in case you bricked your kindle. It ran, showed up on the Kindle screen, and did it's thing without a problem.
Then, when the kindle rebooted, I got the yellow-triangle-fire symbol. It says 'press power button for recovery', but pressing the power button does nothing. Holding it down for a long time shuts the kindle down, but pressing it again brings it right back to the yellow-triangle-fire symbol.
So I uninstalled the drivers from Windows XP (as another thread mentioned). I now have two ways that I can think of to install the drivers. Using the KFU, I get the "unsigned drivers" shutdown even after I went into the Driver Signing menu and chose "ignore and install regardless".
The other option I have is to install the drivers that I downloaded manually -- the same ones that worked in the first place. Problem with that is that I go through the entire process, selecting the directory the drivers are in and whatnot, and the only thing that happens is I get an error that says "These drivers aren't the drivers for your hardware" or something similar to that.
So neither of my options allow me to actually install drivers for my Kindle Fire, and my Fire itself is in a recovery loop. All of the tools that are supposed to address the recovery loop require drivers, so I seem to be up a creek without a Fire.
Any ideas?
Okay, to enter recovery...When you see the yellow triangle, hold the power button until it turns orange then release. It shouldn't take more than 10-15 seconds. If you still can't get into recovery, reinstall it.
For your drivers...uninstall completely and delete them if you're using Win7. Then reinstall using one of the previous methods.
The power button doesn't do anything when I push it. It stays bright green until the kindle fire shuts down. I'm not sure what "reinstall it" means, sorry, n00biness.
The drivers (winXP as mentioned) I've uninstalled, but I can't reinstall. One option says "unsigned drivers" and the other doesn't recognize the device as a Kindle and thus quits the install with a "this is not an appropriate driver for your device" message.
Thanks for trying, though! I appreciate your time and effort.

[Q] Kindle Fire ADB Issue

Too bad i can't edit the post title. Please bare with me.
My fiancee gave me her Kindle Fire yesterday. She got it as a Christmas gift last year and has only started it once since. When i first took a look in the Device information in Settings it said it was running 6.2.2 Stock. So i went to sleep last night with the sound opinion that i would root it and install CM7 Barebones or something likewise and make it functional.
Waking up this morning, i read the beginners guide and i took a look at the rooting guide for the 6.2.2. I install the Java SDK, Android SDK, Google USB Drivers and i do EVERYTHING step by step as directed by the guide. Finally, at the last step, when i try to get the device recognized using cmd "android devices", it fails to recognize. The installation worked like a charm, exactly like in the guide, besides this last step. So i reboot both the KF and the PC, still not working, and surprise, my Device Settings now shows Stock version 6.3 installed, overnight. Take note, i did not approve something like this.
The KF is only recognized as a Disk Device in the Device Manager in Control Panel. I cannot get it to be recognized as an Android Phone. I tried uninstalling the KF through Device Manager, Devices & Printers, but it always reinstalls the driver from the directories. I edited the .ini files as per the guide, so i have no idea what might be wrong. I even uninstalled the Google USB Drivers from the Android SDK Manager and reinstalled them, and the same result is happening. As a last resort, i did a Factory Reset, deleted the drivers from Device Manager and SDK Manager and reinstalled them, to no avail.
How on earth can i get a CLEAN install of ADB and the recognition of my KF for rooting WITHOUT formatting my entire Windows PC? If i take it to another computer and plug it in and follow the Kindle Fire Utility instructions, do i still need to install the Google USB Driver through the SDK Manager, or just the other stuff?
On a side note, if i ever ever achieve this, what custom ROM runs Google Play Store perfectly?
Thanks.
Just use kfu 0.9.5. If I were u I would do latest update before rooting it. You can get it from amazon and manually update it. That's what I did.
Sent from my SPH-D710 using xda premium
Can you just read my post again mate as i did a major edit explaining the situation better. Thanks.
Luppertazzi said:
So i reboot both the KF and the PC, still not working, and surprise, my Device Settings now shows Stock version 6.3 installed, overnight. Take note, i did not approve something like this.
Click to expand...
Click to collapse
This is normal on Stock, OTA updates without your consent unless you have disabled the setting.
Luppertazzi said:
How on earth can i get a CLEAN install of ADB and the recognition of my KF for rooting WITHOUT formatting my entire Windows PC?
Click to expand...
Click to collapse
Try reading this post, it may help you understand what other steps you could take to fix the drivers: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Luppertazzi said:
If i take it to another computer and plug it in and follow the Kindle Fire Utility instructions, do i still need to install the Google USB Driver through the SDK Manager, or just the other stuff?
Click to expand...
Click to collapse
The drivers included with KFU are all you need. If you are to plug it into a different computer, it's suggested that you run the drivers installation on KFU first before plugging in the Kindle Fire.
Luppertazzi said:
On a side note, if i ever ever achieve this, what custom ROM runs Google Play Store perfectly?
Click to expand...
Click to collapse
All I have tried have worked flawlessly, with some exceptions where I just had to flash gapps to fix it.
MAJOR EDIT:
I may have been stupid but something happened. Now i have the Kindle as a Disk Drive and i also have it as a SAMSUNG Android Phone. They both are installed correctly but i STILL CANNOT see the device through cmd "adb devices". It's just a blank line.
Any ideas?
Sorry for the double post but this is worth mentioning separately. I saw in a different post that someone who has Samsung Galaxy SII phones and relative drivers get the Kidnle recognized under Samsung Android Phone. How do i uninstall JUST the Samsung Galaxy SII drivers from my PC? I have a Galaxy SII phone so, figures. Also have Kies installed and Droid Explorer as it runs CM9.
plug in your s2 go to device manager in control panel and you will see the drivers
Read the drivers post I linked you to earlier.
Delete incorrect drivers from the Device Manager and take note of what it should read as.
It may sound a bit too simple, but really, most of the issues come from bad drivers.
Hey Luppertazzi
Just use Kindle Fire Utility 0.9.5 (the latest version).
-> Just keep unplugging, plugging, uninstalling, reinstalling drivers -- and restartting the KFU utility until you can see "Online" as status in KFU.
-> Choose install permanent root with superuser
-> Reboot (power off and on the kindle fire if necessary)
this will automatically install TWRP and superuser and root your kindle fire.
then you can keep using stock ROM by going to extras -> install google framework (where you can use google play with go launcher) or use twrp to backup, restore and flash roms.
Hey guys.
I tried the process on another laptop and it worked. I installed only the basic SDK Tools from the SDK Pack, leaving the development stuff and drivers out of it. Then, i downloaded KFU and used the drivers there as the only installed drivers on the separate PC, and it worked like a charm. I was able to root, install a custom ROM and do every other thing i wanted.
Thing is, on this computer, i can't really get rid of all the drivers and utilities because they keep getting installed back. Should i use something like DriverSweeper or anything of the sorts?
Thanks.
Okay this is what u do. If your kindle is not showing up in device and printers unplug your kindle and power it off. Install drivers from the kfu folder again. After this is completed turn on your device and then plug in your kindle. The kindle should show up as a device on device and printers menu. If your device is showing up click on kindle and then click on hardware. Then click on properties and change setting. There should be a option for update drivers. After clicking on update drivers its going to give you a option to search for drivers. Click browse. Since you have already downloaded the sdk and installed it on your computer install adb composite drivers. It should install the drivers. Now go back to kindle on devices and printers menu and click on kindle. Go back to hardware and check drivers. Under device functions: it should have amazon kindle USB 2. Android composite adb interface 3. E:\ 4. USB composite device 5. USB mass storage device. Now exit all of that stuff. Go back to kfu folder and click run. Make sure the adb status is online and the boot status is 4000. If boot status isn't 4000 then it will not work properly. So what I did was download kfu 0.9.4 and when I clicked on run adb status was online and boot status was 4000. If you do see that, click install permanent root and su (option 2). When this is completed go back to kfu 0.9.5 and adb status should be online and boot status should say 4000. If this is the case go ahead and click 2 again and it should install permanent root and su and twrp. This is what worked for me.
Sent from my SPH-D710 using xda premium
Glad you figured it out.
Sent from my SPH-D710 using xda premium

[Q] Waiting for Device

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

Windows 7 will not recognize Fire

My girl got a Kindle Fire and wants Jelly Bean on it. I plug it into the laptop, Windows start to look for drivers, can't find them. So, thru KFU I install the drivers, open KFU, device is not showing. I open adb, run adb devices, blank. Run adb usb devices,, device not found.
The kindle will say that its connected to the computer and I can transfer files. But windows will not show an external device is attached. So, I go to Device Manager, its an "unknown device". So I looked through post after post, finding out that I need to edit the adb_usb.ini file. Problem is, I can't get to it......
I'm not a noob when it comes to computers or android, but this has me lost......
Your GF wants too much!!!
I had same problem. Errore was plug first kindle then install kfu with drivers. Remove all drivers you installed. Now install drivers provided with kfu. Make sure SDK and java is ok. Then plug kindle.
Sent from my Amazon Kindle Fire using xda app-developers app
smsrat84 - when you plug KF into USB and Windows starts to scream about new unrecognized device, choose an option to install drivers manually from a specified location, and choose {KFU_HOME}/drivers/kindle - KFU will see it after that. Then install FFF, TWRP with KFU and so forth.
Try using Linux (yes I said the dreaded 'L' word ) because apparently it's not as fiddly with drivers as Windows is.
Personally, I used Mac and it was plain sailing all the way. No drivers, everything just worked first time [Just make sure you're careful, nothing is foolproof ]
jji7skyline said:
[Just make sure you're careful, nothing is foolproof ]
Click to expand...
Click to collapse
touché

Categories

Resources