Stuck on Google Logo Screen - Nexus 7 (2013) Q&A

I have 2013 Nexus 7 wifi and have been happily using it since I bought it back in September however I woke up this morning to find my Nexus showing the white google logo and it appeared to be stuck there. I powered it off by holding the power off button until it turned off however when I turned it on it was get stuck at the same place. I can do volume up and power and it wil bring me to a screen that says start, restart bootloader, recovery mode or power off
The fastboot mode info says:
Product name - flo
Variant - flo 32G
HW versions - rev_e
Bootloader Version - FLO-04.02
Carrier Info - None
Serial Number - not important
Signing - yes
Secrure Boot - enabled
Lock State - locked.
This device has never been unlocked or rooted.
If I choose recovery I get taken to the white google logo then a short time I get an android with a red triangle with an exclamation mark inside it. If I leave it there it will eventually show the white google logo again.
Is this terminal and should I return? I can't see any way to factory reset.
Thanks

krz84 said:
If I choose recovery I get taken to the white google logo then a short time I get an android with a red triangle with an exclamation mark inside it. If I leave it there it will eventually show the white google logo again.
Is this terminal and should I return? I can't see any way to factory reset.
Thanks
Click to expand...
Click to collapse
When you get to the android with the red triangle screen press volume up and power. That should get you into recovery.

meekrawb said:
When you get to the android with the red triangle screen press volume up and power. That should get you into recovery.
Click to expand...
Click to collapse
Hi thanks. I can get into recovery and when I try to factory reset I get a whole slew of errors about not being able to locate the cache. I try and wipe the cache and I get the same errors. Not sure what to try now.

This error was mentioned before . You can try flash a factory image but warranty is the best option
Sent from my Nexus 7 using Tapatalk

icrazy said:
This error was mentioned before . You can try flash a factory image but warranty is the best option
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll return it.

I had the exact same thing happen today. Wasn't able to get anywhere with adb in recovery. I'm returning it.

xdhall said:
I had the exact same thing happen today. Wasn't able to get anywhere with adb in recovery. I'm returning it.
Click to expand...
Click to collapse
Phoned ASUS today and they told me that it would need to go back under warranty. Just waiting for them to come back with a courier pickup notice. I'll probably be without it for a couple of weeks.

Did you take picture of your n7 before return it? I read people complaint Asus will do some damage to the n7 skin.
Nam Huy Linux http://namhuy.net

krz84 said:
I have 2013 Nexus 7 wifi and have been happily using it since I bought it back in September however I woke up this morning to find my Nexus showing the white google logo and it appeared to be stuck there. I powered it off by holding the power off button until it turned off however when I turned it on it was get stuck at the same place. I can do volume up and power and it wil bring me to a screen that says start, restart bootloader, recovery mode or power off
The fastboot mode info says:
Product name - flo
Variant - flo 32G
HW versions - rev_e
Bootloader Version - FLO-04.02
Carrier Info - None
Serial Number - not important
Signing - yes
Secrure Boot - enabled
Lock State - locked.
This device has never been unlocked or rooted.
If I choose recovery I get taken to the white google logo then a short time I get an android with a red triangle with an exclamation mark inside it. If I leave it there it will eventually show the white google logo again.
Is this terminal and should I return? I can't see any way to factory reset.
Thanks
Click to expand...
Click to collapse
This is a bit late ant you probably already did a warranty replacement, but I had a similar issue. It wouldn't boot past the Google logo screen, but I fixed it by downloading the KOT49H system restore image, extracting the system.img file, and manually flashing it in fastboot. It booted straight up no issues.

just got mine back today after same problem
took asus about a week to get my n7 repaired. seems to be working fine now. though no idea on what the actual problem was. any takers?

Related

Stuck on Google Screen - Restore Didn't Work

