Related
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
Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.
mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.
Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.
So, I've been trying to fix my Netflix playback issue. I uninstalled Netflix before I started this process.
My FireTV was running 51.1.6.0 rooted, the boot loader was unlocked, I had the boot menu installed, etc.
From what I'd read, it looked like I may have installed a pre-rooted version some time back that had an issue with Netflix, that was corrected in the "updated" version of that release. I didn't have Netflix at the time, so I didn't know I had a problem. So, I loaded the 51.1.4.0 rooted+updated and 51.1.6.1-rooted onto my FIreTV /sdcard/ directory, ran the md5sum to make sure the files were transferred right, then loaded 51.1.4.0 via recovery. After it rebooted, things weren't quite right. I couldn't install the Netflix app (when I selected the icon, I think the screen flashed and it was back to the same screen). PlutoTV would load, but Mediaah complained. On the Apps section, it said something to the effect of "Your apps will show up here soon". I could still launch Kodi and it seemed to work fine.
Anyhow, I entered recovery mode via ADB and installed the 51.1.6.1. Now my FireTV is sitting at the animated FireTV screen. It no longer gives me the boot menu as it boots up.
What did I do wrong? Did I need to do some more steps while running 51.1.4.0 before loading 51.1.6.1? Did I need to install another version between 51.1.4.0 and 51.1.6.1?
So far, I've not been able to make any headway recovering. I can't connect to it via ADB to enter recovery mode. I don't have a USB PC keyboard to try the ALT-I-PrintScreen trick on boot. I've just ordered a USB A to USB A cable to try the fast boot recovery, but if loading 51.1.4.0 has broken by bootloader unlock, then that probably won't work either.
Installing 51.1.4.0 wipes out the boot menu. Since 51.1.6.1 requires the boot menu, you soft-bricked when you installed 51.1.6.1 without having a funcitoning boot menu.
The good news is it's a simple fix. You should be able to get into recovery using the ALT+i+PrintScreen if you can get a hold of a USB keyboard. The A-to-A USB cable will also get you back to working order if you prefer to go that route.
Just follow the instructions carefully here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
EDIT: I've added a warning to my ROM page, next to the 51.1.4.0 download, to help people avoid what you unknowingly did. If you used my ROM page, sorry the warning wasn't there earlier. Please feel free to PM or email me if you need any additional help recovering.
Thank you for the explanation. I thought it was something like that.
Is there any specific time during the boot process that I should be trying to hit ALT-i-Print Screen?
Taige said:
Thank you for the explanation. I thought it was something like that.
Is there any specific time during the boot process that I should be trying to hit ALT-i-Print Screen?
Click to expand...
Click to collapse
There isn't really any indicator. Just continue to press it repeatedly through the whole boot process. I don't mean hold it down the whole time, but rather, press, release, then repeat. If you can't get it to work, just follow the steps under the "Repair Recovery with Fastboot Mode" section of my guide. With that, there's no guess work, and you'll get into recovery immediately.
Got it with the USB keyboard!
But only after I read this link (http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/)...
Before reading that page, I assumed I just had to hit it at the right point in the boot process, like entering a computers BIOS or something. But that page explained what the system did when you hit ALT-i-PrintScreen, so I knew not to give up.
I have a USB A-to-A cable that will be here tomorrow that I don't need now, but it was cheap insurance.
Thanks again! Your web site is a very valuable resource! Not to take anything away from all the hard work of the guys who frequent these forums, but having everything curated in one place, with instructions for mere-mortals is great.
Preface: I am an Android app developer who has had an Apple phone for quite some time, but recently made the switch to stop using work devices.
So I recently purchased my Pixel XL, and tried to run the iPhone transfer thing upon first start. Unfortunately, I was met with a terrible fate of the Pixel dying! Now, with a dead Pixel, I was able to charge it and run it again. I ran the transfer, it worked, great!. Now, all was well and dandy until I restarted the device. After restarting the device, my phone was stuck in a boot loop, bummer. I researched it and found something along the lines of unlocking the phone or something of that nature in order to fix my problem, so I followed the steps. Then it says to run "fastboot continue." Would have been great if that worked, but it didn't. So then I resorted to entering the recovery mode and choosing to factory reset the device, as per advice from another source. Now, by resetting the device, it removed developer options, so I am no longer able to sideload the OTA file AND the phone still won't boot! I waited for 30 minutes praying it would boot, but alas, no results. I'm thinking about taking the phone back to Verizon and seeing what I can get done. I would like to avoid this if at all possible, but if I don't have a solution within 12 or so hours, I'm going to be forced to consulting with Verizon. Any advice is greatly appreciated.
Attempting to sideload the device...
adb sideload '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
loading: '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
error: insufficient permissions for device
Further Attempts:
adb kill-server
sudo adb start-server
NICE
sudo adb sideload '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
serving: '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip' (~7%)
....
It stopped.
I think the phone legitimately died during the sideload..
Turns out it did......
WE HAVE LIFE, MAYBE.
sudo adb sideload '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
Total xfer: 2.00x
It sideloaded, apparently. And now we wait.
AAAAAND dots.
Just going to reiterate, I have no idea what the hell I'm doing, but there's a solid effort being made here.
The dots seem to be endless... I really wish this wasn't happening right now. I tried so hard. I got so far.
But in the end,
It doesn't even matter. :'(
HOLY **** I FIXED IT.
Thanks to anyone who read this. I fixed my problem without you guys. When Google doesn't help, **** with it until it works. That's my motto now.
Solution:
Recovery mode, get into the options, adb update, then pop open your terminal of choice, kill the current adb service (adb kill-server), then run adb as root (sudo adb start-server), then run adb sideload {PATH_TO_OTA_FILE}. Then you wait for what seems like 5-10 minutes for the dots to stop being indecisive and finally decide to become the Google 'G'. When that happens, you're golden. If you have a similar problem, you're in luck, because I just figured this **** out for you. Otherwise, just keep screwing with the options in Recovery mode until something just works. That's what I did. Now I have a phone again.
What a rollercoaster of emotions this was.
I'm simultaneously the smartest and dumbest individual on this planet.
Corey5Star said:
What a rollercoaster of emotions this was.
I'm simultaneously the smartest and dumbest individual on this planet.
Click to expand...
Click to collapse
Whoa
Sent from my sailfish using XDA Labs
Holy crap man, I was attempting to install Weta on my Pixel and ended up not being able to fastboot the device. Flash-all kept giving me an error of the image being too large, and everyone else's recommendations kept making things worse; one ven broke the twrp on my phone. I tried what you said and boom. It booted first try!
Thanks from a college student who thought he just threw 600$+ away
scarface0311 said:
Holy crap man, I was attempting to install Weta on my Pixel and ended up not being able to fastboot the device. Flash-all kept giving me an error of the image being too large, and everyone else's recommendations kept making things worse; one ven broke the twrp on my phone. I tried what you said and boom. It booted first try!
Thanks from a college student who thought he just threw 600$+ away
Click to expand...
Click to collapse
Is your SDK up to date. A lot of people getting that error say it was fixed by updating the SDK.
It was not. I'll take that as what was hopefully causing the issue, as I don't want to repeat it and not get as lucky next time. Thanks for the direction
Google Pixel boot loop after installing the wrong SuperSu version
I was able to installed twrp and I flashed the wrong supersu version on my Google Pixel. Now my phone is stock in boot loop. I can't get go to recovery mode. I tried to sideload ota but adb doesn't recognize my device. Any idea what I can do? Help please. Thanks
pabsoul said:
I was able to installed twrp and I flashed the wrong supersu version on my Google Pixel. Now my phone is stock in boot loop. I can't get go to recovery mode. I tried to sideload ota but adb doesn't recognize my device. Any idea what I can do? Help please. Thanks
Click to expand...
Click to collapse
Hello,
What SuperSU version did you install?
Good luck...
Corey5Star said:
Preface: I am an Android app developer who has had an Apple phone for quite some time, but recently made the switch to stop using work devices.
Solution:
Recovery mode, get into the options, adb update, then pop open your terminal of choice, kill the current adb service (adb kill-server), then run adb as root (sudo adb start-server), then run adb sideload {PATH_TO_OTA_FILE}. Then you wait for what seems like 5-10 minutes for the dots to stop being indecisive and finally decide to become the Google 'G'. When that happens, you're golden. If you have a similar problem, you're in luck, because I just figured this **** out for you. Otherwise, just keep screwing with the options in Recovery mode until something just works. That's what I did. Now I have a phone again.
Click to expand...
Click to collapse
Could you point a non-developer willing to follow instructions to a source that can provide step-by-step instructions for how to do what you did? I have a Pixel XL that I cannot return/warranty claim, and no matter what I do I cannot get it to keep from going in boot circles. I cannot get it to go into recovery mode. Selecting that option doesn't work.
I didn't use a source, I just tinkered with it until it worked. If I remember correctly, you need to hold down power button and the volume up button when turning on the device. Go into that option, connect your phone to the computer, either open up a terminal or Android Studio and type the things I said in the OP.
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.