yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] efrant:
Fastboot.exe was not supposed to come with the driver. It is attached in the first post of this thread.

So now you are not getting the unrecognized command error, correct? You are getting the "waiting for device"? That means either your phone is not booted into fastboot mode or your fastboot driver is not installed.
[Samsung Galaxy Nexus] apoorv007:
installation worked

thanks a lot efrant...:)

i was doing a small mistake, i was using the fastboot that i had previously, and off course that was the reason why my device was not detected.

now successfully installed jelly bean update...:D
[Samsung Galaxy Nexus] colomob:
Quick question, how do I have to wait for the phone to start. I have done all the steps and its been like 10 minutes and the phone is still loading. Stuck on the x with colors.
[Samsung Galaxy Nexus] efrant:
It shouldn't take more than 10 minutes. Reboot into fastboot mode and reflash the boot, system and userdata images, and then reboot. Others have reported it not taking the first time.
[Samsung Galaxy Nexus] colomob:
Sorry another question, ( assuming the file names as these )when fast boot the radio, first is fastboot radio radio CDMA.IMG and then the lte radio which would be fastboot radio-cdma lte.IMG ?
[Samsung Galaxy Nexus] efrant:
I believe that is correct. In any case, I don't think fastboot will allow you to flash the wrong one, so if it is not like that, just reverse them.
[Samsung Galaxy Nexus] colomob:
actually i notice something......

fastboot flash radio ( lte radio img)

fastboot flash radio-cdma (cdma radio img )

please verify this. i thinks thats correct now...
[Samsung Galaxy Nexus] efrant:
I can't verify that as I don't know what the original file names are. Try it one way, and if it doesn't work, try it the other way.
[Samsung Galaxy Nexus] colomob:
Update: finally did it!! If anyone needs help PM me. :):thumbup::D
[Samsung Galaxy Nexus] Nirmal80:
Thanks! Easy instructions, quick and effective!

This post was the most easiest to follow and it literally took me 10 minutes to get my Nexus from 4.0.2 to Jelly Bean 4.1.

Thanks a bunch!
[Samsung Galaxy Nexus] afgomar:
R there Any YouTube tutorials for this???
[Samsung Galaxy Nexus] Zepius:
just follow the steps. you really dont need a video.
[Samsung Galaxy Nexus] scarmon25:
Being familiar with flashing images in fast boot this seems super easy to do. I very well may have to try this over the weekend. I am assuming that if for any reason I needed to refer back to the stock Sprint firmware all I would need to do is flash the Sprint images in fastboot as well. I would actually prefer running this over anything else as when Google updates the os we one could just download from that site and get it. Thanks for the tutorial on this.
[Samsung Galaxy Nexus] efrant:
I hope you are not intending on flashing yakju/takju images on a Sprint device...
[Samsung Galaxy Nexus] scarmon25:
Well. I was thinking about it after I read a little more . Based on that response I take it that is a negatory ghost rider.
[Samsung Galaxy Nexus] efrant:
"The pattern is full." :)

yakju/takju are for GSM devices, i.e. maguro devices

mysid is for Verizon devices, i.e., toro devices

mysidpr is for Sprint devices, i.e., toroplus devices
[Samsung Galaxy Nexus] dulko:
Hi there,

I've converted my SGN yakjuxw version to yakju (4.1.1) following your instruction. Everything went fine, I didn't root it and I didn't lock the bootloader. Recently I've noticed data connection loss, I can't use internet, check my emails or facebook. If I turn the phone off and then on, data connection works fine. This happens 2 or 3 times a week. Is this a hardware issue or I made a mistake while converting?

Another thing, when I check buildinfo in Android System Info application it says: radio unknown. Is this OK?

Today I called Samsung tech support, I told them about the data connection loss, they told me to use code: *2767*3855# and if this doesn't work, I should send it back to the store for repair. Is it OK to use this code with bootloader unlocked?

