Related
My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.
thisisjjd said:
My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.
Click to expand...
Click to collapse
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?
Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.
charesa39 said:
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?
Click to expand...
Click to collapse
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.
thisisjjd said:
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.
Click to expand...
Click to collapse
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051. Pay particular attention to what you need to modify to make sure you don't wipe your userdata.
charesa39 said:
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051.
Click to expand...
Click to collapse
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?
thisisjjd said:
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?
Click to expand...
Click to collapse
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
charesa39 said:
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
Click to expand...
Click to collapse
I thought I had tried that, but thank you, I'll try again. I appreciate your advice.
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.
thisisjjd said:
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.
Click to expand...
Click to collapse
Hmm. Unfortunately, this is issue seems beyond my knowledge. That's odd that yesterday it was showing unlocked, and today it randomly is locked. If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
charesa39 said:
That's odd that yesterday it was showing unlocked, and today it randomly is locked.
Click to expand...
Click to collapse
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.
charsea39 said:
If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
Click to expand...
Click to collapse
I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.
hector333 said:
Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.
Click to expand...
Click to collapse
thisisjjd said:
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.
Click to expand...
Click to collapse
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary. If you are stuck in a boot loop long press the power button to force a reboot, as soon as the screen turns off press the volume down button that will get you to the bootloader. Or if the device is off press and hold both the power button and volume down button to get to the bootloader. Choose recovery with the volume button then press the power button. You should see android laying down with exclamation mark. Press and hold the power button and while holding the power button press and release the volume up button. Stock recovery! Use the volume button to select "wipe data/factory reset" then press power button. If that doesn't take care of it download the factory image and extract, if running 4.4.2 wifi version you should see ;
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
if you double click the "flash-all.bat" with the device already at the bootloader that will flash the complete image including userdata which wipes the device. You can also open flash-all.bat with notepad and remove -w from the script and it should not flash the userdata.img. Or... you could extract all of the images from the "image-razor-kot49h.zip" and flash them seperately with fastboot, whatever images you try to flash need to be in the same folder as fastboot.exe (platform-tools) so you do have multiple options as long as there is no hardware issue that is causing the reboot. Hope this helps!
wantabe said:
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary.
Click to expand...
Click to collapse
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
thisisjjd said:
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
Click to expand...
Click to collapse
Sorry to hear that! I don't remember ever hearing being able to get into the bootloader but not into recovery from there. Your probably right about having to do doing an RMA. If it's any consolation I had a good experience with ASUS when I had to RMA my 1st gen N7 32GB after the speakers went bad.
I'm glad to hear you had a good experience with ASUS support. I have an RMA and am sending it to them. Thanks for your help.
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
mnunez611 said:
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
Click to expand...
Click to collapse
I would say definitely RMA it. With you having a stock tablet it's not worth risking messing something up trying to fix your tablet and then maybe you can't RMA. I would start with Best Buy and them what their warranty period is. If it is within their stories warranty then take it to them. If not then call ASUS.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Help me
Hello Guys I am stuck in a very annoying situation at the moment which is that my nexus 7 has become inaccessiblhttp://forum.xda-developers.com/images/smilies/eek.gife. This is how it happened
one day I tried to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' errohttp://forum.xda-developers.com/images/smilies/crying.gifr. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
thanks in advance
I have the exact same issue as the OP. Can't get to recovery cause the Google logo hangs there. I can fastboot but the N7 is locked since it was not rooted. Using fast boot and Wugs I get the same thing where it just hangs on erasing userdata for hours. Wondering if any fix has been discovered for this since the OP issue was months ago.
Use fastboot OEM unlock command to unlock the boot loader then re flash stock.
Sent from my Nexus 7
Hi
I recently received my shiny new M9 and like I have with many HTC phones prior to it unlocked the bootloader installed TWRP (latest beta version) and installed my rom of choice (LeeDroid). For about 10 days now the phone has been great working well on the new rom and all was well with the world.......
Last night the phone rebooted on me and boot looped about or 6 times before finally booting correctly and then behaving normally. Today however the phone is constantly boot looping and failing to boot. I can access the bootloader menu via vol up and down and power button but if i select recovery or download mode the phone simply boot loops over and over. RUU mode also does this.
Once in a blue moon if the phone is left looping over and over it will actually boot into the rom and work ok but as soon as the phone is reset or runs out of juice its all aboard the boot loop express.
regards
Brian
Fastboot commands work however adb commands do not. I have fixed boot loops previously but on this occasion a solution appears to be evading me.
MightyRaith said:
Hi
I recently received my shiny new M9 and like I have with many HTC phones prior to it unlocked the bootloader installed TWRP (latest beta version) and installed my rom of choice (LeeDroid). For about 10 days now the phone has been great working well on the new rom and all was well with the world.......
Last night the phone rebooted on me and boot looped about or 6 times before finally booting correctly and then behaving normally. Today however the phone is constantly boot looping and failing to boot. I can access the bootloader menu via vol up and down and power button but if i select recovery or download mode the phone simply boot loops over and over. RUU mode also does this.
Once in a blue moon if the phone is left looping over and over it will actually boot into the rom and work ok but as soon as the phone is reset or runs out of juice its all aboard the boot loop express.
regards
Brian
Fastboot commands work however adb commands do not. I have fixed boot loops previously but on this occasion a solution appears to be evading me.
Click to expand...
Click to collapse
Sounds like a tricky one, you cant get to download mode to flash a new recovery and cant boot recovery. So if you can do fastboot commands do you mean at the bootloader? If so you are limited without s-off in what commands you can do from bootloader menu. I would be looking for an RUU based on your cid to get you back to stock at this point. You may have to wait. You say adb commands dont work.. have you enabled developer options and installer drivers on your pc?
gffmac said:
Sounds like a tricky one, you cant get to download mode to flash a new recovery and cant boot recovery. So if you can do fastboot commands do you mean at the bootloader? If so you are limited without s-off in what commands you can do from bootloader menu. I would be looking for an RUU based on your cid to get you back to stock at this point. You may have to wait. You say adb commands dont work.. have you enabled developer options and installer drivers on your pc?
Click to expand...
Click to collapse
Dev options have indeed been enabled and all drivers installed I can use adb on my partners phone with no issues. Fastboot commands as you say only work at the bootloader screen,
Sadly I cant even flash a RUU the moment i try it simply reboots the phone back into the bootloop :crying:
MightyRaith said:
Dev options have indeed been enabled and all drivers installed I can use adb on my partners phone with no issues. Fastboot commands as you say only work at the bootloader screen,
Sadly I cant even flash a RUU the moment i try it simply reboots the phone back into the bootloop :crying:
Click to expand...
Click to collapse
Try updating to very latest fastboot, I had to update my sdk a while back as fastboot wasnt working properly with newer phones. Worth a try
Still fubar
Once in a blue moon the phone boots into the rom fine and you can use the phone its very weird I literally am all out of ideas now.
Think im gonna bite the bullet and send it back to Vodaphone and pay to get it fixed. I cannot enter download or recovery mode by any method that I have been advised or have read about thanks to those who tried to help it was appreciated.
Well you can try this in the bootloader. Open up a cmd window with fastboot in the directory and type fastboot erase cache
then type fastboot reboot
Download an ruu for your device. Rename the file to 0PJAIMG.zip
Place it on a sdcard with lower than 32gb and flash it. Need to flash it twice. Directly after each other. All done in download mode
I can'r get into download mode sadly and I have tried many many methods from threads about how to do so. Recovery mode and Downlode mode are just not working hence I think It's going to have to be repaired :crying:
Tecardo said:
Download an ruu for your device. Rename the file to 0PJAIMG.zip
Place it on a sdcard with lower than 32gb and flash it. Need to flash it twice. Directly after each other. All done in download mode
Click to expand...
Click to collapse
worked for me, thanks
MightyRaith said:
I can'r get into download mode sadly and I have tried many many methods from threads about how to do so. Recovery mode and Downlode mode are just not working hence I think It's going to have to be repaired :crying:
Click to expand...
Click to collapse
That's not possible, do u press power and up volume for 10 secs so it restarts and then immediately volume down?
Tecardo said:
That's not possible, do u press power and up volume for 10 secs so it restarts and then immediately volume down?
Click to expand...
Click to collapse
I do indeed and the phone then either shows the battery indicator for about 5 or 6 seconds then reboots or simply reboots. If i selected recovery mode in bootloader the phone just reboots as well.
How did you get into boot loader?
You could choose download there, or reboot into ruu mode
Tecardo said:
How did you get into boot loader?
You could choose download there, or reboot into ruu mode
Click to expand...
Click to collapse
I can get into bootloader by holding power + volume up+down but If I select either recovery or download mode the phone simply reboots normally and commences boot looping again. If RUU mode is selected the phone DOES reboot into RUU mode but if you try and flash the RUU the phone simply reboots and boot loops.
Try placing the zip I mentioned above on SD card.
Still unable to enter download mode via any means so I think it's going to have to go in the freezer till it wont boot and I can send it back
Things I still CANNOT do
Enter Recovery (Phone simply reboots and commences boot loop)
Enter Download Mode (Phone simply reboots and commences boot loop)
If I try and charge the phone with it turned off as soon as it gets power it boots up and boot loops Once in every few hundred boot loops the phone will make it into the rom and will work ok untill eventually it decides to bootloop again after a few hours.
(TL: DR below)So there's a bit of a story here, I installed cyanogenmod 13 iirc on my phone a while ago and none of the google services would work, so I used TWRP to flash SuperSU and another version of Open Gapps on my phone. The phone got stuck on the application initialization thing for when android updates apps for a new version. After 30 minutes, I restarted my phone like a moron and it wouldn't go past the boot screen. I can't even access the bootloader anymore, holding down the buttons doesn't do anything. I've tried using the android tools and adb sees the phone but it's unauthorized and I don't know how to authorize it without using my phone.
TL: DR: flashed supersu and gapps on cm13 and its in an infinite boot screen, cant get to bootloader either. only thing i managed to do is get the phone to show up with "adb devies" as unauthorized. plz help ;(
Why can't you access the bootloader? Can't you just turn the phone off and hold the volume button down and power button on?
OhioYJ said:
Why can't you access the bootloader? Can't you just turn the phone off and hold the volume button down and power button on?
Click to expand...
Click to collapse
No, I get the "Can't check device for corruption" screen then the "Android" screen also shows your bootloader is unlocked and holding down the buttons does absolutely nothing.
IHaveNoImagination said:
"Can't check device for corruption"
Click to expand...
Click to collapse
It will only pop up when your booting sequence goes beyond boot-loader. Trying holding power+vol down till you get bootloader or 1 min whichever is minimum.
I unlocked the bootloader and installed TWRP Recovery using the OP3 Tool. However now the phone will not boot unless I press the power button a few times. When it does boot I get the "Your device is not safe message", if I boot from here I get the OnePlus logo with the "powered by android" text but then it just shuts off. If I use the volume keys to select something else, I get nothing, the fastboot mode just gets stuck on the fastboot until I turn the device off, recovery just reboots to the "Your device is not safe screen".
Any help would be wonderful
McreativeH said:
I unlocked the bootloader and installed TWRP Recovery using the OP3 Tool. However now the phone will not boot unless I press the power button a few times. When it does boot I get the "Your device is not safe message", if I boot from here I get the OnePlus logo with the "powered by android" text but then it just shuts off. If I use the volume keys to select something else, I get nothing, the fastboot mode just gets stuck on the fastboot until I turn the device off, recovery just reboots to the "Your device is not safe screen".
Any help would be wonderful
Click to expand...
Click to collapse
Did you flash anything while you were unlocking the bootloader? The message is shown when the bootloader is unlocked so that is ok. Your phone, however, should turn on by long pressing the power button. You're getting a bootloop, If I were in such a situation I'd use the fastboot mode to flash the stock firmware again to get the phone working...
mharis05 said:
Did you flash anything while you were unlocking the bootloader? The message is shown when the bootloader is unlocked so that is ok. Your phone, however, should turn on by long pressing the power button. You're getting a bootloop, If I were in such a situation I'd use the fastboot mode to flash the stock firmware again to get the phone working...
Click to expand...
Click to collapse
I managed to get it working in the end by reflashing the stock recovery image ???? thank you for the help
McreativeH said:
I managed to get it working in the end by reflashing the stock recovery image ???? thank you for the help
Click to expand...
Click to collapse
Awesome! Enjoy :good:
I was at work the night before, and my capacitive buttons stopped responding, so I went for a restart in hopes they would kick back on, this just caused my phone to enter a boot loop. Soft resetting and hard resetting both continue the loop, trying to enter recovery mode throws me back into the loop, entering download mode locks the phone on the small HTC screen. I tried to flash the current RUU onto the phone, but it won't proceed with the install due to a low main battery error despite the fact I've had it charging for 6 hours. The only thing I can think of doing now is sending it back in hopes they fix it, but theres a lot of information I ignorantly haven't backed up, and now can't access before sending it back.
If anyone has any helpful tips or ways to move forward I would be grateful.
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
silegeek said:
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
Click to expand...
Click to collapse
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Snickie12 said:
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Click to expand...
Click to collapse
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
Holding Volume up just continued the loop, I can get into the bootloader like you said, but theres not very many options, download locks the phone onto the HTC logo and doesn't proceed, the recovery option just restarts the phone into the loop.
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
silegeek said:
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
Click to expand...
Click to collapse
Whenever I plug it in while off, it shows the low battery icon and tries to turn itself on.
I had exactly the same problem...were you able to sort it out?
same problem except I can charge mine will I be able to ruu even if it is locked ?
isaac1993 said:
same problem except I can charge mine will I be able to ruu even if it is locked ?
Click to expand...
Click to collapse
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
No,it's not. I'm bl ul,s-off,and I can ruu anytime.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
I thought it was charging but now fount out it wont charge
isaac1993 said:
I thought it was charging but now fount out it wont charge
Click to expand...
Click to collapse
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
singlemalt said:
I had exactly the same problem...were you able to sort it out?
Click to expand...
Click to collapse
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Snickie12 said:
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Click to expand...
Click to collapse
Did they tell you what they did to fix it by chance? Thanks.
singlemalt said:
Did they tell you what they did to fix it by chance? Thanks.
Click to expand...
Click to collapse
No they didn't sorry.
singlemalt said:
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
Click to expand...
Click to collapse
My friends s7 completly bricked doing the N update. If you havnt done anything to your phone just take it back and get a new one.
Same exact issue here after the Verizon OTA update.
Failed after the first reboot after the update.
The storage was pretty maxed, wonder if that has something to do with it.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
I have very similar htc 10 issue : (
https://www.reddit.com/r/HTC10/comments/9j8nyk/htc_10_oreo_stuck_in_boot_loop_i_can_only_access/
how do you do fastboot commands when only at bootloader screen when you cant access download mode or recovery : ( also my htc 10 was low on stoage space I must have corrupted the htc 10 oreo : (