Related
Just got a new KF today and tried loading Go Launcher EX. Got to the point where I rebooted the KF and told it to always boot to GO Launcher..... BIG MISTAKE... something had gone wrong in the go launcher install and Not I have a pretty Kindle Fire Logo on my screen that will not go away.
I have downloaded KFU and Installed the drivers. With my KF on and plugged into usb my device manager shows. "Android ADB Device" which if i read correctly is what it should show.
But inside KFU it does not seem to connect to the device.
Is there something i have missed or is it truly a brick ...
I tried that ... Uninstalled device (made sure to remove driver) refresh device manager.. update drivers on kindle device... Then tried KFU
All I keep getting is waiting on device...
On the main screen it says:
ADB Status: Offline
Boot Status: Unknown
When I go into the Bootmode Menu and select 1 it sits on a screen saying waiting on device.
This is pretty much where i have been stuck at all day ...
Power your kindle off by holding the power button for like 30 seconds its very likey that adb will not detect your kindle it cannot while its in fastboot But first try this shift plus right click on the tools folder in kindle fire utility select open command window here power your kindle off and enter the command Fastboot getvar product (hit enter)Plug your kindle in it will power on in fastboot If you get the response product: kindle then we can move on.
if you get the response product: kindle Type fastboot oem idme bootmode 4000 (hit enter)fastboot reboot (hit enter)
Nothing.?then Then next time try fastboot -i 0x1949 getvar product (hit enter) when it says <waiting for device> plug in your powered off device if it says product: kindle type fastboot -i 0x1949 oem idme bootmode 4000 (hit enter)fastboot -i 0x1949 reboot(hit enter)
Fastboot getvar product
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
I tried both of these. Each time i unplugged the KF, held power for 30 secs(using a timer),typed command then hit enter, then plugged in KF.
both times it powered on and went to the Kindle Fire logo and the command window just said waiting on device. A side note is that during power on but before windows beeped as if it had recognized the device the KF logo blinked a few times.
Don't unplug it.
I've found with mine, whenever I'm stuck in fastboot I do the following:
1. LEAVE THE KF PLUGGED INTO THE COMPUTER AT ALL TIMES!
2. Uninstall all instances of the Android Device in Device Manager.
3. Power off KF by holding the power button for NO LESS than 30 seconds. Even when it looks off, keep holding it and count to 30. (keep plugged in)
4. Power on the KF by simply clicking the power button once. (still plugged in)
5. Once the KF is back at fastboot, the computer should automatically install the drivers from the KFU folder, if not then manually point it there.
6. Open KFU and start run.bat
7. At the menu, regardless of device status (mine says offline/unknown when in fastboot mode), press 1, enter, 1, enter.
so are you suggesting i do the command line stuff?
EDIT.... any way i cut it im getting the same Kindle Fire screen ...
one I used this -i 0x1949 one I didnt because sometimes it doesnt matter but lelandfried is suggesting to try to use kfu to reset your bootmode which is logical and keep working with your drivers which also makes 100% sense keep trying you could get lucky and something will work its windows darn drivers that are killing you another option is this http://forum.xda-developers.com/showthread.php?t=1670405 then you wont be messing with the drivers anymore add sudo to the front of all your fastboot commands.
If I have ubuntu running on a VM can I do this through there? I have mixed success using usb devices
whoops sorry soupmagnet will know if it will run on a vm ask him he can give you the best advice
No problem. Im going to give it a shot... I have done everything i can think of to get the right drivers on here in windows. As best as I can tell from the chart on this thread http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
I have the ADB driver loaded for Recovery,Stock SW or ROM (USB Debog On)
I think I will try the ubuntu thing for a bit .... Frustrating .. very frustrating
I gave ubuntu VM a shot. I was able to connect to the device via usb in the VMWare console then i tried to run the two commands given earlier in this thread ... but i was never able to get anything but a <waiting for device> message in the terminal window.
Hopefully someone can give me some new guidance. Or show me where im going wrong so far. I feel like its something dumb that im missing ...
did you use sudo before all your commands and plug in your prepowered off kindle in when it says waiting for device?
Deslyxia said:
I gave ubuntu VM a shot. I was able to connect to the device via usb in the VMWare console then i tried to run the two commands given earlier in this thread ... but i was never able to get anything but a <waiting for device> message in the terminal window.
Hopefully someone can give me some new guidance. Or show me where im going wrong so far. I feel like its something dumb that im missing ...
Click to expand...
Click to collapse
Soupmagnet said he had problems getting the KF to work with VMWare in fastboot mode. YMMV. I use Parallels Desktop and have no problems with it.
The most telling thing you said in this thread...
Deslyxia said:
A side note is that during power on but before windows beeped as if it had recognized the device the KF logo blinked a few times.
Click to expand...
Click to collapse
If the logo "blinked" a few times, then it's not in fastboot mode. It is most likely past the bootloader stage, loaded the boot partition and trying to start up the system. At this point, your best hope is to send it some adb commands to get the KF into fastboot or recovery, but it might not be far enough along in the process to accept adb commands either.
Read the following post about fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
Most people in your situation end up buying a factory cable.
Okay. thank you to everyone for the help so far. From within Ubuntu I was able to use this guide http://forum.xda-developers.com/showthread.php?t=1414832 to get into fast boot mode. From there I installed TWRP Recovery then rebooted into recovery mode. Then I installed FFF, Rebooted into recovery mode and reset to factory.
When I rebooted I got the FFF boot screen and let it boot like normal to a factory reset KF.
Again thank you all for your help .
I'm glad you got it going just make sure you do all the right things if you start flashing roms don't be afraid to ask questions its better than getting messed up again always make backups and do proper wipes just don't wipe your SD card or let your battery die good luck
I dunno how to do adb thru Ubuntu, even though I have it on my desktop. I do all my adb stuff through my Windows laptop.
Glad to hear you got it going. I'm bookmarking this thread for the Ubuntu links and info, Thanks!
My kindle was in the stuck in the recovery loop and wouldn't connect to the pc so I tried using this tool.
http://forum.xda-developers.com/showthread.php?t=1428428&page=17
I tried using the recovery loop but it didn't work so i pressed other... looking to see more options. In the end, it connected to the pc but i think it broke it. Now when i boot up the kindle, it is stuck at the screen that says kindle fire and has the little andriod guy on it. Can anyone provide help to fix it? And is it broken?
lordofthenoobs said:
My kindle was in the stuck in the recovery loop and wouldn't connect to the pc so I tried using this tool.
http://forum.xda-developers.com/showthread.php?t=1428428&page=17
I tried using the recovery loop but it didn't work so i pressed other... looking to see more options. In the end, it connected to the pc but i think it broke it. Now when i boot up the kindle, it is stuck at the screen that says kindle fire and has the little andriod guy on it. Can anyone provide help to fix it? And is it broken?
Click to expand...
Click to collapse
You have FireFireFire installed so this should be fairly easy.
But would you please explain the so called "recovery loop"?
Yes, i do have firefirefire installed, i installed twrp firefirefire, and everything to make the kindlefire and andriod about a year ago. The recovery loop is the twrp loop where you are stuck in twrp no matter how many times you restart. That's just what i call it but yeahh sorry for making it hard for you to understand.
No biggie. I just find it best to not make assumptions around here.
Download this and flash it in recovery
http://forum.xda-developers.com/showthread.php?t=1632375
Read the thread to learn how to use the boot menu then use it to reset your bootmode.
How would i get into recovery? I can only reach the logo screen right now, i can provide a picture tomorrow if needed, thanks!
When you get to the white kindle blue fire quickly depress the power button a few times till you get the boot menu, then select --recovery-- .
soupmagnet said:
I just find it best to not make assumptions around here.
Click to expand...
Click to collapse
And...I just ate my words.
lordofthenoobs said:
How would i get into recovery? I can only reach the logo screen right now, i can provide a picture tomorrow if needed, thanks!
Click to expand...
Click to collapse
TWRP is recovery. You are stuck at the FFF screen, not the TWRP screen. Upon startup, hold the power button until it turns orange then release. Or turn your device off, enter "fastboot oem idme bootmode 5001" at the command line and turn the device on when you see "waiting for device".
From there, you can use adb to push the FFF1.4a.zip to your sdcard, or mount your sdcard to USB and transfer it like that.
My directory is to C:\kfu\fastboot... uhhh when i type in fastboot oem idme bootmode 5001 or fastboot getvar product, it doesn't do anything and just skips to the next line waiting for another input. I am currently running windows 7
except ppinrum
lordofthenoobs said:
My directory is to C:\kfu\fastboot... uhhh when i type in fastboot oem idme bootmode 5001 or fastboot getvar product, it doesn't do anything and just skips to the next line waiting for another input. I am currently running windows 7
Click to expand...
Click to collapse
Excuse me for double post, but i guess this is somewhat a bump to change my old edits because i finally decided to read some old posts but this part is the most troubling and sorry for not reading threads beforehand and rushing into a conclusion.
Pm sent unread your private messages.
lordofthenoobs said:
My directory is to C:\kfu\fastboot... uhhh when i type in fastboot oem idme bootmode 5001 or fastboot getvar product, it doesn't do anything and just skips to the next line waiting for another input. I am currently running windows 7
Click to expand...
Click to collapse
I'm pretty sure that isn't even possible.
There are two things that can happen when when you enter "fastboot getvar product":
You will see the "waiting for device" message, or you will see "kindle".
Anything else would make me wonder if either your fastboot.exe is corrupted, or there is something wrong with the procedure in which you are entering the command.
Maybe it's time to try on a Linux liveUSB.
"That's a special kind of stupid. The kind that makes me laugh"
aceniop scruples
soupmagnet said:
I'm pretty sure that isn't even possible.
There are two things that can happen when when you enter "fastboot getvar product":
You will see the "waiting for device" message, or you will see "kindle".
Anything else would make me wonder if either your fastboot.exe is corrupted, or there is something wrong with the procedure in which you are entering the command.
Maybe it's time to try on a Linux liveUSB.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
So thepooch and i found out that it's not working because of my 3.0usb ports but i'll try again. He also recommended me to use the LinuxliveUSB as well.
We also had another problem with the install_driver.bat inside the kindle fire utility where it wouldn't install the drivers.
I tried searching for methods to install unsigned drivers but none of them worked. Does anyone have a method they that could possibly work?
Thanks!
The device is in fastboot but will to accept fastboot commands terminal instantly reverts to native prompt. The driver uninstall was a hassle and installation happens so rapidly I am inclined to think there is an issue there. The 3.0 usb could be the largest hurdle an is very likely the issue at hand. My guess is that this pc did not do the original rooting and the cable is confirmed different which lends a little more flavor to the 3.0 problem. Best bet is a different machine or a live usb on a different machine just my opinion.
You're all probably thinking "Oh he is stuck in a recovery loop and here's how you get out of it."
This all starts with the fact that I'm trying to use Kindle Fire Utility to root my device. However the normal circumstance is that it must boot into fastboot but in my case it is impossible to get past fastboot no animation and just sits there. I've been trying to my research on how to do this but I can't seem to find an answer for this. I've already told my computer to boot it back into normal mode via ubuntu with the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and it works fine that puts me back in normal mode past the no-animation screen.
So I'm still trying to get rid of this fastboot recovery loop that still persists. I've already restored back into stock rom and the same problem persists. Has anyone have had this experience and successfully the eliminated the loop problem?
In a similar circumstance is that if I have my normal cable or factory cable plugged into between my machine and the kindle, it does the same issue and does not get past no-animation part.
I'm guessing it comes down to the fact that there is a misconfigured setting on the kindle regarding TWRP perhaps. I would appreciate ANY help whatsoever. I want to eliminate this stupid problem. Now, remember, I am able to get back into normal mode via ubuntu with the above command line so that isn't the issue here. The issue is this fastboot / does not get past no-animation stage that I want to fix.
EDIT: I've resolved this. I was missing the fff bootloader which was causing all of my issues in the first place. Sorry for wasting your time looking at this.
So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?
arthurk62 said:
So here's what happened.
About a year ago, I rooted my Kindle and flashed CM 10.1. Everything worked out great.
Fast forward to a few days ago, I thought it'd be cool to give the KF an update. Total mistake. I wanted to flash CM 11, but figured it'd be important to install the latest version of TWRP as well. Before I knew it, my Kindle Fire was bricked. In the process of updating TWRP, I downloaded and flashed the most recent img file (using Flashify), and after the device rebooted automatically, it wouldn't move past the silver/orange "Kindle Fire" screen. I've since tried a number of things, including powering the device on and off, and holding the volume up button to boot into TWRP, but nothing seems to work. I always end up getting stuck at the same screen.
I've also tried using Kindle Fire Unbrick Utility, but I get a "device not found" message. My computer makes a noise, as if to recognize the KF when it powers on, but within seconds, loses communication.
Am I screwed?
Click to expand...
Click to collapse
Can you get into fastboot? Did you restore your backup?
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I had a feeling that must've been the case.
I followed your directions, but can't get past the "<waiting for device> message in CMD. Turning the kindle on or off doesn't seem to make a difference. Am I doing something wrong? Are there other alternatives?
Did you follow the steps in the right order
Turn of Kindle
connect the wire
type command
when waiting for device is shown then only turn on your kindle
Similar Problem
skullarc said:
Don't worry you must have flashed TWRP for the wrong kindle generation.
Connect your kindle to your pc with the normal cable that is provided with your kindle. Now turn your kindle off and type the following in your cmd
fastboot -i 0x1949 getvar product
now it should show
< waiting for device >
then turn on your device
you should be in fastboot now.
From here follow this thread from step 2
forum.xda-developers.com/showthread.php?t=2128175
Click to expand...
Click to collapse
I have a similar problem. I try to give the "fastboot -i 0x1949 getvar product" in windows cmd but it just gves an error. Do I need to install something to fix this
My guess is you don't have the right drivers installed. You have to install the driver while the device is attempting fastboot. If you have the device manager up you'll see it flash for a second when it boots. Right click when it flashes and install the driver.
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
joeldf said:
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
Click to expand...
Click to collapse
When it's in fastboot mode, use fastboot commands, not adb
Sent from my sailfish using XDA Labs
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
joeldf said:
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
Click to expand...
Click to collapse
Did you watch my video?
Sent from my sailfish using XDA Labs
sd_shadow said:
Did you watch my video?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I watched several videos, and I think I started yours at one point, but between my 8 year old running around saying it's almost midnight (it was new years eve), and then trying to get him to go to bed, by the time I came back to this, I may have lost track of what I was watching.
Moral of the story, do this kind of thing without interruptions...
I did re-watch your video all the way through and I see that what happened was normal.
Still, there was that error trying to reset the bootmode (I didn't get what you got), otherwise, it still works and re-boots fine now. Even went into Recovery.
Next thing is trying out a new rom.
Thanks again.
MY DEVICE IS ALSO STUCK!!! After doing the fastboot reboot it gets stuck with the lifeless bootscreen and doesn't do anything from there, I've also tried to use the set boot mode but it hangs on waiting for device