Unfixable Google Loop - So frustrated - Nexus 7 (2013) Q&A

I bought my Nexus 7 2013 shortly after they were available and it was a good device until the release of KitKat. After the KitKat OTA it's been a piece of junk.
After the KitKat OTA it developed a problem where the tablet was on but the touchscreen was unresponsive. The only way to fix it was to shut it down by holding the power button. Eventually it started being stubborn and I'd have to power cycle it several times before it would clear the Google screen. That gradually progressed to having to do a system reset before it would come back to life.
On December 15th it finally refused to go past the Google splash. Attempting to boot into recovery also left you stuck at the Google logo. At the time I tried the WUGFresh tools to do a stock recovery and while I was successful in unlocking no amount of flashing / formatting / erasing would give you a normal boot or a recovery screen.
I sent it off to ASUS on 12/17 and got it back this past Monday (1/13). It worked fine until Tuesday night when once again the screen was unresponsive and I had to shut it down by holding the power button. It's now stuck at the Google screen and no amount of flashing / formatting / erasing using FreshWug or fastboot directly via command line has brought it back.
Here's what I've done so far:
Spammed flash-all at least 6 times
fastboot format of /boot /system /userdata /cache multiple times
Multiple runs of WUGFresh
Flashed 4.4.2 and 4.3 images
What else is there I can do aside from sending it back to ASUS?

Does it boot to bootloader?
Sent from my Nexus 7 using Tapatalk

As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
This
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
Yes to all of those, I just did them again to verify. FYI WUG opens a command shell as it runs fastboot so you can see what it's up to.
Anywhoo I reflashed kot49h (manually) and got the same result, stuck at Google. If this thing wasn't still under warranty I'd snap it in half and light the two halves on fire.
Any other ideas?

What if you tried a custom recovery and custom ROM?

So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?

buelldozer said:
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
Click to expand...
Click to collapse
any updates? is it working fine now? any random reboots? god i hated that on my 1st nex7fhd, im on my 2nd one, its and perfect aside from the 'low speaker volume' stock

Might be an hardware issue, don't get stuck with software too much, send it again until they replace it.

I'd be interested in what ASUS did to it.
Did they include a list of parts replaced, etc?

I'm also curious.
As long as the flashes are done correctly it should boot fine.
However, I had a similar issue flashing stock.
The fix was to flash stock. Boot.
If it boot looped restart and wipe dalivik cache and cache and reboot. It should start then. just an FYI...
Sent from my Galaxy Nexus using xda app-developers app

If u get boot loops = lemon, it will develop those anno ying reboots
Via my NeXus™ 7 FHD on Tapatalk⁴ Pro

So it did it again but following the previous directions I was able to unloop it immediately the big story though is WHY it was looping.
I have a minisuit BT keyboard / case ( http://www.amazon.com/Minisuit-Blue...=UTF8&qid=1390433882&sr=8-3&keywords=minisuit ). The thing is dynamite and I love it and it worked great! The keyboard has a low power battery saver state so after you don't use it for a few minutes it basically goes to sleep until you tap a few buttons and wake it up.
I went a week with no issues but I wasn't using the keyboard. When I did finally use the keyboard I would stop typing and let it go to sleep as I always do. When I tapped a few keys it would wake up and then wake up the N7 and it's screen but the screen would -not- accept touch input. I had to hold the power button down and force the N7 to shut off. When I powered it back up...BAM...LOOPED.
It didn't do this before the Kit Kat upgrade. It's obvious that something is wrong with the BT stack in 4.4.2 and when a HID goes into a low power state it hoses the touch input. Since the touch input is hosed you can't shut it down correctly and the file system corrupts, likely the /system partition.
If I use the N7 without the keyboard it's perfectly fine.
userdelroot I couldn't clear dalvik on mine because I couldn't boot to recovery. All boot options lead to a Google Loop.

I have had exactly the same experience, basically. Just got mine back from ASUS, worked for about a day, and then BAM, back to the same DAMN thing! I think you may be on to something about the BT stack. If there is any common thread to both my breakdowns, its that my Nexus got screwed not long after i paired a BT headset with it. Its late and I'm frustrated as all hell so please forgive my short rant. So what to do? Do I send it back to ASUS and hope they actually replace it this time? (The invoice I got back from them was very strange incidentally. I couldn't tell what they did, except among four parts listed, they seemed to replace a "cracked, broken screen" which was not the way it was when I sent it to them???!) Or should I just keep reflashing and hope it takes, as it seemed to do for you? But then can I risk pairing my BT headset again?! This sux.
Update: Woke up this morning, turned it on, and it booted up! WTF? Not complaining I guess. Taking it easy this time, unlocked bootloader still of course, but holding off rooting, and not going to pair any BT with it for awhile. Although its kinda BS I should have to try it this way...