Thank you for your time and help.
[Samsung Galaxy Nexus] efrant:
"radio unknown" is not normal. Reboot into fastboot mode and reflash the XXLF1 radio.
[Samsung Galaxy Nexus] 3rdstring:
In the Android System Info app that's what I get too. Shows my current baseband in about phone
[Samsung Galaxy Nexus] efrant:
Sorry, my mistake. I thought he meant it showed unknown in "About phone"->Baseband
[Samsung Galaxy Nexus] dulko:
I reflashed the radio again, I didn't see your post on time. Any ideas about data connection loss? Is there anything else I can do or should I take it back to the store? What about the reset code *2767*3855#, may I use it?
[Samsung Galaxy Nexus] efrant:
No idea about the connection loss, sorry. And I have no idea what that reset code does either.
[Samsung Galaxy Nexus] dulko:
thanx efrant for quick help
[Samsung Galaxy Nexus] nitzank9:
my device got stuck

i didnt do the recognize part, then i tried to OEM unlock then it got stuck. is it in brick? i also dosnet turn off. should i take out the battery? what do i do?
[Samsung Galaxy Nexus] efrant:
What do you mean it got stuck? Do you still see the bootloader screen? What do you see in your command prompt? If it says waiting for device, that means you did not install the drivers properly.
[Samsung Galaxy Nexus] scarmon25:
Thank you very much for that info. I had planned on reading through the thread before flashing. You saved me a ton of work.
[Samsung Galaxy Nexus] nitzank9:
ok

if i didnt install the drivers properly what do i do?

it doesnt even turn on or off.

should i take out the battery?

i already cancelled the prompt
[Samsung Galaxy Nexus] efrant:
I still don't understand what you did. If you booted your device into fastboot mode, you should see the bootloader screen. The phone should not turn off. If you see the bootloader screen, there is nothing wrong.

Anyway, I suggest you re-read the instructions (twice) from start to finish, and then try again from the beginning.
[Samsung Galaxy Nexus] nitzank9:
am i able to bring the device to its regular state?

i still see the bootloader screen, just nothing happens
[Samsung Galaxy Nexus] efrant:
Then nothing happened. Just use the volume keys until you see "reboot" and then push the power button to select reboot.

There is nothing wrong.
[Samsung Galaxy Nexus] nitzank9:
nothing happens when i use the volume keys...

nothing moves on the screen...
[Samsung Galaxy Nexus] efrant:
I guess just pull the battery.
[Samsung Galaxy Nexus] nitzank9:
thank you very much, it worked
[Samsung Galaxy Nexus] Androidin':
Quick question efrant

Does doing the steps in the post #1 wipe the dalvik cache? Reason I ask is that I'm currently on takju and can't get any type of satellite lock so I'm gonna give yakju a go in the hope it will solve my problem ( I may be grasping at straws but what the hell) and some posts I read that people had some success by wiping the dalvik cache with a new rom install.
[Samsung Galaxy Nexus] efrant:
Yeah, I think you are probably grasping at straws, but yes, it will wipe dalvik. (The dalvik cache is stored in /data, so flashing the userdata image will certainly wipe it.) But an easier way to do it would be to use cwm - - it has a wipe dalvik option...
[Samsung Galaxy Nexus] Tomaxda:
Canadian JB released

Regarding the "Return to stock" aspect of this thread...

A few days ago, Samsung released JB for the Canadian GNex's.

I had already updated my Canadian GNex from 'yakjuux' to 'takju' - as did many Canadian GNex owners - using the Galaxy Nexus Toolkit.

But my GNex is dropping calls so I need to send it in for service, and want to put Canadian firmware back on it. So, rather then put the original 4.0.1 on it, I would like to put the Canadian JB released today.

So, are there any issues with 'side-ways' firmware upgrading - from takju to yakjuux? I assume this is no different then any other flashing but unlike upgrading I will probably lose my data. I will wait for the new firmware to find its way online, and then use the GNex Toolkit again, same as I did to switch to takju.

