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!
Hi all,
First off, this is my first post :victory: and I need some help.
Last night I used this thread to successfully get root access on my Kindle Fire HD 8.9".
Then, wanting to install CyanogenMod 10.1 on the Kindle, I tried to install the second bootloader and TWRP Recovery. At this point, the Kindle began to reboot. When it turned on, the Kindle Fire logo appeared, shined a few times, then blank red covered the screen.
I can turn on/turn off the Kindle, but all I see is this red screen. Anything I can do?
I've looked at factory cables, hopefully there are some things I can try before I buy that...?
A factory cable won't work on the 8.9
Disconnect the USB cable
Turn the device completely off (hold power button for 10 seconds)
Enter: fastboot -i 0x1949 getvar product
Reconnect the USB cable
As the device powers up, if your fastboot drivers are working properly, the device should boot into fastboot mode. Use it to restore your saved partition images.
Thanks for reply
Hi soupmagnet,
Where do I enter the command "fastboot -i 0x1949 getvar product"?
In command prompt on the computer?
EDIT: Self-explanatory It worked perfectly - thanks!
HAVING SAME PROBLEM KFHD 8.9 2nd Gen RED BOOT.
I have the same problem. Can boot into fast mode with KFFA, but restoring stock settings seem to be Impossible. I have tried to restore with ADB, ADB (Fastboot), KFFA, and KF SRT. No matter what red boot screen will not go away and device can only fastboot. Any help?
JonnyLawless said:
I have the same problem. Can boot into fast mode with KFFA, but restoring stock settings seem to be Impossible. I have tried to restore with ADB, ADB (Fastboot), KFFA, and KF SRT. No matter what red boot screen will not go away and device can only fastboot. Any help?
Click to expand...
Click to collapse
Red screen is also considered a hard brick. Sometimes restore does not work.
Same happened here
Today I rooted my kindle fire 2nd gen10.4.8 using vroot I also installed a boot loader that as soon as I tried downloading shut my kindle fire down and when I tried unsuccessfully to turn it back on the red kindle fire symbol came for a second and then the careen was red
http://forum.xda-developers.com/showthread.php?p=46154263 follow this and you should all be away from that red screen
Sent from my Amazon Jem using XDA Premium 4 mobile app
same here but worse
My kindle is rooted and when i flahsed a recovery it asked if i wanted to boot into recovery after i said yes then when it booted the kindle fire logo appeared for about 1 second then a red screen slid in from the side now it wont boot into recovery fastboot or normal mode and i have reinstalled kindle drivers several times as well as fastboot.exe and also adb.exe and nothing works the computer sees it for 3 seconds if i hold power volume down but then it goes to red screen
You need to run this on the computer: fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in while it is off, if the bootloader isn't too damaged it should kick into fastboot. Hopefully you also installed the fastboot drivers previously or your best bet might be a Linux live distro like Ubuntu.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You need to run this on the computer: fastboot -i 0x1949 getvar product
Once it says waiting for device, plug the kindle in while it is off, if the bootloader isn't too damaged it should kick into fastboot. Hopefully you also installed the fastboot drivers previously or your best bet might be a Linux live distro like Ubuntu.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
fastboot doesn't recognize if there is a way to fix this or a way to keep the kindle connected for more then 3 seconds i would appreciate it
What does the kindle show up as for those 3 seconds? Because usually it shows up as a jem device (without the driver installed) or a adb device (with fastboot drivers installed) and in those 3 seconds that command gets it to go into fastboot mode so you can fix it. All that needs doing is the bootimg needs to be flashed or erased and fastboot should be more cooperative.
Sent from my Amazon Tate using Tapatalk
I ran the fastboot command like you said, and got my kindle to go into fastboot but i have no idea what to do next.
should i run certain files?if so please tell me where and how?
Use kindle fire first aid or system restore tool for the rest once it is in fastboot mode or flash a backup of your boot image with "fastboot -i 0x949 flash boot boot.img", that should fix a red screen/bad loop scenario where fastboot is not working well, etc.
thats the problem
stunts513 said:
What does the kindle show up as for those 3 seconds? Because usually it shows up as a jem device (without the driver installed) or a adb device (with fastboot drivers installed) and in those 3 seconds that command gets it to go into fastboot mode so you can fix it. All that needs doing is the bootimg needs to be flashed or erased and fastboot should be more cooperative.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
i cant tell what it shows up as because by the time it shows up in the device manager the kindle disconnects
how do i flash a boot.img if the kindle is only connected for 3 seconds and fastboot isn't working
A ubuntu live os probably would do the trick
May I give up kindle fire hd 8.9 ?
LinearEquation said:
Red screen is also considered a hard brick. Sometimes restore does not work.
Click to expand...
Click to collapse
As you told. I try use fastboot by KFFirst Aide or KF SRT 2.1 but not thing chance. My screen still blank red. So Sad .
My Kindle Fire HD 8.9 Use stock rom from amazon 8.5.1.
Have we have another way to fix it ?
hi every body
i have KF2 and i try root and install TWRP on it
im on 10.4.6 on my kindle
1- root my device
2-reboot in fastboot and install TWRP
3- blue kindle fire successfully install
now after reboot my device when normal boot goes to "Your kindle device cannot boot" screen and when i factory defualt back to this screen
and when my kindle boot up goes to recovery, my device stuck on kindle fire blue and do not any thing
when this happend.. when i turn of my device and turn on when cable in my device can go to fastboot but i flash otter2-u-boot-prod-10.2.4.bin and now when my device turn on when in cable cant access to fastboot
my device is on Your kindle device cannot boot screen when normal boot or stuck on kindle fire blue when go to recovery
how can fix it?! help plz
sorry for my bad english
I didn't have to reboot to fast boot to install TWRP. I just downloaded the apk from here http://teamw.in/project/twrp2/79 and installed it from es file explorer
Sent from my Nexus 4 using Tapatalk 4
now can i do?!
any one help me?!
Reza WM said:
any one help me?!
Click to expand...
Click to collapse
Do you have a factory cable?
soupmagnet said:
Do you have a factory cable?
Click to expand...
Click to collapse
yes i have factory cable in my box.. do u know any way?!
Get into Fastboot with whatever, uninstall Kindle drivers, reinstall, and do your own recovery stuff.
If by "cable in my box" you mean the one that came with the kindle, that is not a factory cable, I believe the full name is Motorola factory programming cable, I just call it a fastboot cable since you plug it in and the device goes straight into fastboot. You may not need one if the logo turns blue even if you don't have the recovery partition flashed, in my experience, once second boot loader is installed it acts a lot like the 8.9" boot loader in the way we can get it into fastboot without a fastboot cable. If your PC makes a connect and disconnect sound when you plug your kindle in and it powers on to the blue logo, check the device manager to make sure the device is not appearing as otter2 with an yellow triangle, if it is they to update the drivers with the ones in my signature. I suggest downloading and cding (from a command prompt) into kindle fire first aid's directory and running
Code:
fastboot -i 0x1949 getvar product
with the device off and unplugged, once fastboot says waiting for device, plug the kindle in and let it power on and if all goes well it will go into fastboot, and from there I think kffa can reflash the partitions. If after attempting to get into fastboot with above method and failing you will need to order a fastboot cable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If by "cable in my box" you mean the one that came with the kindle, that is not a factory cable, I believe the full name is Motorola factory programming cable, I just call it a fastboot cable since you plug it in and the device goes straight into fastboot. You may not need one if the logo turns blue even if you don't have the recovery partition flashed, in my experience, once second boot loader is installed it acts a lot like the 8.9" boot loader in the way we can get it into fastboot without a fastboot cable. If your PC makes a connect and disconnect sound when you plug your kindle in and it powers on to the blue logo, check the device manager to make sure the device is not appearing as otter2 with an yellow triangle, if it is they to update the drivers with the ones in my signature. I suggest downloading and cding (from a command prompt) into kindle fire first aid's directory and running
Code:
fastboot -i 0x1949 getvar product
with the device off and unplugged, once fastboot says waiting for device, plug the kindle in and let it power on and if all goes well it will go into fastboot, and from there I think kffa can reflash the partitions. If after attempting to get into fastboot with above method and failing you will need to order a fastboot cable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
i use your driver and can access to fastboot then i flash 10.2.3 with 3 file in fastboot to bootup my device... but when reboot my device cant boot and have tringle red logo and i dont have blue kindle fire logo... now what can i do to boot my device.. more time i do reset factory but dont change any thing and i have tringle red logo
Odd, sound alike you will need a fastboot cable this time around and you need to reflash the system image again I think, maybe the last one had a bad md5sum or something.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Did you flash the older 10.2.4 boot loader file. The newer bootloader has the hole fixed
Sent from my Amazon Kindle Fire2 using xda app-developers app
About your drivers
stunts513 said:
If by "cable in my box" you mean the one that came with the kindle, that is not a factory cable, I believe the full name is Motorola factory programming cable, I just call it a fastboot cable since you plug it in and the device goes straight into fastboot. You may not need one if the logo turns blue even if you don't have the recovery partition flashed, in my experience, once second boot loader is installed it acts a lot like the 8.9" boot loader in the way we can get it into fastboot without a fastboot cable. If your PC makes a connect and disconnect sound when you plug your kindle in and it powers on to the blue logo, check the device manager to make sure the device is not appearing as otter2 with an yellow triangle, if it is they to update the drivers with the ones in my signature. I suggest downloading and cding (from a command prompt) into kindle fire first aid's directory and running
Code:
fastboot -i 0x1949 getvar product
with the device off and unplugged, once fastboot says waiting for device, plug the kindle in and let it power on and if all goes well it will go into fastboot, and from there I think kffa can reflash the partitions. If after attempting to get into fastboot with above method and failing you will need to order a fastboot cable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have a problem with my KFHD 8.9 that i cant access my fastboot and im stuck on the orange static logo.
i downloaded your driver.zip files but i dont know what to do with them
help please
jasero12 said:
I have a problem with my KFHD 8.9 that i cant access my fastboot and im stuck on the orange static logo.
i downloaded your driver.zip files but i dont know what to do with them
help please
Click to expand...
Click to collapse
You have to right click the jem device with an exclamation in the device manager, hit update drivers and point it to where you would have extracted my drivers(might have to uninstall the old ones first), but its very difficult to do because the kindle only broadcasts in fastboot for a few seconds, its way easier to just boot a Ubuntu 13.10 live cd and do it because its doesnt require any drivers, just the fastboot command.
So I've got a bricked Kindle Fire 2. It was rooted and running perfectly previously, but then I decided to update to the newest Amazon update 10.4.6. I followed their instructions on doing it instead of flashing, and it got stuck in bootloop. Yay.
I've got a fastboot cable. When I plug it in, my Kindle displays fastboot as expected. I have one with the blinking green light, and solid red light.
When I try to enter any fastboot commands, nothing happens. For example, "./fastboot -i0x 1949 devices" (I'm on a Mac) gets nothing.
On my PC at work, it was recognized as a Kindle in Device Manager. I'm on a Mac at home (no PC) and not sure how to ensure if it's recognized or not. Running adb devices returns nothing as well.
Any bright ideas?
*EDIT:
I had a space in there that I shouldn't have. So "./fastboot -i0x1949 devices" returns the device number, but trying to flash an img does nothing. I have to cancel the entry.
Okay, NOW any bright ideas?
Your syntax is still off, try "./fastboot -i 0x1949 getvar product" and see if it spits anything out.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I've had a 1st Gen Kindle Fire HD 8.9 (or jem-pvt-prod-04) for ages. Rooted it years ago using KFFirstAide, which installed ADW Launcher (I think), but I never took the custom ROM plunge, and now I hardly ever look at it anymore. When I was thinking about installing custom ROM on my phone for the first time, I thought I'd get some practice on a device I don't mind losing (since I barely know what I'm doing...). Had the Kindle in Fastboot Mode and tried to flash different bootloader & recovery (from http://forum.xda-developers.com/showthread.php?t=2128175 ), and I probably flashed something I shouldn't have and corrupted the bootloader:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 reboot
Upon rebooting, the Orange Kindle Fire logo appeared, and froze (it never became animated or turned blue). It is now stuck there. I have held down power button for 30+ seconds, I have tried that with and without using vol down and vol up buttons. I have fully depleted the battery and recharged. I have attempted six ways to Sunday to get my computer to recognize the device so I could issue ADB or Fastboot commands, but when I connect the USB cable and start up the Kindle, Device Manager (I'm on Win 10) sees it as Android Device and shows Android ADB Interface driver for literally one second, then sees the device as disconnected. When I show hidden devices, I can update the driver for that device, and I've tried various ones, but all to no avail. I went further out on a limb and created a Ubuntu Live USB (though I have never used a Linux OS on my PC). I tried to get Java and SDK working in Ubunto OS, but I'm way out of my depth.
If anybody has any suggestions (other than quit doing things to your devices that you don't fully understand...), or can help me try other ways to get the device recognized and able to receive ADB/Fastboot commands, I'd really appreciate it.