yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] SanzaBlancoAkA2C:
Yes. I downloaded the drivers and unzipped them into a folder I called Nexus. Then I downloaded the image and extracted that using 7-zip and placed them into the Nexus folder as well. I opened the command prompt for that specific folder by right clicking on it while holding shift. From there I typed in fastboot devices and it gave me that message. What should be on the screen of my device right now?
[Samsung Galaxy Nexus] efrant:
Not the drivers. The attachment to the first post that contains the fastboot.exe file. That file needs to be in the same directory as your where you opened your command prompt.
[Samsung Galaxy Nexus] SanzaBlancoAkA2C:
No I haven't. I'll look for the fastboot.exe post now.
[Samsung Galaxy Nexus] efrant:
Re-read step C2...
[Samsung Galaxy Nexus] gunner1937:
return to stock

My GN got the JB through the OTA (JB 4.1.1. with XXLF1 and JRO03C).

I unlocked the boatloader and root.

I would like to unroot and keep the unlock.

Following your guide part D, if I apply 9,11, 12, 13, and 15 will it be enough to replace ClockworkMod (6.0.1.0) by the stock recovery and unroot the phone?
[Samsung Galaxy Nexus] efrant:
Yes.

P.S. I just noticed that a skipped over 14 in the numbering. Oops. :o I will fix it later.
[Samsung Galaxy Nexus] lada2107:
Just turn it ON and try

:)
[Samsung Galaxy Nexus] gunner1937:
Thank you very much, sir:highfive:.

I also skipped 14:laugh:but none of my data and applications have disappeared:)

In a similar situation with a Nexus 7 , in your opinion, could I use your guide?
[Samsung Galaxy Nexus] efrant:
Although I haven't really had a chance to look at the Nexus 7, but yes, the procedure should be identical (using the Nexus 7 images instead of course).
[Samsung Galaxy Nexus] billsan101:
I did the flash to yakju, everything works superb, thanks OP.

ONE question/comment though; it seemed like when taking pictures on the old 4.0.X, i can take many quick pictures by taking the button fast, and now in 4.1.1 it seems like it wants to focus before every picture (making it slower). Is this normal?
[Samsung Galaxy Nexus] msavic6:
Yes its normal, it gives the pictures better quality too.
[Samsung Galaxy Nexus] billsan101:
Cool thanks bud!
[Samsung Galaxy Nexus] hp13:
woow... i just flashed all that manually.. feels so great. works like charm. i love this post. Thank You.
[Samsung Galaxy Nexus] mayurjango:
To everyone facing any of the below problems:

- Getting error: (Status 7) Installation aborted while flashing the Android 4.1.1 OTA update

- Unable to update to yakju (encountering errors)

- Device stuck in boot loop or at the Google logo (soft brick)

Here is an easiest and 100% working way to "Change Galaxy Nexus from Yakjuxw (Non-Yakju) to Android 4.1.1 Jelly Bean Yakju/Takju" using Nexus Root Toolkit by WugFresh.

Note: This method will Flash stock 4.1.1 on your device and will unroot it/ remove ClockworkMod Recovery. Also, make sure to backup everything on your device before proceeding as it'll be completely wiped.
[Samsung Galaxy Nexus] efrant:
Note to all who try the information in the quoted post: I have been saying for quite a while now that I do NOT support the use of toolkits. That was the reason I created this thread, i.e., for instructional purposes. Please do not post issues related to toolkits in this thread. Posts in this thread should be related to issues regarding the method described in the first post.

As is mentioned in the first post, this method is to flash the latest version of yakju/takju/mysid manually, i.e., WITHOUT the use of any scripts/toolkits/etc.
[Samsung Galaxy Nexus] onlynexus:
What are the cons of a toolkit? I am looking for the safest way to flash jb on my yakjuzs 4.0.4 .

