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
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
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
EgoTrip26 said:
So, I decided to root my wifes Galaxy S2 due to it being a little older and to get more out of it for her, however I seem to have got my self stuck in a bootloop.
-Downloaded Odin, flashed CWM recovery and rooted phone all relatively easy and with no issues. However I wanted to get CM 10.1.2 stable cuase thats what i run on my Nexus 4. Before i flashed, i ran a Nandroid backup from cwm and did a wipe data/factory reset and rebooted. this is where i got the boot loop, on the T-mobile screen. Tried restoring from the back up, and still boot looped. tried flashing CM and it boot looped on the CM splash screen. On the CM forum it seems someone else had this issue and that kinda how i got pointed here. CM Admin suggested downloading an updated Bootloader. I honestly looked all over this site and couldnt find ANYTHING. I can still get into Download mode, and Recovery mode with no issues.
Thanks for your time
CWM v 5.0.2.6
Samsung T989 (JB 4.1.2)
Rooted
Click to expand...
Click to collapse
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
soupysoup said:
U need to flash the newest twrp recovery, a lot of ppl have been having issues with cwm lately so my advice would be to DL the twrp tar file and use that to root and not cwm
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
EgoTrip26 said:
I will try that, I use TWRP for my Nexus 4. That being said, do i have to go back to stock and unroot, or just flash TWRP and attempt to install CM?
Click to expand...
Click to collapse
Just flash recovery then cm rom.
Sent from my SGH-M919 using Tapatalk 2
Thanks a million!
Thanks to both of you for prompt response, Used TWRP and at least got CM to flash and startup, so far so good. hope it works as well on the S2 as it does on my phone!
Thanks again
So, I was trying to put 4.4 kitkat onto my galaxy nexus verizon phone and I had CM10.3 working on it (which was roughly 4.3.x) and clockword recov mod. and then I got a new clockwork rom (as attached) and I ran: fastboot flash recovery newrecovery.img
Then it successfully ran via adb, but then when I rebooted it, i told it to go to recovery mode, but it brings up a default "Google" page with a unlocked symbol on the bottom. Its been running for about 10 minutes now and it will not get off this page.
What can I do? Is this thing done for? I cannot seem to get it to work.
Thank you.
Flash the newest cwm via fastboot and reboot to recobery.
Sent from my Galaxy Nexus using XDA Premium HD app
Hi guys, I managed to do something I've never heard of. To be fair, I try to follow directions pretty well, so I don't screw things up too often, and I'm not sure what to do now. Any help or guidance would be appreciated.
The symptom is that the phone will boot witht eh Samsung boot animation, I will see the Clockworkmod icon at the bottom, some Clockworkmod version information, then the phone will reboot. This will happen presumably indefinitely. I have watched it do it 3 times in a row and then pulled the battery. Post Philz, I get Android tablet icons instead of Clockworkmod icon and version info.
I loaded Whompasaurus http://forum.xda-developers.com/showthread.php?t=2039564 to my phone yesterday and I was about to load Venom http://forum.xda-developers.com/showthread.php?t=2121063 to my phone this morning (I had just copied it to the SD card). I told the phone to reboot into recovery by pressing the power button and selecting the option "reboot, recovery". The phone is now stuck rebooting attempting to enter recover and failing, or so it appears. I upgraded the Clockworkmod version to 6.0.4.3 yesterday, and that did act a little weird in my opinion, but since I had never done that before, I wasn't sure what to expect.
When I told it to upgrade in the Clockworkmod app, the phone powered off and I had to remove the battery to turn it back on. I booted to recovery and it said it was now at 6.0.4.3, so I booted normally. Back in the app it said it was 5.something. I kept poking around and it eventually asked for root access, which it hadn't before, and when I told it to upgrade the recovery this time, it actually rebotted the phone rather than turn it off.
I reflashed the CWM 6.0.4.3 recovery with Heimdall per these instructions (why aren't there proper instructions for Odin?!?!?! ermahgerd!!) via this link http://wiki.cyanogenmod.org/w/Install_CM_for_l900
That was successful but did not affect the symptoms.
I upgraded to Philz recovery thinking maybe I had to use a different recovery to reset the "boot to recovery" flag. I used this file and Odin, after resetting the Samsung driver: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900/philz_touch_6.26.6-l900.tar.md5
The process was successful, but did not change the symptoms. Instead of seeing a Clockworkmod icon and version info at the bottom, I see what looks like android icons at the bottom, and then the phone reboots.
What can I do to fix my phone? I can boot to downloader mode fine. I would prefer to use Odin, but it seems I have Heimdall set up and working too.
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Team Win FTW!!! That fixed it!
jlmancuso said:
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there something special about 2.6.x? I saw that there's a 2.7.x available now. 2.6.x doesn't seem to like my 64GB SD card, or maybe something else is going on. I factory reset a few times and will upgrade to the latest TWRP and try to flash that latest Venom ROM now and see what happens.
*Edit* No, there's SDCARD, SDCARD1, and EXTERNAL_SDCARD and I didn't check all of them, that's all. Oy, oy, oy.... But I'm up to 2.7 and installing Venom now....
Are asking for ROM recommendations still a no-no?
Yeah still pretty much a no no. I have used all the roms here and they are all pretty good.
Now I do suggest that you flash philz 6.07.9 for your recovery. First is that it properly flashes 4.4 and TW 4.3 roms. Second it makes proper backups. Twrp still has issues with aosp 4.4 and TW 4.3.
Sent from my SPH-L900 using XDA Premium 4 mobile app