Develop Bugs

[Q] Help! Boot Loop after Flashing ROM

I am fairly new to Android, but am comfortable with command line operation on other Unix systems, etc. I read every thread I can find on this, but did not find my problem described exactly (there are some similar problems), so here it is:
My phone is a GSM Galaxy Nexus, about a month old. I rooted and unlocked it right away using post 1 from this guide: [VZW/SPRINT/GSM][Guide] Ultimate Galaxy Nexus Guide (Unlock/Root/Flash Roms/FAQ) - thanks Jubakuba!
I did NOT use any of the toolkits or automated methods.
A couple of days ago, I decided to try loading another ROM. I read through post 2 of the above guide. I followed the instructions in that thread and flashed a Trinity ROM. The flash seemed to go fine, and completed normally, but when I rebooted the phone, it was stuck in the Google Lock screen bootloop. I was able to restore a nandroid to get it back to where it was before, and the phone operates normally, no resets, reboots, nada. I inquired in Jubakubas thread as well as in the Trinity ROM thread in the developers section, and got some suggestions, which I tried. None of them worked. I also tried flashing a few other ROMS, a CM9 ROM and the RASCREAM ROM, and they all do the same thing. I have tried flashing these without wiping data or cache or dalvik cache, wiping some of them and wiping all of them, and the results are always the same - boot loop, which I can restore using CWM recovery and my nandroid.
One of the posters in the developers forum suggested taking the phone back to unrooted stock condition, so I did that, using this thread: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid build / Return to stock - another excellent guide, which worked exactly as described.
After that, my phone was back to as new, and I had to go through the whole start-up and restore applications, etc. I made a new nandroid so that recovery would be relatively painless, etc. Not too tough. I then Rooted the phone (it was always unlocked) and tried flashing a ROM again, with exactly the same results. Again, I was able to restore my nandroid and get back to operational.
I guess my question at this point is what on earth could be causing this? Some of the threads on boot loops where peoples phones start to boot loop spontaneously suggest a hardware problem, but the fact that I have NEVER had a boot loop in a month of use while running 4.0.4 stock rooted and unlocked seems to point more toward software as the cause. I will say one thing - I am learning how to use CWM and the bootloader commands! But, I would really like to be able to use some custom ROMS, not that there is anything really wrong with stock - this is a great phone. But, please HELP!

Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2

d0msen said:
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into fastboot mode, then flashed the bootloader (bootloader-maguro-primela03.img) and radio (radio-maguro-i9250xxla02.img). I rebooted the bootloader, then went into recovery mode. From recovery mode, I selected "Install zip from sd card", "Choose zip from sd card", then selected the zip file in the /Download folder "TNP1536-384-Alpha86b-4.7-lto.zip". It went through its' install and said "System successfully corrupted" at the end and "Install from sdcard complete." I went back to reboot system rom and rebooted. Now, it is not looping anymore, but just sitting at the Google lock screen for about 2 minutes now. I will wait a few more minutes to see if it boots the rest of the way or starts looping, etc.
Okay, it has been 5-6 minutes with no additional changes, so I am pulling the battery. Powering it on now results in the same boot loop as before, so I will need to boot into bootloader mode and restore my nandroid.

are you wiping data when you flash the rom?
if not, you need to do that first inside of cwm

I would let it sit longer before pulling the battery
Sent from my Galaxy Nexus using xda premium

Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.

CYoung234 said:
"System successfully corrupted"
Click to expand...
Click to collapse
The
BOOM!
System successfully corrupted
Please freak out now
is a joke. By your account the kernel flashed successfully. Try flashing another kernel, perhaps not an Alpha version, although I've run that particular Alpha successfully. Do you have an app that sets kernel settings on boot by chance?

Hmmm thats a Kernel i think try another kernel.. Franco is a option ... maybe ur phone can't handle the undervolt of Trinity? I don't know worth a try download franco and post ur results here
Good luck

Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2

d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The nandroid I am restoring to is stock 4.0.4. I will wipe everything, then try flashing a known stable aokp build, then report back.

efrant said:
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
Click to expand...
Click to collapse
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.

CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.

CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2

CMNein said:
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
Click to expand...
Click to collapse
Yes, pretty much this. If you are updating CM9 to the next build, no need to wipe. If you are going from CM9 to AOKP, then you need to wipe.
Updating: no need to wipe.
New ROM: wipe.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?

efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You are correct, it is a kernel, not a ROM. I have tried 3 different Trinity kernels and one Franco kernel, all with the same results. The specific kernel I flashed for post #3 was TNP-1536-384-ALPHA86b-4.7-LTO.zip. The other two I tried were both stable releases. Morfic asked me to try the alpha kernel.

CMNein said:
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
Click to expand...
Click to collapse
Google Galaxy Nexus i9250.

CYoung234 said:
Google Galaxy Nexus i9250.
Click to expand...
Click to collapse
Okay, was asking in the event that you were also flashing Rascream, or Morfic's build of it.
Re: wiping, since we now know that we're just talking kernel here, wiping dalvik + wiping cache is indeed approaching useless, so they weren't leading you astray. I can't think of what would be causing you to boot loop however.

d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.

CYoung234 said:
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
Click to expand...
Click to collapse
This got me thinking: is trinity even compatible with a stock ROM (regardless of it being 4.0.4)? Maybe that is why you were having issues.

Superuser installation aborted (tried pretty much everything..)

Okay, this is extremely irritating. I'm getting an "installation aborted. Status (0)" when trying to install the SU zip from recovery. If I use superboot it just gets stuck at Google's logo. Below are some more info:
running IMM76I 4.0.4 (GSM)
I tried using CWM, CWM Touch, TWRP 2.1 (all "booted" only), superboot. All recoveries were for GSM Galaxy Nexus (maguro)
I tried using su binaries only, full su, downloading again both. MD5 is correct.
I tried fixing permissions, wiping dalvik cache, mount/unmount system, toggle signature verification, toggle script asserts, fastboot oem lock/unlock
At the end of everything, SU is installed but I have no root..
Update: I think I *might* have pinpointed the problem: it appears that the recoveries are trying to read the su.zip from /sd-ext, which if I'm correct does not exist on the GNex (only sd-int).. now why the heck would that happen? Might it be because I only fastboot boot'ed them and not fastboot flash'ed? I'd rather keep my stock recovery if possible..
Any help would be greatly appreciated, I've been going crazy for the past 3h trying to gain root, which should be a matter of minutes with a "dev phone" like the Gnex...

Unless you're specifically trying it the manual way for the experience why not just use the GNex toolkit to unlock/root/etc?

Why not just flash the recoveries then return flash the stock recovery back..?
Why do you want to keep the stock recovery?

Copy the file from here to the root of your /sdcard, reboot into CWM and flash the zip... Or better yet, just follow the instructions in that link.

Ok, I tried WugFresh's Gnex toolkit. Everything goes fine till the phone reboots, than it gets stuck at "rooting your Galaxy Nexus".
I'm starting to think it might be the ROM, despite it being 100% stock. I will try re-flashing the whole stock image (downloading atm) and see what happens.
p.s.: I'm not a noob (I thought it would be obvious from the first post but apparently some people missed it :laugh: ), so I know how to root under "normal" circumstances. No need to point me at "how-to-root" threads unless they contain particular information about this specific situation (su.zip installation aborted).
Thanks to everyone who has replied so far!!

Lazer Bear said:
Ok, I tried WugFresh's Gnex toolkit. Everything goes fine till the phone reboots, than it gets stuck at "rooting your Galaxy Nexus".
I'm starting to think it might be the ROM, despite it being 100% stock. I will try re-flashing the whole stock image (downloading atm) and see what happens.
p.s.: I'm not a noob (I thought it would be obvious from the first post but apparently some people missed it :laugh: ), so I know how to root under "normal" circumstances. No need to point me at "how-to-root" threads unless they contain particular information about this specific situation (su.zip installation aborted).
Thanks to everyone who has replied so far!!
Click to expand...
Click to collapse
I pointed you to that link because you may have downloaded an incompatible superuser zip. I packaged that one up, so I know it works.
P.s. Not sure about other recoveries, by the non-touch version of CWM looks for files in /sdcard (i.e., /data/media) and sub-folders, not anywhere else...
Sent from my Galaxy Nexus using Tapatalk 2