I only recall flashing Once before on my nexus one and I remember it as an easy experience. Must have been gingerbread that I flashed since I wouldn't risk it for small update. Near the end of my nexus one life I decided to root and after doing so successfully kept on tinkering and ended up bricking it. Been traumatized since lol
[Samsung Galaxy Nexus] efrant:
Here is a brief, non-exhaustive list of cons:

1) You don't learn anything using a toolkit or 1-click solution;

2) You have no idea what that toolkit is doing;

3) If something messes up, you have no idea what messed up;

4) There have been numerous reports of toolkits flashing the wrong images, particularly the wrong stock recovery image;

5) There have been reports of toolkits showing IMM76K as a toro device, when it could actually be a toro or maguro device;

6) http://xdaforums.com/showpost.php?p=2031989&postcount=45

7) http://xdaforums.com/showthread.php?t=1469909

8) I could keep going, but I'll leave it there. Bottom line is the point in #6 above.
[Samsung Galaxy Nexus] Zepius:
no. just no.

this post has nothing to do with the thread. plus toolkits are just bad.
[Samsung Galaxy Nexus] hp13:
If few commands does the trick then why risk your device with toolkit unless you are absolutely unsure of typing ...
[Samsung Galaxy Nexus] efrant:
It looks like a link to his own site. Needed some publicity I guess.
[Samsung Galaxy Nexus] onlynexus:
I'll follow the xda how to when I get home tonight
[Samsung Galaxy Nexus] GRS10:
Very quick question: will the Android SDK drivers for fastbook and adb work with this method? Or will I have to grab the drivers listed in the OP?

Update1: Just checked my devices using adb devices. Nothing listed. Looks like I'll have to install this driver!
[Samsung Galaxy Nexus] onlynexus:
Here goes...I guess the hard part is these drivers

---------- Post added at 08:54 PM ---------- Previous post was at 08:40 PM ----------

after installing the drivers my phone stayed frozen with android lying down and chest door looking thing open ..says start at top and seems to point aarow at power button but nothing happens.. im going to pull the battery
[Samsung Galaxy Nexus] onlynexus:
success!! :)

Aside from a few hiccups I did it!!! was a little worried when the command on step d5 was not going thru but it seems after closing the command window and reopening it it fixes the problem, accidentally discovered it the first time but when the radio would not load as well I closed it and reopened the command window and voila command went thru no problem!!

Minutes after being with phone recieved OTA update for jelly bean!!!!!!

Really thankful for this magnificent thread!
[Samsung Galaxy Nexus] 1stHTCphone:
Just want to post back and tell you guys that the service depot replaced component part; PBA; mainboard, power key PCB and PCB w/ i/o & mic... Blah.. whatever... now my phone works.. LOL

I am so happy that they fixed my phone under warranty while my bootloader was unlock & rooted.

Back to business =)

:good::good::good:
[Samsung Galaxy Nexus] ddragman:
I'm having out of the box nexus with android 4.0.1 with yakjuxw build. Will it be OK if I take 4.1.1 yakju image and flash it or do I have to first update nexus to yakjuxw 4.0.4 an then flash yakju 4.0.4 image and then flash yakju 4.1.1?
[Samsung Galaxy Nexus] segv11:
Read the OP: "You can easily convert ANY GSM/HSPA (i.e., maguro) device to stock yakju (or takju) from any non-yakju build (yakjuxw, yakjuxs, yakjuux, yakjusc, yakjuzs, yakjudv, yakjukr and yakjujp)."

Follow the methods in the first post, NOT the second post, to flash stock JRO03C (4.1.1) yakju (or takju if you prefer) over your current build. You should back up your current build first, in case you want to return it to "stock" condition for your country.
[Samsung Galaxy Nexus] ddragman:
@segv11 thanks

Just asking to be sure:good:
[Samsung Galaxy Nexus] mayurjango:
Seems you've not gone through that post. Doesn't it describes how to convert a non-yakju device to yakju/takju?, which I guess is certainly related to this thread.

