Develop Bugs

[HOW-TO] Update stock Galaxy Nexus to Android 4.1 Jelly Bean guide by Camazza

There seems to be a lot of information thrown all around the place regarding the Jelly Bean update. But there are a lot of users who have not rooted, flashed or updated their phone outside of OTA cycle before and all of this is rather intimidating.
With Jelly Bean, there seems to be issues with different phones, radios, firmware and ROM's and it's just all a huge mess. While people who have done it before possibly have no problems, a lot of users have not. The threads that have shared ROM images have not been clear about how the update works, unless you have done it many times before.
Could someone please write a simple step-by-step guide how to update stock yakju 4.0.4 Galaxy Nexus to Android 4.1 Jelly Bean?
I am sure a lot of people would appreciate this, me included! Thanks!
EDIT: The post below is the recommended guide, thank Camazza for posting!

I'll try since I updated my yakju some hours ago. Here's what I did, but should work with every ROM.
1) Download and install the Galaxy Nexus Toolkit. It's awesome.
2) Download the ROM
2b) Put the ROM zip file on your phone wherever you like
3) Turn off your phone, press Volume UP + DOWN and then press power, you should then be in bootloader mode.
4) Connect your phone
5) If driver installation fails, open the Toolkit and choose option 1 (Install Drivers), then reconnect.
6) Open the Toolkit, choose whatever rom you have (I still have to find out if it really makes a difference for the options we're going to use)
7) Select Option 3 and confirm from Phone (WILL WIPE DATA) <-- NOT NECESSARY IF YOU ARE ALREADY UNLOCKED
8) When in bootloader mode again, choose option 9 and then Option 1
9) You should see CWM. Choose "install zip from sdcard"
10) Select the file you sent to the phone on step 2b
11) Wait.
12) Wipe data/factory reset
13) Reboot
YAY! You now have Android 4.1 Jellybean
This guide was written mainly for Stock users, as more advanced users probably already know how to flash a ROM.
Please correct any errors I may have made.

Camazza said:
I'll try since I updated my yakju some hours ago. Here's what I did, but should work with every ROM.
1) Download and install the Galaxy Nexus Toolkit. It's awesome.
2) Download the ROM
2b) Put the ROM zip file on your phone wherever you like
3) Turn off your phone, press Volume UP + DOWN and then press power, you should then be in bootloader mode.
4) Connect your phone
5) If driver installation fails, open the Toolkit and choose option 1 (Install Drivers), then reconnect.
6) Open the Toolkit, choose whatever rom you have (I still have to find out if it really makes a difference for the options we're going to use)
7) Select Option 3 and confirm from Phone (WILL WIPE DATA) <-- NOT NECESSARY IF YOU ARE ALREADY UNLOCKED
8) When in bootloader mode again, choose option 9 and then Option 1
9) You should see CWM. Choose "install zip from sdcard"
10) Select the file you sent to the phone on step 2b
11) Wait.
12) Wipe data/factory reset
13) Reboot
YAY! You now have Android 4.1 Jellybean
This guide was written mainly for Stock users, as more advanced users probably already know how to flash a ROM.
Please correct any errors I may have made.
Click to expand...
Click to collapse
This is one of a way, but i encourage OP to read up on ADB and fastboot and try to do it the manual way.

Mach3.2 said:
This is one of a way, but i encourage OP to read up on ADB and fastboot and try to do it the manual way.
Click to expand...
Click to collapse
Agreed. Familiarity with ADB is vital if you're going to root your device. Because if you can't access the bootloader or recovery, ADB is your only hope.
Sent from my Galaxy Nexus using xda premium

I'd just like to call out OP on this thread for sort of shady use of [HOW-TO] thread-title tag.
You asked a question, you didn't provide a howto. Don't pretend you did
Not trying to be an asshole or anything, but if enough people are inaccurate in their use of tags, searching the forums later just becomes impossible and every thread needs to get repeated on a weekly basis.

CanesDrew said:
Agreed. Familiarity with ADB is vital if you're going to root your device. Because if you can't access the bootloader or recovery, ADB is your only hope.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The Jellybean update gave me an opportunity to root the manual way.
I admit i used the toolkit to root, that was when i know nuts, frankly it's not hard, give it a few days, you will roughly know what to do.

