Database Users

Solved having trouble getting root

I am running Windows 7 x64 I have no idea if following this guide on another operating system will work, this is just a step by step of EXACTLY how I did this, Not to say this is the only way. I have tested other methods and I have put in different variables and I have successfully gotten it to work several times in a row doing it this way while following jp4756's guide. I am sure this is not the only way to accomplish root, however this worked for me perfectly. PLEASE don't skimp out on any step. There is no shortcut here just follow the steps and jp4756's guide to the TEE!!!
Step 1.
Uninstall pdanet/htc sync/ any other thing you installed to get all this to work before
Unplug phone from computer usb cables and have phone powered on and in settings menu
Step 2.
download USBDeview(install it) easy to google it
download HTC SYNC(do NOT install it yet) for mytouch slide easy to google it
Step 3.
While in settings menu go to Application
go to Development
and check the box USB debugging
Step 4.
In settings go to Connect to PC
touch Default connection type and choose Sync
At this point you have the phone not plugged in, you have the setting on the phone changed, you have dowloaded usbdeview and installed it, and have htc sync dowloaded
Step 5.
Start USBDeview(some may have to right click the exe and run as administrator) and delete all android drivers and mytouch drivers, anything relating to android
Install HTC SYNC and let it completely install
Step 6.
Plug phone into computer and let the computer auto install drivers etc...
Step 7.
turn the phone off. Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button ) After it does its little thing your computer will beep and start auto installing drivers and stuff
Step 8.
If everything has gone according to plan in Device Manager it will show Android 1.0 or w/e with a exclamation point. Right click on that and choose Update Driver Software
2 options pop up choose Browse my Computer
then choose Let me Pick from list...
a list will appear giving lots of choices
choose Android Phone should be the first choice that says android....
then 3 options will appear, choose the 3rd one that has Composite in it and choose okay.
Step 9.
Now select Recovery from the bootloader menu
after it is done doing its thing completely 2 things will happen
1) In device manager you will now have something under disk drives
2) USBDeview a new driver will pop up at the end of the list, something like this:
Port_#0004.Hub_#0004 T-Mobile myTouch 3G Slide USB Device Mass Storage Yes No No No E: HT05RPS05696 6/16/2010 4:00:58 PM 6/16/2010 4:07:35 PM 0bb4 0ff9 08 06 50 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB @usbstor.inf,%generic.mfg%;Compatible USB storage device
Step 10.
This new driver to appear shows Yes under the Connection column. This needs to be disabled. Right click on it and choose Disable Selected Device
after about 10 seconds it should no longer say Yes under connection column, if this does not happen then you are not running it under Admin.
Okay so now you are literally almost freaking there.
Step 11.
Now basically all you have to do is follow jp4756's guide starting with step 5. Im going to assume you already understand steps 1-4 in his guide. And you already have the package listed in his guide as well. You have already put those files where they belong
Step 12.
Okay so we are basically following his guide now. first things first
5. run the update.zip it will fail(MUST DO)
6. now in cmd type adb reboot recovery (don’t press enter)
7. in the recovery hit reboot system now( once it starts rebooting run that command rapidly untill back into recovery) <--- Basically while the phone is rebooting you are just hitting up arrow enter up arrow enter up arrow enter up arrow enter in CMD. You will know when you can stop when the CMD freezes for a sex, computer makes beeping noises and the phone reboots basically. It is headed for recovery and we must switch our command now
8.type adb devices(if it says nothing repeat the steps, if it says offline unplug it and then plug it back in, if it says recovery your fine) <---- Basically after you know its headed for recovery you change command to adb devices and you repeat previous procedure, up arrow enter up arrow enter up arrow enter etc.... I did not use loop, i did this all manually.
This may take a few tries, if it does not show offline then go back to step 6 rinse and repeat. You go back and forth just a few times and you will have it. Literally within about 3 tries you should accomplish the annoying goal of having offline stay there.
My job is done, follow guide and continue on your quest for root
There is no guarantee this will work for everyone. I am not claiming that this is 100% Im just giving an explanation as to how i got it and what might have been causing everyones trouble. Results may vary
Thank you to all the devs who made this possible and jp4756 for his wonderful guide

Wow that is just way to much stuff there...
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
Also It just might be your computer so I would try and use a different one if you can.

jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
Sorry that we all can't be as cool as you jnight666, but some of us are having real problems with no apparent explanation. I am an IT professional with access to every kind of computer used in the modern world, and trust me, I've tried all the ones that apply. Rubbing it in our faces that it was just so easy for you is just rude.

THE DRIVER MAKES NO DIFFERENCE FOLKS. IF YOU CHANGES DRIVERS AND THEN IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON MANY DIFFERENT DRIVERS.
THE CONNECT TO PC SETTING ON THE PHONE DOES NOT MAKE A DIFFERENCE IN FASTBOOT/RECOVRY FOLKS. IF YOU CHANGED THIS SETTING AND IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON VARIOUS DIFFERENT SETTINGS.
That being said, this didn't solve mine. I still cannot root.
And Yes, my cap locks was on purpose.

Okay, please dont come in here and start telling me how my method is wrong. I already stated there are other ways to accomplish it. I had already stated that this isnt 100%. I am merely offering an exact procedure that i duplicated SEVERAL times, with it working for me every time. If this isnt how you accomplished it then pls, theres no reason for you to be in this thread posting negative comments.
With that said fermunky, did you follow the procedure to the tee? - btw im not assuming anything so please dont take it personal. Im just trying to help ppl : )

My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.

Completely understandable, and definitely no disrespect to you or anyone here

When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,

jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
And if anyone want to say anything about this I'll go load up my Pentium III machine and see if it works on that...
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
3 different computers 3 different op systems installed uninstalled drivers different programs etc...some phones are hard to root its a ambiguous situation

Yeah sorry I wasn't trying to be rude.
I was just trying to be helpful, sorry if it came out that way...
I also have the loop not working issue but i usually only happens once or twice..
I feel your pain I had trouble with the push Update.zip part of this thing and I was trying it for hours...
I was just trying to tell you what worked for me...
If you tried different computer and still no luck then im guessing its the Phone that is the issue or the USB Cable...

gofizzle said:
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
Click to expand...
Click to collapse
You definitely don't want to do that, as one of them is one that you need to be connected once you finally get to see offline stay. Are you rebooting using the method described in jp4756's guide? meaning your rebooting using the recovery option reboot, then in command doing the adb reboot recovery, then once you no the phone is gonna boot into recovery you switch to spamming adb devices? When you say your in a loop it sounds to me maybe your not doing the adb devices after the phone listened to your adb reboot recovery command

Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)

before plugging your phone into your computer a single time, can you confirm that you started up USBDeview and uninstalled every single driver related to android, or mytouch or htc etc... Also before ever plugging your phone in a single time did you install htc completely?