---------- Post added at 02:50 PM ---------- Previous post was at 02:41 PM ----------

Hey efrant, sorry to say but I feel you aren't happy with the success of Wug's toolkit. If you kindly go through the comments section of that post, then you'll probably notice that a lot of users have successfully and easily updated to yakju 4.1.1 using described process performed via toolkit. Btw.. I don't need any publicity, I just posted the link to help n00bs who are new to this flashing task and find it utterly complicated. You can remove my post anytime if you like. *I Respect XDA and its community*
[Samsung Galaxy Nexus] efrant:
Yes, but it relates to a toolkit, so this should have been posted in a toolkit thread.

As is mentioned in many places, particularly in the "The dangers of tool kits and one click root methods" thread http://xdaforums.com/showthread.php?p=21936493 is that n00bs do NOT learn anything by using a toolkit, and it breeds another generation of ignorant users. This is why I don't like toolkits. If people know what they are doing, fine let them use a toolkit -- but you will see that those who understand won't use a toolkit anyway.

Don't forget that this site is not about fixing/modding people's phones -- it's about helping people LEARN how to fix and mod their phones. Big difference. If that isn't clear, have a look at the "what matters" link http://xdaforums.com/showpost.php?p=2031989&postcount=45 in my signature posted by a senior mod a few years back.
[Samsung Galaxy Nexus] mayurjango:
Thanks for the reply. I got your point. I think we should leave it to users to opt for a way they find more convenient. :)
[Samsung Galaxy Nexus] efrant:
I guess you didn't get my point. :) It's not about convenience at all. It's about learning.

I could write up a script and package it up in a GUI with one button: "flash yakju" which would do this entire method in one push of a button. But I won't. Because it goes against everything I believe in and what XDA is about.
[Samsung Galaxy Nexus] mayurjango:
Yes, I got your point. Learning something is way better than blindly following a guide to accomplish a task, without knowing what's actually happening in back end. :)
[Samsung Galaxy Nexus] efrant:
Correct. That is why people should not blindly follow my guide. I tried to split out each step so nothing is done via a script, so that people can try to understand the process.
[Samsung Galaxy Nexus] Blink01:
Thank you so much for your guide, I'm still in the process of installing the drivers. Just don't understand why my drivers don't seem to work, and why the guide mentioned we should install the driver for ADB twice...

---------- Post added at 08:01 PM ---------- Previous post was at 07:45 PM ----------

Thanks so much for your guide, I'm a newbie trying to learn the ropes here, need some extra help...

Basically I have a softbricked GNex, never unlocked/ rooted/ flasehed etc.

It is now in bootloop, and I can't boot Android at all.

I notice the guide telling us to install the 2 drivers in 2 different methods -- one in Android boot with USB debug enabled, another in fastboot mode.

I can complete the latter but having problems with the first.

Seems I can't carry out the first step since I cannot boot Android at all at current state, so I have no way to access settings to enable USB debug.

Any idea how to sort out my problems?

Thanks again and sorry if my question seems dumb :cowboy:
[Samsung Galaxy Nexus] efrant:
The GNex has two interfaces: fastboot and adb. There is a driver for each one (included in the same package linked in the first post). We only use fastboot for this guide, so only the fastboot driver needs to be installed for the purposes of this guide. There is NO need for the adb driver to do the steps in this guide -- I was just pointing out, as you will likely need it for doing other things (unrelated to this guide).
[Samsung Galaxy Nexus] jmcdonald58:
I will add that you are doing a fine job and your patience is remarkable I use this thread as a reference whenever I am fiddling around the Gnex is an amazing device (my 1st nexus) I have learned much from following this thread Keep up the good work and Thanks for giving me a better understanding-:)
[Samsung Galaxy Nexus] Blink01:
It's Ok now Efrant, I managed to proceed to step D and has unlocked my GNex.