Camazza said:
I'll try since I updated my yakju some hours ago. Here's what I did, but should work with every ROM.
1) Download and install the Galaxy Nexus Toolkit. It's awesome.
2) Download the ROM
2b) Put the ROM zip file on your phone wherever you like
3) Turn off your phone, press Volume UP + DOWN and then press power, you should then be in bootloader mode.
4) Connect your phone
5) If driver installation fails, open the Toolkit and choose option 1 (Install Drivers), then reconnect.
6) Open the Toolkit, choose whatever rom you have (I still have to find out if it really makes a difference for the options we're going to use)
7) Select Option 3 and confirm from Phone (WILL WIPE DATA) <-- NOT NECESSARY IF YOU ARE ALREADY UNLOCKED
8) When in bootloader mode again, choose option 9 and then Option 1
9) You should see CWM. Choose "install zip from sdcard"
10) Select the file you sent to the phone on step 2b
11) Wait.
12) Wipe data/factory reset
13) Reboot
YAY! You now have Android 4.1 Jellybean
This guide was written mainly for Stock users, as more advanced users probably already know how to flash a ROM.
Please correct any errors I may have made.
Click to expand...
Click to collapse
But what was all this talk about radio firmwares and whatnot? You don't mention anything regarding them?

josteink said:
I'd just like to call out OP on this thread for sort of shady use of [HOW-TO] thread-title tag.
You asked a question, you didn't provide a howto. Don't pretend you did
Not trying to be an asshole or anything, but if enough people are inaccurate in their use of tags, searching the forums later just becomes impossible and every thread needs to get repeated on a weekly basis.
Click to expand...
Click to collapse
I left the tag, but edited it and referred to Camazza's post

Look, OP asked for a simple way. That's a simple way. People looking for an easy guide won't be running custom roms (as I wrote in the how-to).
I understand the importance of being able to use ADB (and I know my way around it), but that's not the aim of this guide.
---------- Post added at 02:13 PM ---------- Previous post was at 02:06 PM ----------
kristovaher said:
There seems to be a lot of information thrown all around the place regarding the Jelly Bean update. But there are a lot of users who have not rooted, flashed or updated their phone outside of OTA cycle before and all of this is rather intimidating.
With Jelly Bean, there seems to be issues with different phones, radios, firmware and ROM's and it's just all a huge mess. While people who have done it before possibly have no problems, a lot of users have not. The threads that have shared ROM images have not been clear about how the update works, unless you have done it many times before.
Could someone please write a simple step-by-step guide how to update stock yakju 4.0.4 Galaxy Nexus to Android 4.1 Jelly Bean?
I am sure a lot of people would appreciate this, me included! Thanks!
EDIT: The post below is the recommended guide, thank Camazza for posting!
Click to expand...
Click to collapse
Glad I could be of help!

Camazza said:
Look, OP asked for a simple way. That's a simple way. People looking for an easy guide won't be running custom roms (as I wrote in the how-to).
I understand the importance of being able to use ADB (and I know my way around it), but that's not the aim of this guide.
---------- Post added at 02:13 PM ---------- Previous post was at 02:06 PM ----------
Glad I could be of help!
Click to expand...
Click to collapse
Exactly, I don't want to meddle with custom ROM's and whatnot. I just want the latest version of Android from Google on my Nexus phone and so do majority of others I believe.
But this radio thing is still confusing to me, what are all the other threads talking about? I don't need to update some firmware separately to this?

kristovaher said:
Exactly, I don't want to meddle with custom ROM's and whatnot. I just want the latest version of Android from Google on my Nexus phone and so do majority of others I believe.
But this radio thing is still confusing to me, what are all the other threads talking about? I don't need to update some firmware separately to this?
Click to expand...
Click to collapse
It's all in there. You should have the latest LF1 radio when flashing this.

kristovaher said:
Exactly, I don't want to meddle with custom ROM's and whatnot. I just want the latest version of Android from Google on my Nexus phone and so do majority of others I believe.
But this radio thing is still confusing to me, what are all the other threads talking about? I don't need to update some firmware separately to this?
Click to expand...
Click to collapse
You don't have to flash the new radio. There is a new radio available, but it isn't necessary to flash it. If you do want to, you can either flash it with fastboot or there may be a CWM flashable .zip available.

Camazza said:
It's all in there. You should have the latest LF1 radio when flashing this.
Click to expand...
Click to collapse
Oh thank you so much! I'm a tech-guy myself and have developed for Android, but the whole rooting-flashing-updating business paired with the fear of bricking have kept me away from knowing anything more than Android app development.
This is really appreciated, I've done this before (when 4.0.4 was released), I just got very confused by the multiple threads and posts that talk about extra steps and radios.

