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.
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
lob455 said:
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
Click to expand...
Click to collapse
Does it show up in Device manager? as kindle, android phone, or something else...?
sd_shadow said:
Does it show up in Device manager? as kindle, android phone, or something else...?
Click to expand...
Click to collapse
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
lob455 said:
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
Click to expand...
Click to collapse
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Thepooch said:
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Click to expand...
Click to collapse
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
lob455 said:
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
Click to expand...
Click to collapse
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Thepooch said:
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Click to expand...
Click to collapse
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
lob455 said:
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
Click to expand...
Click to collapse
Android adb interface alone is a detection of fastboot composite is normal boot. This could be due to a partially broken shell try while the device is in recovery not at the bootloader your bootmode is iffy.
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x http://techerrata.com/browse/twrp2/blaze
sd_shadow said:
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x ..................
Click to expand...
Click to collapse
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
lob455 said:
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
Click to expand...
Click to collapse
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
When in recovery if there is no adb my first thought is driver. Two other things are possible missing or broken shell or broken recovery. I myself lean to the side of it being a driver issue. Attach your working Kindle to pc while in recovery. Type adb devices it should say 12345678 blah blah recovery. If it does not then it's your driver.
sd_shadow said:
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
Click to expand...
Click to collapse
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Just place a Rom on your Sdcard and flash it.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Try the mount option in twrp again
sd_shadow said:
Try the mount option in twrp again
Click to expand...
Click to collapse
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
The battery will always charge in recovery. When it goes flat you end in a 5 second boot loop. Try 2 things since your bootloader is equipped to hand such things as a failsafe attach to pc via USB right when it powers on long press power button till it powers off and let sit for 24 hours. The low level charge might even kick in and indicate charging on the screen if so let it sit and it will eventually boot properly on its own. Good luck
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
I suspect it's the usb port that is bad, not the battery. The Kindle's usb port is weak and has a high failure rate, it can be repaired but likely not worth it, unless you know how to solder connections.
Alright so this morning my wife handed me her Kindle Fire and said "It's not working, fix it." Well that is all I got out of her, nothing of what was she doing when it went borked. All she said was yesterday she put it in her bag at the beginning of the day and at lunch time, when she tried to turn it on, nothing happened. Great, troubleshooting without a clear problem is just how I wanted to spend my day.
Device specifics.
+Kindle Fire first gen
+OtterX bootloader v2.05
+TWRP for OtterX 2.7.1.0
+OtterX partition files
+SlimROM v6.4
Windows 7 32bit enviroment
Well anyway first thing I did was plug it in to charge it. Once I plugged the device into a wall outlet the power light turned orange after a second or two but the screen never turned on. Not to the charging screen or the ROM unlock screen. Ok, no biggie, she let the battery run down and it just needs to charge.
After a few hours of charging the power light was green so I unplugged the device. Thinking the device was in the charging mode I held the power button, it turned orange then turned off but no bootloader screen or ROM splash screen. OK so that's odd. Did a hard reset and second time I tried to turn the device on sane thing, power light turned green for a few seconds and then turned off, again no OtterX bootloader or ROM splash screen. Ok, now there is a definite problem.
Plugged the device into the computer and Windows made the device connecting sound and I opened Windows Explorer. In the explorer window I saw the device connected as an OtterX, opened the tab>internal storage and all the files and folders displayed. Opened a command window from the folder I have my adb and fastboot and ran the adb devices command and it came back with the device ID>device. OK so maybe the screen is hosed. Still want to troubleshoot and attempt to re-flash the bootloader, TWRP and the ROM before I say the digitizer is hosed.
Typed adb reboot recovery and Windows made the device disconnecting sound and a few seconds later the device connecting sound. I typed adb devices and the same thing, the device ID>recovery. I was successfully able to push and pull a test file so I know adb commands are working just fine.
Here is where I'm running into a problem. I try to type the command adb reboot-bootloader and nothing happens in the command window, nor does Windows make the device disconnecting sound. I also try to hard reset the device, type the command fastboot devices, turning the device on at the <waiting on device> but it just boots into the ROM and OtterX appears in the Windows explorer window.
How do I put the device into fastboot node so I can re-flash the bootloader and recovery? Mind you as I already said at this point nothing appears on the screen so pressing the power button as normal is out of the question.
sabres032 said:
Alright so this morning my wife handed me her Kindle Fire and said "It's not working, fix it." Well that is all I got out of her, nothing of what was she doing when it went borked. All she said was yesterday she put it in her bag at the beginning of the day and at lunch time, when she tried to turn it on, nothing happened. Great, troubleshooting without a clear problem is just how I wanted to spend my day.
Device specifics.
+Kindle Fire first gen
+OtterX bootloader v2.05
+TWRP for OtterX 2.7.1.0
+OtterX partition files
+SlimROM v6.4
Windows 7 32bit enviroment
Well anyway first thing I did was plug it in to charge it. Once I plugged the device into a wall outlet the power light turned orange after a second or two but the screen never turned on. Not to the charging screen or the ROM unlock screen. Ok, no biggie, she let the battery run down and it just needs to charge.
After a few hours of charging the power light was green so I unplugged the device. Thinking the device was in the charging mode I held the power button, it turned orange then turned off but no bootloader screen or ROM splash screen. OK so that's odd. Did a hard reset and second time I tried to turn the device on sane thing, power light turned green for a few seconds and then turned off, again no OtterX bootloader or ROM splash screen. Ok, now there is a definite problem.
Plugged the device into the computer and Windows made the device connecting sound and I opened Windows Explorer. In the explorer window I saw the device connected as an OtterX, opened the tab>internal storage and all the files and folders displayed. Opened a command window from the folder I have my adb and fastboot and ran the adb devices command and it came back with the device ID>device. OK so maybe the screen is hosed. Still want to troubleshoot and attempt to re-flash the bootloader, TWRP and the ROM before I say the digitizer is hosed.
Typed adb reboot recovery and Windows made the device disconnecting sound and a few seconds later the device connecting sound. I typed adb devices and the same thing, the device ID>recovery. I was successfully able to push and pull a test file so I know adb commands are working just fine.
Here is where I'm running into a problem. I try to type the command adb reboot-bootloader and nothing happens in the command window, nor does Windows make the device disconnecting sound. I also try to hard reset the device, type the command fastboot devices, turning the device on at the <waiting on device> but it just boots into the ROM and OtterX appears in the Windows explorer window.
How do I put the device into fastboot node so I can re-flash the bootloader and recovery? Mind you as I already said at this point nothing appears on the screen so pressing the power button as normal is out of the question.
Click to expand...
Click to collapse
with OtterX bootloader v2.05, every time kindle is booting, fastboot commands can be used, but the window is short.
with kindle off, enter command
Code:
fastboot devices
then power on kindle, if you get a response like 123456789 fastboot
then you could try flashing bootloader again, but likely LCD is bad
unzip OtterX bootloader v2.05.zip, copy otterx-u-boot_v2.05.bin from cache folder, paste to your adb folder
verify md5:241A3FD1EDAD0A0D95886DDEB4693E1C
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
I'll give it another go. One thing I forgot to mention, when I rebooted the device to recovery I pressed the power button and the TWRP screen briefly displayed. Then the screen went blank again.
EDIT: I try the fastboot>devices command, power on the device and Windows comes up with device not recognized and the device booted into ROM. I have confirmed this is also happening with my Kindle Fire so looks like I'm missing a driver. Both devices connect successfully within the ROM and Recovery so is it just a bootloader driver issue????
Screen shot of the error and code number.
Windows 7 or 8?
Sent from my XT894 using Tapatalk
sd_shadow said:
Windows 7 or 8?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Windows 7 32bit. I did a search of the forums and found a thread with a link for signed Kindle Fire drivers from Amazon. Downloaded, installed and rebooted system. Plugged in and powered up my Kindle Fire into SlimKat and Windows recognizes device and I'm able to transfer files no problems. I'll have to try the adb and fastboot commands later, I have to get my son to a college entrance exam soon. I'll let you know the results when I return home.
Had to step away for a few days because work but now I have five days off to diagnose this fastboot issue. Anyway installed the signed Amazon drivers and adb still works with no issues but still unable to get fastboot to work. Next steep I updated the the adb and fastboot files from the Android SDK tools and still same issue. Next step I put my phone into bootloader and was successfuly able to issue fastboot commands so I know fastboot is working. Now I know the problem is isolated to the Kindles and not my system.
sabres032 said:
Had to step away for a few days because work but now I have five days off to diagnose this fastboot issue. Anyway installed the signed Amazon drivers and adb still works with no issues but still unable to get fastboot to work. Next steep I updated the the adb and fastboot files from the Android SDK tools and still same issue. Next step I put my phone into bootloader and was successfuly able to issue fastboot commands so I know fastboot is working. Now I know the problem is isolated to the Kindles and not my system.
Click to expand...
Click to collapse
Use the drivers from the Kindle Fire Utility, the other drivers do not work with fastboot mode
sd_shadow said:
Use the drivers from the Kindle Fire Utility, the other drivers do not work with fastboot mode
Click to expand...
Click to collapse
I'm on the OtterX partition, will the drivers still work or do I have to revert back to Amazon partition?
shouldn't need to revert, just use the install drivers.bat, then reboot pc
sd_shadow said:
shouldn't need to revert, just use the install drivers.bat, then reboot pc
Click to expand...
Click to collapse
Sweeeeet!!!!! Thank you. I've just been tasked with a project from the captain at my fire department so once again I have to put this on hold for a few hours. Once I'm done there I'll give it a go and report back.
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.