Related
Please help!
I recently rooted my sons Kindle fire 2 using TWRP, all was going ok until reboot when screen would flash every couple of seconds, flashing the kindle logo even when at the carousel screen etc.. also slow and slow to react to touch of the digitiser screen. From here I think I have got it terribly wrong and have wiped the KF of its OS and with it also stuck in fastboot.
I have made wrong selections on TWRP, then used TWRP command to boot the KF into fastboot. Now have no way to get it out of fastboot, only recognised on windows 7 device manager as Kindle Fire - Android ADB interface and also as a Other Devices - coprocessor which has no recognised driver.
Please note: i think I used nearly all options in TWRP and this is why I think I may have wiped the OS from the KF.
The fastboot screen is the traffic light logo, the green light is the only light that flashes!
when holding for 20 secs then powering back up it boots straight to fastboot after 1 sec of kindle logo showing.
Has anyway managed to save a KF2 from this state?
use this tool to recover:
http://forum.xda-developers.com/showthread.php?t=2035047
otherwise read in the q&a section.
there are many more with similar probelms.
Thanks for supplying this info flopower!!
Lets give it a go!:fingers-crossed:
Totally Mental!
Ok, firstly I feel bad to all of you who do have a bricked Kindle but I have no idea how my Kindle has now recovered!
I bought another Kindle Fire as I made the conclusion that I had totally made my son's unusable. Tried all the recovery programmes with no joy. Was permanently stuck in fastboot mode with the assumption that no OS was on it after deleting all by accident.
My plan was to use the replacement box and put the bricked Kindle in it and return it to the store where i got the new one from, explain to the staff member that my son had just purchased this the other day and on start up and registering the device he was then informed that the Kindle needed to update the firmware. On reboot this Kindle would always show this fastboot screen, explain that I had a look also and could not get it back to its normal state. So I went round but switched off the Kindle first, informed the staff member of what has happened at the same time handing it over to her whilst switching on. I noticed that the Kindle logo as normal would come up but normally within a second it would go to the fastboot screen. This did not happen and I was like twat u twat you have brought round the new one by mistake! right enough the Kindle started up with the original first setup state. So I got myself away as quickly as possible and thought I will just do the same at another branch but this time put the right Kindle in the box. So now back at the house made a cup of tea and sat down, the Kindle which I left behind was on the table next to me and was switched off, I pressed the power button for some reason on it, to my surprise I was welcomed with also the orignal new set up screen! This was the new Kindle!!!!!!!!! I did take the bricked Kindle to the branch and for some reason it was now working, I have even just updated it from to 10.2.6 as it was on 10.2.0 with no issues, turned it on and off nearly 10 times all is perfect!
Unbelievable totally unbelievable! do not understand how the Kindle is now back in play!
I have rebooted tried all options of KFU, KFFirstAide etc etc..... always instantly rebooted in fastboot state! even upto an hour before going round to the shop it was still doing the same, I also tried to electrocute the Kindle so the mainboard would be fried! cant be believe it!
Sorry I will never be able to give an explanation of how it worked!
It seems as if you got off lucky. I incorrectly installed CyanogenMod, and got stuck on the boot anmation. Of course, I din't make a backup, and so I went to another thread and someone stupidly said to wipe the system. Now I'm left without an OS, as TWRP tells me. I don't know how I am going to fix this, as I can't post a thread because I have less than 10 posts.
AW: [Q] Kindle Fire 2 stuck in fastboot - No OS possibly installed
Restore your entire system with fastboot
Gesendet von meinem LG-P990 mit Tapatalk 2
soulcedric said:
It seems as if you got off lucky. I incorrectly installed CyanogenMod, and got stuck on the boot anmation. Of course, I din't make a backup, and so I went to another thread and someone stupidly said to wipe the system. Now I'm left without an OS, as TWRP tells me. I don't know how I am going to fix this, as I can't post a thread because I have less than 10 posts.
Click to expand...
Click to collapse
Surely you just need to flash CM10.1 again?
Normally it happens when you flash a custom ROM over the KF2 standard rom. Wiping system and flashing cm10.1 again should allow you to boot, or you might have to do a factory reset to wipe the leftovers out.
Read the OP of this link for info.
http://forum.xda-developers.com/showthread.php?p=36867464
[ROM] [JB 4.2.2]cm10.1/sgt7 [20130218] ALTERNATE UPDATE
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Surely you just need to flash CM10.1 again?
Normally it happens when you flash a custom ROM over the KF2 standard rom. Wiping system and flashing cm10.1 again should allow you to boot, or you might have to do a factory reset to wipe the leftovers out.
Read the OP of this link for info.
http://forum.xda-developers.com/showthread.php?p=36867464
[ROM] [JB 4.2.2]cm10.1/sgt7 [20130218] ALTERNATE UPDATE
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks. I'll try it.
---------- Post added at 11:05 PM ---------- Previous post was at 10:58 PM ----------
chronicfathead said:
Surely you just need to flash CM10.1 again?
Normally it happens when you flash a custom ROM over the KF2 standard rom. Wiping system and flashing cm10.1 again should allow you to boot, or you might have to do a factory reset to wipe the leftovers out.
Read the OP of this link for info.
http://forum.xda-developers.com/showthread.php?p=36867464
[ROM] [JB 4.2.2]cm10.1/sgt7 [20130218] ALTERNATE UPDATE
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks so much. I figured out that all I had to do was wipe the system. Now I have Jelly Bean!
Almost same problem
flopower1996 said:
Restore your entire system with fastboot
Gesendet von meinem LG-P990 mit Tapatalk 2
Click to expand...
Click to collapse
I'm running into similar problem, i "successfully" installed FFF1.4A and TWRP with it won't boot into recovery.
How can i Restore your entire system with fastboot ??
LUC4X said:
I'm running into similar problem, i "successfully" installed FFF1.4A and TWRP with it won't boot into recovery.
How can i Restore your entire system with fastboot ??
Click to expand...
Click to collapse
Read the dev section. Not sure why anyone would do anything with their device without learning how to unbrick first...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
The Problem I am having seems to be a Infinite boot logo after Undoing a custom Otter jelly bean KF rom. I went through the motions of ADB KFU booting into recovery. I factory restored, wiped and attempted to install my back up of the stock kindle fire rom. wiped caches, and then let it do its "boot up" how ever it did not move past that point, and has been stuck at the "kindle fire" logo screen.
Is there anyway to fix what I probably broke?
KFU Utility vers 0.9.6
TWRP vers 2.4.4
OS version Windows 8 X64
Kindle fire Rom version 6.2.1
Otter jelly bean was 4.2.1 a release sometime in February is the closest I can get. I can't exactly roll back now can I?
Any other information I forgot or neglected to supply on first post was unintentional. First time I have ever had a problem.
Thanks in advance
~ Zach
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
jakeyablosky said:
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
leroy329 said:
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
Click to expand...
Click to collapse
I think you're having the same problem I'm having. If you look at my post regarding stuck at logo that I posted yesterday see if it's the same.
What is your logo doing? Does it stay bright or does it turn on and blink and then fade?
Based on what I've read we need them to get them into fastboot and then side load TWRP and FFF and start again.
I think what we've done is removed or cleared too much in TWRP and our bootloaders are broken, but I could be talking out of my you know what.
Good luck to you and I will follow your thread and you may want to follow mine.
The only thing I can think of is getting a Factory Cable and reset you Kindle Fire
Sent from my Nexus 7 using xda app-developers app
Leroy,
I think Jakey has it.
I was just about ready to pitch this thing in the trash and I decided to plug in my factory cable one last time and run KFU.
For whatever reason I decided to select the root option again even though it said status offline and it rerooted my device.
My logo is now white/blue and I think I can get a rom back onto it.
You may want to hit Skorpn up for a cable, he shipped it super fast and it's great work.
Leroy,
Since it seems you are having the same problem I was and replies are pretty slow in here these days (I'm sure most people are tired of repeat posts like mine), I thought I would post precisely what I did to fix mine.
I too had the infinite boot logo that stayed bright and tried everything from KFU, to unbrick tool, to Soupkit, nothing seemed to work. I bought a factory cable from Skorpn, but didn't really understand how to use it. I think there is so much information here and many various ways to get things fixed it takes awhile to digest it.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
Device said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Again, Skorpn was awesome to work with and sent the cable to me quickly.
Good luck to you!
I obtained a demo version 8.9 that I successfully rooted and installed 8.1.3 on. it worked perfect until like an idiot i tried to update to 8.1.4, manually. When it rebooted, after i started the update, a red screen scrolled across the screen and it went back into fastboot mode and has remained there since. I tried to use ADB in the android sdk to do a restore and everything seems to work, the 8.9's screen even shows the process in the upper LH corner like you'd expect but when it reboots I get the fastboot mode again. I can only select fastboot options with ADB, so I don't think I can install a second bootloader or a backup....can someone please help me
Um in fast boot you cant use adb commands only fast boot commands, so try flashing the stock recovery and system, I think your boot loader still works because you getting into fast boot without trying.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Rooted HD 8.9 stuck in fastboot mode after attempted fw update.
stunts513 said:
Um in fast boot you cant use adb commands only fast boot commands, so try flashing the stock recovery and system, I think your boot loader still works because you getting into fast boot without trying.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Can you provide info or a link on how to do that?
I just realized how vague my instructions are going to sound lemme try to find some actual instructions. Hmm maybe you shouldn't follow my instructions to avoid worse brick. Most everything I have read says to flash a custom recovery to recover stock but those weren't on already bricked devices ... Researching.....
I believe this will be a lot more helpful so I will delete what in said to do in this post and say this is probably a lot more useful. I believe it comes with the boot loader, recovery and system images, you probably don't need to flash the bootloader though.
http://forum.xda-developers.com/showthread.php?t=2011126
Hope this is helpful, I'm slightly half asleep so it wasn't my best research, but I think I'm right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thank You
stunts513 said:
I just realized how vague my instructions are going to sound lemme try to find some actual instructions. Hmm maybe you shouldn't follow my instructions to avoid worse brick. Most everything I have read says to flash a custom recovery to recover stock but those weren't on already bricked devices ... Researching.....
I believe this will be a lot more helpful so I will delete what in said to do in this post and say this is probably a lot more useful. I believe it comes with the boot loader, recovery and system images, you probably don't need to flash the bootloader though.
http://forum.xda-developers.com/showthread.php?t=2011126
Hope this is helpful, I'm slightly half asleep so it wasn't my best research, but I think I'm right.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I don't even know how I can thank you enough, the link you gave me was perfect. Everything works great now!
Hi everybody,
I'm so angry with my Nexus 7 (wifi 2013) because I just made it mess up.
Let me tell you how stupid I was.
First, I tried to root but it failed.
Second, I used 'Back to Stock' with 'Nexus Root Toolkit v1.7.2'. Finally, I got stuck at Google logo
I tried some solutions on the internet but it still unchanged anything.
Could you show me how to fix it, please?
Thank you so much.
This is the images of error that I got (I'm sorry I cannot insert image because I'm a new member of this forum, could you go to the link below to see more details?)
s1019.photobucket.com/user/namserious/media/Error_Nexus7.png.html
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Restoring Successfully
sfhub said:
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
How did you do that?
namserious said:
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
Click to expand...
Click to collapse
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
nexussucks said:
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
Click to expand...
Click to collapse
If you didn't root the device or do anything else with it, you should be able to get into Recovery Mode and do a factory reset.
https://support.google.com/nexus/answer/2668187?hl=en
Even recovery doesn't work
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
nexussucks said:
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
Click to expand...
Click to collapse
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
RenderBroken said:
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
Click to expand...
Click to collapse
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
You could try re-flashing the factory image.
http://forum.xda-developers.com/showthread.php?t=2487757
Latest factory image build is JSS15R
https://developers.google.com/android/nexus/images#razor
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Success
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
nexussucks said:
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
Click to expand...
Click to collapse
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Name change
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
nexussucks said:
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
Click to expand...
Click to collapse
This is the price we pay for the cutting edge. Also , at least for me, this is part of the fun. Now I have a much better understanding of Android than if I did being an avg. user. I was thinking the same about the name change. lol
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
Hey, know it's been a little bit but my nexus 7 says no OS in TWRP recovery. I tried flashing it back to stock but it doesn't work. The bootloader is locked and when I try to do anything manually it just hangs on stuff like erasing 'system'/cache etc... in fastboot. I have not been able to find anything to work. And when I try to fastboot oem unlock it gets stuck when i press volume up and power to accept unlocking it. I have tried different cables and another computer. maybe I should try a third computer.. Do you have any suggestions?
RenderBroken said:
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Click to expand...
Click to collapse
I know this is an old thread, but I'm having this exact issue. I'm just stuck on the google screen. I can get into the bootloader just fine, but not the recovery. I followed these directions. Flashed the factory image and everything. But I still can't get past the google logo. I've followed every bit of advice I could find on this issue and I can't seem to get it working. Any help would be greatly appreciated!
*bump*
Does anyone know what's going on? I've tried everything I could find. Multiple times. From the suggestions listed here to the WUG kit to this http://forum.xda-developers.com/showthread.php?t=2381582
Nothing is working. I goes through the reflashing successfully. The command prompt says that everything is done. And then it just gets stuck at the Google screen again. I'm at my wits end and have no idea what to try next. I know that because I can get into the bootloader still, there has to be SOMETHING that will work. But I just don't know. Any ideas?
is there a android L Developers Preview flashable zip? thanks
Sent from my Nexus 7 using XDA Free mobile app
Anyone figure out what is causing this? I got a remanufactured 2nd Gen N7 16G yesterday. Updated to 4.4.4 over the air. Then unlocked the bootloader and rooted. Everything went fine. I installed Franco's latest kernel (r17) over stock and all was well. However, this morning, while using the device in the middle of GoW, it rebooted to the Google Screen and froze there. I could boot into the bootloader and have my comp recognize the device, so could ADB and Fastboot, however, I could not get into recovery. (I had installed TWRP 2.7.1.1 when I rooted). Trying to get into recovery would just freeze at the Google Screen.
So, I then tried both manually ADB'ing commands, as well as using Wug's Toolkit, and both methods seemed to complete successfully without error (I was using the latest Razor-Flo 4.4.4 files from Google's Dev Page so it is not an issue where I am using the Gen 1 files for Grouper or anything like that in error), however, neither method allowed me to boot into recovery, and left me at the same place. No matter what I did, I was stuck at that screen. I ended up calling Asus to RMA.
So, while it is not a current issue for me, I am interested to know if anyone has sorted what the root cause is, and whether it is an issue on the hardware side. I am not a complete noob to the N7 (I have 2 Groupers), and have been modding for a few years on Samsungs, and until this morning, have never had a soft brick I could not fix. This time, I gave up.
Same problem here, I have a Deb 32g, it went a little wonky and then rebooted. No amount of flashing and wiping and fastbooting has been able to recovery it. Gets stuck on Google Logo no matter what I do. Can't get recovery. Can't boot past Google. It will do fastboot without errors, but that's the only thing it will do.
Hi!
I have a kindle fire hd 8.9 running the 8.5.1 version.
I managed to root it using the key root master app (i think it was an indonesian/chinese language, which was suggested by one poster), although it was kinda weird because it didn't install the superuser app. Then, i tried to install the 2nd bootloader and twrp using the fireflash app from this thread http://forum.xda-developers.com/showthread.php?t=2277105. But somehow, i couldn't get it to fastboot mode, although it wasn't needed according to that thread. I flashed it using the fireflash app, however, i couldnt get it to go to the TWRP recovery. Then, i noticed that there was an option to go into recovery from the fireflash app, which i pressed, and now, i'm stuck in the bootscreen showing the kindlefire logo. i could turn it on and off, but that's it.
sorry, im quite a relatively newbie at this. from what i've searched, maybe the KFHD srt tools can help with this. Will it work even if i cannot go into fastboot mode?
Thank you. any help would be greatly appreciated!
notiboy07 said:
Hi!
I have a kindle fire hd 8.9 running the 8.5.1 version.
I managed to root it using the key root master app (i think it was an indonesian/chinese language, which was suggested by one poster), although it was kinda weird because it didn't install the superuser app. Then, i tried to install the 2nd bootloader and twrp using the fireflash app from this thread http://forum.xda-developers.com/showthread.php?t=2277105. But somehow, i couldn't get it to fastboot mode, although it wasn't needed according to that thread. I flashed it using the fireflash app, however, i couldnt get it to go to the TWRP recovery. Then, i noticed that there was an option to go into recovery from the fireflash app, which i pressed, and now, i'm stuck in the bootscreen showing the kindlefire logo. i could turn it on and off, but that's it.
sorry, im quite a relatively newbie at this. from what i've searched, maybe the KFHD srt tools can help with this. Will it work even if i cannot go into fastboot mode?
Thank you. any help would be greatly appreciated!
Click to expand...
Click to collapse
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
11fan said:
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
Click to expand...
Click to collapse
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
notiboy07 said:
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
Click to expand...
Click to collapse
First off you have got to get adb and fastbook working, if not you will probably never get it back useable. have you installed android sdk? if not go here >http://developer.android.com/sdk/index.html#Other< and download the android-sdk windows zip file and install, that should get your drivers going so you can access adb and fastboot. for help installing the sdk manager go here >http://developer.android.com/tools/help/sdk-manager.html< after sdk manager install check your C:/users/yournamehere/ folder and make sure it put a .android folder there (sometimes it don't) and it should be a file in there called android_usb.ini, if that don't get you hooked up to adb and fastboot (assuming you know how to check if adb and fastboot is working correctly) install the Kindle driver package found here >https://www.dropbox.com/s/c0w3po7r65fwltb/Kindle%20Fire%20HD%208.9%20ADB%20drivers.zip< and if STILL you can't get adb and fastboot working i will help you edit that android_usb.ini file(what i ultimately had to do to cure my fastboot woes on this windows 7 box) that i mentioned earlier in this post. once you get adb and fastboot working correctly i will try to help you get your KFHD back up. keep me posted and i will check back as regular as i can! GOOD LUCK!
Mike
edit: windows 8 driver problems/errors go here >http://forum.xda-developers.com/showthread.php?t=2093296<
!
11fan said:
First off you have got to get adb and fastbook working, if not you will probably never get it back useable. have you installed android sdk? if not go here >http://developer.android.com/sdk/index.html#Other< and download the android-sdk windows zip file and install, that should get your drivers going so you can access adb and fastboot. for help installing the sdk manager go here >http://developer.android.com/tools/help/sdk-manager.html< after sdk manager install check your C:/users/yournamehere/ folder and make sure it put a .android folder there (sometimes it don't) and it should be a file in there called android_usb.ini, if that don't get you hooked up to adb and fastboot (assuming you know how to check if adb and fastboot is working correctly) install the Kindle driver package found here >https://www.dropbox.com/s/c0w3po7r65fwltb/Kindle%20Fire%20HD%208.9%20ADB%20drivers.zip< and if STILL you can't get adb and fastboot working i will help you edit that android_usb.ini file(what i ultimately had to do to cure my fastboot woes on this windows 7 box) that i mentioned earlier in this post. once you get adb and fastboot working correctly i will try to help you get your KFHD back up. keep me posted and i will check back as regular as i can! GOOD LUCK!
Mike
edit: windows 8 driver problems/errors go here >http://forum.xda-developers.com/showthread.php?t=2093296<
Click to expand...
Click to collapse
@11fan - thank you so much!
Anyway, i was able to go into fastboot, yahoo! i was able to see that Jem-PVT-Prod-04 on the command prompt. (i used my windows 7 laptop, i dont know why i couldnt get it to go into fastboot while in win8). i'm beginning to have some hope now.
Thank you!
notiboy07 said:
@11fan - thank you so much!
Anyway, i was able to go into fastboot, yahoo! i was able to see that Jem-PVT-Prod-04 on the command prompt. (i used my windows 7 laptop, i dont know why i couldnt get it to go into fastboot while in win8). i'm beginning to have some hope now.
Thank you!
Click to expand...
Click to collapse
thats good news! adb and fastboot working now? i hope i helped in some kind of way! you can surely get it back straight now! and btw if you were successful in installing that 8.1.4 bootloader when it messed up, IT DONT GO AWAY! i flashed mine twice with MY factory backup images and still retained the 8.1.4 bootloader from Hashcodes OP. and retained root! anyway im so stubborn and determined to figure things out like this, i decided to try again only after i figured out i still had the 8.1.4 bootloader, and THE ONLY way i could figure out which boot loader i had was to load up fireflash again and see if it give me the RED WARNING in the first line about flashing or not flashing the 8.1.4, sure enough it showed no warning with 8.1.4 bootloader! SO instead of using fireflash i just used fastboot to apply the "stack override script" and flashed the freedom boot 8.4.6 image and the 2.7.0.0 TWRP and went smooth as butter, booted up in TWRP recovery and then rebooted several times to make sure all was good and then last boot in recovery i did a wipe with TWRP and installed CM11 and GAPPS zip and all has been good every since! :laugh: it really is a whole new tablet with CM11! :good: if you need more help i will do my best, trust me i know what it feels like to have the RED SCREEN and stuck in fastboot! keep me posted!
Mike
11fan said:
thats good news! adb and fastboot working now? i hope i helped in some kind of way! you can surely get it back straight now! and btw if you were successful in installing that 8.1.4 bootloader when it messed up, IT DONT GO AWAY! i flashed mine twice with MY factory backup images and still retained the 8.1.4 bootloader from Hashcodes OP. and retained root! anyway im so stubborn and determined to figure things out like this, i decided to try again only after i figured out i still had the 8.1.4 bootloader, and THE ONLY way i could figure out which boot loader i had was to load up fireflash again and see if it give me the RED WARNING in the first line about flashing or not flashing the 8.1.4, sure enough it showed no warning with 8.1.4 bootloader! SO instead of using fireflash i just used fastboot to apply the "stack override script" and flashed the freedom boot 8.4.6 image and the 2.7.0.0 TWRP and went smooth as butter, booted up in TWRP recovery and then rebooted several times to make sure all was good and then last boot in recovery i did a wipe with TWRP and installed CM11 and GAPPS zip and all has been good every since! :laugh: it really is a whole new tablet with CM11! :good: if you need more help i will do my best, trust me i know what it feels like to have the RED SCREEN and stuck in fastboot! keep me posted!
Mike
Click to expand...
Click to collapse
Thanks again @Mike. However, i wasn't able to do my factory backup images. and secondly, what did you use to restore the images? Did you use KKFA or the KFHD SRT? i'm sorry, i kinda scared now to proceed on my own.
From what i've read, you use the KFHD SRT for bricked devices USING a factory cable, is that right? from http://forum.xda-developers.com/showthread.php?t=1951254. Or do i use the KKFirstAide tool from this http://rootjunkysdl.com/?device=Kindle Fire HD 7in ?
Thanks again @11fan!
notiboy07 said:
From what i've read, you use the KFHD SRT for bricked devices USING a factory cable, is that right? from http://forum.xda-developers.com/showthread.php?t=1951254. Or do i use the KKFirstAide tool from this http://rootjunkysdl.com/?device=Kindle Fire HD 7in ?
Thanks again @11fan!
Click to expand...
Click to collapse
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
11fan said:
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
Click to expand...
Click to collapse
Thank you for the prompt reply. So now i know those wouldn't work. Yes, fastboot is working - it says fastboot on the screen of the kindle fire 8.9. Ok, so i need to get that recovery image - however, i think you were not able to link that thread. I'm sorry, can you please paste the link again?
I'm on google hangouts now. [email protected]
Thanks a lot @Mike!
I have been reading XDA for years, My KFHD 8.9 recently stopped booting also
My KFHD (Kindle Fire HD ) 8.9" (JEM) recently stopped working one day (about a month or 2 ago) while it was sitting plugged into a wall charger . Mine , since coming back to it while it was charging, stopped running and I can't remember if it was on or off while I charged it, but it's 100% stock and now it only boots as far as the non-animated part of the "Kindle fire" logo screen, and stays there indefinitely until the battery dies , or until I hold down the power button long enough to shut it down. I'm pretty sure it's either bricked (for whatever reason) , or has some part possibly broken on it (internally) ?
--- sidenote: one time I was given a case for a tablet, and without thinking about it, tried to see if my 8.9 inch model fit inside it and it didn't. Without forcing it in, as far as it did get in, caused my KFHD to reboot on its own?!
my only question here is , Is this a similar enough case , or is there anything else I should do to fix this? my device beeps on multiple computers I've attached it to , notifying it was detected by windows, and about 1/4 second later it dings the disconnected sound and I've never managed to get KFHD SRT (of any version) to work for me at all. Fastboot does not detect my device, even after installing drivers (have attempted this on a windows 7 64 bit computer, and a windows 8 64 bit computer, neither have shown any sign of functionality with fastboot)
Umisguy said:
My KFHD (Kindle Fire HD ) 8.9" (JEM) recently stopped working one day (about a month or 2 ago) while it was sitting plugged into a wall charger . Mine , since coming back to it while it was charging, stopped running and I can't remember if it was on or off while I charged it, but it's 100% stock and now it only boots as far as the non-animated part of the "Kindle fire" logo screen, and stays there indefinitely until the battery dies , or until I hold down the power button long enough to shut it down. I'm pretty sure it's either bricked (for whatever reason) , or has some part possibly broken on it (internally) ?
--- sidenote: one time I was given a case for a tablet, and without thinking about it, tried to see if my 8.9 inch model fit inside it and it didn't. Without forcing it in, as far as it did get in, caused my KFHD to reboot on its own?!
my only question here is , Is this a similar enough case , or is there anything else I should do to fix this? my device beeps on multiple computers I've attached it to , notifying it was detected by windows, and about 1/4 second later it dings the disconnected sound and I've never managed to get KFHD SRT (of any version) to work for me at all. Fastboot does not detect my device, even after installing drivers (have attempted this on a windows 7 64 bit computer, and a windows 8 64 bit computer, neither have shown any sign of functionality with fastboot)
Click to expand...
Click to collapse
I dont think this is the same case @Umisguy as you have not tinkered with your tablet (100% stock), while mine happened while trying to install a custom ROM. Maybe the amazon guys can help you?
Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files
11fan said:
no, you DO NOT need a special "factory cable" for the 8.9 inch just the regular cable that come with the KFHD 8.9 or ANY usb/microusb cable like the one that come with your kindle, it's nothing special to that cable. and although i tried using those utilities you mentioned in your previous post to fix mine, NONE of them worked for me! the only thing i used was adb and fastboot commands and a recovery image DOWNLOADED from a thread here, thats was what ultimately booted my kindle back up in "factory" recovery mode (NOT fastboot mode) and it went through a couple prompts (on the kindle screen) and using the vol up/down and power buttons to select and enter respectively to do a factory restore all from the kindle screen once i finally got it to boot into it's own factory recovery. do you have fastboot working? if so i think we can fix it! mite have to go to a IM kinda app or google hangout or something for realtime communication but i feel like it can be fixed!
Mike
edit: all those file on rootjunky you linked to look to be for Kindle Fire HD 7 inch, you do have the 8.9 inch, correct???
Click to expand...
Click to collapse
Folks,
I got in to the same trouble able to mess up the KF and get a redscreen but used KFHD SRT to reflash the 8.1.4 system image, boot image, recovery image but now I ended up in the boot loop mode where it shows reboot kindle or Reset to factory Dafaults but as I flashed every thing am unable to reset to factory. As I got the tablet recently it came with 8.5.1 so I need to try with the latest image I can get.
If there are any suggestions i can try please let me know.
Which stage of bricked are you at? I don't exactly understand how far you got or didn't get? Red screen? Orange kindle screen? Boot loop? If you can give a little more detail I may be able to help
Mike
sent from my jem running CM11 using TapaTalk
---------- Post added at 12:21 PM ---------- Previous post was at 11:32 AM ----------
"Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files"
I was on 8.5.1 when i did mine, BUT the boot image you will be using is the freedom BOOT image is 8.4.6 from Hashcodes thread and the "2nd" BOOTLOADER is 8.1.4 also from Hashcodes thread.....I also have "my" STOCK BOOT IMAGE from 8.5.1 from my backup i did BEFORE i started this OP
Hope this helps and not confuses you more!
Mike
11fan said:
Which stage of bricked are you at? I don't exactly understand how far you got or didn't get? Red screen? Orange kindle screen? Boot loop? If you can give a little more detail I may be able to help
Mike
sent from my jem running CM11 using TapaTalk
---------- Post added at 12:21 PM ---------- Previous post was at 11:32 AM ----------
"Do you have 8.5.1 or 8.4.6 system image and the boot and recovery files"
I was on 8.5.1 when i did mine, BUT the boot image you will be using is the freedom BOOT image is 8.4.6 from Hashcodes thread and the "2nd" BOOTLOADER is 8.1.4 also from Hashcodes thread.....I also have "my" STOCK BOOT IMAGE from 8.5.1 from my backup i did BEFORE i started this OP
Hope this helps and not confuses you more!
Mike
Click to expand...
Click to collapse
I am at the boot loop where it shows the kindle reboot or factory restore option and it loops into that screen forever. Before that I hit with a redscreen and able to get the device into this loop mode by using the 8.1.4 system image, boot , recovery images. Now I ended up in this boot loop so I wonder If I have the actual 8.5.1 system,boot,recovery images I can flash them in the fastboot mode on the device. Also another issue am facing is ADB command cannot recognize the device even though am in the fastboot mode.
Thanks for the prompt reply mike.
I'm at work so kinda limited to my replies and quickness, and I'm by no means a dev or pro at this, I just learn by trial and error and lots of reading, especially when it comes to the kfhd! I went through this same mess SEVERAL times with my kindle before I finally got it straight! Bricked mine several times, once to the point I thought it was toast! So I no how you feel! 1st thing u need to know is adb only works when device is booted up in the os, that's why you getting device not found, but fastboot will work as you know, if you successfully flashed the 8.1.4 boot loader then its there to stay at least in my findings, after flashing back all my stock images and multiple factory resets I still had the second 8.1.4 bootloader installed. I'm using tablet now at work and I have the thread bookmarked on my PC at home that ultimately got me back up and going but I will try to find it and get you a link, if not I will post the link when I get home after work around 5 30 est, there is a recovery image that you will need to flash that should get you back into factory recovery mode and work instead of looping
Mike
sent from my jem running CM11 using TapaTalk
11fan said:
I'm at work so kinda limited to my replies and quickness, and I'm by no means a dev or pro at this, I just learn by trial and error and lots of reading, especially when it comes to the kfhd! I went through this same mess SEVERAL times with my kindle before I finally got it straight! Bricked mine several times, once to the point I thought it was toast! So I no how you feel! 1st thing u need to know is adb only works when device is booted up in the os, that's why you getting device not found, but fastboot will work as you know, if you successfully flashed the 8.1.4 boot loader then its there to stay at least in my findings, after flashing back all my stock images and multiple factory resets I still had the second 8.1.4 bootloader installed. I'm using tablet now at work and I have the thread bookmarked on my PC at home that ultimately got me back up and going but I will try to find it and get you a link, if not I will post the link when I get home after work around 5 30 est, there is a recovery image that you will need to flash that should get you back into factory recovery mode and work instead of looping
Mike
sent from my jem running CM11 using TapaTalk
Click to expand...
Click to collapse
That will be great Mike.
Thanks,
Krishna
krishnasanga said:
I am at the boot loop where it shows the kindle reboot or factory restore option and it loops into that screen forever. Before that I hit with a redscreen and able to get the device into this loop mode by using the 8.1.4 system image, boot , recovery images. Now I ended up in this boot loop so I wonder If I have the actual 8.5.1 system,boot,recovery images I can flash them in the fastboot mode on the device. Also another issue am facing is ADB command cannot recognize the device even though am in the fastboot mode.
Thanks for the prompt reply mike.
Click to expand...
Click to collapse
sent from my jem running CM11 using TapaTalk
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
11fan said:
hopefully you backed up all images first? i made that same mistake with fireflash to "boot into recovery" yep booted mine right into a brick, after several different types of "softbricks" i finally got mine back straight and now kinda scared to try the 2nd bootloader OP again, because idk which bootloader i am on right now and cant find a way to identify it! i will try to find the thread that got me back straight, give me a while
Mike
Click to expand...
Click to collapse
notiboy07 said:
Thanks @Mike. It kinda reassuring to know that somehow you were able to fix your kindle. BUT i have a big problem, i was not able to back up the images (i wasnt able to go into fastboot, i think my windows 8 pc has a problem with that, or is it just me?). is it possible to use your images? (we're both 8.5.1).
Thanks again mike. I think i'll be scared to try the 2nd bootloader again too.
Click to expand...
Click to collapse
sent from my jem running CM11 using TapaTalk
krishnasanga said:
That will be great Mike.
Thanks,
Krishna
Click to expand...
Click to collapse
ok @krishnasanga go here http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193 and grab the boot image from step 3 and the recovery image from step 4 and place those in C:/ or wherever you have your adb and fastboot tools, should be in C:/ to make things easier but don't HAVE to be if you know how to enter correct paths in the command prompt. IGNORE all the Kindle First Aide stuff, you will just flash these with regular command prompt running as ADMIN (right click command prompt,click run as admin) start at step # 6 (ignore first aide stuff) and open command prompt running as admin and go from there EXACTLY as it says with kindle plugged up to usb and powered OFF. most likely HOPEFULLY you will not have to go past the reboot in step 8 and you will be in factory recovery and will be able to "reset to factory settings" assuming the recovery file is flashed successfully, if you do get to step 8 without issue and get to the fastboot erase userdata -i 0x1949 command, don't panic if it seems like it's taking a long time, i have seen this userdata erase take up to 40+ minutes! IF you get that far and userdata gets erased properly the next command to reboot "should" put the kindle into factory recovery where you can "reset to factory" and will not keep looping. GOOD LUCK! hope this helps and works out for you and i will be around the rest of the evening if i can help let me know and i will try
Mike
11fan said:
ok @krishnasanga go here http://forum.xda-developers.com/showpost.php?p=37278819&postcount=193 and grab the boot image from step 3 and the recovery image from step 4 and place those in C:/ or wherever you have your adb and fastboot tools, should be in C:/ to make things easier but don't HAVE to be if you know how to enter correct paths in the command prompt. IGNORE all the Kindle First Aide stuff, you will just flash these with regular command prompt running as ADMIN (right click command prompt,click run as admin) start at step # 6 (ignore first aide stuff) and open command prompt running as admin and go from there EXACTLY as it says with kindle plugged up to usb and powered OFF. most likely HOPEFULLY you will not have to go past the reboot in step 8 and you will be in factory recovery and will be able to "reset to factory settings" assuming the recovery file is flashed successfully, if you do get to step 8 without issue and get to the fastboot erase userdata -i 0x1949 command, don't panic if it seems like it's taking a long time, i have seen this userdata erase take up to 40+ minutes! IF you get that far and userdata gets erased properly the next command to reboot "should" put the kindle into factory recovery where you can "reset to factory" and will not keep looping. GOOD LUCK! hope this helps and works out for you and i will be around the rest of the evening if i can help let me know and i will try
Mike
Click to expand...
Click to collapse
Mike,
I tried with this new boot and recovery images but still stuck in the loop , can you upload your backup files of 8.5.1 system.img,boot.img,recovery.img I think that will be my last shot to try to unbrick this device.
Thanks,
Krishna