Camazza said:
I'll try since I updated my yakju some hours ago. Here's what I did, but should work with every ROM.
1) Download and install the Galaxy Nexus Toolkit. It's awesome.
2) Download the ROM
2b) Put the ROM zip file on your phone wherever you like
3) Turn off your phone, press Volume UP + DOWN and then press power, you should then be in bootloader mode.
4) Connect your phone
5) If driver installation fails, open the Toolkit and choose option 1 (Install Drivers), then reconnect.
6) Open the Toolkit, choose whatever rom you have (I still have to find out if it really makes a difference for the options we're going to use)
7) Select Option 3 and confirm from Phone (WILL WIPE DATA) <-- NOT NECESSARY IF YOU ARE ALREADY UNLOCKED
8) When in bootloader mode again, choose option 9 and then Option 1
9) You should see CWM. Choose "install zip from sdcard"
10) Select the file you sent to the phone on step 2b
11) Wait.
12) Wipe data/factory reset
13) Reboot
YAY! You now have Android 4.1 Jellybean
This guide was written mainly for Stock users, as more advanced users probably already know how to flash a ROM.
Please correct any errors I may have made.
Click to expand...
Click to collapse
Can I just use fastboot to boot into CWM and apply the linked Rom via "install zip from sdcard"?

I got it updated and can confirm than the posted step by step does indeed work, no problems so far. I was slightly worried while the device was booting up very slowly, but other than that everything seems perfect!

Did you try it with a yakjuxw? Or the Google version? Dont know if i have to change from yakjuxw

MrSvedberg said:
Did you try it with a yakjuxw? Or the Google version? Dont know if i have to change from yakjuxw
Click to expand...
Click to collapse
I had the regular yakju myself, don't know about yakjuxw.

MoosDiagramm said:
Can I just use fastboot to boot into CWM and apply the linked Rom via "install zip from sdcard"?
Click to expand...
Click to collapse
If you are already running CWM of coure you can. In the end this tutorial is meant just to get into CWM and flash the zip file.

In order to keep things organized we'll be linking to everything from a single thread. Please refer there for more information about updating.
http://forum.xda-developers.com/showthread.php?t=1737899

Problems With GNex

Hi all, I have some problems on my gnex.
This happens because I think I have deleted some system files.
1st problem: when I install a rom at the first boot the phone gives me this error: "the application speech engine Google has locked in an unusual way"
2nd problem: when I open camera or gallery the phone gives me this error: "no external storage available"
3rd problem: sometimes the phone gives me the error: "youtube application has locked in an unusual way"
Ok...there are too much problems...just a question now: I want to reset ALL my gnex, I want to delete ALL the files there are in it. I can't do it flashing a new rom or formatting system from recovery. How can I do?
Thanks!

need more details
Without some more details on what ROM you are having these issues with, which recovery you're using, ... it's kind of difficult to help out... That aside, when you flash a new ROM, be sure to first do a full wipe through the recovery. I've flashed my phones numerous times over the years and every single time I had a problem at first boot it was because I didn't do the full wipe. Also, carefully read the instructions posted on the first (and second & third if any) thread, usually the dev explains carefully which steps are necessary to succeed.

Gunthy` said:
Without some more details on what ROM you are having these issues with, which recovery you're using, ... it's kind of difficult to help out... That aside, when you flash a new ROM, be sure to first do a full wipe through the recovery. I've flashed my phones numerous times over the years and every single time I had a problem at first boot it was because I didn't do the full wipe. Also, carefully read the instructions posted on the first (and second & third if any) thread, usually the dev explains carefully which steps are necessary to succeed.
Click to expand...
Click to collapse
I have these problems with all roms, recovery cwm non touch and i always do a wipe before flashing roms
Now I just want to know how to delete every file in my phone and come back to original

Frenix27 said:
I have these problems with all roms, recovery cwm non touch and i always do a wipe before flashing roms
Now I just want to know how to delete every file in my phone and come back to original
Click to expand...
Click to collapse
That's odd... Maybe something wrong with the device itself in that case... To go back to stock, the easiest way by far is the GNex Toolkit. It has an option to download the Google image & lets you easily flash it.

Gunthy` said:
That's odd... Maybe something wrong with the device itself in that case... To go back to stock, the easiest way by far is the GNex Toolkit. It has an option to download the Google image & lets you easily flash it.
Click to expand...
Click to collapse
And via gnex toolkit, with this option, all system files will be deleted?

Frenix27 said:
And via gnex toolkit, with this option, all system files will be deleted?
Click to expand...
Click to collapse
Well that depends what you mean by that... What it will do is flash the stock ROM that is made by Google onto your device. It will replace the current installed system with the stock one. It will be like when you first got the phone, with the default ICS installed. Obviously a device without a system installed on it would be useless, unless you're looking for a new expensive paper weight of course .
If you still have the same problems after that, I'd recommend returning it to the shop you got it from for a repair/refund. Don't forget to re-lock it though if you decide to go that way .