It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.

buelldozer said:
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
Click to expand...
Click to collapse
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?

Demian87 said:
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Click to expand...
Click to collapse
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.

buelldozer said:
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
Click to expand...
Click to collapse
Thank you a lot! I'll try to leave it turned on for the whole night. I left it only for 45 minutes before that. Probably, that was not enough.

My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.

buelldozer said:
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
Click to expand...
Click to collapse
My tablet is now at 9:15 hours and still at Google logo. I'm guessing that the time is not the only matter for normal boot up.
---
Now after 11 hours I gave up. =(

Related

[How To] Fix Stock Kindle Fire 2 Bootloop

A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
Where do i enter this in when I'm in fastboot?
Karetus said:
Where do i enter this in when I'm in fastboot?
Click to expand...
Click to collapse
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).
hexd said:
You need to use the fastboot application. You can get it either via the Android Development Kit (just google for it) or just use it from any other source (I know the FlashTool for Sony phones has it along with ADB). Once it is on your PC, open a command prompt window to that folder and run it from there.
Just remember you need the Kindle to be in FB Mode (the screen has a picture of a red and green stoplight on it) and you need fastboot drivers installed for the device (this is a bit tricky for Win8, no problem for Windows 7 though).
Click to expand...
Click to collapse
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"
Karetus said:
I'm at a screen with a blue arrow a and yellow text that says "fastboot mode"
Click to expand...
Click to collapse
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).
hexd said:
Please make sure that you have a Kindle Fire 2 (or at least something in the second generation Fire range). It might help if you take a picture of the device in fastboot mode and post it here.
Also did you boot the kindle into fastboot mode using a factory cable, or using a command from Android itself (it would have involved adb shell).
Click to expand...
Click to collapse
From the computer. KFF Aide. I'm still stuck I have been looking for hours.
hexd said:
A few months ago I tried to root/ gapps a KF2 for a friend, and after a freak OTA update the horrible thing kept getting stuck in a bootloop.
Basically if you powered it on it would get stuck on the Kindle pulsing logo until it restarted itself from scratch and did it all over again. Then on the few times it would get to the standard lock screen it would freeze up there and restart itself anyway.
Every now and then it would boot in and work fine though.
What I eventually did to get it working:
1.) Get a factory cable (they don't cost too much off ebay).
2.) Using fastboot mode clear the data and cache partition:
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
20 seconds later the device worked perfectly and hasn't bootlooped since.
It might also be possible to do this by a.) installing TWRP and erasing the cache/ data from there, or b.) booting into the bootloader from a rooted system. I don't want to test this though because at this point I just want to make this awful thing work properly in stock.
I hope this helps someone else in the same situation. I do remember reading a similar problem on XDA a few months ago when it started giving trouble.
Click to expand...
Click to collapse
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable
JORDANZ1998 said:
my kindle fire hd 7 7.3.1 just went into a boot loop. it is recognized by my computer the drivers work it says device cant startup. adb wont work. how do i get it into fast-boot without a factory cable
Click to expand...
Click to collapse
Trying to do any work on a Kindle without a cable is a total pain. If you own the device just pay the few dollars to get one and make your life easier.
If you cannot get into ADB with full root, or a 3rd party recovery that was already installed you will need the cable to fix things.

Nexus 7 2013 stuck at Google screen

