Related
First, sorry for my english.
I have a Kindle Fire OS 6.2.1. I dont know why my Kindle didn't work with ADB driver.
Only one time it work when I used Kindle Fire Utility 0.9.1, then I run option 2 then 3. After that, my Kindle reboot and stop at logo's screen, and adb didn't recognize my Kindle anymore.
I tried install/uninstall, downloaded new driver, install Android SDK,.... but don't luck.
All method to unbrick need adb work well.
Help me fix this issue, please. I live in Asia and can't return my Kindle for Amazon.
first - have you read and done the tricks from 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
second - don't use the drivers from kfu - do according:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
This helped me get out of a brick 4 times I hope it helps you-
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Just to be redundant this is not a 'brick'
Confirming the driver issue- gotta use diff drivers I restored my Win8 to the kfu .6 just to get adb working
Sent from my Amazon Kindle Fire
b63 said:
first - have you read and done the tricks from kfu ?
second - don't use the drivers from kfu - do according:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
Click to expand...
Click to collapse
The 2nd option help me out to get my kindle fire recognized.
Thanks.
On mine I booted it up to the firefirefire logo and right before the screen flickered I'm not sure if yours does that) I ran a command on the an adb shell command then re ran Kindle fire utilitity's taro installed and it fixed it!
I spent two weeks with a similar problem, finally have everything working. My biggest problem was a USB to micro USB cable that worked fine for charging, but seldom worked for communication between the Fire and my PC. Try another cable.
If your PC beeps when you insert the USB cable, then the cable is probably OK.
Next likely problem is that you don't have ADB installed properly. You can check this by typing adb help at the CMD prompt. (START, RUN, CMD, adb help) If you get a lengthy response, then ADB is installed OK. If you get an error msg, then you need to fix that. Google "How to Install ADB"
If ADB is OK, and you still can't see your Kindle, you probably haven't updated your PATH Variable properly. "How to Install ADB" should include instruction for doing that, but you need to be sure you enter the actual path that your have to the SDK Platform_Tools folder on your PC, not the one described in the video.
Once I managed to get these three thing all working at the same time, things started to fall into place. To most of the people on this forum, these things are probably obvious, but to an old geezer like me every step is a painful learning process.
Good luck
I am stuck with this headache and have stressed my self for hours trying to fix this so now I turn to you guys for help.
My Situation:
I had kindle to 6.2.1 then I rooted it, installed CM7.
after using it for 7+ days there is an update of CM7 by another dev. which had sound in the CM7 so I tried to flash it.
I put it in the SD card and renamed it CM7.zip from Update.zip so I flashed on Custom Recovery to flash the Update.zip later finding out that I renamed it to CM7.zip so I was stuck at Customer recovery bootloop so I enter the command to flash stock recovery to boot as the CM7 required.
so after stock recovery flash on Kindle the Kindle got stuck on the "kindle fire logo"
I think it was stuck in Fastboot.
I tried with KFU and Kindle Fire Unbrick software but the thing is NONE of them detect my kindle
I have tried soo many ways to Get my kindle detected to unbrick it but still no luck
Any help would be greatly appreciated.
Thanks
BUMP!
Still need help with a bricked kindle
BUMP!
Any1?
Kindle Still Bricked and not working >.<
Have you tried Kindle Fire Utility 0.9 to install the latest drivers? After that install Kindle Fire Unbricking Utility 0.1 to unbrick. If that doesn't work, reply with a detailed explanation of what you're seeing and what you have already tried.
This post has links to both and a good alternative option: http://forum.xda-developers.com/showthread.php?p=21232193
Good luck.
Sent from my rough sketch of a Vibrant on a brick.
Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?
umarsl said:
First of all, I would like to thank you guys for your help, really appreciate it.
Now, I have tried both of your suggestions and I had no success
I have the latest drivers and everything but still adb doesnt detect it and the KFU says adb status: offline, bootmode: unknown and adb root: No.
in the Kindle Unbrick tool it says error finding device and KFU is stuck on waiting for device.
whenever I connect my kindle fire I dont hear any sound but when I connect my htc sensation it says device ready to use.
I think I will have to contact amazon to get this kindle fire replaced ='(
Click to expand...
Click to collapse
In my case, KFU also stated
status: offline
bootmode: unknown
adb root: No
but it still worked when I tried to change bootmode to 4000.
Also, are you sure your KF is charged enough to start? Try plugging it for a while, then recheck in windows.
b63 said:
it looks like you have a driver issue - primarily
this is what has to be corrected first
then we could see what to do
therefor some info about your os would be helpful (os/bit)
what drivers are you using ?
do you have the newest kfu available ?
if yes - moved and renamed to c:\kfu ?
Click to expand...
Click to collapse
I am running Windows 7 64bit on two of my laptops and windows 7 32 bit on my desktop.
the Kindle logo is not glimmering or flashing so it is in fastboot, I know that much.
I have tried the drivers that came with the KFU 0.9.2 (Newest, I believe)
and Yes the Kindle Fire is fully (if not mostly) charged as I had it on the charger for 6 hours last night.
and No I have not placed it or renamed to c:\kfu
I will let you know in a minute about the results
If it keeps saying Waiting for Device then it's not really in fastboot. I had a similar issue and got it solved through this thread:
http://forum.xda-developers.com/showthread.php?t=1430515
It was stuck in a boot loop and appeared like it was in fastboot, but it would hang up and not respond. You may need to install the fastboot package manually and force it into the right mode. Then you can load TWRP and put it all back together.
If ADB isn't working though, you will need to start by getting that to work. It sounds like a driver issue even though you said you worked on that. You should try the Ubuntu boot method and Firekit to install the fastboot package through ADB. Those are outlined in the link above.
got it ?
if you have a 32 bit machine available that is the better choice cause you don't have to hassle with the 64 bit drivers too
here some information that should clarify the driver things:
in normal boot the device is "android composite adb interface"
in fastboot the device is "android adb interface"
here again all the possible commands to change bootmode:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Still no results
I connected my brother's kindle and the computer immediately recognized it and when I connect mine, it doesnt work! :'(
apparently still having the driver issues :'(
any help?
I have tried the KFU driver and that didnt work
I had a similar problem while trying to install TWRP the first time via KFU except I was stuck at the yellow triangle and not the Kindle Fire screen.
First I replaced run.bat in the KFU folder with the one from this post because my Kindle was 6.2.2. Next I installed the drivers for my uknown device in device manager both by pointing the unknown device to where I saved android_winusb.inf and also ran the install_drivers.bat. I got an error saying they could not install.
Next, I followed the steps here
•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
Click to expand...
Click to collapse
and when I rebooted my Kindle, it booted normally and appeared as Kindle in Device Manager. So despite KFU not detecting my device, and the drivers giving me problems, I was still able to issue the command in KFU for normal boot mode and held the power button for 30 seconds and it was back to normal. This is on a Windows7 64bit machine. I hope this helps.
Make me the third. Here is my story.
I have lots of rooted and rom'd devices so I'm agreeing that this might be device related and not the drivers? Or maybe specifically the Kindle driver? Since all my other devices work fine.
I bought my kindle and rooted it on day one 6 weeks ago using TWRP. things have been perfect on my KF. I decided to install CM7.1 yesterday morning and it was working great. I just realized I never rebooted it so what Im going to say shortly may have been bound to happen.
So last night I decided to add a google Market update per a link on XDA that stated this can be updated to my current CM7 install. After this my KF just kept going into TWRP automatically. I then decided to load my backup rooted stock room and still my KF just boots into TWRP.
Next I decided to use rootkindlefire's unroot/stock rom to 6.2.1 (drop the bin renamed to update.zip to the SD) and got a TWRP logo screen. I powered off a couple times and now I get a KF logo screen. I tried the 20 second reset and it flashes (Windows XP see the request for a USB device also), but no KF OS loads. Windows is showing Android Phone > Android Composite ADB Interface but the SDcard does not mount files.
I tried:
Kindle Fire utility and it says: Oops... something went wrong. We are unable to locate your Kindle Fire. Make sure it is plugged in and powered on. Press any key to continue . . .
SuperOneClick 2.1 says device isn not found
SuperOneClick 2.3.3 just sits at * daemon not running. starting it now on port 5037 * * daemon started successfully *
Stuck on logo option for Kindle Fire unbrick says: Kindle unbrick in progress... adb server is out of date. killing... * daemon started successfully * error: device not found error: device not found Congratulations, your Kindle should be unbricked!
My Sonxy Xperia, Eris, Vibrant and LG470 all work fine when connected.
At a loss here..
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
scrols said:
Hey,
My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot:
Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized.
BUT this worked for me. I do not know if it will work for you! I takeno responsibility or whatsoever.
Good luck sir. Do not give up
Click to expand...
Click to collapse
I went to another site and was able to get my kindle recognized by my PC (manually edited the drivers and reinstalled) and now Kindle Fire utility sees my device but KFU keeps saying these two lines when attempting to recover and root
adbd cannot run as root in production builds and
- exec '/system/bin/sh' failed: No such file or directory (2) -
So i may have bricked my Kindle Fire. I rooted it successfully, did not install TWRP or anything similar. Installed the Android Market but could not get it to work so i "deleted from device" from my carousel and my Kindle turned off and couldnt turn back on Then I attempted the Kindle Unbrick Tool and tried that, but it seemed that it could not find my Kindle on my computer (I'm running windows vista) Even when i plug in the usb it doesnt make the happy little noise it makes when you plug in something. I went to device manager and saw that it was recognizing it both as "Android" and under portable devices, "Kindle" or a few times it came up as "L" which is the usb port I had it plugged into.
tldr; Unbricking tool is not "finding" my Kindle on my computer Also I'm kind of a n00b at this, as far as running codes and whatnot.
side note: My kindle is also low on battery at the moment. I have it charging right now, so maybe that's a factor?. When I turn it on, I get the Kindle fire logo but no animation, it still stays lit after that screen as if it's still on but nothing happens..Any advice would be appreciated ^.^
Hey, My kindle got stuck in fastboot too. It wasnt recognized by KFU and unbricking tool. Here is how I managed to recover to normal boot: Remove the drivers in device manager and reboot your stuck kindle fire, but do not unplug it (just hold power button for pretty long time till it shuts down, then just turn it on). Windows should recognize some device. now install adb drivers and launch KFU. If it sees your fire you are good to go, if not just try changing bootmode to 4000 as if it was recognized. BUT this worked for me. I do not know if it will work for you! I take no responsibility or whatsoever. Good luck sir. Do not give up
So after reading and trying how others on here fixed that very same problem I deiced its time to make a post and ask for help because those other methods did not work.
Ok I did something stupid and I went ahead and did a factory reset to my kindle. Yes I know it was a complete noob thing to do and I should have known better seeing that I have rooted and flashed ROMs on all my other android devices and never once did something that dumb but I did it this time. Now I do have a back up made and had it safely stored on my PC.
Problem is that I can't get into recovery it stuck on the FFF logo and holding down the button only brings it back up. When the device restarts windows recognizes it as an unknown usb device and won't connect and Adb also wont recognize the device or show that it is connected. So now I need to ask someone who is more knowledgeable then me on what to do next. Any help will be appreciated
Ok update: Was able to solve my own problem using the Kindle fire utility and by uninstalling the drive for the kindle through the device manager, then using the drive install_drivers.bat in the KFU folder to reinstall the drivers. I next unplugged my kindle from the pc, turned it off by holding the button on the kindle in and then restarted it with the usb plugged into the pc. My Pc recognized my kindle and I was then able to use KFUs Bootmode menu and once in there used option 1. to boot it in normal mode. Hope this helps anyone who was stuck like I was. My memory of which adb commands to use was a bit rusty but using the KFU helped with that part.
I have read the write up on how to restore the Kindle after being bricked by miui4.0
I however am on a new macbook pro, have downloaded KFU for mac, have everything installed and where it should be, (i suppose. I have done this on my parents windows machine but this mac is new to me.) I have all files needed in the same folder as dab.exe and fastboot.exe.
When I run either script it just pops up in the terminal and really doesn't run through the script like it does on windows. And definitely nothing happens.
When I open the terminal and start putting in the commands in the thread about restoring the kf, every command just says "command not found"
So now I'm stuck, and would very much like to use my kindle fire. I will get back to my parents house to use the windows machine in a few weeks and can def. get it restored then, seeing as how I know how to do it on windows, but this is my first mac.
Thanks guys!!!
Chad
EDIT: SOLVED.
after spending about 20 minutes with "b63" on TeamViewer, I was able to get the commands correct for a mac. mainly just newbie stuff due to the os change.
just took a look to the linux/mac version
if you open a terminal and cd to the tools directory of kfu then there are the commands
for mac it's:
adb.mac and fastboot.mac
that means you have to adapt the commands like eg:
fastboot.mac -i 0x1949 boot twrp-blaze-2.0.0RC0.img
edit: attached corrected run.sh - just rename (remove .txt)
trying to cd to the folder but says no such directory.
even though when I go through the hd, its right there.
the terminal doesn't make sense to me like it does with a PC.
Need Assistance Via Teamviewer to Fix Kindle
Hi
My Kindle is stuck into the yellow triangle blinking when I link it via usb.
The Kindle run flat and when I tried to get it going again it was stuck in this loop.
I tried unsuccessfully to get it out.
If there's someone willing to assist me via teamviewer please let me know.
I am on a mac.
when the yellow triangle is blinking it is booting constantly
means the battery is dead - try to charge it with the wall charger
for some hours - best over night - if you don't use the original charger
be shure it has ~2A - most replacement chargers have only 1A - that is
too few to charge when the battery is so low
wall charger
Hi b63
I have no wall charger. I will check with the friend who brought it into South Africa if he got one with.
If not. You are saying that I can get such a wall plug micro USB as long as it has ~2A.
Thanks for that.
wotandsdwys said:
trying to cd to the folder but says no such directory.
even though when I go through the hd, its right there.
the terminal doesn't make sense to me like it does with a PC.
Click to expand...
Click to collapse
On a Mac, type:
cd <space> and drag the folder you want to change to, into the Terminal window.
You can only cd directly into the next folder in the tree. Otherwise, you need to type the full path.
i.e. $ ~/Users/JohnDoe/AndroidSDK/platform-tools
Sent from my Kindle Fire using xda premium
johanhorak said:
Hi b63
I have no wall charger. I will check with the friend who brought it into South Africa if he got one with.
If not. You are saying that I can get such a wall plug micro USB as long as it has ~2A.
Thanks for that.
Click to expand...
Click to collapse
every replacement usb charger will work as long it mets the specifications
I am currently working on a Mac, and do not have access to Windows.
My Kindle Fire was running v6.3, and I rooted it using BreakDroid v0.6.
And now I'm stuck at the yellow triangle. Pressing the power button during this phase won't bring me into recovery mode.
While the device is powered on, and plugged into my Mac, at the yellow triangle screen, I opened a Terminal window and typed "adb shell", but am receiving "error: device not found."
Also, wotandsdwys, where is the post on how to restore the Kindle after being bricked by MIUI 4.0? A link would be very helpful.
And is this the Kindle Fire Utility you are referring to? Is the script that user b63 attached to this thread supposed to convert that to be able to be used on a Mac?
Anything at this point would be helpful. I keep finding solutions that require a PC, but not so much when you're on a Mac.
Thanks!
STuck on Yellow Triangle with Mac
cocco3 said:
I am currently working on a Mac, and do not have access to Windows.
My Kindle Fire was running v6.3, and I rooted it using BreakDroid v0.6.
And now I'm stuck at the yellow triangle. Pressing the power button during this phase won't bring me into recovery mode.
While the device is powered on, and plugged into my Mac, at the yellow triangle screen, I opened a Terminal window and typed "adb shell", but am receiving "error: device not found."
Also, wotandsdwys, where is the post on how to restore the Kindle after being bricked by MIUI 4.0? A link would be very helpful.
And is this the Kindle Fire Utility you are referring to? Is the script that user b63 attached to this thread supposed to convert that to be able to be used on a Mac?
Anything at this point would be helpful. I keep finding solutions that require a PC, but not so much when you're on a Mac.
Thanks!
Click to expand...
Click to collapse
I am in the same boat. I used Breakdroid, and was stuck at the kindle fire boot screen. Stupidly turned the power off and have been stuck on the yellow triangle. Could someone help me out? I am a total noob at this stuff
Bump?
cocco3 said:
Bump?
Click to expand...
Click to collapse
Don't own a mac but consider this link for how to input adb commands
http://forum.xda-developers.com/showthread.php?t=1443071
and this link for the necessary commandlines:
http://forum.xda-developers.com/showthread.php?p=24129239
If you are stuck at the boot logo then you are in fastboot mode. ADB commands will not work here, only fastboot commands.
Read this thread: http://forum.xda-developers.com/showthread.php?p=23747567
It will tell you what you need to know about the difference between the two.
If your boot logo is simply a Kindly Fire logo without an android above it then you need to install FIREFIREFIRE, else you will not be able to enter recovery with the power button.
Find the FIREFREFIRE development thread for instructions on installing.
Mac is not much different from PCs when using adb and fastboot other than driver installation, but you should already have that taken care of.
In some cases you may need to type ./fastboot ... rather than just fastboot but other than that the commands are the same.
Sent from my Amazon Kindle Fire using xda premium