Related
I got this kindle fire that I am trying to fix for my kid. I don't know what firmware was in. The KF has never been rooted. We tried to call Amazon for a replacement, but since I didn't remember which email account was tied to this KF and I couldn't find the Serial Number either, I got stuck with it. If could make this device to boot one more time to see the amazon account or the serial number that will be great.
Well anyways, these are the symptoms. After lots of hours of reading about bricked Kindle Fires I decided to order a factory cable suspecting the problem was a low battery KF going into a 5 second loop. The process went good. I was able to flash FFF 1.4a and TWRP 2.2.2.1 by going into fastboot mode, but the problem is that the KF does not want to start in recovery mode, nor in normal mode.
At this point, I think I can rule out a battery low problem, but I am not sure.
No matter what I do, I cannot enter to adb mode, and this is the real problem I don't seem to find an answer. If there was a way that I could upload the firmware from fastboot mode or a tool that forces recovery mode.
As I said this KF was always stock until today that I tried to unbrick it by installing the FFF and the TWRP. The TWRP never started.
As I said earlier my only objective at this point is to recover the serial number or the account email associated with my KF.
Question 2, how can I revert to the stock bootloader if everything else fails?
Any suggestions, links, ideas will be welcome.
gwmadrigal said:
I got this kindle fire that I am trying to fix for my kid. I don't know what firmware was in. The KF has never been rooted. We tried to call Amazon for a replacement, but since I didn't remember which email account was tied to this KF and I couldn't find the Serial Number either, I got stuck with it. If could make this device to boot one more time to see the amazon account or the serial number that will be great.
Well anyways, these are the symptoms. After lots of hours of reading about bricked Kindle Fires I decided to order a factory cable suspecting the problem was a low battery KF going into a 5 second loop. The process went good. I was able to flash FFF 1.4a and TWRP 2.2.2.1 by going into fastboot mode, but the problem is that the KF does not want to start in recovery mode, nor in normal mode.
At this point, I think I can rule out a battery low problem, but I am not sure.
No matter what I do, I cannot enter to adb mode, and this is the real problem I don't seem to find an answer. If there was a way that I could upload the firmware from fastboot mode or a tool that forces recovery mode.
As I said this KF was always stock until today that I tried to unbrick it by installing the FFF and the TWRP. The TWRP never started.
As I said earlier my only objective at this point is to recover the serial number or the account email associated with my KF.
Question 2, how can I revert to the stock bootloader if everything else fails?
Any suggestions, links, ideas will be welcome.
Click to expand...
Click to collapse
I hate to ask this question but do you know how to access recovery by using the power button to get the boot menu then selecting recovery? If you are using the boot menu to attempt to access recovery and its not cooperating it`s possible that points to a broken bootloader or a broken recovery. When you flashed both fff and twrp did you see that it sent and physically wrote each one? maybe explain how you flashed them so we can see if a error was made there. What level do you believe the battery is at? Possible it could be playing a role in your present issue.
Thepooch said:
I hate to ask this question but do you know how to access recovery by using the power button to get the boot menu then selecting recovery? If you are using the boot menu to attempt to access recovery and its not cooperating it`s possible that points to a broken bootloader or a broken recovery. When you flashed both fff and twrp did you see that it sent and physically wrote each one? maybe explain how you flashed them so we can see if a error was made there. What level do you believe the battery is at? Possible it could be playing a role in your present issue.
Click to expand...
Click to collapse
I have done a lot of experiments with my SGS2 about installing ROMS using ODIN or CWR, backing up my own images and making backups. Most of the work I do though is in CWR. I haven't dealt with TWR yet. I also installed ICS on my HP Touchpad. So, even though this is the first time I deal with the KF, I already some experience working with ROMS and images.
Back to the process. I installed the FFF using the Kindle Fire Utility. The KF was forced to fastboot mode via the factory cable. At first I could see on the KF splash screen with the black and orange logo, and now the KF is booting using a Black and Blue kindle fire logo with 1.4a on top. At the bottom of the splash I see instructions of the bootloader selector indicating to press the power button and select the mode that I want to boot. Either Normal Mode or Recovery Mode.
I flashed the TWRP 2.2.2.1 in fastboot mode using my command prompt by putting this code:
Code:
fastboot -i 0x1949 flash recovery [path]\openrecovery-twrp-2.2.2.1-blaze.img
I was following the instructions on this guide.
http://forum.xda-developers.com/showthread.php?t=1638452
I got stuck on step 3 after attempting to boot into recovery mode.
I can select which boot mode I want to go, but none of them work. I only get on the bottom of the screen saying Booting... and then the KF shuts down.
I suspect the battery had a good level of charge, but I can't tell for sure.
Thanks for everything.
Download TWRP again, check the md5, reinstall, and post whatever error messages (if any) that are in your command window here.
In the meantime, enter the following command and let me know what happens after you reboot.
Code:
fastboot oem idme bootmode 5001
fastboot reboot
soupmagnet said:
Download TWRP again, check the md5, reinstall, and post whatever error messages (if any) that are in your command window here.
In the meantime, enter the following command and let me know what happens after you reboot.
Code:
fastboot oem idme bootmode 5001
fastboot reboot
Click to expand...
Click to collapse
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.
gwmadrigal said:
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.
Click to expand...
Click to collapse
What happens when you change the bootmode to 5001?
soupmagnet said:
What happens when you change the bootmode to 5001?
Click to expand...
Click to collapse
It accepts the command.
The command prompt responds saying something like it took 0. something seconds to execute the command.
Thanks for reading my thread.
If upon rebooting, the result is the same after changing the bootmode, it is possible the bootloader isn't working properly. If that's the case, flashing a new bootloader (with md5 verified) might not work, but it's worth a shot.
If that doesn't work, you should be able to change the bootmode to USBboot (4003) and use Firekit to replace the bootloader, but that's speaking theoretically. I've never tried it so I couldn't tell you whether it would work or not. But then you could always pull the back cover off the device and use the shorting trick to use Firekit in USBboot.
If installing a bootloader with the Firekit doesn't work, you're likely looking at a hardware issue, and there's not much we can do about that.
soupmagnet said:
1. If upon rebooting, the result is the same after changing the bootmode, it is possible the bootloader isn't working properly. If that's the case, flashing a new bootloader (with md5 verified) might not work, but it's worth a shot.
2. If that doesn't work, you should be able to change the bootmode to USBboot (4003) and use Firekit to replace the bootloader, but that's speaking theoretically. I've never tried it so I couldn't tell you whether it would work or not. But then you could always pull the back cover off the device and use the shorting trick to use Firekit in USBboot.
3. If installing a bootloader with the Firekit doesn't work, you're likely looking at a hardware issue, and there's not much we can do about that.
Click to expand...
Click to collapse
2 sounds too complicated. I will need to read more.
I'm at work. I am going to try number 1 when I get home.
One more question, how can I revert the KF so when the it boots it shows the original orange white logo?
Thanks for everything.
gwmadrigal said:
2 sounds too complicated. I will need to read more.
I'm at work. I am going to try number 1 when I get home.
One more question, how can I revert the KF so when the it boots it shows the original orange white logo?
Thanks for everything.
Click to expand...
Click to collapse
If you have any questions about using Firekit, don't be afraid to ask.
Get your device working properly before attempting to revert the bootloader back to stock. Contrary to what you may think, the custom bootloader is much better for you in this situation.
gwmadrigal said:
All commands were successful.
When I'm doing instead of the fastboot reboot is to remove the factory cable. Shutdown the KF by holding the power button. Then I connect a regular USB cable. The KF starts the boot process. It enters the first splash screen. Then it moves to booting, but the booting fails. The only thing that I see is that the button light turns from green to yellow and then it shuts down. And the boot process starts again going into a boot loop.
Click to expand...
Click to collapse
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.
Thepooch said:
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.
Click to expand...
Click to collapse
I think that would be the case if the device just rebooted. The OP is saying the device shuts down when FFF starts to load the operating system (Booting...) or recovery, which is why I think it is either the bootloader or some hardware issue.
soupmagnet said:
If you have any questions about using Firekit, don't be afraid to ask.
Get your device working properly before attempting to revert the bootloader back to stock. Contrary to what you may think, the custom bootloader is much better for you in this situation.
Click to expand...
Click to collapse
I tried reloading the u-boot using fastboot and the upload was successful. But it's doing exactly the same.I guess my only question right now, do you know of any good guide that I should start reading to get my feet wet on what the firekit is and how to get started?
Thepooch said:
I suspect your battery is still depleted because it still sounds like a 5 second boot loop. Try this hold the power button down till it`s off and plug it to your pc for a few hours to see if you cannot get some power to your battery.
Click to expand...
Click to collapse
I have nothing to lose. This KF is already bricked. I can certainly try anything. Which cable do you suggest I use? the Factory cable or the USB cable?
I think I answered my own question now. Using a regular USB cable puts the KF in the bootloop. I will use the factory cable instead. I shut down the KF, put the factory cable connected to my computer and the KF. Right now the KF is in the KindleFire splash screen waiting for fastboot commands of for me to use the button to tell it which mode to boot. I will leave it plug overnight.
Thanks for replying on my thread and trying to help me.
soupmagnet said:
I think that would be the case if the device just rebooted. The OP is saying the device shuts down when FFF starts to load the operating system (Booting...) or recovery, which is why I think it is either the bootloader or some hardware issue.
Click to expand...
Click to collapse
I posted a video in utube of what the KF is doing, so you can see what I'm seeing.
Link
Thanks for coming back several times to reply on my thread.
That looks like your battery. From what I can tell, the device is just rebooting, not shutting down.
Unplug the device and hold the power button to perform a hard shutdown.
Plug the device in (it should power up on it's own) and hold the power button to shut it down again.
Leave it plugged into the computer until sometime tomorrow and try again.
Same thing I was thinking 5 second bootloop Thank you the video was very helpful to see just how its acting. Use stock cable to charge not factory.
OKay. I'm glad I came to check the thread one more time before going to bed. I removed the factory cable and put the regular usb instead. The KF was rebooting. I shut down the KF by holding the power button without unplugging the cable. Now the KF appears to be shut down, but the cable is still plugged. The yellow light does not appear as it normally would if it was charging though. I don't know if this is normal.
gwmadrigal said:
OKay. I'm glad I came to check the thread one more time before going to bed. I removed the factory cable and put the regular usb instead. The KF was rebooting. I shut down the KF by holding the power button without unplugging the cable. Now the KF appears to be shut down, but the cable is still plugged. The yellow light does not appear as it normally would if it was charging though. I don't know if this is normal.
Click to expand...
Click to collapse
I think you're fine let it rest.
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.
hello...im hoping someone here can help me. i was helping a friend with his kf2 and found kfu0.9.9 and got the right drivers installed and got the two connected. thinking a needed fastboot right away i flashed FireFireFire without first rooting and when the kf2 rebooting, it went to solid white-n-orange logo (stock fastboot i believe) and is now stuck right at that point.
the big problem seems to be that win7 no longer recognizes it at any level so no commands seem to get to it, thus i cant
"fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot"
or even
"fastboot devices"
i get nothing. can anyone here steer me a useful direction?
advTHANKSance!
There's so much wrong with what you're doing, I don't even know where to begin.
Are you 100% certain you are dealing with a KF2?
soupmagnet said:
There's so much wrong with what you're doing, I don't even know where to begin.
Are you 100% certain you are dealing with a KF2?
Click to expand...
Click to collapse
Lol you know what? I had a couple of tabs open and posted this to the wrong forum...its a KF with 6.3.2..thanks for your help.
Does your Kindle Fire logo stay brightly lit, or does it go dim at any point?
Right, so, I've done some googling and some searching about here and there but either I'm being dense and the solution is really simple, or nobody's done what I've done with this tablet before and, again, I'm being dense. Here's my issue:
Kindle Fire 2 (2nd gen, also second-hand) tablet: stock, rooted, that worked fine with the tool by bin4ry.
Rebooted after that, verified root was working, adb and fastboot perfectly fine (sidenote: linux user, no shonky Windows drivers at fault here)
My ultimate goal is to get CM on this device, so, started after this to follow the instructions in this thread regarding getting the second bootloader on the tablet.
Realised I need a factory cable, ordered, delivered, works but not all the time, I'm not sure if it's a dodgy cable or not but did get into fastboot.
Got new bootloader installed, saw Kindle Fire logo in blue. Proceeded to boot the stock rom after this and use adb push to put the CM 11 zip and the gapps zip files on /sdcard.
adb shell, su, reboot recovery, intending to boot into TWRP to flash new rom
Tablet reboots, but is now stuck with the stock boot logo (orange) and then a black screen with a white triangle and exclamation mark on it. I haven't seen any references to this particular delight.
Fastboot cable does not, no matter how I fiddle with it, put the tablet in fastboot mode. Holding down the power button for five minutes did nothing.
I've read that if it turns on, it can probably be recovered, but I don't know what to do from here. Can anyone render assistance?
So, after much fiddling, I discovered that my problem was actually that my fastboot cable was loose in the microUSB end, and not contacting properly with the pins - thus not sending the tablet the requisite signal to enter fastboot mode.
I've successfully got TWRP onto the fire and thus CM 10.1 now.
I hope this update helps anyone who finds themselves in a similar situation; fastboot still works, keep wiggling.
xyonofcalhoun said:
So, after much fiddling, I discovered that my problem was actually that my fastboot cable was loose in the microUSB end, and not contacting properly with the pins - thus not sending the tablet the requisite signal to enter fastboot mode.
I've successfully got TWRP onto the fire and thus CM 10.1 now.
I hope this update helps anyone who finds themselves in a similar situation; fastboot still works, keep wiggling.
Click to expand...
Click to collapse
I had this problem with a 2nd gen Kindle that was also second hand.
Phoned Amazon UK, described the problem (not mentioning I'd done it myself) and they replaced it.
Seems there's not a lot they won't replace.
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.