I have GSM Galaxy Nexus running 4.0.1 ICS on T-Mobile and when I get the notice there is an update for the phone, I OK the update and the phone reboots and tries to install the update, but then goes into the screen with the android guy lying down with the red triangle?
I wait a few minutes and the phones reboots and I am still on 4.0.1? I have tried this three times with the same results. Any help would be appreciated.
Are you rooted? Custom recovery installed? Sounds like you have a custom recovery installed which is making the update fail case its trying to use stock recovery. You could pull the update from your cache folder and manually flash it via adb there are threads around on how to do it
Sent from my Galaxy Nexus using XDA App
Related
Ok so i got my nexus today and it is fantastic. I unlocked the bootloader and rooted the phone no problem. installed clockwork with rom manager though, I turned the phone off and then while pressing vol up and down went into recovery again. Rebooted into clockwork and bam we're good. I rebooted to move some files over and when i tried to get into recovery again i get the android dude with the yield sign over and over again. Im not sure why this is happening, any suggestions?
I was having the same problem at first. Problem was fixed by "flash clockwork mod" and then reboot into recovery. After that I had no problems. :beer:
Sent from my Galaxy Nexus using Tapatalk
I also initially tried to install CWM thru rom mananger but after a reboot or 2, booting into recovery always led do a android with red triangle and I'd have to re-install (this was happened many times)
To finally fix it I downloaded the CWM .img and flashed it using fastboot on my laptop while the phone was in the bootloader. Recovery image hasn't died since.
Means image isn't applied.
Get Rom manager from the market and it will flash image.
Done.
Android with yield sign is stock Android recovery.
Sent from my Galaxy Nexus using XDA App
Hi,
I bought the GNexus a month ago, its my 1st android device. (I had a Blackberry for the last 3 years).
I have unlocked my Gnex, and rooted it, then i have installed yakju in order to get rid of my yakjuux ROM, it was my 1st time doing it... Everything worked fine, all my apps were automatically redownloaded and reinstalled from my google account. (Very nice feature).
But for some reason now, I have lost my root acces and I am not sure why or how.. is it normal? I have installed root checker, and supser user returns messages saying he cant get root privileges on my phone.
I tried rooting the phone using superboot. Everyting seemd to have worked fine:
C:\Nexus\r3-galaxynexus-superboot\r3-galaxynexus-superboot>install-superboot-win
dows.bat
C:\Nexus\r3-galaxynexus-superboot\r3-galaxynexus-superboot>fastboot-windows.exe
boot boot.superboot.img
downloading 'boot.img'... OKAY
booting... OKAY
The phone reboted but stayed at the Google logo for like 3 mins. I pulled the battery and after that the phone rebooted normally except superuser cant access root.
Any tips or help is welcome on how to root the phone (already unlocked)
Thanks
You should have left it on there! Mine got stuck on the Google boot logo for around 10 minutes before it was done? I was just about to pull it before it booted up. Go through the process again and give it time
Sent from my Galaxy Nexus using xda premium
Go on YouTube and look for zedomax. He has an easy root video with a link to all the software
Sent from my Galaxy Nexus using xda premium
when you installed the yakju ROM to change yakjuux it deleted root because you fully wiped your phone for a yakju build. just reapply superboot (or install clockwork recovery and flash su.zip that will give you root) and you'll have root.
either that or flash a custom ROM with clockwork recovery and you'll have root.
Another thing is always make a backup of your current favorite rom before flashing anything. I have my original rom and 1 favorite rooted rom on backup at all times. If you do this and encounter problems you can always go in recovery and restore your custom rooted rom. The only reason I keep a stock rom on is in case I have to return the phone. You can remove your unlock symbol by going in fastboot and typing (fastboot OEM lock) I think! This was how I locked my bootloaders back up on my beloved nexus s, good luck and pm me if you need anything
Sent from my Galaxy Nexus using xda premium
zephiK said:
when you installed the yakju ROM to change yakjuux it deleted root because you fully wiped your phone for a yakju build. just reapply superboot (or install clockwork recovery and flash su.zip that will give you root) and you'll have root.
either that or flash a custom ROM with clockwork recovery and you'll have root.
Click to expand...
Click to collapse
Didn't know about su.zip option in CWM, where can I find this zip file for the GNex GSM?
mike216 said:
You should have left it on there! Mine got stuck on the Google boot logo for around 10 minutes before it was done? I was just about to pull it before it booted up. Go through the process again and give it time
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I gave it like 30 mins and still the Google logo was displayed. It seems my rooting did not work properly. Maybe i am not using the right tools?
Zedomax has a nicve procedure, but the link to doenload is GalaxyNexusRoot.zip file is dead. I cant use his method..
Thanks for the help.
gabster21 said:
Didn't know about su.zip option in CWM, where can I find this zip file for the GNex GSM?
Click to expand...
Click to collapse
I couldn't find it on XDA but I did get it off XDA before and have tested it on 4.0.2 when I used 4.0.2 stock. I just uploaded it: http://www.mediafire.com/download.php?4qq8mhu7w0437ky flash in cwr.
md5: 3450886EA845813637419C10DA01BA9D
I've flashed 4 times the Vicious V3 and TR4NSCEND ROM once last night. Each time the ROM works fine and then I reboot it and it goes into bootloop mode. I lose all data and have to reload the OS from scratch. I've followed all the instructions to the letter, and still the JB ROM works for a day or so and then it crashed.
What could be the issue? Is it a phone (hardware issue), one of the appa that I'm using, or something I'm doing wrong?
When I'm retoring the apps, I'm not reinstalling the data, apps only.
Really getting tired of reflashing the ROM and having it crash.
Any help would be greatly appreciated!!
Thanks
At list yours can boot up.. mine just stock in boot loop the first time I flash jb rom it works and I used it for a couple of days and try to flash different jb rom then boom! Boot loop.. I've flash 3 different jb rom with no success.. I'm not new to this stuff I've flash more than 100 different rom since vibrant gs2 and now gnex. I really don't have any idea what happen.. I think one of the jb rom had mess up my gnex. I've I restore to fresh and unbrick state many times and every time I flash jb rom it just stock in boot loop.. I read in some post that I should wait but I don't think 30to 1hr in boot loop is to long.
Sent from my Galaxy Nexus using XDA Premium App
bigdaddy rob said:
Each time the ROM works fine and then I reboot it and it goes into bootloop mode.
Click to expand...
Click to collapse
does it bootloop when boot animation is rolling, or on the google screen?
if it is the first, then connect the phone to adbd, and see 'adb logcat', there might be some useful information there.
if it is the second, there must be something else. do you use an app to reboot? which recovery? if you shut the device down, and power up again, does it still bootloop?
advice: reflash stock from fastboot, flash cwm non touch or twrp 2.1.2, reboot to recovery, flash rom
advice update: use cwm 6.x.x.x or TWRP 2.2.x
long first boot
I am also encountering boot issues. On my Toro Gnex with every ROM I have put on that is Jelly Bean ( vicious, and bug less beast) the first boot just sits at the Google logo. If I do a battery pull and try to start my phone again it boots up within a minute. I will try the log to see what it reads and I will post the results. Is this happening to everyone else where it sits at the Google logo until you do battery pull?
Mine sits at Google logo regardless if I do a battery pull or data wipe on toro galaxy nexus.
Sent from my Galaxy Nexus using xda app-developers app
I hope someone can look at this and help us fix this...
Sent from my Galaxy Nexus using XDA Premium App
Having similar issues - phone will be operational for around 20 seconds, then reboots - but it does not show the Google logo, only the coloured Nexus logo.
Additionally, for me it ONLY happens when WiFi is enabled. Hope this helps someone!
I had this problem on my gnex toro and I managed to get around it by:
Back up any data or be prepared to lose it
Reflash phone to factory 4.0.2 image using GNEX TOOLKIT (google [GNex TOOLKIT V7.4] )
Let the phone boot on stock OS
Download the ROM you'd like to flash on to your phone's sdcard
Shutdown and start on bootloader / fastboot (power + both volume buttons while phone is off)
Flash CWM recovery
Boot in to CWM recovery
Factory data reset
Flash zip from SD card
Reboot and let it load completely
I hope this helps. The gnex toolkit is really helpful and it resolved my issues with getting Vicious and other roms to load
When you say flash cwm you mean flash a zip file of cwm? I've use toolkit 7.4 many times with no problem.. I can restore flash new ics rom.. but when I flash a jb rom any kind of jb rom my phone will be just stock in nexus logo..
Sent from my Galaxy Nexus using XDA Premium App
I recently got a GSM gNex and last night I decided to upgrade to JB using the OTA links posted here in the forum. I unlocked the boot loader, flashed twrp's recovery, installed SuperSU and then the JB 4.1.1 OTA file and everything went smoothly. Since after the upgrade, on my PC when I connect my gNex, I'm getting a "Fast boot read error" and my PC stopped recognizing the device. I switched to my Mac and got everything I needed done. Why am I here? Obviously I've been able to go into twrp recovery to do a lot of this stuff. But now, anytime I try to go into recovery mode, I get the screen with android lying on back with the exclamation point. I have to flash recovery (I've tried CWM, CWM touch, optimus prime touch) using fast boot every time I have to go into recovery. I tried going to recovery using ROM manager and that gets me to same situation. (Android on back).
Any thoughts?
Sent from my Galaxy Nexus using xda app-developers app
verruckterGeck said:
I recently got a GSM gNex and last night I decided to upgrade to JB using the OTA links posted here in the forum. I unlocked the boot loader, flashed twrp's recovery, installed SuperSU and then the JB 4.1.1 OTA file and everything went smoothly. Since after the upgrade, on my PC when I connect my gNex, I'm getting a "Fast boot read error" and my PC stopped recognizing the device. I switched to my Mac and got everything I needed done. Why am I here? Obviously I've been able to go into twrp recovery to do a lot of this stuff. But now, anytime I try to go into recovery mode, I get the screen with android lying on back with the exclamation point. I have to flash recovery (I've tried CWM, CWM touch, optimus prime touch) using fast boot every time I have to go into recovery. I tried going to recovery using ROM manager and that gets me to same situation. (Android on back).
Any thoughts?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If 4.1.1 is anything like 4.0.x, you'll have to rename/remove this file: /system/etc/install-recovery.sh
Hello everyone.
I have my GN with stock room 4.1.2 and I want to update to 4.2... everything is stock but my phone is rooted...
I manually go to the settings, about phone and search for the update. When it appears, I download the uptate normally and reboot
The problem starts now... the GN instead of aplying the update boots to a kind of app which you may know... it shows the logo in a blue background with letters TEAMWIN of something line that... From there, I dont know what to do and end up turning off my phone who is still in 4.1.2
What can i do?
That's not an app, that's TWRP recovery. You can't install OTA with a custom recovery. I have same problem with my moms gnex. I hear about the annoying update msg whenever I hear from her. I have to figure out what to do about it for her.
I think the best bet is to just use the recovery to flash a rooted stock (or custom) 4.2 ROM here, from xda.
hurled from my AOKP'd Evo LTE. Enjoy.
Can I disable that recovery? I dont use it for anything and I like to keep my Roms stock
Flash the stock recovery in fastboot or let TWRP install the update.
Next time don't use a toolkit to root your phone
Sent from my Galaxy Nexus using Tapatalk 2
If OP had read this thread, at least the first post, he would know almost everything he needed to know.
Sent from my i9250