Related
Ok im posting in hopes to help someone else and myself.
DEVICE: 1st Gen Kindle Fire (D01400)
PROBLEM: Kindle quickly flashes stock logo then displays red screen.
I created this problem by using the wrong root tool (Qemuroot) [This tool is made for a Kindle Fire HD]
I bought a fastboot cable i hopes to use KFU/KUU to unbrick the device.
However Windows 8 only shows the device driver listed as Otter2-Prod-04 (Unknown Device) I proceeded to install the ADB drivers, even manualy assigned the device driver, and disabled driving signing and reinstalled drivers. (Drivers appear to install correctly however won't show up in connected adb devices.)
At this point im going to use SoupKit. I will post the outcome.
If you have had a similar problem or know of a fix which I have yet to research please let me know.
Thanks
Tested with Ubuntu linux using soupkit & firekit.
Both resulted in <Waiting for Android device> same in windows as well.
So I tried another computer also running windows 8, installed fresh SDK/Java/Drivers.
Once again had to force the driver to replace the unknown device "Otter2-Prod-04" now the device says its working in device manager yet nothing in ADB or fastboot.
I will add when I plug the device in using the fastboot cable it shows a red fastboot text and a stoplight green is flashing.
At this point im stuck and have reached the end of google. Yup thats right the very last page.
More hours put into this. I can issue fastboot commands. So this now turns into a question.
Is it possible to restore my kindle using fastboot?
tmobile-repair said:
More hours put into this. I can issue fastboot commands. So this now turns into a question.
Is it possible to restore my kindle using fastboot?
Click to expand...
Click to collapse
You should be able to if you can push fff and recovery over and flash them via fastboot
Should enable you to have recovery back and work from there
Sent from my YP-G1 using Tapatalk 4 Beta
Well I killed my kindle.
Pushed the FFF via fast boot and now the device no longer powers on, no lights, no sign of life.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here> which was u-boot
guess its time to cash in on my my rapid exchange at Best Buy
Or get a new battery
Sent from my Amazon Kindle Fire using xda app-developers app
joshuabg said:
Or get a new battery
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
New battery ? Can you explain never heard of this before. I was under the impression that I killed the bootloader.
I was just thinking that the battery may have died
Sent from my Amazon Kindle Fire using xda app-developers app
ah that better explains it.
Thanks
My kindle fire is stuck in a boot loop (i think) it just keeps saying "Kindle Fire" then restarts then says the same thing and does this for ever in this state the computer doesnt find the device. I have a fastboot cable and it does put the device in to fastboot. Then I switch the fastboot cable with a regular kindle cable then it finds the device as otter2-prod-04. This all happened when I was trying to put twrp on it. And I think I rooted it.
If it shows up now as otter on your PC you just need to use fastboot to reflash the system image. If you are have an exclamation mark in the device manager you need to install the adb drivers for it when its in fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for the reply but another problem that i forgot to mention is that neither adb nor fastboot find the device.
Check the device manager for an an exclamation mark then also, what fastboot command are you running? If you don't run the command with -i 0x1949 it won't detect it. So for a test try running "fastboot -i 0x1949 getvar product".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
when I run that command it only says <waiting for device>. And also in device manager it has a exclamation mark.
Then u need to tell it to install the adb drivers for the device with the exclamation mark. That would be the reason the fastboot command isn't working. If u have rooted it then you should have the appropriate drivers laying around somewhere for adb mode. If not send either rpost back or pm me, and I will link u to my drivers I customized for kindles, though I am unaware if they will work with kf2 as is because I don't have its pid, only the vid may be the same, if that's the case I can always fix it and reupload it.
Sent from my Amazon Kindle Fire HD using xda app-developers app
bootloop
stunts513 said:
Then u need to tell it to install the adb drivers for the device with the exclamation mark. That would be the reason the fastboot command isn't working. If u have rooted it then you should have the appropriate drivers laying around somewhere for adb mode. If not send either rpost back or pm me, and I will link u to my drivers I customized for kindles, though I am unaware if they will work with kf2 as is because I don't have its pid, only the vid may be the same, if that's the case I can always fix it and reupload it.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
I also have a kindle fire second generation. But it's in a different bootloop, with the first bright white and orange kindle logo repeating every 10 seconds or so. Nothing else. No adb, no fastboot. Not recognized by the computer at all! Could you please help?
Sounds like you will need a fastboot cable to attempt fixing that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jarjacksn said:
I also have a kindle fire second generation. But it's in a different bootloop, with the first bright white and orange kindle logo repeating every 10 seconds or so. Nothing else. No adb, no fastboot. Not recognized by the computer at all! Could you please help?
Click to expand...
Click to collapse
You need to get a fastboot cord. There is some great info here http://forum.xda-developers.com/showthread.php?t=2271909
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
z1326 said:
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
Click to expand...
Click to collapse
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once the tablet is connected to the computer it will fall into red screen and become invisible to the computer in 1 second so the computer is not able to recognize the tablet.How can i install the necessary drivers?
BTW,you mentioned the instructions to factory reset,could you give me the link of the thread?
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have opensuse installed in my PC but that doesn't work either. Connect the tablet with the computer and the red screen shows up then the connection breaks and the tablet become invisible to the PC,just the same situation as it is in windows.
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you for you reply.I'd like to know if I could use this method in opensuse?
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I tried thay in suse but it didn't work.I think when the yellow kindle fire logo shows up the tablet is in fastboot mode but I'm just wondering why the tablet can't stay in fastboot after the screen truned into red.
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So your suggestion would be
step1，Download a Ubuntu live CD image file，write the image into a usb disk，and reboot into the live CD.
step2，Open a terminal，input the fastboot command，then connect the tablet to the PC when the terminal says"waiting for device"
step3，Then the tablet should stay in fastboot and it is now possible to fix the bootloader and system with fastboot command.
Did I understand that correctly？
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
And since my tablet is dead now， is it possible to install the fastboot driver in windows without the tablet？
It would be very difficult' unless you can get the driver into the driver cache but I haven't looked up how to do that, also on Ubuntu you will have to install the fastboot command, it should be in the Ubuntu software center, I'd give u the terminal command but I don't know the package name offhand.
Sent from my Amazon Kindle Fire HD using Tapatalk
Just out of curiosity have you tried KFFirstAide?
Sent from my KFTHWI using xda app-developers app
So I managed to brick my rooted Kindle Fire 2nd Generation after trying to install a rom with TWRP app. Anyways, I have a fastboot cable, and the correct drivers and Android SDK, but when I plug in my cable, turn off the device (holding button for 20 seconds), then turn back on, it still goes to red screen immediately after the brief kindle fire logo, exactly the same without fastboot cable. What am I dong wrong?
Would really appreciate any help .
-Thanks,
Jacoobyman
You sure the fastboot cable works? If it does I would keep the device manager open and see if it is briefly being recognized as a adb device or not. If it briefly detects it then I would attempt a "fastboot -i 0x1949 getvar product", then plug the kindle into fastboot cable while off and see if that works, and yes I know that is typically meant for a 8.9" model but if its a weird circumstance then it couldn't hurt to try.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You sure the fastboot cable works? If it does I would keep the device manager open and see if it is briefly being recognized as a adb device or not. If it briefly detects it then I would attempt a "fastboot -i 0x1949 getvar product", then plug the kindle into fastboot cable while off and see if that works, and yes I know that is typically meant for a 8.9" model but if its a weird circumstance then it couldn't hurt to try.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
No it does not detect it at all in device manager. not even briefly. :/
That sounds bad, I don't trust windows too much for debugging but I'm guessing Linux would say the same thing, what were you trying to flash that caused this?
Sent from my Amazon Kindle Fire HD using Tapatalk
The kindle is stuck in fastboot mode and will launch immediately into fastboot once the power button is pressed. Also the device does not show up in device manager when connected to a computer. Currently TWRP is installed but I can not figure out the get to the recovery. This started after flashing a custom bootloader while I was converting it into an otterx. Any help is appreciated. Thanks.
N O T E:
I found the solution to my problem. The battery was too low to boot into the recovery so after a full charge the problem was solved
SuperHira said:
The kindle is stuck in fastboot mode and will launch immediately into fastboot once the power button is pressed. Also the device does not show up in device manager when connected to a computer. Currently TWRP is installed but I can not figure out the get to the recovery. This started after flashing a custom bootloader while I was converting it into an otterx. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Stock fastboot or does it say fastboot mode.?
Sent from my XT907 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
Try powering off, and connecting to wall charger.
Sent from my XT907 using Tapatalk
sd_shadow said:
Stock fastboot or does it say fastboot mode.?
Sent from my XT907 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
Try powering off, and connecting to wall charger.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply.
It says fastboot mode and when connected to a wall charger it also goes straight to fastboot mode and is stuck.
SuperHira said:
Sorry for the late reply.
It says fastboot mode and when connected to a wall charger it also goes straight to fastboot mode and is stuck.
Click to expand...
Click to collapse
So you flashed OtterX bootloader? What else did you do? Convert to OtterX partitions? OtterX twrp?
Okay im new to this thread and am (sort of a noob dev). I have the same issue what i did was.
1. download saferoot(installed that worked perfect.
2.went into adb following your guide for twrp and fff while in adb. instead of a (-i) i thought it said (-1) so i put that after 0x1949 i think anyway.
3. noticed what i did then changed it waited a little bit and it just kept saying waiting for device. Then i closed adb and shut it off. rebooted it and opened adb nothing.
It isn't being recognized by windows and it is making the usb connection error sound when plugged in. all that adb says is no device connected. however in my windows devices menu it says other device\kindle? as in a malfunctioned device. i need to try and fix this and i wanted cm11. but if i need to go back to stock i will. Thanks.
Same issue
Relyt2012 said:
Okay im new to this thread and am (sort of a noob dev). I have the same issue what i did was.
1. download saferoot(installed that worked perfect.
2.went into adb following your guide for twrp and fff while in adb. instead of a (-i) i thought it said (-1) so i put that after 0x1949 i think anyway.
3. noticed what i did then changed it waited a little bit and it just kept saying waiting for device. Then i closed adb and shut it off. rebooted it and opened adb nothing.
It isn't being recognized by windows and it is making the usb connection error sound when plugged in. all that adb says is no device connected. however in my windows devices menu it says other device\kindle? as in a malfunctioned device. i need to try and fix this and i wanted cm11. but if i need to go back to stock i will. Thanks.
Click to expand...
Click to collapse
Did you ever get this resolved? I am currently stuck in the fastboot mode, although it doesn't say fastboot on my screen, just the non-animated "kindle fire" boot screen. I have been browsing for a while now and no solution, so hopefully if you found a fix then it is related!
I got rooted, ran some fbmode thing to get to fastboot to install a custom recovery and now I'm stuck here without being able to actually access fastboot. Shows up as "other devices/kindle" with a yellow triangle. Both "adb devices" and "fastboot devices" returns no results. I am now on Ubuntu hoping that the drivers would be as automagic as every other Android device, but still no fastboot/adb devices results.
I'll probably post a new thread by the way, but really hoped you had found a way past this already!
Thanks
uxonith said:
Did you ever get this resolved? I am currently stuck in the fastboot mode, although it doesn't say fastboot on my screen, just the non-animated "kindle fire" boot screen. I have been browsing for a while now and no solution, so hopefully if you found a fix then it is related!
I got rooted, ran some fbmode thing to get to fastboot to install a custom recovery and now I'm stuck here without being able to actually access fastboot. Shows up as "other devices/kindle" with a yellow triangle. Both "adb devices" and "fastboot devices" returns no results. I am now on Ubuntu hoping that the drivers would be as automagic as every other Android device, but still no fastboot/adb devices results.
I'll probably post a new thread by the way, but really hoped you had found a way past this already!
Thanks
Click to expand...
Click to collapse
used install.drivers.bat from kindle fire utility?
windows 7?
Sent from my XT912 using Tapatalk
sd_shadow said:
used install.drivers.bat from kindle fire utility?
windows 7?
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
Actually I followed the guide at Cyanogenmod, but was unable to fastboot so I followed their instructions to manually fastboot and after successfully entering fastboot from running their "./fbmode" script and rebooting, I'm now stuck without being able to contact the device. Nothing shows up under "fastboot devices." I guess I tried on Ubuntu and Windows 8, not Windows 7. I will try installing the Kindle drivers under Windows 7 when I get home later this evening. Thanks.
uxonith said:
Actually I followed the guide at Cyanogenmod, but was unable to fastboot so I followed their instructions to manually fastboot and after successfully entering fastboot from running their "./fbmode" script and rebooting, I'm now stuck without being able to contact the device. Nothing shows up under "fastboot devices." I guess I tried on Ubuntu and Windows 8, not Windows 7. I will try installing the Kindle drivers under Windows 7 when I get home later this evening. Thanks.
Click to expand...
Click to collapse
Hi, did you fix it? if you fixed it, please tell me, I had same problem like you did.
zjwrm said:
Hi, did you fix it? if you fixed it, please tell me, I had same problem like you did.
Click to expand...
Click to collapse
[6.3.3] Flashing FFF and TWRP without Fastboot Cable
Sent from my XT907 using Tapatalk
sd_shadow said:
So you flashed OtterX bootloader? What else did you do? Convert to OtterX partitions? OtterX twrp?
Click to expand...
Click to collapse
I flashed the OtterX bootloader and then tried to convert to OtterX partitions. Here something went wrong and now it is stuck in fastboot. The device does not appear in any way in device manager and a live Linux OS does not recognize the device either. Also, when in fastboot it does not seem to run off of the device's own battery, but I can get it to charge the battery if needed by connecting it to wall power.
Thanks for any help
SuperHira said:
I flashed the OtterX bootloader and then tried to convert to OtterX partitions. Here something went wrong and now it is stuck in fastboot. The device does not appear in any way in device manager and a live Linux OS does not recognize the device either. Also, when in fastboot it does not seem to run off of the device's own battery, but I can get it to charge the battery if needed by connecting it to wall power.
Thanks for any help
Click to expand...
Click to collapse
need to get it out of fastboot mode, just keep trying different combinations of power off, connected to pc, power on connected, power on not connected, power on not connected, power on connected to wall charger...
Sent from my KFFOWI using XDA Labs