HOORAY! I did it!!!
This is what I did:
1-downloaded latest WugFresh's Toolkit (tired of doing everything manually and getting 0 results..)
2-tried flashing stock rom, got stuck after it flashed the bootloader
3-Downloaded another toolkit from xda (Gnex toolkit 7.0)
4-successfully flashed stock with that.
5-tried rooting using that one, got stuck after booting insecure image
6-went back to Wugfresh's, successfully rooted using it!!
So, basically I have no idea how or why this problem happened nor how I solved it, but after 2 days and 5h I did it! Lol..

JB boot loops my phone!

So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.

EDIT: Missed the fact that this is a Verizon Nexus so removing this comment.

asawoszc said:
Have you tried a stock version of Jelly Bean from the files on XDA? Sorry but it just sounds like you've tried custom ROM's. My other suggestion would be to put on 4.0.4 takju from Google's site and see if you get the Jelly Bean OTA update and if it resolves the issues in the short term. If it does then it must be the process you're going thru to put on the ROM's..... might be missing something simple like Dalvik cache wipe, etc. Just speaking in very general terms.
Click to expand...
Click to collapse
no, he shouldnt do any of what you said. he is on a VERIZON nexus. not a GSM. if he flashed takju there could be serious problems.

Apologies... I missed the last line. Will edit out my comment.

lacesout said:
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
Click to expand...
Click to collapse
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389

Zepius said:
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Click to expand...
Click to collapse
Thanks Zepius but I already did this. It's the only way for me to recover. My phone is fine now on AOKP M5 but I want to use Jelly Bean. Is there any reason JB would cause boot loops after 24 hours? It's just a pain in the ass because I can't simply recover through CWM. I need a PC. The first time this happened I had to back up my SDCARD from ADB. This took forever!!
BTW, I know how to Root, ROM, etc. I always do everything twice. Wipe Data/Dalvik/Cache and install the ROM twice.

just curious... which version of CWM are you using?

Oh man I have the same issue I just get stuck at the Google screen or the jb splash screen on my cdma nexus I tried everything and wiped every last thing on my phone I just gave up and said ile wait for the official update I guess. Anyway I hope this thread shed some light on the situation we having
Sent from my Galaxy Nexus using xda app-developers app

Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.

What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.

Zepius said:
just curious... which version of CWM are you using?
Click to expand...
Click to collapse
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
XfrostX said:
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
Click to expand...
Click to collapse
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
akira02rex said:
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Click to expand...
Click to collapse
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.

lacesout said:
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
Click to expand...
Click to collapse
Is it getting wet??

akira02rex said:
Is it getting wet??
Click to expand...
Click to collapse
Lol nope. The shark fishing trip was the third boot loop for me.

Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App

landrian18 said:
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Interesting that you got it to work once, because I have the same issue you do but have never gotten it to boot past the Google animation. Wonder if there was a Rom that we flashed that caused the issue to begin with. I have tried so many JB roms now that I don't know which one I started with, but I think it was Vicous JB since that was the first one I saw released at the time. Just wish someone out there that has had our symptoms and finally got past them could tell us what they did.

Well at least I'm not the only having this issue. Hopefully someone can shed some light.

@nothingshocking
Its the [email protected]_jelly jb rom that I flash when this things all starts.. the vicious rom works for me since v1 to v3.. I'm trying other rom because of grs issue in vicious at that time. I'm not afraid to flash or be in softbrick because I know I can always use my backup and restore or there's toolkit just in case ,but this thing I'm really puzzled this is so weird.. I can flash any ics rom but not the jb rom.. someone suggest me to use jb bootloader and I did and same results.. I'm really hoping that someone of our bright dev can look in to this and help us..
Sent from my Galaxy Nexus using XDA Premium App

Same exact problem here. I would boot loop anytime I rebooted or powered down my phone. Today, I flashed the new clockwork recovery (v.6.0.0.?). So of course I rebooted my phone to see what it looked like. Well it looked cool but when I went to reboot my phone it was just stuck on the google screen. Wouldn't boot at all. Tried wiping data/cache/dalvik cache/format system/format cache/fix permission. Got desperate cuz nothing worked. Backups wouldn't restore. Got "installation aborted error". Finally did like the op and flashed stock image. Works fine now. Just seems like my phone doesn't like the JB at all. Has done this on every JB I flashed.
Sent from my Galaxy Nexus using xda premium