(BTW, the call dropping was happening on the original firmware too - not caused by using takju firmware on yakjuux.)
[Samsung Galaxy Nexus] efrant:
There is a CWM backup of the stock yakjuux in this thread. You can flash that in recovery. There is no requirement to use any toolkit (ever... :) ).
[Samsung Galaxy Nexus] Ummr:
Noob to moderate - Thank you erfant

Hello erfant,

few weeks ago I simply wanted to upgrade from my very stock Nexus S to Galaxy Nexus, and due some country restrictions my only way to get it was to sign a contract with Vodafone EG and pay $656 to get a carrier locked GNex :/

but I managed to pay a lot less than that and got it from aboard...

problem was when unsealed the package and started the Gnex for first time, I was not sure what is wrong, to discover later that it came with a "Pre-Released developing android version" No Gapps, no connectivity at all!! it couldnt even connect to SIM services! :crying:

And I think its time now to say a loud "THANK YOU" not only for following this helpful thread and managing to install the stock pure Jelly Bean on my Gnex, but also I am very thankful for everything I have learned during the whole process like installing drivers, backing up, being familiar with adb/fastboot commands, unlocking bootloader, rooting and installing custom recovery...

and now I am exploring custom ROMs and lots of other stuff, so thank you again for such a kick start : )
[Samsung Galaxy Nexus] chrone:
Couldn't agree more. I always look for his guidance. As for me, efrant is like gnex rockstar. :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Tomaxda:
Ok. I see (in the other thread) that you are waiting to confirm whether the previously leaked yakjuux JB is the same as the one released in the last few days. I'll wait for the answer to that.

One thing that confuses me a bit is that getRIL tells me I have "XXFL1; UGLH1 (JB; 4.1.1)"? Does my phone have 2 RIL on it?

The ROM I flashed was the standard (from Google site) takju ROM, so why would it includes UGLH1? Isn't UGLH1 the new Canadian RIL?

Or is it just the UGLH1 baseband that is new (my baseband is I9250XXFL1)?
[Samsung Galaxy Nexus] efrant:
Must be someone else. I'm not waiting for any confirmation. I was just waiting for the OTA so that I can post it in the OTA Update thread.

No idea. Don't forget that GetRIL is only as accurate as the info submitted to the devs database. Maybe the XXLF1 RIL and the UGLH1 RIL are the same? Maybe there was a mistake when the dev put in the MD5 hash? Who knows. Just flash whichever RIL you want (there is a link in my sig), and you'll be sure to have the one you flashed.

[/QUOTE]
[Samsung Galaxy Nexus] MitchellOsterlund:
thanks for the guide dude.

but i get past unlocking my phone, and then you say to reboot the bootloader, and it says it "failed.<unknown error>>".

what am I doing wrong? Please help.
[Samsung Galaxy Nexus] efrant:
No idea. Maybe best if you post a screen shot?
[Samsung Galaxy Nexus] Tomaxda:
Ok, I used CMW & fastboot method to flash back to stock. I got the 'yakjuux IMM48' image from here.

After flashing my phone wouldn't boot - had to wipe data (makes sense). Now it boots fine and is on 4.0.4.

Now the only problem remaining is that it isn't seeing any updates - claims my phone is up to date. I'm assuming it doesn't matter which carriers' SIM I put in it, but I have a Bell one now.

I guess I'll wait and try again in a few days - maybe they haven't finished rolling out 4.1.1 to everyone.
[Samsung Galaxy Nexus] efrant:
Why would you flash that build (which is a leak by the way) instead of flashing the the yakjuux JRO03C build that I linked for you?? :confused:

There will not be any updates from the build you flashed to anything newer -- that is a leak, not a release build. The JRO03C build which I pointed you to is not a leak -- it is the ROM that is shipping with new GNex's sold in Canada.
[Samsung Galaxy Nexus] Tomaxda:
Whoops. It sounded like the JRO03C was a leak so I went back to the big list and grabbed the first yakjuux listed - the only one that was a complete update. Figured that would take me back 4.0.1 or 4.0.2 stock, and then I would receive the 'official' yakjuux 4.1.1 update.

Do we know whether the JRO03C image is the same as the 4.1.1 OTA that people received last week?