The problem is that with root explorer i see two folder about storage: sdcard and storage>sdcard0. I think i have deleted some files in these folders. Is there a way to reset their files?

/sdcard & /storage/sdcard0 both refer to the same, namely the internal memory. No way to recover deleted data though. What exactly did you delete??

Frenix27 said:
The problem is that with root explorer i see two folder about storage: sdcard and storage>sdcard0. I think i have deleted some files in these folders. Is there a way to reset their files?
Click to expand...
Click to collapse
Flashing the stock image will return all your files to factory. You don't need to delete anything.
Sent from my LGL55C using Tapatalk 2

Gunthy` said:
That's odd... Maybe something wrong with the device itself in that case... To go back to stock, the easiest way by far is the GNex Toolkit. It has an option to download the Google image & lets you easily flash it.
Click to expand...
Click to collapse
Use odin or fastboot. Kits are easier but i trust fastboot above all. And do a backup before flashing anything...tag way can restore. Then factory wipe, then format cache, then go to advanced and format dalvik, THEN flash the ROM
Android is upgrading...

JediNinjafication said:
Use odin or fastboot. Kits are easier but i trust fastboot above all. And do a backup before flashing anything...tag way can restore. Then factory wipe, then format cache, then go to advanced and format dalvik, THEN flash the ROM
Android is upgrading...
Click to expand...
Click to collapse
The toolkit uses fastboot... It just presents you with scripted menus and composes the correct command depending on your choices. Makes it a lot easier to get stuff done without having to remember all the different commands .

Are you sure? So i have to flash the stock image?

Without more info on what exactly you deleted it's hard to say. Flashing stock should work for restoring the phone though .

Gunthy` said:
The toolkit uses fastboot... It just presents you with scripted menus and composes the correct command depending on your choices. Makes it a lot easier to get stuff done without having to remember all the different commands .
Click to expand...
Click to collapse
Ahhh. I dunno, I like it. And I usually watch a qbking77 video while I do it.
Android is upgrading...

JediNinjafication said:
Ahhh. I dunno, I like it. And I usually watch a qbking77 video while I do it.
Android is upgrading...
Click to expand...
Click to collapse
Ok so the last question: i remember i had imm76i when i bought the phone. I have to flash that? Where can I find?

Just use the toolkit I linked to earlier. You can make it download the latest google stock image and flash that one.

