So I've had my Nexus 7 for a while now and I was using it for GPS maps the other day. The thing went to sleep and when about half an hour later I tried to unlock it, it didn't respond. The screen came on but it didn't seem to detect my finger. So I held the powerbutton for like 20 seconds and ever since it stuck on the google screen. When I go to bootloader and select recovery, it also stucks on the Google screen. I can also unlock the bootloader and flash TWRP but when I type fastboot oem device-info it will still tell me it is untampered and locked. Does anyone have any idea why this might happen? The thing wasn't rooted/bl unlocked. Thanks in advance.
PS: Don't respond with the 'try flashing a factory image/recovery', because trust me, I've tried those.
I had basically the same issue, however, I was unlocked and running stock 4.4.4. Mine reboot in the middle of Game of War, and was stuck at the Google Logo. I could get into Fastboot and my computer recognized, so I tried reflashing the stock images, but no dice. They appeared to flash fine without any error messages, but did not fix the issue. Also, selecting recovery, brought me back to the Google logo.
That said, I RMA'd the tablet. Apparently, there was a hardware failure as the packing slip from Asus noted that issue was a LED (Indicator) Error, and as a result they replaced what appears to be the main board (part number 90NK0080-R01000 Description ME571K MAIN_BD_2G/Q8064/16G).
So, this is likely not what you want to hear, but it sounds like a hardware failure. I bought a refurb tablet, and mine failed less than 24 hours out of the box. Thankfully, it came with a 90 day warranty.
if you cane unlock boot loader you can flash it , if you cant' there no way as i know
Related
First post here - I promise I searched for similar problems and didn't find anything exactly like this....
I am running an unlocked version of 4.0.2 - it is the version that updated the day I bought it. The phone was unlocked the day I got it, which was also the day it came out in the US. The Nexus is LTE/CDMA version
Little history first: The phone has been more or less fine from day one, though there had been an occasional unexplained restart. Normally when it randomly does this, it just restarts normally and everything is okay besides the brief interruption.
This morning, a few minutes after making a phone call, my phone restarted. However this time the phone got stuck in a boot loop which involves a brief freeze while the colored flying checkerboard video is playing. No matter how many times I let it loop through this it never progresses past this video.
To try and fix this I tried to fastboot the clockword recovery image and it just caused it to crash earlier in the boot sequence, ie, when the the google screen is up.
My feeling is this might be a hardware issue - the problem is of course that my phone is unlocked which kills the warranty.
Anybody have any ideas on what to do or a better explanation of what is wrong?
Many thanks for any help.
You can flash the stock images in fastboot. They are located here: http://code.google.com/android/nexus/images.html
If you just want to re-lock your bootloader and warranty the phone just type
Code:
fastboot oem lock
perfect, thanks. phone is now re-locked
thanks again
Hi,
I have a really tough problem with my Verizon Galaxy Nexus. After I boot it up it shows the Google logo and then the screen goes black. It is still on because I have left it there hoping it would pass this screen but the battery died eventually. If I put the phone into a computer I get the charging screen and it will charge. I can get into fastboot mode. I have tried unlocking the device so I could flash a new ROM but as soon as I use the Gnex toolkit to unlock it, the fastboot mode reboots and it is locked again. When the device is plugged into the computer in fastboot mode Windows is constantly giving the noise that something is plugged in than unplugged then plugged in, on and on and on. I have put it in Odin mode and flashing the 4.04 image ROM looked like it worked but still after the phone reboots it just shows the Google Logo and then goes black. I have gotten into the stock recovery and wiped data and cache and that did not help either. Any help would be appreciated!
Nick
PS
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
I followed that and afterwards my screen still comes up black after the Google logo.
I just tried to install TWRP recovery to see if that would help. I went through all of the fastboot commands and they said they completed successfully. When the phone rebooted the stock android recovery was still on the device... so for some reason this phone is taking the commands and they are getting returned as successful but they are not successful... super strange.
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
My Gnexi said:
Sorry I can't help you but I've read several reports (forum posts) about Galaxy Nexus devices becoming "read only". I think the eMMC got bricked and can't be fixed.
Click to expand...
Click to collapse
Correct, seems highly likely his eMMC deep fried. If unlocking bootloader doesn't even work, I would try nothing else and get its mainboard replaced.
Thanks. Now that I know, I can stop wasting my time trying to fix this.
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!
Greetings!
My girlfriend's Nexus 5X recently got stuck into boot loop. What I tried to fix it:
- Completely discharging it and charging it again
- Get into recovery mode - after going to the bootloader and choosing recovery mode, the phone reboots to the google logo
- I tried reflashing system, boot and recovery with TWRP - still the phone reboots when trying to get into recovery mode
What else can I try, having in mind that I can't get into recovery or boot it at all? The bootloader is unlocked, so I can try flashing anything.
You could try the BLOD-fix boot/recovery images on other threads in this forum.
If the phone is still in warranty (and even if it's not), I'd suggest getting in touch with your local LG repair people.
My wife's Google Nexus 5x died yesterday too after updating. Go to load recovery mode, and it does nothing. I can get into developer boot screen, but that's it... Nothing works. Her bootloader is locked though, so no flashing anything. Any idea on how to contact Google about getting a replacement?
Squealor said:
My wife's Google Nexus 5x died yesterday too after updating. Go to load recovery mode, and it does nothing. I can get into developer boot screen, but that's it... Nothing works. Her bootloader is locked though, so no flashing anything. Any idea on how to contact Google about getting a replacement?
Click to expand...
Click to collapse
No point contacting google, you have to go to the manufacturer LG wherever they happen to be in your country. A simple replacement phone will only potentially have the same issue - its a hardware problem and the PCB/motherboard must be replaced. I had a brand new phone (well 'brand new' as bought in 2016 but only unboxed last Tuesday lol) which didn't last 6 hours before getting overly hot and going into bootloop...tried a factory reset and got into setup but it shutdown and bootlooped again halfway through. Fortunately it was within the 2 year warranty period, so LG authorised the replacement motherboard on Thursday (1 hour wait as a walk-in service) and it has been fine (and cool!) ever since.
As a bonus, they upgraded it from 6.0 to 7.1.2, which LG considers the "latest" stable version for the 5x.
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
i think if anything at this point, you need to assume none of your data can be saved. if you send it to google for them to fix, no data will be kept most likely, nor if you find any solution to do yourself. what happens if on the google screen you hold down power and voldown until it turns off and then keep holding them down?
It goes into fastboot with the android guy on it's back and it gives me the "restart bootloader", "recovery mode", "barcodes", etc, options. None of which the phone can enter apart from the barcodes and the powering off option. :crying:
HanaTruly said:
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
Click to expand...
Click to collapse
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Nilkong said:
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Click to expand...
Click to collapse
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
sudoxd said:
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
Click to expand...
Click to collapse
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Nilkong said:
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Click to expand...
Click to collapse
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
I flashed the new version of OTA from google's site. And it looks like it's booting up. Will report back if it crashes or continues to hold up.
Thanks!
EDIT: It's back to boot looping. It was at the "G" screen with white loading bar underneath. It froze there and went back to bootloop. Looks like there might be no avail.
Similar issue here. I gave up on it a month ago, but I figured it can't hurt to ask around. FWIW, there seem to be a lot of similar reports on Google's Pixel support forum.
Anyway, during the 2nd year of owning my Pixel XL (got it in Septempter 2017), I started experiencing slowdowns and random reboots more frequently, but never any bootloops until after receiving Android 10. After receiving Android 10, the random reboots seemed to be happening more frequently. I also experienced a weird issue where the phone would spontaneously exit out of the Google app (reached by left edge swipe from home screen) consistently within a few seconds of entering it.
Eventually, after another increasingly common random freeze, the phone rebooted and got stuck in a bootloop. Initially, chances were high that I would be able to complete the boot process after a few attempts, but inevitably, it would freeze and start bootlooping again. During the handful of successful boot attempts, I was able to backup some photos, and more importantly, enable OEM bootloader unlock in the developer options. After several more failed attempts to boot successfully, I did a total reflash of the latest factory image as of September 2019, after which I was able to get partially through the new phone setup process before crashing. For each subsequent attempt, the crash would happen earlier and earlier in the setup process until it wouldn't get further than the 'G' logo before rebooting. When the October 2019 factory image became available, I tried flashing that as well, but no luck.
On one hand, considering that the failures got progressively worse over time, it seems that this is fundamental hardware failure in the SOC, motherboard, RAM, etc. On the other hand, there seems to have been so many recent reports of this, especially after the Android 10 update, that I wonder whether or not it is software issue. Or could it be some combination of both, where the Android 10 update is pushing the hardware in new ways that is more likely to exacerbate an underlying hardware flaw?
Should I try re-flashing with Android 9 instead? At this point, it is a total brick...
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
ckidmcd said:
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
Click to expand...
Click to collapse
Needs to boot to any recovery, custom or not, to sideload an ota
sudoxd said:
Needs to boot to any recovery, custom or not, to sideload an ota
Click to expand...
Click to collapse
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
ckidmcd said:
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
Click to expand...
Click to collapse
does fastboot see your phone at all if you type `fastboot devices`