had this happen on my cdma toroplus any ics rom will install and work fine but no jelly bean rom will boot past the bootanimation

Maybe it has to do with hardware version? For those of you with problems like me, are you on a launch Nexus? That is what I have.
My SKU is SCHI515MSV
I am not sure if they redesigned the hardware at some time.

[Q] Have to Factory Reset every 24-48 hours - this is getting old!

Got a Nexus about a week and a half ago...flashed almost every JB ROM out there now (Paranoid, Bamf, AOSP variants, AOKP 7-29, SlimBean, etc.) but all of them do not boot after the third or fourth reboot.
Here's the scenario:
I flash phone to stock using mskip's GNex Toolkit
Copy a custom JB ROM over to the sdcard
Boot into Touch Recovery 6.0.1.0 (Format /system, Factory data/cache wipe, Dalvik cache wipe)
Install ROM zip from SD card (then 7-26 JB Gapps if ROM requires it)
Reboot then use Franco Kernel app to get latest 384mhz kernel zip file, and flash it in CWM Touch Recovery
Reboot, then 24-48 hours later (even after going through a few more reboots) the phone will not get past the Google boot text/lock icon. It just stays on that screen forever. I wait an average of 5-10 minutes each time, and even waited 15-20 minutes a few times. I then have to start back over at STEP 1 and do this all over again and re-set up everything.
Here are my list of non-system Apps - any of these problematic?
3rd party apps:
ROM Toolbox Pro
Google Voice
Google Wallet
Bible (YouVersion)
Bank Of America
SMS Backup+
Temple Run
Facebook
Touchdown (Exchange mail app)
AdFree
Franco Kernel app
I know ROM Toolbox Pro has a lot of modification tools, but all I use is the boot animation changer. The phone boots three or four times after I change that, so I know that isn't it. I am getting jaded and tired of having to use mskip's GNex Toolkit to factory reset my phone every 48 hours. At this point I am so exhausted...I love the AOKP JB ROM the best, but cannot run it for more than a day or so before I HAVE to factory rest to get past the Google screen.
FYI - Once I get into the stuck state, I have tried everything - wipe system/data/cache/dalvik, reinstall from CWM, try different ROMs, try to restore backups, try Fix Permissions - but I never get past the Google screen until I reset to stock and lose everything. Is it JB? Do I have to resort to using only custom-ICS ROMs on this phone for now?

1. Don't use toolkits
2. Return the device to stock to see if the problem persists. If so, it may be a hardware issue. Also, wipe the SD card.
It may actually be the boot logo changer. I suggest sticking to the stock kernel for a few days and not changing the boot logo, to see how things go.
Sent from my Galaxy Nexus using Tapatalk 2

infazzdar said:
1. Don't use toolkits
2. Return the device to stock to see if the problem persists. If so, it may be a hardware issue. Also, wipe the SD card.
It may actually be the boot logo changer. I suggest sticking to the stock kernel for a few days and not changing the boot logo, to see how things go.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The only wait I know how to return to stock is via mskip's toolkit. Is there a more "official" way to do it?
Once I do get back to stock I will flash just AOKP JB, with no ROM Toolbox Pro installed, no boot animation changes and no Franco kernel.

