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.
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
its not booting up
stuck in Google logo
fastboot page doesnt help too
help pls
i was working regularly when restarted and locked in the google logo
not rooting and unlocking boot loader or sth like that
mahyarn said:
its not booting up
stuck in Google logo
fastboot page doesnt help too
help pls
i was working regularly when restarted and locked in the google logo
not rooting and unlocking boot loader or sth like that
Click to expand...
Click to collapse
Had to RMA mine to Asus within 24 hours of receipt for this very same issue. It was a failure on the motherboard and they had to replace. They noted the problem as LED (Indicator) Error on the packing slip as the reason for the repair. Hope you are still under warranty. You did not get a 16G from the recent ebay sale for 129, by any chance, did you? A few people have reported the same.
Mine just did the same thing.... screen started acting wonky, it did a reboot and BAMN google logo. No recovery, only bootloader. No amount of factory image flashing brings it back.
Have no warranty due to it having had a screen replacement in the Spring... ...
And it's a Deb. This tablet has been a terrible experience.
So pressing the power button does not cause the device to boot normally (the second screenshot)?
Hello,
i have messed up a bit while rooting my LG G3 but finally everything went smooth and i even had TWRP installed (hurray!). But now i need to go to stock because i need to get my phone fixed on warranty. The problem is that when i press Volume Up and plug in USB cable i see on screen: download mode, in the left top corner there are some little words "boot certification verify..." and then everything goes black and there is no 2nd step Download Mode screen.
https://www.youtube.com/watch?v=x_1YLCfv630
If you enter this video you will understand me. I can see the images which are in 1:03, but right after everything is black and i do not see "Firmware update" images in 1:14.
How can i fix it?
maciek1o3s said:
Hello,
i have messed up a bit while rooting my LG G3 but finally everything went smooth and i even had TWRP installed (hurray!). But now i need to go to stock because i need to get my phone fixed on warranty. The problem is that when i press Volume Up and plug in USB cable i see on screen: download mode, in the left top corner there are some little words "boot certification verify..." and then everything goes black and there is no 2nd step Download Mode screen.
https://www.youtube.com/watch?v=x_1YLCfv630
If you enter this video you will understand me. I can see the images which are in 1:03, but right after everything is black and i do not see "Firmware update" images in 1:14.
How can i fix it?
Click to expand...
Click to collapse
I made the exact same thread not long ago but NO ONE helped, sadly...
Got the exact same problem as you, I got no choice but to send back my phone for repair!
I completely messed up my bootloader... I tried reflashing etc, it even got worse (no TWRP, nothing, DEAD)
On the report they wrote "flash failed" and they eventually replaced the PCB (the main board).
Was lucky that they didn't charge me anything haha
either they didn't know anything, or they were nice with me lol
If ever you send for repair, Just don't mention you flashed or rooted or whatsoever lol ...
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`