Gunthy` said:
Just use the toolkit I linked to earlier. You can make it download the latest google stock image and flash that one.
Click to expand...
Click to collapse
ok ty

[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

[Q] error installing cyanogenmod

Hi guys. Before you bash me saying I did not search, trust me I did.
Goal:
I am trying to install cyanogenmod 10 M2 following this guide: oh well, I guess I can't post URL's. But the guide is a wiki from cyanogenmod and is called "Galaxy Nexus (GSM): Full Update Guide"
wiki.cyanogenmodDOTCOM/wiki/Galaxy_Nexus_%28GSM%29:_Full_Update_Guide
When I get to the second command which is to enter the CW menu: fastboot boot boot.img
Problem: My phone gets stuck at the Google logo and my PC says that the driver failed to install.
Here's what I have tried doing and what I installed:
Android SDK + Google USB driver are installed
Universal Naked Driver is installed
I tried re downloading all the files and restarting
I tried changing computers
I even tried FORMATTING my computer and installing a fresh copy of Windows 7 64 bit.
My phone is showing bootloader in the device manager like it should. Everything is FINE and working except for that part. All my drivers are correctly installed on my PC. I have been trying to solve this for exactly 5 hours.
So my question is: how do I solve this ?
Thanks in advance
cheers

You don't have to manually flash the boot.img, just flash the ROM through CWM

Redownload the ROM, check md5 hash, flash away.
Restore the nandroid of your previous working state btw.

cyanogenmod's thread, FIRST POST
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Click to expand...
Click to collapse

EddyOS said:
You don't have to manually flash the boot.img, just flash the ROM through CWM
Click to expand...
Click to collapse
OK but I'm trying to get in the CWM menu. That's not working. How do I enter that menu on my phone ?
Also I don't want to root my phone.

Installing CM10 WILL root the phone as it's a custom ROM
Super n00b...

EddyOS said:
Installing CM10 WILL root the phone as it's a custom ROM
Super n00b...
Click to expand...
Click to collapse
lmao

Yep. I am a noob. My first android phone....
So I really need your help guys ..
I just learned that I need to root my phone.
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Click to expand...
Click to collapse
Ok so, I need the "instructions are available here" please Or I guess a guide to root my phone and be able to get in the CWM menu....
Ok. EDIT: I understood how it works. I'm doing it now... I'll let you know if something goes wrong. Thanks guys.

Just Google how to flash a new ROM on the Galaxy Nexus - they are plenty of how to guides and videos

ekoloud said:
Yep. I am a noob. My first android phone....
So I really need your help guys ..
I just learned that I need to root my phone.
Ok so, I need the "instructions are available here" please Or I guess a guide to root my phone and be able to get in the CWM menu....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529058

Yeah. Thanks guys. I did it. I guess we all start by being noobs

Np, but you need to refine your search skillz.
Sent from my i9250

Do you lose LTE or other functionality with CM10 on the CDMA GNex?

shizat63 said:
Do you lose LTE or other functionality with CM10 on the CDMA GNex?
Click to expand...
Click to collapse
Dont hijack the thread. It has completed its purpose, and it should be closed.
Sent from my i9250

GNEX frozen at JB startup animation (multicolored X)

Hi, hope my exact issue wasn't discussed after page 10 of the help & troubleshoot forum, anyway my rooted, unlocked cwm recovery stock 4.2 yakju (if I remember well) Samsung GNEX started to behave strangely slower then usual less then a week ago, then a couple of days later I woke up after night battery recharge to the boot up animation which never gave way to the operating system starting up.
After the first moment of despair I tried reading something here and with the use of adb I was able to first see the device and, after backing up via recovery, to pull the files from the phone (backup included). Problem is the 0 folder is very light for all the data and apps that I had, and inside the DCIM folder there's nothing, no trace of the 1k+ picture I shot in the past couple years, only an igc file which should have been in another folder. But strangely enough the backup weights almost 6GB which is consistent with what was inside prior to the crash.
Before attempting the backup I fiddled with recovery and tried to wipe cache, dalvik and fixing permissions, with no apparent results.
So now I'm undecided whether to take the phone to a samsung job centre which will surely wipe all data and possibly find out I have a corrupt memory or partition table, which renders many files and folders unavailable to be adb pulled or to wipe data/restore factory by myself hopying, fingers crossed, that the backup actually saved all my files and that could be restored without hassle. I actually had hoped that, like for the desktop environment, there was the possibility to awake my phone with a linux live or whatever to check if all files were present and downloadable before actually restoring the phone.
Thanks for your interest and help.
https://drive.google.com/file/d/0B8Pbk0TslYN6cm1wWWZydVM2V0k/edit?usp=sharing

Have you tried dirty flashing your rom?
Sent from my Galaxy Nexus using XDA Free mobile app

This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app

berniefranz said:
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app

As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
mrgnex said:
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse

berniefranz said:
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
Click to expand...
Click to collapse
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app

Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
mrgnex said:
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse

berniefranz said:
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
Click to expand...
Click to collapse
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info

Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
ashclepdia said:
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Click to expand...
Click to collapse

small update, I managed to download the correct rom and I tried to adb push the .tar to the device (twice and attempting a third to /sdcard/ /sdcard/clockworkmod/ and now /sdcard/0/Download/) but still haven't been able to spot the uploaded file to choose for dirty flash. adb shows the file as uploaded , but again no sign of it with CWM Recovery. should I try to install TWRP recovery? with the nexus toolkit there is a function to flash a rom, but it says it will wipe the device first, so it's really not the option I was looking for. Another strange behaviour of CWM Recovery, or maybe my phone, inside mounts and storage menu, mount sdcard seems to be not working as it never changes to unmount after you click it. I think my memory went berserk and that's the reason why the phone rebooted and never woke up again. Maybe I'll take to the nearest job center to ascertain the damage...
thanks for all your help
berniefranz said:
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
Click to expand...
Click to collapse

installed TWRP and was able to see to rom.tar uploaded via adb in the download folder, but wasn't able to use to flash as probably both recovery wants .zip and not .tar, so I'll now untar and zip the stock rom and upload it again...
small steps...

had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?

went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
berniefranz said:
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
Click to expand...
Click to collapse

Had to take it to the job center where, it was downgraded to 4.0.4 (have still to check which flavour) fixed something and Wiped everything. When I side about he post mortem backup and the intention to try a restore from there I was give an are you kidding look, it could crash again... sigh.
Anyway thanks everyone that spent some time to try and explain a noob how to try to solve this issue.. Now I've got a new galaxy nexus, so after a little grievance I'll start reading on how to flash a nice rom...
berniefranz said:
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
Click to expand...
Click to collapse