In any event, I will now flash that image.

Thanks for steering me back in the right direction.

---------- Post added at 10:02 PM ---------- Previous post was at 09:42 PM ----------

Follow up to my previous post.

I flashed using CWM before by pointing CWM to a zip file. With JRO03C you says to un7zip it and put it in sdcard/clockwordmod/backup. When I use fastboot to invoke CWM recovery, I don't see an option to point it to this folder. I must be missing something or maybe you intent quite a different method.

Perhaps I can just take the 7zip you provide, rework it into a .zip, and then follow my fastbook/cwm method?

Most importantly, am I correct in assuming that there is no harm if it takes me a few tries to get it right: if I end up flashing this thing, say 20-30 times in its life, that's not a problem. And as long as I don't do anything too wacky then I'm unlikely to brick it.
[Samsung Galaxy Nexus] efrant:
You unzip it into that directory, and you use the restore menu in cwm, not the flash-update-from-zip menu.

And yeah, no harm in taking 20-30 tries. I :)

By the way, in case you don't have it yet, I would flash the LC03 bootloader first. Link in my signature.
[Samsung Galaxy Nexus] efrant:
Let's try to keep this thread on topic please.

(And you already posted your question in the Jellybean Information sticky - - no need to spam the board.)
[Samsung Galaxy Nexus] Tomaxda:
Glad there is no harm in many tries - looks like I'm going to need it!

I flashed the JRO03C ROM from the other thread, as you described. That worked fine, but I notice that my 'baseband' is still UGLC1, not UGLH1.

I guess that means the baseband must be flashed separately, and I guess baseband is the same thing as radio cause there is a radio download in that thread too (cwm-radio-i9250-uglh1) - so that is what I should flash next.
[Samsung Galaxy Nexus] 3rdstring:
Correct
[Samsung Galaxy Nexus] Tomaxda:
Okay, all done. Now to see whether this helps with the call dropping.

Thanks (mainly to efrant) for all your help!
[Samsung Galaxy Nexus] angel.a:
Thanks, efrant for this very clear guide.

One thing that is not clear to me: Is there any reason not to use the flash_all.sh script that comes in yakju-jro03c-factory-3174c1e5.tgz? Or is it just that the guide is aimed for Windows users?
[Samsung Galaxy Nexus] efrant:
As I mentioned in the first post, I wanted to split out all the steps to the lowest common denominator for instructional purposes, so that people do one step at a time, and actually see what they are doing. This will help people understand the process better and help them in troubleshooting later on if required. Using the script hides a lot of this from the user. , but the script will work fine though.
[Samsung Galaxy Nexus] randomme:
Great work, thanks
[Samsung Galaxy Nexus] J450N79:
Need a little help

Hi efrant,

I have followed your directions to unlock my bootloader successfully. I am now stuck trying to root using your guide. I am probably just too much of a newb but maybe you can help. My issue is around step 5. I type: fastboot boot cwm.img in command prompt but I get cannot load 'cwm.img' error. What am I missing? Bootloader is unlocked. CWM file is renamed to cwm.img and is in the same directory as fastboot.exe. I am sure I missed something obvious or some step but I have read over this many times and my eyes aren't seeing it. If you or anyone else who knows what I missed can help, I would really appreciate it. Thanks :)
[Samsung Galaxy Nexus] efrant:
Is your command prompt showing that you are in the same directory as cwm.img?
[Samsung Galaxy Nexus] J450N79:
Yes.
[Samsung Galaxy Nexus] efrant:
Can you post a screen shot of your command prompt window after you execute these commands, so that I can see the output:

dir

fastboot devices

fastboot boot cwm.img
[Samsung Galaxy Nexus] J450N79:
If I knew how I would :D I think I am in over my head on this. I was the guy using tools like superoneclick and taking for granted that the work was all done for me with my last phone (T-mobile SGS 4G). The bootloader unlocking seemed so easy that I didn't think this would be much of an issue for me.
[Samsung Galaxy Nexus] efrant:
Just type in the commands I mentioned above (hitting enter after each of course :) ) and copy all the text in the command window, and paste it into a post here.
[Samsung Galaxy Nexus] J450N79:
Hopefully this is what you're looking for:

