Related
This is my 1st time asking for help since I really have never needed it. I got a kindle fire HD 7" and rooted it. I added TWRP and a 2nd bootloader. For a long time I was stuck in TWRP and every time I tried to reboot it would just go back to TWRP. This morning I tried using the Kindle fire utility and selected option one. It seemed like it worked. I then rebooted and now I am stuck on the Kindle Fire boot screen. It shows Kindle fire on the screen, goes black for a few seconds, then back to the kindle fire, then goes black again. It keeps doing this over and over again. I am not able to get back into TWRP now. I am not sure what to do at this point. I have read just about every thread out there and cannot find a similar situation to mine. Any guidence would be appreciated.
OK mistake number one, do not use kindle fire utility on a kfhd, you could easily hard brick the kindle. That was designed for first gen it's and they work a bit differently than yours. OK now that I got that out of the way, does your kindle still have the logo turn blue?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for the quick reponse. When I installed the 2nd bootloader and TWRP I got into the bootloop. At that time when it would bootloop it would go from orange to blue twice before going back to TWRP again. After I made the mistake of using the Kindle FIre utility it now just keeps on the kindle fire start-up screen and it is always orange.
You are either going to need a fastboot cable to fix or have some luck getting a command to work... If you open the device manager, and plug your kindle in while its off, does a Tate device show up for a few seconds? If so try updating the drivers on the Tate device to the ones in my signature. From there you should be able to use a fastboot command to get the kindle to boot into fastboot. The command would be "fastboot -i 0x1949 getvar product", but if your not seeing a Tate device then this command will be useless, and I don't wanna finish explaining how to use this command until I know your PC is detecting it, assuming you don't know how to use the fastboot command by itself from a command prompt since I don't know your skill level with android stuff and windows command prompt stuff.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks again for replying. I would say my experience level is low when it comes to command prompts. I get the basics though. I will check when I get home if I see if a Tate device shows up when I connect with my usb and get back to you. Even when I was in TWRP I was having difficulty seeing my device on the computer to add a custom rom to the sd card. I tried sideloading and tried mounting the sd card but nothing worked. I wish now I would have just left it in TWRP and did some more research. Live and learn I guess. I will let you know what I find out. Thanks again.
Ok. I turned off the Kindle and then attached the USB to the computer. Nothing is being recognized. I see now too that my adb interface is also gone. It appears the computer is no longer picking up anything. When I attach the Kindle to the computer it starts the bootloop again flashing the kindle fire screen over and over again. Let me know your thoughts. Thanks again.
I think your only hope is a fast boot cable, and honestly or just depends how broke it is whether it works or not
Sent from my XT907 using xda app-developers app
Thanks for the reply. So let's say I get a factory cable and I can get into fastboot mode; what are my next steps?
http://forum.xda-developers.com/showthread.php?p=33156486
Sent from my XT907 using xda app-developers app
Ok. I wanted to clarify what I did to get in the situation that I am in. I rooted my device with no issues. I then decided to install a 2nd bootloader and TWRP. After all was done my Kindle Fire HD 7" booted to TWRP. I could not get my computer to show my device so I was stuck. Every time I would reboot it would flash kindle fire in orange, then in Blue, then in Orange, the in Blue then would go back to TWRP. I then put the device with the USB attached to my computer and from TWRP I put the device into fastboot mode. I then used the KFHD SRT v1.3.5 tool and opened the SR.Tool.bat and chose option 1. After it was done I rebooted and now I am stuck on the Kindle fire screen (in orange) and it will show for a few seconds, turn off, then go back to the kindle fire screen again (in orange) and just keep repeating. I ordered a factory cable to try to get back to fastboot mode but since it did not work for me the 1st time I was wondering if anyone had any ideas for me. Thanks in advance.
Are you sure it is a factory/fastboot cable? I would either get them from skorn or proxenusa since I know they are reliable.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello again. I don't have the factory cable yet; I just ordered it yesterday. When I used the fastboot mode the last time I entered the mode from TWRP and was connected to my computer with a regular usb charger. When it was in fastboot mode I selected the option 1 from the tool I mentioned in my previous post. I am just wondering if the fastboot did not work with the KFHD tool I used because I did not have a factory cable connected hence why I am stuck on the Kindle fire screen. What do you think?
No, typically it is said to use a fastboot cable just to get the device into fastboot, then plug the normal cable in afterward.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
For future reference, when you get your kindle back up and running again, you need to flash a custom ROM to boot. The TWRP boot loop stems from trying to boot into stock ROM, it won't work. So just put a ROM on your kindle before you flash bootloader + twrp next time.
Sent from my MB886 using xda app-developers app
So I'm trying to flash CM 10.1 onto my KFHD 7, and I've installed TWRP. Now when I try to boot up so I can move the ROM onto the device storage, it won't fully boot. I get the regular Kindle fire logo, then the blue one, then the flashing one as normal, but then it flashes, goes back the the first, then the blue, and finally opens TWRP. In TWRP, I can't get the device to mount so I can see it on my computer, so I'm not sure how to get the ROM onto the device to flash. Any help would be greatly appreciated. Thanks!
Try my tutorial, I have been seeing this a lot lately, it just has to do with with something amazon did to their os.
http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jonnyc1003 said:
So I'm trying to flash CM 10.1 onto my KFHD 7, and I've installed TWRP. Now when I try to boot up so I can move the ROM onto the device storage, it won't fully boot. I get the regular Kindle fire logo, then the blue one, then the flashing one as normal, but then it flashes, goes back the the first, then the blue, and finally opens TWRP. In TWRP, I can't get the device to mount so I can see it on my computer, so I'm not sure how to get the ROM onto the device to flash. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
I think in twerp, you can mount usb
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
You need to flash a custom ROM to boot. I really think the development or Q&A section should have a sticky regarding this issue, or at least Hashcode make note of it in his how-to guide on 2nd bootloader and recovery.
Sent from my MB886 using xda app-developers app
Thanks all. Stunts513, I'm trying it now, I'll let you know.
So there is no device with an issue in my device manager, I see Kindle Fire and under that is Android ADB Interface. But, when I do "adb push ..." all I see is the same thing as if I just type "adb" and the file doesn't transfer. Sorry, I'm a noob.
When typing adb push, it displays the help text? Type adb devices and see if it lists it, also make sure your command prompt is being run as admin, I probably should mention that in the tutorial, because I use windows 7 with uac disabled so I don't have to worry about that kinda stuff.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jonnyc1003 said:
So I'm trying to flash CM 10.1 onto my KFHD 7, and I've installed TWRP. Now when I try to boot up so I can move the ROM onto the device storage, it won't fully boot. I get the regular Kindle fire logo, then the blue one, then the flashing one as normal, but then it flashes, goes back the the first, then the blue, and finally opens TWRP. In TWRP, I can't get the device to mount so I can see it on my computer, so I'm not sure how to get the ROM onto the device to flash. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
My advice is to go to the Kindle Fire FirstAide thread on here. Run KFFA back to 7.2.3 and root from that simple script. Then use Hashcode's 7.2.3 bootimg and the TWRP he has on his thread. This way you have matching bootimg and you should not bootloop.
I would put the rom you're going to flash on the root of the SD card before flashing first as well. If you do bootloop, you can flash the rom anyway and save some hassle.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers app
So my device shows up as "0123456789abcdef recovery" or something along those lines. Is this right (the ordered numbers and letters look kind of funny)? Also, I am an admin, so that can't be the problem.
OK that's good that is how the device is supposed to show up. If it displayed the help text last time I'm guessing there was a typo in the adb push command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
If you get frustrated or simply can't get ADB Sideload or ADB push to work, you may have to go into "Advanced", then "Reboot Bootloader" in TWRP and use KF First Aide to flash to 7.2.3 stock. From there, repeat the process of installing TWRP and Second Bootloader but put a custom ROM on your SD card before the procedure. Your fastboot drivers might not work, I know Stunts513 has drivers you can install.
Sent from my MB886 using xda app-developers app
Ok so when I wrote that, it was showing up when I typed "adb device," but it wouldn't push. I tried again today, triple checking my typing, but now it doesn't show up on "adb device," just the help menu. I just uninstalled and reinstalled the drivers with no luck.
Ok so I finally figured out the issue, it's really kind of silly. In your tutorial Stunt513, you show the push command like this:
Type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
All I had to do was replace the forward slash between the file name and 'sdcard' with a space. Problem solved. Thanks again for helping out!
Hello, everyone!
Yesterday I tried to flash CM10 in my kindle fire (already running CM9).
I followed the Cyanogen Mod site (wiki.cyanogenmod.org/w/Install_CM_for_otter) instructions.
I downloaded Kindle fire utility 0.9.9 (from CM site), and started the process of updating TWRP. At some point of the installation, KFU rebooted my device in fastboot mode, and kept waiting an awnser from Kindle.
It was taking a bit too long, so I restarted the tablet. Now it keeps on the "Kindle Fire" screen forever, and don't respond to ADB anymore (the "adb device" command don't return anything).
I believe it is not bricked yet, because when we connect it to the PC, it does that connection sound. However, I can't reach it with ADB anymore.
Can Anyone give me an advice for this situation?
Thanks a lot !!
You got very lucky, kindle fire utility is not meant for second generation devices, usually using it results in a hard brick. The correct way to update twrp is to grab the latest version's flashable zip from the dev section for your device and flash it from inside twrp and reboot. If you no longer have the blue logo and it is a 7" device you will need a fastboot cable, if you do have a blue logo or this is a 8.9" device you won't need a fastboot cable to fix, but you still need to get it into fastboot mode to reflash some partitions back to stock to fix this unless you get a blue logo in which case you could probably just flash the recovery but from what you said I'm assuming you don't get the blue logo anymore. And only the 8.9" models tend to be detected briefly while passing the bootloader.
Sent from my Amazon Kindle Fire HD using Tapatalk
In fact, my Kindle fire is a 1st generation one! I had already used KFU to flash CM9 on it (before, it had stock OS) .
Do this fact help in any form?
And, about the cable, I will search one imediatly!!
Thanks for your reply!
O well then this is the wrong device forum on xda... If its a kf1 then I think fastboot cable will still apply to this. Not positive, kf1's aren't my specialty, while my mother has one I never did much beyond rooting and installing twrp. Flashed a Ubuntu touch preview os on it once but that's about it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hey all,
I am in quite a conundrum. My Kindle Fire HD 7" tate device is bricked. Let me explain what I have done so far...
1. I first installed TWRP using the standard and I was planning to install CM 11 on it
2. I accidentally deleted the CM 11 rom files while doing a wipe on TWRP
3. Tried side-loading the rom but somehow ADB sideload didn't work and the device was not being recognized and sideload would hang for hang (tried waiting as long as 1 hour)
4. Then I tried to reinstall FireOS using the KFDH System.img Restore tool from the forums here and managed to somehow uninstall TWRP and get it into a infinite logo loop
5. So tried using various methods to reinstall either TWRP or FireOS and after some 3-4 different utilities that I found on the forums here, I finally tried Kindle Fire Utilitiy 0.9.9 to unbrick it. Tried changing the bootmode to recovery (5000) and have managed to brick it for good.
We are now in the present day (after step #5). As soon as I turn on the Kindle, it shows KF orange logo and then switches to Fastboot mode even though the Factory USB cable is not plugged in. Once I plug it in, it goes into infinite loop with screen going off and windows giving me a constant USB plug-in and un-plug sound. The device is being detected as OMAP 4440 (or 4400?) and I am unable to do anything at all. Have I gone to no-man's land? Or can I still salvage the kindle?
Looking for some help... Any help :crying:
You should plug in the fb cable with the Kindle powered off. See if that gives you a stable fb state wherein you can push your files via adb.
Rushead said:
You should plug in the fb cable with the Kindle powered off. See if that gives you a stable fb state wherein you can push your files via adb.
Click to expand...
Click to collapse
Hey when I plug it in to the fb cable it boots up into the orange and white kindle fire logo and goes into fastboot and then starts re-loading in windows. After plugging in, if I shutdown the device by pressing power button for 15 seconds, the re-loading in windows stops but after than adb doesn't recognise the device - says error no device
"reloading in windows"? What do you mean? It should be powered down when you plug it in, then when it boots into fb mode, you're ready to adb.
OMAP 4400 is a hard brick. You flashed KFU and now the bootloader is screwed. You will need to look up how to flash the emmc on here.
KFHD 7" 2012 (TATE) Hard Brick recovery process....
LinearEquation said:
OMAP 4400 is a hard brick. You flashed KFU and now the bootloader is screwed. You will need to look up how to flash the emmc on here.
Click to expand...
Click to collapse
I know this thread is a little old but, if anyone is looking for how to get there hard bricked kindle fire HD 7" Tate recovered do a search for: TOPIC # t2828906 by overlode
On page 4 of the thread I have posted a procedure.
Bogie
Hi all,
Okay, so long story short my mother has been using this Kindle Fire HD 7 with CM10? on it for awhile. Very recently it started to become sluggish and I offered to take a look. We decided that she should go back to the stock OS as she literally uses it only to play Scrabble and to read an occasional book and that's where things get weird...
It does/did have TWRP 2.6.3.0 installed, however whenever I would mount the device to my computer (Windows 10) it would never show up as a drive.
Then I decided to wipe it...and now, I cannot get passed the Kindle Fire blue/white logo
I have installed Kindle Fire Utility 0.9.9 and when connected it gives me an ADB Status of Online and a Boot Status: Unknown
I'm really just at a loss on what to do at this point...I have installed the drivers that came with the Kindle Fire Utility and my device manager does show Kindle when it's plugged in.
Thanks in advance!
thegame310 said:
Hi all,
Okay, so long story short my mother has been using this Kindle Fire HD 7 with CM10? on it for awhile. Very recently it started to become sluggish and I offered to take a look. We decided that she should go back to the stock OS as she literally uses it only to play Scrabble and to read an occasional book and that's where things get weird...
It does/did have TWRP 2.6.3.0 installed, however whenever I would mount the device to my computer (Windows 10) it would never show up as a drive.
Then I decided to wipe it...and now, I cannot get passed the Kindle Fire blue/white logo
I have installed Kindle Fire Utility 0.9.9 and when connected it gives me an ADB Status of Online and a Boot Status: Unknown
I'm really just at a loss on what to do at this point...I have installed the drivers that came with the Kindle Fire Utility and my device manager does show Kindle when it's plugged in.
Thanks in advance!
Click to expand...
Click to collapse
If you can post into recovery . you could adb push some ROM and flash it using the recovery. You might have wiped the system off I suppose???
thecoolster said:
If you can post into recovery . you could adb push some ROM and flash it using the recovery. You might have wiped the system off I suppose???
Click to expand...
Click to collapse
I'm about 99% sure I did wipe the system. How do I boot the device into recovery? I tried a few different methods and haven't been able.
well simulataneously clicking the hardware buttons did the work for me ???