crobs808 said:
The only wait I know how to return to stock is via mskip's toolkit. Is there a more "official" way to do it?
Once I do get back to stock I will flash just AOKP JB, with no ROM Toolbox Pro installed, no boot animation changes and no Franco kernel.
Click to expand...
Click to collapse
Here, return to stock. Without toolkit, easy step-by-step.
Edit: Just noticed that you won't need it easy, I guess. But anyway, it's perfectly working. (;

Odin
You will find links to factory images. Download and flash. Sorry if I can't be more specific at this point but I'm running out. Surely the people here will help you with more info
http://www.theandroidsoul.com/update-galaxy-nexus-to-android-4-0-4-using-odindownload-mode/
Sent from my Galaxy Nexus using xda app-developers app

Thanks both of you. I saw the Odin method, and the superboot method, and am going to try to do the superboot as it looks more simplistic just for time sake...I wanna go to bed, but need my $500 alarm clock to work...
-edit-
Excellent! The steps from HERE for Windows worked perfectly. there's room for improvement though, as I had to make my own batch file/commands and could not just copy verbatim since the sample steps were for a different model...I feel a guide coming on, lol.

Well, here we are, the next day and after a reboot my phone is stuck at the Google screen....yet again. Originally I was excited to switch from the Bionic, but now I am starting to regret it.

crobs808 said:
Thanks both of you. I saw the Odin method, and the superboot method, and am going to try to do the superboot as it looks more simplistic just for time sake...I wanna go to bed, but need my $500 alarm clock to work...
-edit-
Excellent! The steps from HERE for Windows worked perfectly. there's room for improvement though, as I had to make my own batch file/commands and could not just copy verbatim since the sample steps were for a different model...I feel a guide coming on, lol.
Click to expand...
Click to collapse
I have made a more detailed step-by-step. Look at the "flash" link in my signature.
crobs808 said:
Well, here we are, the next day and after a reboot my phone is stuck at the Google screen....yet again. Originally I was excited to switch from the Bionic, but now I am starting to regret it.
Click to expand...
Click to collapse
Flash back to stock, do not flash cwm 6, do not flash a different kernel (use stock), do not install any root apps. Now see if you are having issues.
Sent from my Galaxy Nexus using Tapatalk 2

I'm fine now. I made my own 'return to stock' exe file for the toro (VZW Galaxy Nexus) that does everything I need automatically. It's only 209MB so I'll just keep it on my Google Drive and have it wherever I may be when the occasion arises.
Thanks. The same ROMs I was having problems with before are not causing issues now. I was even able to flash CWM Touch v6.0.1.0 and the Franco kernel and still OK after multiple reboots

crobs808 said:
I'm fine now. I made my own 'return to stock' exe file for the toro (VZW Galaxy Nexus) that does everything I need automatically. It's only 209MB so I'll just keep it on my Google Drive and have it wherever I may be when the occasion arises.
Thanks. The same ROMs I was having problems with before are not causing issues now. I was even able to flash CWM Touch v6.0.1.0 and the Franco kernel and still OK after multiple reboots
Click to expand...
Click to collapse
Whew, congrats! Your situation made me cringe! :victory:

It makes me wonder. I've been using mskip's toolkit to return to stock previously, which works, but once I want to flash a custom ROM, it'd go belly up after a few reboots. So far, I've done about 10 reboots on AOKP JB, that I loaded after running my stock reset script and have had no problems.
I have not compared my code to mskip's, but I cannot imagine of being vastly different.

crobs808 said:
I'm fine now. I made my own 'return to stock' exe file for the toro (VZW Galaxy Nexus) that does everything I need automatically. It's only 209MB so I'll just keep it on my Google Drive and have it wherever I may be when the occasion arises.
Thanks. The same ROMs I was having problems with before are not causing issues now. I was even able to flash CWM Touch v6.0.1.0 and the Franco kernel and still OK after multiple reboots
Click to expand...
Click to collapse
So.. sorry for my crappy knowledge on some of this, if I understand correctly flashing jb and rebooting after multiple times caused a boot loop or stuck in the splash screen "Google".
You did what that makes it so its not boot looping?
I'm getting a nexus Tuesday and I'd rather avoid this issue since it will be toro "vzn". Any advice?
bOx Stash - https://www.box.com/shared/d8a46b7252c38069deb1

Do you have a VZW Nexus (toro)? I can post my EXE if so.

crobs808 said:
Do you have a VZW Nexus (toro)? I can post my EXE if so.
Click to expand...
Click to collapse
Yes, but can I ask what the exe. Does? Forgive me as the nexus will be my second android and its kind of new territory in rooting.
Using a Rooted HTC Droid Incredible at the moment.
And as you said, this supposedly fixed your jb boot loop issue correct? I was thinking of using Tecfanatic's root method as it seems everyone is using Mskips which "I'm positive is giving people jb issues" although I may be wrong.
bOx Stash - https://www.box.com/shared/d8a46b7252c38069deb1

Just to be clear, the script I made is not a rooting tool. It just takes your VZW Nexus (toro) from any state it is in and reverts the ROM back to factory stock (except for re-locking the bootloader, if it is unlocked)).
This is dependent upon having the fastboot-windows.exe and supplemental img/zip files, but here are the commands I used (I have removed all instructional text, wait and pause code):
Code:
fastboot-windows flash bootloader bootloader-toro-primela03.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-toro-i515.fc05.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-mysid-imm76k.zip
If you do not want to make a fancy batch file, then just install he drivers, put your phone in USB mode, attach it, then run each of those commands one at a time. You'll need to get the supplemental files first of course.
-edit-
FYI - For rooting I use mskip's Galaxy Nexus Toolkit. You can find it HERE.