C:\Users\Jason\Downloads\Galaxy Nexus\platform-tools-v19>dir

Volume in drive C has no label.

Volume Serial Number is E698-3961

Directory of C:\Users\Jason\Downloads\Galaxy Nexus\platform-tools-v19

09/17/2012 11:34 AM <DIR> .

09/17/2012 11:34 AM <DIR> ..

09/17/2012 09:25 AM 341,773 adb

09/17/2012 09:25 AM 162,816 adb.exe

09/17/2012 09:25 AM 96,256 AdbWinApi.dll

09/17/2012 09:25 AM 60,928 AdbWinUsbApi.dll

09/17/2012 01:42 AM 674,673 CWM-SuperSU-v0.94.zip

09/17/2012 11:34 AM 5,427,200 cwm.img.img

09/17/2012 09:25 AM 127,435 fastboot

09/17/2012 09:25 AM 70,144 fastboot.exe

8 File(s) 6,961,225 bytes

2 Dir(s) 294,283,329,536 bytes free

C:\Users\Jason\Downloads\Galaxy Nexus\platform-tools-v19>fastboot devices

014E05DE0C013013 fastboot

C:\Users\Jason\Downloads\Galaxy Nexus\platform-tools-v19>fastboot boot cwm.img

cannot load 'cwm.img'

C:\Users\Jason\Downloads\Galaxy Nexus\platform-tools-v19>
[Samsung Galaxy Nexus] efrant:
Based on that, you have cwm named as cwm.img.img not cwm.img :) This is probably because you have "Hide file extensions" turned on in Windows settings.

You can either rename it to cwm.img, or use: fastboot boot cwm.img.img

Done!
[Samsung Galaxy Nexus] J450N79:
I unchecked the hide file extensions and it was named cwm.img.img so I renamed it correctly and still had the same problem. Do I need to close the command prompt, reopen it and go through all of the steps again?
[Samsung Galaxy Nexus] efrant:
You shouldn't, no. Re-type in the commands I mentioned above, and re-paste the output again here.
[Samsung Galaxy Nexus] J450N79:
Well thank you so much for your time! Once I re-entered the commands it worked! :) I really appreciate it! Do you still want me to paste the output again? I think I am good since I booted into cwm and installed the SuperSU zip without issue.
[Samsung Galaxy Nexus] androidsetting.com:
THANK YOU
[Samsung Galaxy Nexus] rslembo:
com.android.phone

First of all, thanks efrant for this tutorial, flashed to yakju last night.

However, I noticed that "com.android.phone has stopped" every time e reboot the phone.

I just get the error message, click "OK", the mobile network seems to reset and everything goes back to normal.

That's damn annoying, could you help me figure this out? (Already tried a factory reset, unsuccessful)

Best regards
[Samsung Galaxy Nexus] efrant:
That is certainly not normal. I would run through the flash procedure again.
[Samsung Galaxy Nexus] rslembo:
The WHOLE procedure or starting at some point?