Code3VW said:
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click to expand...
Click to collapse
Right Click Android Phone - Properties - Driver - Update Driver - Browse My Computer - Let me pick from a list of device drivers (click this, don't give it the path in the upper box) - Have Disk - Browse to yours C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 - click androidusb.inf and select Open - OK - Unclick Show compatible hardware - Select "T-Mobile myTouch 3G Slide" - Next - All Done.

after getting some sleep and starting fresh, i tried this method again this morning. on the fourth or fifth try i got my slide to stick in offline mode. so then i unplugged it and plugged it back in to get into recovery. lost it, and now im on my 50th or so try to get it back to offline mode.
i need a stiff drink lol
it seems partially a driver issue and also an adb issue i thinks. it connects 'when it feels like it'
i'll report back if i make any progress.
btw im doing this on XP Pro SP3 fully updated
edit: I also noticed when adb does catch the slide, 2 instances of adb are running, then one closes and loses the phone. maybe this will help solve some of the problems

You've misunderstood that post. Only one instance of ADB will show when the loop is not running. Once you start the loop, another instance of ADB will show up and disappear many times. This is normal. As long as only one instance is showing before loop, you are fine.

fermunky said:
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Click to expand...
Click to collapse
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

mtjnkee said:
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
maybe your downloads were corrupted. that's really strange...
man, that really sucks! I am truely sorry...
after spending 20 hours or so on rooting, I really feel your pain.

After I reboot into recovery mode and then use adb to check for my device I never get it to show up. Just so I am clear when you say 'spamming your device' you mean after reboot and rapidly entering the reboot recovery command, then looking for device with adb devices command. I never get it to show.
Thanks for the reply!

No devices in adb?
So I had this same problem with my MT3G. Type in "adb devices" kills the last device and it lists connected devices and NONE were listed. Not sure exactly what I did, but did eventually get it working. (I was trying to use the emulator)
Now though I'm having the same problem with my wife's MTS. Any ideas?

Something Went Wrong w/ Rooting - Please Help!

I seem to be having a little problem here. I've been wanting to root an android device and after reading about how simple and fail proof the TF rooting experience is I decided to take the plunge.
I found a tutorial on another site (I'm not able to post the link because of forum rules) and decided to proceed. I followed the instructions to the letter and got confirmation that the “phone update was successful” but after rebooting the TF is stuck on the “Eee Pad” screen. I’ve tried rebooting into APX mode but the computer doesn’t find the device.
I’ve looked elsewhere regarding how to unbrick the device but every solution that I see requires booting into APX. Please help!
Edit: I'm sure that it's important that you know what exactly I did. The site that I got the tutorial was eeepadhacks dot net. I'm almost positive it's using the Nvflash method.

Posted this in the middle of the night and it's almost off the first page. Bumping it for an answer...hopefully.

You are in the wrong section. Look in the Android Development section. The first topic there is about unbricking your device.
http://forum.xda-developers.com/showthread.php?t=1123429

Not too experienced with the TF, but had the same bootloop type problem on Android phones straight after rooting.
Can you still get into recovery (power off, then hold the power button + volume down until the message shows up, then press volume up)? Try this if you haven't already. If you can get into the recovery you've installed (clockworkmod), you'll be able to flash a new ROM such as Prime and it should be working. If it's the same problem I've run into then it's not bricked, it's just somehow screwed up the original ROM during the rooting process.
Try to get into recovery and let me know. If it doesn't work, then hopefully someone else can help but I wouldn't worry much. It should be relatively easy to fix.

I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714

Thanks for the replies guys. I saw your thread last night Vert and that does seem to be the exact problem that I am having. The difference is that I can't get the TF to turn off.
If I hold the power button until the screen shuts off it just reboots. The only way that I can get the screen to turn off is by holding down the volume up button and the power button simultaneously but that doesn't appear to put it in APX mode. At least my computer doesn't seem to recognize it as such.
My plan is to redo it by following the link that you posted (I saw that last night too) but I don't think there's any way to do that until I can get the TF to show up on the PC. Anyone have any suggestions?

After playing with it for a couple of minutes I've noticed that when I put the TF into APX mode a new entry appears under the USB Controllers. It is called NVIDIA USB Boot - recovery driver for Mobile devices.
Hopefully that is helpful information....
Thanks again!!

Are you on windows 7? If so, open up device manager by going to start menu>right click on computer>manage>device manager. Then hold power/vol up on your transformer until the screen doesn't turn on. Device manager should then refresh. Look under Universal Serial Bus controllers and "Nvidia USB Boot-recovery driver for mobile devices" should show up. This means it is in APX mode. If that doesn't show up try reinstalling the drivers. From there you can run root.bat and it will boot up
Good luck
EDIT:Looks like you got it while I was typing lol

Thanks for your help guys!!
I'm back up and running. I'm not rooted but at least my TF is back alive.
I'll try again later today using that video that you posted Vert.
Thanks to all and enjoy the rest of your weekend!

At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.

poltak11 said:
At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.
Click to expand...
Click to collapse
Yup, got it all up and running and am happy to report that I am now sporting Prime 1.5 on my newly rooted TF. Thanks again to everyone that helped out!

I had this problem earlier, and I used nvflash to recover. I thought I was not in apx mode as well but I was. Win 7 64 did not show it but when I flashes it worked. Just try it.
Sent from my Transformer TF101 using XDA Premium App

Vertiginouz said:
I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714
Click to expand...
Click to collapse
The reason why you forgot may be because in the instructions it tells you to unzip the files higher in the thread before Step 1 begins.
"
extract the file inside the zip to directory root before running root.bat
for ww 8.4.4.11 version. thanks for the help from poet,paddy01,peacemaster,rebound821 provide me the boot file
for tw 8.4.4.11 version thanks for the help from butro for the boot file.
Thanks for the fone_fanatic to do the walkthru.
Ok, just did this and worked flawlessly, have root and CWM in under 10 minutes!
I'll replay step by step what i did to help those that are still confused. (it looks long but its really not, i was just very detailed causing this to be more of a "take my hand and i'll walk you through it")
Some background info. Highly recommend reading these if you don't know what either is!
Rooting Explained + Top 5 Benefits of Rooting by androidpolice.com
What is ClockWorkMod recovery and how to use it by addictivetips.com
STEP 1. Make sure you have all the correct asus drivers installed. Not sure if this is necessary but i had them all installed previously and i didn't run into a single issue.

I bricked the kindle

Ok, Im new to android and this account is new also because I cant remember the password of the old account...
So i was in 6.2, supposedly I rooted it, because I was able to run the Android marketplace. So Today I decided to give CM7 a try, so I follow a "tutorial" on
liliputing dot com, it is using "KindleFireUtility"
So when I hit "7" on KindleFire Utility , it downloaded twrp and the it said it has to check if the device was rooted or something, so it did all that, then it stay for like 10 minutes on "restarting device" or "waiting for device", and the kindle was doing nothing at all, it didnt turn off or do anything, so I got tired of waiting and hit the "Disconnect" button on the kindle screen, unplug the USB, the Kindle turned off and back on and it stays on the very first screen with the KinleFire Logo, it doesnt even shows the little animation. Now the computer doesnt detects the kindle at all...
I try to follow the steps in the topic : [HOW TO] Unbricking/Restoring your Kindle Fire 9 Attachment(s)
But it says "error: device not found"
What now?
I dont know is this has any relevance at all, but Im using a MacBook running Windows7 on "WMware Fusion"

Throwing a guess out there, you're probably still in fastboot.
//KindleFire.Tapatalk//

You're definitely on fastboot mode.
I just answered a similar problem here http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
Hope it helps you too.

ch0mch0m said:
You're definitely on fastboot mode.
I just answered a similar problem here http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
Hope it helps you too.
Click to expand...
Click to collapse
nope, either I cant seem to undestand exactly what i have to do and im doing it wrong, or it doesnt work on mine...
at one moment the computer recognize the kindle as a "unrecognize device" but still didnt work, or maybe I dont know how to do it, and now it doesnt recognize it anymore, just like it was yesterday, I connect it and nothing happens...
:/

You need to reinstall drivers to get your machine to see the kindle properly.
Sent from my PC36100 using xda premium

When The computer detects ir as a "unrecognize device" if I click update drivers I point it to where the drivers are and it tells me the drivers are up to date.
Kindlefiteutility shows "error: device not found" or something like that...
I'm still stuck /:

Shadow-of-Death said:
When The computer detects ir as a "unrecognize device" if I click update drivers I point it to where the drivers are and it tells me the drivers are up to date.
Kindlefiteutility shows "error: device not found" or something like that...
I'm still stuck /:
Click to expand...
Click to collapse
The instructions from this link fixed it for me the other day. I would do a complete shutdown of your Mac/PC instead of a reboot as a simple reboot didn't work for me the first time.

Ramer84015 said:
The instructions from this link fixed it for me the other day. I would do a complete shutdown of your Mac/PC instead of a reboot as a simple reboot didn't work for me the first time.
Click to expand...
Click to collapse
the thing is that I cant get the computer to recognize it as a kindle, or even a android phone!...
-_________________-
If I direct it to the folder with the drivers it doesnt do anything, and if I click pick from list, like the guy say on that post theres no "android" on the list.
So It seems I will just have to enjoy my Brick Fire how it is, I guess I can use it as a pretty expensive door stoper or paper weight....

[Q] Kindle fire stuck at yellow triangle while Flash Custom Recovery (TWRP)

My kindle fire stuck at yellow triangle while Flash Custom Recovery (TWRP).
Kindle fire can not found in device manager.
In device manager show USB device but I cann't install driver.
Please help me to solve this problem.

were you flashing with KFU? Try using v0.9.1 rather than 0.9.3

from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
and
http://forum.xda-developers.com/showpost.php?p=22065426&postcount=846
if you'r on win7:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41

Thanks for your help.
I have done on my problem.

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

what if I unplugged it? Nevermind, got it. Thanks for the links!

ethanova said:
what if I unplugged it? Nevermind, got it. Thanks for the links!
Click to expand...
Click to collapse
Hey guys, normally I would research this good, but I'm in a bit of a time crunch. So, if I unplugged it, I need to follow the directions linked above (uninstalling drivers / reinstalling drivers)?
This kindle belongs to my nephew and I've had it for almost two weeks, I would like to return it to him soon.

arqbrulo said:
Hey guys, normally I would research this good, but I'm in a bit of a time crunch. So, if I unplugged it, I need to follow the directions linked above (uninstalling drivers / reinstalling drivers)?
This kindle belongs to my nephew and I've had it for almost two weeks, I would like to return it to him soon.
Click to expand...
Click to collapse
just make shure you have installed the right drivers
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

[Q] [Trouble] Rooted 6.2.2 - Stuck on yellow fire triangle

Hi there,
I rooted my Kindle Fire (6.2.2) a few days ago. It was working perfectly for two days. When I turned it on the 3rd day, the following happened:
1. It went into the recovery screen without me pressing the on/off button to turn it orange.
2. A few seconds later, a big android logo came up and there was a message (I'm sorry, I don't remember what it says)
3. I didn't know what happened so I turned the device off hoping to get rid of this problem.
After that, whenever I turn it on, it only shows the yellow triangle with picture of fire in it. I tried to hold on to the on/off button for 30, 60 and 90 seconds, all it does is to turn the device off.
I really need some help, please. I don't understand why it suddenly stopped working after two days. Is it related to the new 6.3 update?

Go into kfu and ten go into the boot menu... (1) then choose normal boot.. hope this helps!

Is the battery low or almost dead. You could try plugging it in and see if it boots up. Mine does this exact thing when the battery is dead. Just charge it up and good as new
Sent from my ADR6400L using xda premium

fiddlefaddle said:
Go into kfu and ten go into the boot menu... (1) then choose normal boot.. hope this helps!
Click to expand...
Click to collapse
Hi fiddlefaddle,
Thanks for the idea, but my Mac doesn't recognize the device.
Should I use a Windows machine and download the kfu somewhere?

Jmjohnson1717 said:
Is the battery low or almost dead. You could try plugging it in and see if it boots up. Mine does this exact thing when the battery is dead. Just charge it up and good as new
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Hi jmjohnson,
Thanks for your help. I'll charge it for a day and see what happens.

william_leong said:
Hi fiddlefaddle,
Thanks for the idea, but my Mac doesn't recognize the device.
Should I use a Windows machine and download the kfu somewhere?
Click to expand...
Click to collapse
Yes you should use windows... sorry I forgot you were using Mac... you can download the kfu in the android development part of the kindle forums.
---------- Post added at 09:06 PM ---------- Previous post was at 09:02 PM ----------
fiddlefaddle said:
Yes you should use windows... sorry I forgot you were using Mac... you can download the kfu in the android development part of the kindle forums.
Click to expand...
Click to collapse
Here is link http://forum.xda-developers.com/showthread.php?t=1399889

when you choose 1 for normal boot it will say waiting for device... shut your kindle off by holding the power and then turn it on.. and it will connect as its turning on

fiddlefaddle said:
Yes you should use windows... sorry I forgot you were using Mac... you can download the kfu in the android development part of the kindle forums.
---------- Post added at 09:06 PM ---------- Previous post was at 09:02 PM ----------
Here is link http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
Thanks for your patience.
I downloaded and unzipped the file. After turning the Kindle Fire on and off and "waiting for device..." didn't do/show anything else --- stuck.
Then I try to run the "install_drivers" from the extracted files list, the following message popped up:
"The current language is not supported by the Device Driver Installation Wizard.
Contact the vendor that provided you this package."
Does it mean I need to get a computer that is running English Windows to do this?
Thanks for your patience again.

william_leong said:
Thanks for your patience.
I downloaded and unzipped the file. After turning the Kindle Fire on and off and "waiting for device..." didn't do/show anything else --- stuck.
Then I try to run the "install_drivers" from the extracted files list, the following message popped up:
"The current language is not supported by the Device Driver Installation Wizard.
Contact the vendor that provided you this package."
Does it mean I need to get a computer that is running English Windows to do this?
Thanks for your patience again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

DJLamontagneIII said:
when you choose 1 for normal boot it will say waiting for device... shut your kindle off by holding the power and then turn it on.. and it will connect as its turning on
Click to expand...
Click to collapse
Thank you so much.

b63 said:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Click to expand...
Click to collapse
Hi guys,
I don't know what else to say. IT WORKS!
I'm so grateful for all of you here helping a total stranger.
Thank you so much!

glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

william_leong said:
Hi guys,
I don't know what else to say. IT WORKS!
I'm so grateful for all of you here helping a total stranger.
Thank you so much!
Click to expand...
Click to collapse
No problem... This is why we are here to help! (We all have to start somewhere) It took me 4 hours to get my drivers installed and rooted... lolz