Good Morning All -
A few days ago, I dualbooted my N7 with Ubuntu. The installation went fine and the tablet was working with no issues over the last several days. Last night, I was using the tablet and set it down. I went to pick it up (roughly 5 minutes later) and the touch screen was unresponsive. I was at the lock screen but couldn't get it to unlock. I pushed the wrong key-combo first and the device took a screen shot.
I was able to reboot into fastboot and attempted to go to recovery. The device would just hang at the Google logo. I pushed a factory firmware update from my Ubuntu system and attempted to reset -- no joy. This morning, I used Nexus Root Toolkit from my Windows 8 machine to see if I could get it up. Root Tool kit worked fine, pushed the images over again and restarted but it continues to hang at the Google logo.
Looking for any other advice folks may have on getting the device to boot.
EDIT: I can get to the bootloader fine and the computer recognizes it.
Thanks!
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
xbi0s said:
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
Click to expand...
Click to collapse
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
antonio824 said:
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
Click to expand...
Click to collapse
I'm unable to get into the restore menu. Hangs at the Google logo when attempting to get there.
I've tried about any solution I could find... Bumping one last time before I torch the unit :\
Nothing can be done. Its something inside. If its the 2013 model, call and get it rma'd. Sorry man.
Sent from my LG-LS970 using XDA Premium HD app
Resurrecting this thread to keep a work log.
I made have made some progress but hitting another roadblock. I've been holed up at home due to an auto accident so I started tinkering with the N7 2013 again.
Using the Nexus Root Toolkit, I am able to launch "Boot Temporary - Custom Recovery" from the advanced options. The problem I now run into is TWRP's touchscreen will not work. I attempted to do volume up/down to see if I could select but it wouldn't. The software is not frozen as I can see the temperature changing.
Anyone have any thoughts or information on how to boot another custom recovery that uses button inputs? I appreciate any input.
Updates:
1. I was able to push TWRP via "fastboot flash recovery." It went to the Google Logo then loaded TeamWin screen. I started to see errors when the program launched. "Unable to mount..." multiple times then the device rebooted. Device stuck on the Google screen.
2. Shut the device down, booted back into Fastboot. Selected Recovery and it began loading again. This time, the app launched and worked. Touchscreen does not work but the CPU temp is fluctuating and minutes tick up.
Update 4:49PM Central:
1. I am able to install and boot into TWRP 2.8.0.1 through TWRP 2.7.1.1. Those versions load but of course touch screen does not work.
2. I have been unable to get CWM to load... It installs fine but I cannot boot into.
3. The factory recovery images also do not load.

Chinese M9 bootlooping after OTA

Hi All,
Really hoping someone can suggest a possible solution for this one, only had the phone a few months!
So, Chinese released M9. Unlocked. Stock recovery, not rooted. Gapps installled.
Everything perfect, then today I got the 5.1 update.
Seemed like a slightly iffy install process...looked a little like it failed a couple of times and tried again.
Finally finished, the phone shows the white screen with the one logo, takes a while, opens on the desktop and turns off, back to the white screen with the logo.
I have been able to boot into safe mode, which is stable
I have been able to get to download mode and bootloader. Neither of these offer a cache wipe or a factory reset.
I have not been able to get into recovery mode, it shows a phone with a red triangle and an exclamation point.
So for my (largely uneducated) part I have two theories for the cause:
1) Gapps is somehow proving a problem, either faulting the install or causing a fatal error on startup
2) Since the update was notified and downloaded while on a VPN via Hong Kong, I wonder if I accidentally ended up with the HK version in which case I suspect there may be hardware differences (at least the radio). This seems unlikely, I would hope there were enough checks in place to prevent this happening.
No solid idea where to go from here. I have not yet tried ADB access, but even if I can connect, what will I do? Flash a new ROM? I'd rather not. And surely I'd need to root in order to do that....
At a loss, any potential solutions welcomed whole heartedly!
Thanks...
Booting into safe mode, but not booting otherwise, indicates a problem with some app or rom setting.
You're probably going to need to do a factory reset, but that's odd that it doesn't show up in bootloader or download mode. Have you tried the options in stock recovery (which is that screen with the red triangle)? Use the volume keys to change options.
Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.
Trying a factory reset from safe mode - I'll let you know what happens!
misteral1970 said:
Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.
Click to expand...
Click to collapse
Hmm. It would seem the Chinese models are set up differently, which would not surprise me at all.