Never heard of a problem like this before or any way to fix this? :(

edit: When I boot my device in airplane mode, this error only appears when I switch it off back again

Regards
[Samsung Galaxy Nexus] efrant:
It's not like it takes long. Reboot into fastboot mode and re-flash all the images again.

I've never seen that either -- that is why it's best to reflash the images to make sure you are starting with a clean slate.
[Samsung Galaxy Nexus] rslembo:
So I could skip those drivers procedures and etc, going straight to "D. Type in the commands into the command prompt"?

Adding, I've flashed images without the GSM chip on device, should this be the problem or whatever about this?

Regards
[Samsung Galaxy Nexus] efrant:
Yes, part D. Sorry if I wasn't clear.

And leaving the Sim card out is fine.
[Samsung Galaxy Nexus] rslembo:
You made it clear, was just checking if I understood well, thanks.

Going to flash images again, coming back in a few with the results.

edit:

Flashing done.

The error persists, at the very first boot.. googled about this error before and nothing worked.

Whatever, maybe I should just accept this and move on, but it's really annoying lol

(baseband version i9250XXLF1 should I flash another one?)
[Samsung Galaxy Nexus] efrant:
Sorry, I have no other ideas for you.
[Samsung Galaxy Nexus] edgebond:
Amazing post, but will try to do this this week... Hopefully I see myself using jelly bean on my yakjuzs device this week... Thank u again.
[Samsung Galaxy Nexus] Tomaxda:
I believe I saw that same error after flashing my Canadian Galaxy Nexus. I flashed a few different firmwares and can't remember when I got it, but I remember getting that error and being concerned about it, but now I don't see it any more. Sorry that I can't remember more, but maybe it will just go away for you too?
[Samsung Galaxy Nexus] rslembo:
Guys, after several attempts I finally got things working.

Instead of flashing the 4.1.1 directly to the phone, I flashed the 4.0.4, let the device download de JB from Google by itself and everything went normal through de process!

Don't really know why was having problems with de JB version, but no more "com.android.phone has stopped" for a while.

Thanks for the help you gave me :)

Best regards

Additional information: Brazilian Galaxy X (yakjuvs) to International Galaxy Nexus (yakju)
[Samsung Galaxy Nexus] edgebond:
confused need urgent help

what exactly do u mean by

Open a command prompt in the same directory ..

i am on a mac... a noob.. damn confusing

help please
[Samsung Galaxy Nexus] efrant:
A command prompt (called a terminal window in MacOS) is a command line interface where you can type in commands.

I've never used MacOS, so I can't tell you how to open one.

But it has nothing to do with Android - - it's just basic computer usage, so I'm sure if you can't find the answer here, a quick Google search will help you out...
[Samsung Galaxy Nexus] segv11:
Open a finder window. Find Applications on the left. Navigate: Applications > Utilities > Terminal.

You'll get a unix shell. I put Terminal in my Dock because I use it so much.

Sent from my Jelly Beaned "toro" Galaxy Nexus.
[Samsung Galaxy Nexus] :
Easy and helps you learn!

Thank you for the easy to follow and intuitive guide! All I wanted to do was completely re-do my Nexus, this helped me do that and learn some things, thank you again!
[Samsung Galaxy Nexus] Meshal Alharbi:
Dear efrant,

Could I just use flash-all.sh to flash all the files? and why in your guide we need to flash only 3 .img files? what about the rest?
[Samsung Galaxy Nexus] efrant:
http://xdaforums.com/showpost.php?p=31645788&postcount=1136

Not sure what you are talking about. The instructions are for flashing 6 images, not 3...
[Samsung Galaxy Nexus] Meshal Alharbi:
i'm one of the n00bs so i don't get to flash recovery or radios, according to your guide :D

anyways, i would prefer to go with flash-all.sh, so what's the command to use it? i'm on Windows!

I really appreciate your help
[Samsung Galaxy Nexus] 3rdstring:
Those steps are labeled "

NOT

optional for n00bs"
[Samsung Galaxy Nexus] efrant:
If you are asking how to run the script, it should be a good indication to you to avoid it.
[Samsung Galaxy Nexus] Meshal Alharbi:
okay I followed the instructions and now my device is stuck at google logo. Any thoughts?
[Samsung Galaxy Nexus] efrant:
Did you flash all six images?

If not, do so.

If yes, try flashing again the boot system and userdata images and then reboot.
[Samsung Galaxy Nexus] Meshal Alharbi:
Flashed them all, and it's working like a charm now! :good:

Thank you.
[Samsung Galaxy Nexus] segv11:
Since toro (Verizon GNex) users have been getting a Jelly Bean 4.1.1 (JRO03O) OTA, it should come as no surprise that JBQ has posted

Many of you have already noticed this, but JBQ recently posted the associated full factory image files for JRO03O.

https://developers.google.com/android/nexus/images#mysid

Toro users, you can now join the official Jelly Bean party! :)