VZW Galaxy Nexus goes black after the Google logo - Samsung Galaxy Nexus

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.

Related

[Q] Can't boot to recovery or download mode

It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
dileepan said:
It is a long story, started with wanting Photoshare App. After rooting using Odin got into all sort of process stopped error. Desperate, downloaded and tried to flash CM10 using CWM. All I got was CM logo circling endlessly for 30 minutes. Pulled the plug and now, I seem to have a brick, can't even boot to recovery or download mode. When I try to boot to downlad mode, the warning screen appears for just a second and goes away. When I try recovery mode Samsumg log appears and then blank.
Is there anything I can do at this point? I appreciate any help I can get.
Click to expand...
Click to collapse
Hm. if you boot up your phone are you stuck at the cm bootup? If you are im sorry bro you cant fix it for free by sending it to samsung. JTAG for 60 bucks or samsung for 60 bucks. Reason being that it shows that you have rooted and modded your device. If you were hardbricked and nothing would turn on at all you would be able to send it to samsung and get it fixed for free!
Well if it shows Download mode then it might be working, just not showing, if you see a blue ID:COM number in Odin its working. Try to flash a stock ROM in Odin while in Download mode and make sure its in PDA or you will brick. Check only Auto-Reboot and F. Reset time.
If it works congrats if not search this forum for a service called JTAG which repairs bricks.
\(._.\) To the window, to the wall.
(/._.)/
A little update ...
I was able to get to download mode after many trys and got back to stock -- unrooted. I should have stopped when I was ahead, but I was feeling invincible after this feat of reviving the phone and that was really stupid.
I wanted to root and flash CM10 nightly. I followed the instructions from http://rootzwiki.com/topic/32486-gu...m10-nightlies-without-k-exec-updated-8-18-12/. After unlocking the bootloader step, I wanted to backup the stock ROM I had on the phone -- I don't know why I wanted to do that as I had just flashed the stock and didn't have anything customized. Anyway, when I clicked backup from CWM everything died, kaput, nothing. I have been desperately holding the power button, reovery combination of buttons, download mode combination, anything I can think of, the phone is giving me the total silent treatment, which BTW I am used from a more human source.
Let me know if there is anything I can do, perhaps stand on one leg and try switching it on perhaps. http://forum.xda-developers.com/images/smilies/redface.gif
Sorry for the dumb jokes, I am a little frustrated, but I am sure I will get over it.
Thanks for those who took interest to read my question and those who cared to respond, I appreciate it....
Cheers!
are you getting any signs of life with the phone plugged in with or without the battery in?
jeeper11 said:
are you getting any signs of life with the phone plugged in with or without the battery in?
Click to expand...
Click to collapse
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
dileepan said:
Absolutely nothing, not even the light that comes on when plugged in for charging.
best ...
Click to expand...
Click to collapse
Best advice...take out the battery, leave for 1-2 hours, insert battery, try to access download, flash stock in odin, reboot, don't flash any more Jelly Bean roms. lol

[Q] Nexus 7 (2013) stuck on Google logo.

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

Soft Brick from bad cable?

So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Lohboh said:
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Click to expand...
Click to collapse
So you can't even get to download mode by holding power+vol down for several seconds?
Tarima said:
So you can't even get to download mode by holding power+vol down for several seconds?
Click to expand...
Click to collapse
No, it just brings up the same issue of it getting stuck on the monochrome HTC logo.
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
ffuser1 said:
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
Click to expand...
Click to collapse
I've tried that, and I have the latest TWRP.

Probably bricked, don't know what to do

Hey all,
So like about a year ago I installed twrp and rooted my one m8s and couldn't care less to update anything but everything was working fine.
Recently I bought a new phone so today I thought lets wipe the device and factory reset it. Well thats where it went wrong.
After the reset it tried to boot but was just stuck on the white screen with the HTC logo.
I then held the power + vol up, which triggered something and showed an other logo for a second then just going dark, but the device is still on and backlit.
I cant get out of this for some reason neither will the device turn off. When i connect it to my pc it gets recognized but I cant get into storage.
Also adb and fastboot won't see the device and the htc_fastboot.exe I got from here throws an adbwinapi.dll missing error.
I am really stuck on what to do and i was hoping maybe someone could help me out here?
Thanks in advance.
Regards,
Bart
EDIT: got the phone to turn off when the battery died and was able to boot into fastboot from there, lets see where this gets me.
EDIT #2: Welp I fixed it I suppose. If someone please could remove this thread since I can't

US Unlocked stuck in bootloop. Unable to boot into recovery/download.

Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
bmx4lfe said:
Okay, I have never had to create a thread for this kind of thing. I have always been able to solve these issues. This time around, I have ran out of ideas. I have been searching and searching Google, Xda and any other Android forum. I have seen multiple threads with this problem, some cases exactly like mine. Not one thread with this problem ends with a solution, they're all just dead ends. My HTC 10 started doing this a couple days ago after a notification popped up saying that I was using an incompatible charger after using a Samsung USB cable on a Quickcharge 3.0 car charger. 30 minutes later, my capacitive touch buttons were not responding. So, I just figured that I would reboot and everything would be fine. Now, my phone is stuck in a bootloop with no signs of recovery. The only thing it will boot into is the white bootloader screen. Trying to boot into recovery or download just throws it back into a bootloop. When its powered off and I put it on a charger, the charging animation will show for about 15 seconds then, back into a bootloop. Trying to use a RUU.exe doesnt work, just a message shows up saying that my phone is below 30% charge. The device will show up in fastboot devices when its in the bootloader but, its useless. Trying to flash anything in fastboot fails or does nothing. The bootloader doesnt recognize 2PS6IMG.zip in the sd card. I really need my phone for work and cant afford to wait for HTC to repair it, especially since Hurricane Harvey hit their repair center in Houston. I've taken out the Sd Card and sim to see that would help but nothing. I let it die completely and still nothing.
My bootloader screen shows
Status: Official
***Unlocked***
***S-OFF***
I have been running Viper 3.5.0 for awhile.
This is my last option to see if anyone else has got through this problem without sending it off.
Thank you
Click to expand...
Click to collapse
Hold down the power button and vol down until your phone reboots. It'll take 20 seconds or so, and the capacitive button lights should flash until it reboots.
That should take you to download mode where the RUU.zip on your SD can be flashed.
If that doesn't work, try power + vol up + vol down, then switching to power + vol down when the screen goes black. I think I remember having to do that once when I first got the 10 for a different problem, but it could have been a different device

Categories

Resources