OP3 rebooting to blank screen (with white notification light)?

Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
AWretchSavedByGrace said:
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
Click to expand...
Click to collapse
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
thelad said:
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
Click to expand...
Click to collapse
So done that and got one black screen and the white light,went to work had 3g/4g on all day didn't get one black screen,got home connected to wifi and I got a black screen,so something to the with wifi seems to cause it for me
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Paradoxxx said:
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Click to expand...
Click to collapse
I think I'll have to its pissing me off now,goes great for hour or two then I'll get this black screen 4 or 5 times in a row
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
nono77240 said:
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
Click to expand...
Click to collapse
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
I don't know how much time after, maybe 6 hours later or so...
I had a freeze yesterday evening and had to reboot my phone.
Everytime it freezes on reboot and I have to wait 3 to 4 tries before the phone really boot.
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
I created a RMA ticket this morning.
My phone will go to repair center
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
My situation
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Breecko said:
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Click to expand...
Click to collapse
Have you tried holding power and volume down for a few seconds without the cable plugged into the phone?
thelad said:
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
Click to expand...
Click to collapse
acmerw said:
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
Click to expand...
Click to collapse
AWretchSavedByGrace said:
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
Click to expand...
Click to collapse
I received a mail yesterday evening saying that they can't take my phone and I have to do a factory reset.
I replied to this mail saying that I did multiple factory resets and even do a remote session with a oneplus tech support.
They sent me a mail an hour after with a number and the process to send my phone.

HELP - New Update Bricked 5x

Today I downloaded the new firmware update for the 5x. I installed using fastboot as normal, knowing that boot.img, vendor.img and system.img had changed.
I used fastboot to flash all three, then booted to TWRP and flashed SuperSU 2.76, ElementalX kernel and the AdAway file hosts.
The phone booted as normal and was running just fine for about 2 hours. Then, while playing music, I attempted to unlock the screen with the screen passcode. The device froze.
Attempting a reset only allowed it to get to the "Google" screen with the lock on the bottom, then the screen would go black. I could hard reset into bootloader mode. I attempted to flash back to stock, but the same freeze on the "Google" screen happened upon reboot.
Now, the device will not even get to bootloader mode. Holding the power + either of the two volume keys renders nothing on the screen, nor does plugging into USB on the computer. I'm fearing the device is hard bricked. Any recommendations?
Moonboots said:
Today I downloaded the new firmware update for the 5x. I installed using fastboot as normal, knowing that boot.img, vendor.img and system.img had changed.
I used fastboot to flash all three, then booted to TWRP and flashed SuperSU 2.76, ElementalX kernel and the AdAway file hosts.
The phone booted as normal and was running just fine for about 2 hours. Then, while playing music, I attempted to unlock the screen with the screen passcode. The device froze.
Attempting a reset only allowed it to get to the "Google" screen with the lock on the bottom, then the screen would go black. I could hard reset into bootloader mode. I attempted to flash back to stock, but the same freeze on the "Google" screen happened upon reboot.
Now, the device will not even get to bootloader mode. Holding the power + either of the two volume keys renders nothing on the screen, nor does plugging into USB on the computer. I'm fearing the device is hard bricked. Any recommendations?
Click to expand...
Click to collapse
There is a post 4 down from yours on fixing bricked phones.
Tulsadiver said:
There is a post 4 down from yours on fixing bricked phones.
Click to expand...
Click to collapse
Hi Tulsa,
Unfortunately, that post doesn't apply to this situation, as my bootloader is unlocked, and I can't even get to the stage of having the drivers recognize the phone, because the phone will not turn on to bootloader mode, recovery or download mode.
UPDATE:
The phone reached the point last night where it would not even power on, access bootloader or download mode. Any button presses/holds left the screen black.
Today, for whatever reason, the device booted into fastboot mode. I was able to flash the complete stock factory image for the August security update Android 7.0 - the first stable build. However, when the device began to boot, it once again does not get past the Google page with the lock on the bottom. The screen goes black after that without entering the boot animation.
I've called Google to get a warranty replacement unit sent.
I was having a similar situation last night, gave up after trying for a few hours...the googs is sending a "new" refurbished one. I had 1 month left on the factory warranty
http://forum.xda-developers.com/nexus-5x/help/bootloop-enter-recovery-wont-stay-t3456659
quadracer06 said:
I was having a similar situation last night, gave up after trying for a few hours...the googs is sending a "new" refurbished one. I had 1 month left on the factory warranty
http://forum.xda-developers.com/nexus-5x/help/bootloop-enter-recovery-wont-stay-t3456659
Click to expand...
Click to collapse
Thanks for the reply, quadracer. I'll be taking the same path you are - Google already has the reorder on the way. Still trying to tinker in case there's a chance. Luckily, all the pictures from my engagement this past weekend were backed up to Photos or I'd be devastated.

Nexus 5X stuck at Google Screen. Won't boot stock recovery.

I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!

Categories

Resources