Now my real problem is that after fastboot reboot, I am unable to flash the bootloader of my choice.

It says " FAILED <command write failed<Too many Links>>"

and my GNex will also show a glitchy/shaky bootloader image.

What do you think is the problem?

Thanks so much for your help :D
[Samsung Galaxy Nexus] efrant:
That sound like a hardware problem to me...
[Samsung Galaxy Nexus] franciscojunior:
Hi, efrant!

Would you mind to confirm if your root procedures (with the mentioned files) in your signature still applies to 4.1.1?

I noticed that your post about root was updated recently, so I'm assuming it is working ok, but I just wanted to confirm with you first.

Thanks in advance.

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] efrant:
Yes, it should be fine.
[Samsung Galaxy Nexus] chewping:
HELP !

i'm getting fail error on part D9 > fastboot flash system system.img

it's say

sending 'system' <396675 KB>. . .

FAILED (remote: exceed buffer size (0x16400000))

finished. total time: 0.006s

what did i do wrong?
[Samsung Galaxy Nexus] efrant:
Close the command prompt window and reopen it and try the command again.
[Samsung Galaxy Nexus] chrone:
Dear Efrant,

Sorry to bother you with the private message, I somehow didn't read that you didn't answer technical question in PM.

So here's my question regarding root. Where can I find the official superuser/root package for galaxy nexus?

Can I get it from Google Android SDK tools? or is it only available through ClockWorkMod?

Up until now I'm still hesitate to root an android phone. hehe :D Thanks in advance!

Kind regards,

/chrone
[Samsung Galaxy Nexus] Zepius:
there is no official root from google.

use this: http://xdaforums.com/showpost.php?p=26328017&postcount=123
[Samsung Galaxy Nexus] chewping:
it's still failed, can i skipped this?
[Samsung Galaxy Nexus] efrant:
No, that is one step you cannot skip. Try changing USB cables or try a different port.
[Samsung Galaxy Nexus] tulinoobnihit:
OTA Failure

Hi there,

My phone was yakjujp build. So i manually installed yakju 4.0.4 factory image using the procedure that was mentioned here.

Then I got a notification for 4.1 OTA update. The update downloads well but during installation it stops and the green android with the exclamation mark shows up. When i restart the phone it runs on the 4.0.4 and then it shows no further update. Could you please tell me what is wrong.
[Samsung Galaxy Nexus] hoagieh:
Did you change anything bootloader/radio since following his step? From what I read everything has to be stock.
[Samsung Galaxy Nexus] tulinoobnihit:
Nope nothing at all. No changes.
[Samsung Galaxy Nexus] Zepius:
did you follow all the steps including flashing the radio and bootloader?
[Samsung Galaxy Nexus] tulinoobnihit:
No I skipped the ones that said "not for noobs"
[Samsung Galaxy Nexus] efrant:
Steps say: NOT optional for n00bs...

Go back and do the steps you skipped.
[Samsung Galaxy Nexus] tulinoobnihit:
Ok sorry. Did everything. Now it is stuck on the 'Google' screen.
[Samsung Galaxy Nexus] efrant:
Something must have messed up. Backup anything you want to keep to your PC, and start from the beginning: flash all the images, and this time use the JRO03C images.
[Samsung Galaxy Nexus] chrone:
thanks dude, much appreciated. :)

forgot to ask you, is it safe to enter the bootloader (pushed the volume up+down and power) while still connected to PC via USB cable??

i somehow skipped your part to enter the bootloader first then plug it in to PC later, this noon.

i was able to flash all the img step by step as your instruction in respective order without any error, though.

tonight, after several power cycle (on and off), i found that my nexus was not able to power on, so i plugged the battery off and placed it back on, and voila, it turned on!

should i reflash it again with the correct order on entering the bootloader then plug it in to PC via USB cable?
[Samsung Galaxy Nexus] efrant:
Yes it is safe to boot into fastboot mode while connected to the PC. No need to do the steps again.