So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.
[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.
anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state
hard reset ?
hard reset always works for me. 20 seconds
krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Is your device rooted? If not that is just rediculous on asus's part
slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.
I would return it..I'm sorry to hear that I have had troubles myself with two devices so far
krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?
I have no way to enable usb debugging since I cant tun on the device, right?
krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.
Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you

Z00A stuck on Error! msg during boot, can't access recovery

So here's the deal, I tried to format the cache partition of a stock, non-rooted and non-unlocked bootloader Zenfone 2 (Z00A) through recovery, and it somehow failed/got stuck. After about 1h, I shut down the phone via long-pressing the power button and now it won't boot.
Booting it just leads to an "error!' message and stay there. Trying to go back to recovery does the same thing, I can get to the initial fastboot screen, but selecting recovery mode and pressing power+vol up after the reboot doesn't lead to recovery at all. Instead, every 5 or 10 seconds, the screen clears to black for 1 sec and the same error message shows up.
I tried to get access to it through ADB, but it won't show up in the device list under either the fastboot screen or the Error! message screen on which it stays stuck. Also, the phone was setup so that it didn't allow USB debugging, but I doubt that matters, given that it can't even load Android at all.
Is there something I can do about it? Any tip is greatly appreciated, I looked around XDA and Reddit but didn't find anything that really helped.
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
ultramag69 said:
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
Click to expand...
Click to collapse
Thanks, I had tried various variations of that approach but the issue was a bit more complex than that. In the bootloader, the phone was detected by Windows and drivers from Asus installed properly. ADB wouldn't list the phone, but fastboot did. However, any operation by fastboot was denied access because USB debugging was not enabled prior to the phone going down. Otherwise, as you mentioned, fastboot erase cache would have worked fine.
In the end, I found another post on XDA by Theja which linked to a post in Spanish. The modified ADB and fastboot packet there contains a batch file that manages to bypass this issue and installs CWR, from which clearing the cache is possible. Upon reboot, Asus replaces CWR with the original recovery and things look back to normal.
Sweet, as long as you got it back up and running...
ultramag69 said:
Sweet, as long as you got it back up and running...
Click to expand...
Click to collapse
Hehe, thanks. I'm pretty happy indeed, was already considering the need for a new phone.
However, I must say that finding this toolset worries me a little bit. I thought the whole point of disabling USB debugging was to ensure that people can't perform low-level operations on the phone via fastboot/adb. In this case, this protection is somehow bypassed. I didn't have time to read through the entire batch file, nor am I proficient-enough in Android to make sense of it all, but I wonder how it was done...
In any case, I now have USB debugging left on. It increases convenience and the ability to recover things if problems occur, and it seems like the security benefits are not that strong anyways.

[TRIED FLASHING FACTORY IMAGES] H790 random power-offs, not bootloop

Hi,
I did try to search this problem but couldn't really find the words I needed to get enough specificity to differentiate it from other problems which weren't mine, so sorry if this post is a duplicate of something else.
My problem is that my 5X 16GB will power off consistently and boot itself up again. It isn't a bootloop because it isn't an instantaneous shut down, but can often stay on for about 2-5 minutes, sometimes staying on for almost an hour. There doesn't really seem to be any pattern or predictable nature to it, as sometimes when the device powers back on the default launcher and 'system' will stop working and the device will just give up, skipping straight to the boot animation and skipping the google logo.
I have tried erasing and formatting all partitions on the device i could get my hands on (namely recovery, cache, system, userdata, and boot), then flashing in the following order:
fastboot flash bootloader bootloader-bullhead-bhz11h.img
fastboot flash radio radio-bullhead-m8994f-2.6.36.2.20.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Sometimes I was able to get the device working for a long time such as two days with the device acting completely normally, and it would only enter its old state when it powered off. I can't really remember what I did to get the device working before, but I'm fairly sure it was something like flashing 6.0.0 (which would behave strangely, with the setup sometimes crashing and the device rebooting) and update the device OTA, which restored it to a state of normality.
Am quite lost right now and very frustrated- this is my second phone, the first being a Oneplus One which is also cocked up :crying:
Thanks for any help
bilboswaggins22 said:
Hi,
I did try to search this problem but couldn't really find the words I needed to get enough specificity to differentiate it from other problems which weren't mine, so sorry if this post is a duplicate of something else.
My problem is that my 5X 16GB will power off consistently and boot itself up again. It isn't a bootloop because it isn't an instantaneous shut down, but can often stay on for about 2-5 minutes, sometimes staying on for almost an hour. There doesn't really seem to be any pattern or predictable nature to it, as sometimes when the device powers back on the default launcher and 'system' will stop working and the device will just give up, skipping straight to the boot animation and skipping the google logo.
I have tried erasing and formatting all partitions on the device i could get my hands on (namely recovery, cache, system, userdata, and boot), then flashing in the following order:
fastboot flash bootloader bootloader-bullhead-bhz11h.img
fastboot flash radio radio-bullhead-m8994f-2.6.36.2.20.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Sometimes I was able to get the device working for a long time such as two days with the device acting completely normally, and it would only enter its old state when it powered off. I can't really remember what I did to get the device working before, but I'm fairly sure it was something like flashing 6.0.0 (which would behave strangely, with the setup sometimes crashing and the device rebooting) and update the device OTA, which restored it to a state of normality.
Am quite lost right now and very frustrated- this is my second phone, the first being a Oneplus One which is also cocked up :crying:
Thanks for any help
Click to expand...
Click to collapse
Request an exchange from LG or Google.
Sent from my Nexus 5X using Tapatalk
HW bootloop begins with random reboots. So bring back to LG right now.
(Flash stock, Lock the bootloader if unlocked etc)

Bootloop issue finally killing my phone?

I've been having the bootloop issue ever since ~November, where the phone will randomly reboot itself for no reason; charging, not charging, screen on or off, in any number of apps or phone call or just on the lock screen. Since I'm bootloader unlocked, I found that going into TWRP and clearing the Dalvik cache immediately fixed the issue (until tomorrow)! It typically happened once per day or every other day, seemingly depending on usage, until this week... I used it as normal, and it hasn't rebooted at all in over 5 days. Today it finally did, and now clearing the Dalvik cache does nothing for it; continuous bootloops. I decided now is as good as ever of a time to do a factory reset and update to stock 8.1 (previously was on stock 8.0 - I did the full wipe with the -w flag). Now it starts going through the setup process but locks up and turns itself off after about 60 seconds. I tried flashing BenzoRom using the below instructions and the same thing happens. Does anyone have any other thoughts? I really have nothing to lose at this point.
EDIT: Also tried Safe Mode with 8.0, 8.1, and BenzoRom 8.1. None worked better than without it.
EDIT2: Well this time I got all the way through setup (did set up as new device) and then went to download an app from the Google Play Store when it turned itself off. Lasted about 5 minutes.
EDIT3: It occasionally even freezes/turns off in TWRP. This is what's really making me think it's a phone defect.
EDIT4: I left it off overnight and it worked for an hour this morning before it turned off. Then I left it off for an hour but it froze immediately after turning on. Bizarre. Will let Verizon "troubleshoot" today (which will be a factory reset and then a shrug) and see what they recommend from there. Don't have high hopes since my bootloader is unlocked, even though that's completely unrelated to any issue. This shouldn't be happening after 15 months. I'm still making payments on it for the next 9
EDIT5: Verizon said out of warranty and no insurance so too bad. Checking with a different Verizon tomorrow and then ubreakifix. Not sure why I'm supposed to have insurance for something completely out of my control.
EDIT6: See reply below. Verizon is replacing with same phone.
xanaxdroid said:
For people having trouble booting custom roms please read:
Get a copy of the stock boot.img, twrp-3.2.0-0-marlin.img, twrp-pixel-installer-marlin-3.2.0-0.zip and the Benzo Rom zip.
1. Boot into bootloader
2. run: fastboot --slot all erase boot
3. run: fastboot --slot all format system
4. run: fastboot --slot all format vendor
Go to where you extracted the stock boot image
5. run: fastboot --slot a flash boot boot.img
6. run: fastboot --slot a flash boot twrp-3.2.0-0-marlin.img
7. run: fastboot --set-active=a
8. run: fastboot reboot-bootloader
9. Then select recovery from the bootloader menu
10. Go to wipe. Move the slider to factory reset which will wipe data, but not internal storage.
11. Install benzorom-8.1.0-date-version-marlin.zip and twrp-pixel-installer-marlin-3.2.0-0.zip
12. Reboot
If you want to install root after boot back into recovery by rebooting and holding volume down after you hit reboot then selecting recovery from bootloader. That will take you into TWRP on slot b which is where you want to install Magisk from. I don't use SuperSU anymore so Magisk is all I know that works.
You can get the twrp .img and .zip from their site right here.
Click to expand...
Click to collapse
Long story short, Verizon Extended Warranty at 866-406-5154 went through some troubleshooting (clear cache, then factory reset) then said this is NOT an insurance claim since it's a phone defect and they will replace the phone with a refurbished Pixel XL 128GB (same phone). Was hoping they could bump me up to an XL2 but no dice lol. They sent it with free overnight shipping and I have to send mine back within 5 days. Trading in my bootloader unlocked device hurts, but it's better than having no phone at all. Hope this helps others having the same issues.

Categories

Resources