Related
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.
Kooky_Lukey said:
Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.
Click to expand...
Click to collapse
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.
Thepooch said:
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.
Click to expand...
Click to collapse
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks
Kooky_Lukey said:
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks
Click to expand...
Click to collapse
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?
Thepooch said:
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?
Click to expand...
Click to collapse
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.
Kooky_Lukey said:
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.
Click to expand...
Click to collapse
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.
Thepooch said:
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.
Click to expand...
Click to collapse
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.
Kooky_Lukey said:
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.
Click to expand...
Click to collapse
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.
Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thepooch said:
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.
Click to expand...
Click to collapse
Thank you so much you do not know how much I appreciate it. If anything youre writing has anything to do with java i would love to help but if not then i wouldnt be of much help
stunts513 said:
Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I wouldn`t even bother opening it let Amazon do their job. Case openers, case damage it would be pretty hard to pin the issue on them if you were to open the device.
Actually because of the present condition of the device I would go this route http://forum.xda-developers.com/showthread.php?t=2096888 . Just pick the latest version of the 8.9 to restore to you should also be prompted with an option to wipe cache and data please do so. All the partitions will be restored to stock and the device will be ready for return. Say nothing about modifying the device just leave those details out. If you want help catch me online and we will set something up. Some of this does depend on the state of your warranty. Be courteous with customer service and brief as to what caused the issue you simply just found it that way Good luck.
Good point, wasn't really thinking about "what if the problem wasn't that".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
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
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.