I doubt your problem is related to this.
[Samsung Galaxy Nexus] tulinoobnihit:
Thank you so much efrant. 4.1.1. still got stuck. But I installed 4.0.4 correctly again and then did the OTA update for 4.1.1.

Appreciate your patience to answer each and every question.

Thank you. :)
[Samsung Galaxy Nexus] chrone:
Oh ok then. Hope it won't experience the cold boot issue ever. Thanks again! :)
[Samsung Galaxy Nexus] Thorgoth:
i really can't understand...

basic steps...

flashing bootloader..rebooting..

flashing radio..rebooting..

flashing system...dead..

restarted pc and phone..

tried to flash the system...it worked now..

rebooted phone...stucked in google logo...

did i just soft bricked it?? :(((

but system got through....hmmmm
[Samsung Galaxy Nexus] efrant:
Ok, if you managed to flash the system and boot partitions, then you are fine.

Close the command prompt window and open a new one just to be safe.

Type this:

fastboot erase userdata

fastboot erase cache

fastboot reboot-bootloader

fastboot reboot

Your device should boot after that. It may take a while for the first boot... maybe ~5 mins?
[Samsung Galaxy Nexus] Thorgoth:
i just don;t know what is wrong...tho i did use the system.img from jb and i waited more that 10 mins i could not wake up my phone..then i reflashed everything from imm76i image (bootloader/radio/system/userdata/boot/recovery) and it worked... so i guess the jro03c image has something do to...tho i did not get any error other than buffer size once..and still i was able to fastboot flash the jro03c system.img in the phone...

update..

i re-download the jb image extracted it again restarted pc/phone and re-flashed all 6 .img files...

finaly i have jb in this nexus too!!!
[Samsung Galaxy Nexus] efrant:
Glad to hear it. For future reference, you should always verify either the MD5 or SHA1 hash to make sure that it downloaded correctly before attempting to flash.
[Samsung Galaxy Nexus] MersauX:
Followed the guide. Everything works!
[Samsung Galaxy Nexus] Androidin':
Quick question efrant.

If I'm already on 4.1.1 takju JRO03C (got there via flashing to 4.1 and then by updating to 4.1.1 via CWM) and want to install 4.1.1 takju JRO03C fresh, just follow all the steps in post 1? I'm having problems getting any kind of GPS lock and want to try this in the hope it'll solve my problem.
[Samsung Galaxy Nexus] efrant:
Yes, follow the steps to flash the images. If you want, you can try skipping flashing the userdata image which may save your data. But if you want a full wipe, flash it as well.
[Samsung Galaxy Nexus] franciscojunior:
I think you could try flashing the 4.0.4 radio and see if you get better gps locks. I noticed that my gps precision was worse when I updated to 4.1.1 and did that. Now I think my gps is a little bit better.

I hope it helps.

Enviado de meu Galaxy Nexus usando o Tapatalk 2
[Samsung Galaxy Nexus] Anthonymcp:
Instead of showing up ad "Android 1.0" as shown in your screenshot, mine is showing up as "Galaxy". When I try to update the driver, I get a screen that reads "Windows could not find driver software for your device". What am I missing?

---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------

Instead of showing up as "Android 1.0" as shown in your screenshot, mine is showing up as "Galaxy". When I try to update the driver, I get a screen that reads "Windows could not find driver software for your device". What am I missing?
[Samsung Galaxy Nexus] efrant:
That's because either you already installed a driver, or Windows installed it for you automatically. You need to uninstall them, and prevent Windows from installing them.
[Samsung Galaxy Nexus] jobe1785:
Can't get signal

I did every step, and it worked fine, but when I started the phone again is not getting any data connection. I can't make phone calls, and I don't have 3G or 4G. What did I do worng? What can I do?
[Samsung Galaxy Nexus] bourne-nolonger:
More then likely it isn't picking up the device properly. Your device showing up as "galaxy nexus" is correct.

For the installation of the other two drivers you need to do two additional steps. First, with the phone booted normally, enable USB debugging and plug it into your computer. Windows will pick up and new device and if you've disabled Windows from trying to install drivers automatically you will see that Windows just says it can't install it. At this point you can install your own drivers. Then for the second driver you have to boot your phone in fastboot.

Follow efrants instructions line for line and all will work!
[Samsung Galaxy Nexus] bourne-nolonger:
Although I don't like the idea - since enabling Google's "location service" I get GPS locks in a few seconds as opposed to minutes or not at all. But not really sure this topic is right for this thread so I'll leave it at that

Cheeeeeeers :D
[Samsung Galaxy Nexus] dejavecu:
I'm a bit confused. So for verizon users this guide is to only return to stock? Can I use a jb image from one of the other countries

and just push the cdma radios or will that not work?
[Samsung Galaxy Nexus] efrant:
There is no JB factory image available for Verizon devices yet, so you cannot flash JB using this guide. You need to look in the Dev section and grab a custom JB ROM for toro devices.
[Samsung Galaxy Nexus] Baalzamon:
I just bought a second hand GNex with Scandinavian ICS 4.0.4 (probably yakjuxw), but when every time I tried flashing the stock yakju JB I got the Exceed Buffer Size-error message. So instead I flashed my GNex to yakju ICS 4.0.4 and tried to update OTA. When the device reboots to install JB, it crashes after about 20%. I removed and reinserted the battery and now I'm back at 4.0.4. Has anyone experienced anything like this?

EDIT: Forget it, I tried going into Recovery which crashed, and therefore updated it. After that, flashing the system.img file wasn't a problem anymore.
[Samsung Galaxy Nexus] efrant:
Most likely:

-You have an anti-virus software that is messing something up.

-Bad USB cable.

-Need to change USB ports on your PC.

-Did not check MD5 of images when you downloaded to make sure they were not corrupt.

Less likely:

-Hardware issue, i.e., faulty NAND.
[Samsung Galaxy Nexus] kyokeun1234:
Hey thanks alot for this simple instruction :D

If I want to unroot, do I have to flash the whole zip file (stock image) to lose root?

Also rooting doesn't stop the OTAs, do they?
[Samsung Galaxy Nexus] efrant:
No, to "unroot" all you have to do is remove the two files that were copied over when you flashed the zip.

And no, root does not affect OTA updates.
[Samsung Galaxy Nexus] kyokeun1234:
LOL that's simple :D

Also I flashed SuperSU that is compatible with Jelly bean and there is unroot option. If I use that, would it do the same thing?
[Samsung Galaxy Nexus] efrant:
Not entirely sure, as it probably depends on how you installed it, whether through the market or some CWM-flashable zip.
[Samsung Galaxy Nexus] kyokeun1234:
I did cwm zip flash
[Samsung Galaxy Nexus] Urimagination:
just did this for the first time on my day old phone, how long does the first reboot take?

I can also see a unlock symbol which im sure just means your boot loader is unlocked?
[Samsung Galaxy Nexus] msavic6:
First boot should take 2-7 minutes while the OS is being prepped. The unlock symbol means the boot loader is unlocked.
[Samsung Galaxy Nexus] Urimagination:
thanks, how long should i wait before I need to start to freak out? 15-20 minutes?

all i still have on the screen is the google symbol an the unlock symbol

---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------

also once i typed in the reboot thing at the end, once i saw everything looked done i unplugged the phone, was the phone meant to be plugged in?
[Samsung Galaxy Nexus] efrant:
It shouldn't take more than 5-10 mins. If it's not working, just reflash the images again.
[Samsung Galaxy Nexus] Urimagination:
whats the best way to turn it off without bricking it. holding the power button doesn't do anything
[Samsung Galaxy Nexus] efrant:
As long as you are not flashing it, just pull the battery.