Hello, I am looking for some assistance, Tried to install a new rom by first rooting and then trying to install TWRP, after that the unit boots up with the Kindle logo, goes into fastboot mode for 2 seconds and then screen goes dark, I could hear the sound Windows 7 attempting to install the drivers, device manager shows OMAP4440 for a second and then goes away for second and then back to showing the OMAP4440 and stays on that loop forever, I am unable to break the loop cycle, driver install stay on view for only a second, so there is no time to provide or suggest drivers. all this time the kindle remains unaccessible because of the drivers. I also have a fastboot cable and tried with that and same results, please advise.
Thank you
Related
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
I swear I looked far and wide but this appears to be different from the usual "bootloop" questions. Apologies if not.
I flashed a bad ROM, and the device won't boot all the way into the OS. Just sits at the ROM logo for hours.
I previously installed FFF 1.4, so I do get the blue KindleFire logo momentarily, but any fastboot commands I try to send to it just come back with "waiting for device" and then "ERROR: Unable to create a plug-in (e00002be)". I've got TWRP installed and backups galore but I cant figure out how to get to it. I do have a fastboot cable.
Totally at a loss as to what to do. I feel like there's a really simple fix I'm missing, but I've poured through pages of Kindle Fire posts and everyone seems to be having a problem with the KindleFire logo screen and pre-getting all the way to recovery and ROMS installed.
Any help would be much appreciated dudes, you guys always get me sorted out. Thanks!
It sounds like you need the fastboot drivers loaded. Does it appear in device manager when it is plugged in and in fastboot mode?
It comes up under Other Devices: Kindle
Well, now I've got it coming up under Kindle Fire: Android ADB Composite Device. But at no point, apparently does it enter fastboot mode and I can't get any commands to work. Just scoots right through both KindleFire logos and then on to the ROM logo ad infinitum.
Okay so hey guys, so first off I've searched all over the forums for a potential fix with no such luck so i'm finally making a post seeing if anyone has a fix.
So the issue, my Kindle Fire HD 7"(2012 version) is rooted, TWRP is installed, and i tried flashing Cyanogen mod 12.1(clean flash, not a dirty flash), everything went fine until CM 12.1 started booting up. At this point the little blue android head loading comes up before the screen transitions to a "optimizing apps 1 of 95" window, when that gets done it goes back to the blue android head before transitioning to another "optimizing apps 1 of 16" window, once that completes it just alternates between the CM blue android logo and another "optimizing apps 1 of 16".
I have tried turning off and booting in TWRP recovery mode by holding the up volume button until the blue fire logo displays and then letting go(even tried holding it and not letting go) but it just waits 15-20 seconds on the blue fire logo before transitioning again to the CM blue android boot up logo and beginning a boot loop again.
I also have tried ADB to get into recovery mode but my kindle is unauthorized, it's recognized when i type in the command "adb devices" it's just not authorized. Apparently to authorize it, when you try to get adb to recognize it and it says it isn't authorized, a prompt on whatever device you are using comes up once you unlock the screen asking whether or not you want to authorize said device with said computer. I know this because that's what came up on my phone when i tried to get adb to recognize it, once i accepted it it became authorized and i could use commands with it such as simply rebooting it. I have yet to find a way to authorize my kindle through the terminal rather than through the device itself.
I have not tried the kindle fire first aide as the link for that .zip file on this site takes me to a file storage website that says the shared file or folder link has been removed, so if anyone knows where that .zip file is and thinks it will solve me issue, link me to it please.
I also have not tried Kindle Fire Utility as to my knowledge that tool is for original Kindle Fires only, if that is wrong and it will work just as well for Kindle Fire HD 7"(2012 version) then sorry for my noobness in that aspect.
If no one knows of or has a potential fix i can still buy a fastboot cable and figure out how to fix it through there, i was just wondering if there was any alternative method before i bought one.
Thanks to all who will contribute to me fixing this problem! -Mayhem
EDIT-Solved, not entirely sure how but managed to finally get into TWRP and re-flash everything
This might help you out http://forum.xda-developers.com/kin...ix-fastboot-mode-using-factory-cable-t3168767
didn't work for me
xlr8edmayhem said:
Okay so hey guys, so first off I've searched all over the forums for a potential fix with no such luck so i'm finally making a post seeing if anyone has a fix.
So the issue, my Kindle Fire HD 7"(2012 version) is rooted, TWRP is installed, and i tried flashing Cyanogen mod 12.1(clean flash, not a dirty flash), everything went fine until CM 12.1 started booting up. At this point the little blue android head loading comes up before the screen transitions to a "optimizing apps 1 of 95" window, when that gets done it goes back to the blue android head before transitioning to another "optimizing apps 1 of 16" window, once that completes it just alternates between the CM blue android logo and another "optimizing apps 1 of 16".
I have tried turning off and booting in TWRP recovery mode by holding the up volume button until the blue fire logo displays and then letting go(even tried holding it and not letting go) but it just waits 15-20 seconds on the blue fire logo before transitioning again to the CM blue android boot up logo and beginning a boot loop again.
I also have tried ADB to get into recovery mode but my kindle is unauthorized, it's recognized when i type in the command "adb devices" it's just not authorized. Apparently to authorize it, when you try to get adb to recognize it and it says it isn't authorized, a prompt on whatever device you are using comes up once you unlock the screen asking whether or not you want to authorize said device with said computer. I know this because that's what came up on my phone when i tried to get adb to recognize it, once i accepted it it became authorized and i could use commands with it such as simply rebooting it. I have yet to find a way to authorize my kindle through the terminal rather than through the device itself.
I have not tried the kindle fire first aide as the link for that .zip file on this site takes me to a file storage website that says the shared file or folder link has been removed, so if anyone knows where that .zip file is and thinks it will solve me issue, link me to it please.
I also have not tried Kindle Fire Utility as to my knowledge that tool is for original Kindle Fires only, if that is wrong and it will work just as well for Kindle Fire HD 7"(2012 version) then sorry for my noobness in that aspect.
If no one knows of or has a potential fix i can still buy a fastboot cable and figure out how to fix it through there, i was just wondering if there was any alternative method before i bought one.
Thanks to all who will contribute to me fixing this problem! -Mayhem
EDIT-Solved, not entirely sure how but managed to finally get into TWRP and re-flash everything
Click to expand...
Click to collapse
How did you do it?
Hi,
I know you should have seen this a lot but i'm kinda stuck, i tried to upgrade my Recovery TWRP with a new version with flashify but now my tablet is unusable.
It show the kindle fire (red logo, not blue) and restart over and over again...
I plugged it to my pc but i can't see it in my devices manager, like it never connect...so no ADB (no devices), i tried different drivers to be sure but it doesn't work.
I need help.
Thanks
Hello,
I tried installing a custom recovery on my Kindle HD 7 3rd generation. After entering the fastboot commands, the terminal didn't react anymore and now I'm stuck on the Kindle boot, just showing the "Kindle fire" logo. I tried getting into the recovery by pressing the Power and Volume down buttons and factory reset it, but this takes no effect.
What can I do?
Thank you in advance!
krmax44 said:
Hello,
I tried installing a custom recovery on my Kindle HD 7 3rd generation. After entering the fastboot commands, the terminal didn't react anymore and now I'm stuck on the Kindle boot, just showing the "Kindle fire" logo. I tried getting into the recovery by pressing the Power and Volume down buttons and factory reset it, but this takes no effect.
What can I do?
Thank you in advance!
Click to expand...
Click to collapse
Which recovery?
What steps?
Same exact issue, I am waiting for my factory cable to arrive. All the reading I've done says that's the only way to get the 3rd gen into fastboot from this lockup. I will have my cable tomorrow and will post from there.
I'm having the same exact issue as well unfortunately the fastboot cable didn't work. The first thing the twrp instructions has you do is erase the boot... Recovery is still there but that is useless. No ADB or Fastboot access either. OMAP USB connects briefly during recovery boot tho...