New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
emptyreddata
Old
(Last edited by emptyreddata; 21st July 2012 at 04:59 AM.)
#1  
Junior Member - OP
Thanks Meter 0
Posts: 1
Join Date: Jul 2012
Default [Q] Stuck at Kindle Fire booting screen

I was attempting to root my friend's Kindle fire with the SuperOneClick method. You can google (kindle fire root) and it is like the second result I think. I would link it to you, but XDA tries to prevent spam by disallowing me to do so (good idea, just not working in my favor atm xD)

After completing all the steps and running the final program, it became stuck on step #7. I scrolled the comments and it seems like about half of them were of people getting stuck on step #7. So I thought nothing of it and tried to just switch to a different method which is Kindle Fire Utility. It had a problem with adb and couldn't get in touch with the device.

We tried to reboot the device, but it became stuck on the kindle fire boot screen. All it says is Kindle Fire and it stays on forever unless I press on the power button for over 20 seconds.
After fiddling with the drivers for what seemed to be an eternity, I finally gave up and went home (switched to Ubuntu 12.04 x64).

So after installing the JDK, Android SDK, and configuring everything the way they need to be configured, adb could still not even find the device.

adb_usb.ini
Quote:
empty@reddata:~/.android$ cat adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x0006
0x181D
Android rules
Quote:
empty@reddata:/etc/udev/rules.d$ cat 51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"

Here is some output I get from adb after I tried restarting it and starting it back up again with the above files the way they are.

Quote:
empty@reddata:~/Downloads/android-sdk-linux/platform-tools$ ./adb kill-server
empty@reddata:~/Downloads/android-sdk-linux/platform-tools$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
.empty@reddata:~/Downloads/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached

empty@reddata:~/Downloads/android-sdk-linux/platform-tools$
I can't quite figure out what to do past this point. I am quite terrified that I bricked the damn thing .

I never really finished rooting it (I think). So I am quite stuck and would absolutely adore some help. I've went around google for many hours searching for even one person who has the same problem, but I never came close. I think I just never really knew how to word the problem correctly.

Thanks for the help in advance.

EDIT:
I would also like to note that I haven't a thing installed on it. I haven't gotten FFF on it or anything in the slightest. This seems like the epitome of fail when it comes to a rooting attempt. I thought it would be a simple process, but let me be the example of how bad things could possibly get messed up xD
 
Toxeia
Old
#2  
Junior Member
Thanks Meter 1
Posts: 6
Join Date: Jul 2012
Speaking from experience when I first rooted my Kindle, your looking at 3 options.

1) Use a factory cable to connect the device to a computer (A factory cable pins 1 and 4 at the Micro end while a normal cable doesn't use the 4 pin).

2) Pray you can time it right with ADB to change the boot mode back to normal. Seems like the window's pretty small on this though.

3) I assume the issue with working from Windows was drivers? If you can figure out the drivers in Windows so that it shows up as a Android phone under device manager (I had to use a virtual machine to get it there because of issues with previously installed drivers) then Kindle Fire Utility will do the timing for you and install Fire Fire Fire and fix the problem.