crobs808 said:
Just to be clear, the script I made is not a rooting tool. It just takes your VZW Nexus (toro) from any state it is in and reverts the ROM back to factory stock (except for re-locking the bootloader, if it is unlocked)).
This is dependent upon having the fastboot-windows.exe and supplemental img/zip files, but here are the commands I used (I have removed all instructional text, wait and pause code):
Code:
fastboot-windows flash bootloader bootloader-toro-primela03.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-toro-i515.fc05.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-mysid-imm76k.zip
If you do not want to make a fancy batch file, then just install he drivers, put your phone in USB mode, attach it, then run each of those commands one at a time. You'll need to get the supplemental files first of course.
-edit-
FYI - For rooting I use mskip's Galaxy Nexus Toolkit. You can find it HERE.
Click to expand...
Click to collapse
Thanks man!
bOx Stash - https://www.box.com/shared/d8a46b7252c38069deb1

Why not use TWRP 2.3.1.1?

So,
I used BreakDroid to get a TWRP on my fire and then installed twa_priv's ROM on it and I'm enjoying Jelly Bean. I first tried the 0804 build and then updated to 1202. I started running into Sleeps of Death and so I backed down to 1127. Still having SOD's I installed the SoftLocker tool to deactivate deep sleep and things seem to work just fine. The only issues I've found is 1) sometimes when doing a google search, with NOW that I can't click on any results for a number of seconds and 2) I've had trouble posting replies or threads to this site. Other than that, things work very well and I'm extremely impressed. Now, I noticed that I'm actually running TWRP 2.3.1.1 since that is what BreakDroid installed. I backed up the stock rooted ROM with that so I was wondering, what problems would I run into. I did some searching around here but didn't find anything definitive.
Just curious if I should downgrade or not. If I do, from what I've read, I might not be able to use my stock backup which might be a problem if I ever want to go back.
Thoughts?
thanks peterb

You should certainly downgrade because how it wipes is broken best wait till that is fixed.

Ah OK, so wipes are clean then? Is downgrading done thru fastboot? How about my stock coup, is that usable with older versions? Is 2.2.1 OK?
Thanks peterb
Sent from my Galaxy Nexus using xda app-developers app

Transfer this zip to your sdcard and flash it in recovery then reboot do not extract it http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 make sure to thank Tera Tike for providing it. Your stock backup will still be fine. When you reflash Sgt7 or upgrade reflash gapps then wipe dalvik and cache this should clear up any problems with G Now. I'm using jb-20121011-signed.zip on the same ROM most recent build works perfect.

OK so I downloaded that zip and moved it to the sdcard. Should I flash it with my current recovery or with fastboot or does it matter?
Thanks peterb
Sent from my Galaxy Nexus using xda app-developers app

It totally matters this is intended to be flashed only in recovery the other way will break your recovery or brick you. Never fastboot flash a zip file.

Thepooch said:
It totally matters this is intended to be flashed only in recovery the other way will break your recovery or brick you. Never fastboot flash a zip file.
Click to expand...
Click to collapse
OK, thanks! Will do that tonight and then apply the 1210 image. Also, is the wipe issue the only problem with 2.3.1.1? I ask because I could use fastboot to erase cache and userdata (it's been a while since I did phones so my memory is rusty) and that would essentially net me a factory reset, right? I don't recall ever being able to use fastboot to erase the dalvik-cache so I'm thinking that might be a unique thing to recovery.
I will say that this recovery is really a step forward from what I remember using on a couple of ION phones years ago.
thanks peterb

Third post down kinfauns explains the fastboot erase commands most eloquently http://forum.xda-developers.com/showthread.php?t=1552547 if you so desire personally recoveries that work correctly is the safest approach. 2.3.1.1 has an adb sideload feature that could be handy but I have never tested it. Other than that I don't believe it it has anything extra that 2.2.2.1 doesn't.