My friend has the toro(Verizon) variant of the Galaxy Nexus. One day it rebooted and barely can get past the nexus boot animation... and sort of bootloops. Sometimes after a battery pull it gets as far as the selecting english language screen but does not let me even press the button, and after a few seconds just reboots. I took the phone in order to try and help him revive it and during some processes with ODIN i now am stuck on the infamous {phone...yellow triangle...pc} screen. No other mode accessible, i'm positive of it. No download mode, no fastboot, nothing but the {phone...triangle...pc} screen. Some refer to this screen as a "soft brick" however, every method ive tried to remedy this that has worked for others has not worked. I have tried flashing the ODIN PDA and PHONE files. adb, and toolkit will not work because usb debugging is not accessible. However ODIN still recognizes the device. I've read about an OMAP flashing but i couldnt figure out how to go about doing this... BTW his phone was never rooted, just stock Android. Is there a possibility that this screen can show up due to a hardware failure?(motherboard, cpu, etc.)
Anyone have any ideas on how to fix this besides all the methods on the popular forums?
Related
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.
My Sprint Galaxy Nexus recently got submerged in saltwater (it was in a drybag that failed). After lots of rinsing and drying, I finally got it to turn on with the Google logo and go into a boot loop. I held vol up/down/power to get to recovery mode once and decided to do some Googling to make sure how to proceed. Ever since then, the vol up/down/power mode doesn't even work. Trying that, the phone will start up and just go to a black screen (if I'm in a dark room, I can see that the display is on, just black). As opposed to just hitting power which still shows the Google logo and boot loops.
I also can't seem to connect to adb, although I've done that many times in the past. I suspect it's because I can't get to bootloader mode. If I could get to that, I think I'd be golden. It seems, the only thing I can get to is odin mode, so I tried returning to stock using that. I was unfamiliar with that process, so I walked through the guide here and used the FH05 tar, however, it always seemed to error on the radio-cdma.img. If I remove that from the tar, it'll write fine, but nothing really changed in terms of what I could do. I was unable to find any other working tar links.
Any ideas on what to try with ODIN or help getting my adb connected or getting to recovery mode?
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk
I have a little experience with custom roms and rooting, but i have not yet set anything back to stock. I tried to set my GT-S7560m back to stock with a stock rom from sammobile(dot)com. I flashed it with odin like normal, and it said everything was good, but the phone never booted.
It got past displaying the model but got stuck at the samsung flashing while booting. I have left it at the screen for 30 minutes hoping it would boot, but no luck. I removed the battery for a day and tried to boot again and still no luck.
I read somewhere that sometimes help if you can clear the cashe but i can not enter the recovery(I can still enter download mode). I have noticed when i try and enter the recovery when the phone is plugged into the computer it just keeps saying disconnecting and reconnecting, with nothing on the phone it self.
I also tryed to use samsung kies to reset it but it just told me this device was not supported or something similar to that.
Now i have tried anything that i have found, i am willing to try just about anything, any help or input would be appreciated.
Hello All,
I recently found a Sprint Samsung Galaxy S3 (SPH-710T) that cannot boot to its custom ROM, CyanogenMod. The only thing I vaguely remember is a few years back when a coworker of mine had pulled out the battery when the phone was either rebooting or installing an update. The phone still boots to download mode, but when I do the combonation for recovery mode (Volume Up, Power, and Home), it shows the startup logo and blue text at the upper right corner, but then immediately shuts off. I have tries using download mode to install TWRP, but every time I do it, the program on my computer says that the process was successful, but the phone shows no sign of the program being installed. I have also been successful when downloading CF-Root to the phone, but the attempts at installing TWRP after that yeild the same result. I saw a video detailing a de-bricking SD card, but got scared after I learned that the card were not interchangeable between models. I am here for any questions you might ask and I will happily try any of the solutions provided by people.
Thanks so much for all of your help,
Max