yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] daidalus:
Very useful guide!! It worked for me!
[Samsung Galaxy Nexus] AayBedi:
Hello sir, I'm a noob but I have a question that I've installed the drivers (both fastboot and simple one) but still there is an error: fastboot command read error 2147483647

I've tried every possible way to install those drivers but my device ain't getting connected on fastboot. It is charging or getting connected as mtp device though :/

I'm sorry for such a noob question :)
[Samsung Galaxy Nexus] chikito-rikiyano:
THanks !

Hi, noob here.

I've just finished and everything is ok.

Had just one issue when flashing system.img getting error: FAILED (remote: Exceed Buffer Size (0x16400000))

But i've flashed the bootloader and everything worked fine after that

Just wanted to say thanks to efrant !
[Samsung Galaxy Nexus] Zepius:
are you in the bootloader or in android?
[Samsung Galaxy Nexus] kiwiBeans:
Quick couple of questions: I fired up my old GSM GNex, which was on 4.1.2, with the intention of wiping everything out, updating it to the latest & greatest 4.3, and re-rooting before I gave the phone to a family member. So I used this guide to do so and it went without a hitch (thank you, OP).

After all was done, I was surprised to boot to the Google logo and the unlocked icon still there. What's more, I can boot into the recovery (CWM 5.5.0.2). Was I mistaken in thinking following the reversion steps from this thread would not only return the phone to stock but would also remove root? If so, I'm glad, because I won't have to root it again.

At this point, is installing SuperSU 1.50 by Chainfire (confirmed to be working for 4.3) all I need to do? Should I upgrade my CWM to a more current version? Thanks for your help!
[Samsung Galaxy Nexus] Zepius:
the unlocked icon means the bootloader is still unlocked (fastboot oem lock to lock it)

if you never flashed the recovery partition, it would never reset to the google factory recovery.

dont confuse root, with unlocked and custom recovery.
[Samsung Galaxy Nexus] efrant:
Unless you specifically executed the "fastboot oem lock" command, your bootloader will remain unlocked.

If you skipped step D12, your CWM will remain untouched. Root, however, will be gone, so you will have to re-flash a superuser zip.

The latest is 1.51, and yes, that is all you need to do.
[Samsung Galaxy Nexus] kiwiBeans:
Thank you, both. As a user who tinkers and is pretty good at just following instructions, some of the logic of what's happening can be misunderstood. I must have just always associated the unlocked icon with root since it's one of the first things you see upon reboot during the root process.

I did not re-lock the bootloader. I did get SU 1.51 from Chainfire's Google Plus posts and flashed it, so I guess I'm all set. If this older version of CWM works with no problems on 4.3 then I will consider everything a success and stop messing about. Thank you, again. The help and advice is greatly appreciated. :good:
[Samsung Galaxy Nexus] Natakranta:
You can instal ROM manager from playstore and use it to update CWM to latest version. Free and painless ;)
[Samsung Galaxy Nexus] rrohanjs:
for the command prompt section, there is flash-all.bat .. so i can type that command right instead of one at a time ?

also op says i need to have 6 files, but 4 of them are in a zip "image-yakju-jwr66v" .. so its ok or do i have to extract it ?

and i found this video showing with flash-all command - http://www.youtube.com/watch?v=uO7HkTrRzwM

so this is the updated method ?
[Samsung Galaxy Nexus] efrant:
Yes, you can use the flash-all script. HOWEVER, as stated in the first post:
[Samsung Galaxy Nexus] kiwiBeans:
I've never done this but was aware of it. Thanks for reminding me. My concern, however, is whether or not it is advisable to update to the latest version of CWM. I saw one blurb from someone that had trouble with the newest CWM and 4.3, so that worried me a little. Aside from that, unless there was something substantial to be gained by upgrading, or a problem with the older version I am running and 4.3, then maybe I'll just sit pretty.
[Samsung Galaxy Nexus] crespo80:
thanks a lot for this simple and very informative guide!

I had problems in returning to stock with the Galaxy Nexus Toolkit (full donate version) but your method was a blast, it took me a couple of minutes and I learnt some things of fastboot that I've always missed!
[Samsung Galaxy Nexus] efrant:
There shouldn't be any issues with the latest CWM. That being said, if the version you are using fulfills your needs, no point in changing.
[Samsung Galaxy Nexus] acras13:
Efrant , thanks for the great guide . Flashed factory 4.3 on my GSM Nexus, no problems that I didn't cause ( kept forgetting to add .img when flashing boot, worked when I pulled my head out). Very glad you took the time to post your guide for those of us who are recreational root users , I'm comfortable with adb , fastboot , flashing etc. because of you and others taking the time to help the community . Now to get the nerve to try to compile a deodexed stock Rom for myself... Thanks again.
[Samsung Galaxy Nexus] DomieMic65:
Just finished upgrading my G.NEX (maguro - yakju, unlocked, rooted, 4.2.2) to 4.3 with total success!!! I am a total noob and I was very anxious not to brick my phone!! The unlocking & rooting was made with toolkit so you understand I guess...

Thank you very much for the analytical and explicative guide!!!!

Two questions!

1. In step 9 didn't complete from the first time. I had something like error msg on the phone (on bootloader mode of-course) and on the computer among other things that I don't remember: "too many links". Anyway after restarting bootloader and waiting some time it did it and was able to move on! Then, on the next steps, on the phone this msg was showing (in blue frame on the down-left side of the screen), but on the computer the procedure was going on OK so I finished it an ... yeahh 4.3 is here!!

I suppose there would be no problem rebooting the bootloader after every step and not only after the first 6. Am I right????

From step 9 and on I just crossed my fingers and went on but thank God no problems occured!! :good:

2. I had a problem with the drivers but after some attempts finally managed to overcome it. I use a quite old Win XP pc where I am right now and the whole driver installation was somehow different than the one described on your link! For sure the fastboot driver installation was ok -as long as I went on with the procedure. I am not sure about the Android driver though!

After setting up, rebooting etc, my phone the computer can't see it and now I can't put any files (music etc..) in!!

I don't want to install Samsung drivers again -if this is possible- . What can I do???

THANX!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Samsung Galaxy Nexus] 3rdstring:
IIRC Win XP needs a newer version of Windows Media Player that includes the MTP drivers, make sure you have the latest WMP. The other options would be something like AirDroid to do tranfers over WiFi orusing a cloud service like Drive.

HTH
[Samsung Galaxy Nexus] kenken3012:
boot takes to long and still booting...

I want to ask regarding to this procedure.

I had already follow all step until it finished.

but when first boot, it takes to long until now, (already around 20 minutes)

is this normal or anything?

i'm still noobs btw and this is my first post in this forum

thanks anyway
[Samsung Galaxy Nexus] ahmadairfan:
Just knew there is flash-all script

Just followed your thread, and get work official 4.3 on my maguro..

But lately after that I just found an easy "flash-all" script haha :silly: fool me

Noob on nexus

Nice thread anyway!
[Samsung Galaxy Nexus] CyberNexii:
It worked!!! Now i have 4.3 on my yakjuux gnex!!!

Mod edit: Do not quote the entire first post...

Thank you SOOO much!!! This worked out awesome!!! Rockin' 4.3 yakju on my yakjuux hardware!!! I did end up using the "Flash-All.sh" script instead of flashing everything manually cuz I'm kind of a noob, but I used everything else in your guide Thanks!!! So happy now :laugh:
[Samsung Galaxy Nexus] etMind:
One of the most descriptive and yet simple guides I have ever had the pleasure to use!

I've got a habit to follow the instructions in a guide to the letter and that is all one needs to do with the OP in this thread. End result is I had zero issues throughout the process while saving lot of time as well. Am already on to my first custom ROM for 4.3!

Thanks a ton OP!

:good:
[Samsung Galaxy Nexus] lucascaldas:
Ok guys i need some help here.

Here is the deal! 2 days after i recived my autoupdate to android 4.3 (yakju),

my gnexus bricked for no especial reason,i was just using my commom apps, and the screen froze,

i had to remove my battery to get out of that, and then i was stucked on google logo, 1 or 2 days later

i could power on it but the phone reboot by itself after less than one minute allways, i tried to wipe data and cache,

but doesn't work

I can go into fastboot and download mode, but im having trouble to put a new rom o on it, via odin

first and also following Efrants guide, via Odin it fails while flashing the system img.

By efrant Guide

i did all the steps to the end (tried to flash 4.3, 4.2.2 and 4.1.2 rooms) but even after that i still got the same android 4.3 that restarts after some seconds.

I was quiet relaxed knowing that if i can go to fastbot or download mode i might be able to solve any problems

but some days have past and i cant solve this. =/
[Samsung Galaxy Nexus] samersh72:
did it take too much time flashing system before fail??

did you mean that if you flash 4.2.2 or 4.1.2, you still on 4.3??

it is something to do with emmc
[Samsung Galaxy Nexus] lucascaldas:
Yes to all the questions.
[Samsung Galaxy Nexus] samersh72:
maybe your emmc and/or board has fried.

if you fastboot oem lock or unlock, does the bootloader lock or unlock?

see this http://xdaforums.com/showthread.php?t=2354641&highlight=emmc
[Samsung Galaxy Nexus] lucascaldas:
My fastboot is unlocked, when i do the lock command it apears as locked on the cel screen but after i restart bootloader it apears as unlocked again.

I'll take a look on this post. tnx

This look like my problem. =/
[Samsung Galaxy Nexus] Zepius:
your emmc is fried.
[Samsung Galaxy Nexus] orangecream:
Thank you OP, this helped me out of a bind. I've been over zealous with my flashing lately with the new 4.3 build out, and needed to go back to a baseline
[Samsung Galaxy Nexus] theboywonder:
Guys I need to return to bone stock AND lock the device as its going back to vzw.

Do I just follow the steps in the first post? Confused on whether to follow first post or second.

I'm currently rooted, rom'd, and have cwm
[Samsung Galaxy Nexus] samersh72:
first post and you will be ok :good:
[Samsung Galaxy Nexus] theboywonder:
Thanks. Reason for my concern is I used wugfresh toolkit to unlock device. Tried using it a few times to re-lock and it wouldn't work.

It had me install drivers and I don't know if I should uninstall those
[Samsung Galaxy Nexus] samersh72:
you can keep installed driver

dont use toolkit.

follow the op exactly and you will be fine.

it is good to learn something :good:
[Samsung Galaxy Nexus] theboywonder:
im having issues already with the drivers. i keep getting this, even after uninstalling multiple times AND disabling windows update!!!!

---------- Post added at 12:56 AM ---------- Previous post was at 12:40 AM ----------

now i have the first driver installed but when im in bootloader, the device isnt showing up as Unknown in Device Manager so I can't get the SECOND driver on there.

UGH!

edit:

so after completing part 1 of the driver install, this is what i see (NOT ADB, like it says i should see)
[Samsung Galaxy Nexus] efrant:
All you need to complete this guide is the bootloader driver (which you managed to install). The ADB driver will only install if either a) you are booted into a custom recovery; or b) you are booted into Android with USB Debugging enabled in settings.
[Samsung Galaxy Nexus] theboywonder:
thank you but the way i got the bootloader driver was by doing what you referenced in b) - which i find strange. it was never ADB driver, it always said bootloader.

also when i open a CMD on my PC and type fastboot devices i get this message:

"Fastboot is not recognized as an internal or external command..."
[Samsung Galaxy Nexus] efrant:
The fastboot.exe file (attached in the first post) needs to be in the same directory as where you opened CMD. For example, if you downloaded fastboot.exe to C:\junk, then your command prompt needs to be in C:\junk. Type cd c:\junk to change directory
[Samsung Galaxy Nexus] theboywonder:
and for this part:

i extracted using 7zip and NO .img files came up.

this is what i have

---------- Post added at 02:04 AM ---------- Previous post was at 01:59 AM ----------

thank you for responding.

im sure i dont have the drivers d/l and installed correctly. now it says in device manager (with usb debugging enabled) that i have ADB interface.

it used to say fastboot. no idea how that changed. my head is spinning and this phone needs to go back to vzw in a day or two.

---------- Post added at 02:10 AM ---------- Previous post was at 02:04 AM ----------

ok so im starting from scratch.

just uinstalled all the drivers and deleted that directory.

im about to install the FIRST DRIVER VIA USB DEBUGGING.

THIS is what i see, instead of Android 1.0 as noted in the guide:

---------- Post added at 02:14 AM ---------- Previous post was at 02:10 AM ----------

im going to post my progress. i apologize im annoying

this is after step 1 of the driver install

---------- Post added at 02:16 AM ---------- Previous post was at 02:14 AM ----------

ok, so now i just booted up into bootloader, but didn't have to do ANYTHING and this is what shows under device manager
[Samsung Galaxy Nexus] efrant:
If you are booted into the bootloader, you will not see the adb driver as being installed. If you are booted into Android with usb debugging enabled, you will not see the fastboot driver as being installed.
[Samsung Galaxy Nexus] theboywonder:
finally got it working!!! thank you all
[Samsung Galaxy Nexus] thienquang07:
m420k

I'm using the m420k - the galaxy nexus for korea, not the i9250. does my device can flash rom for i9250?
[Samsung Galaxy Nexus] WHOneedsSOX:
Thanks for this!
[Samsung Galaxy Nexus] pro_granade:
Thanks,

Thanks a lot for this. :good:
[Samsung Galaxy Nexus] NCguy:
Hi efrant, been a long while since I last posted. Anyhow I installed the stock 4.3 v version when it became available on my GN and rooted all using this thread. I flashed all of the images (5 I think) in the stock zip and did not permanently install a recovery. Everything went smoothly. Today I received the 4.3 Y version ota update. I let it update and it it failed with one of the Android symbols. I rebooted and it booted up fine but with the existing 4.3v, not the ota 4.3y version.

I probably should know better at this point but what probably happen and how should I proceed to install the OTA? I do have a copy of the OTA now.
[Samsung Galaxy Nexus] efrant:
You can do one of two things:

1) Download the JWR66Y factory image (yakju or takju depending on what you want) from Google's Dev page, extract the system.img file from within and flash it using fastboot, as per the first post of this thread. Done.

2) If you are using SuperSU, then you need to "unroot" using SuperSU. Then go to the OTA Update URL's thread, download the JWR66Y-from-JWR66V update (yakju or takju, depending on what you already have on your device), place it in /sdcard, and download CWM or TWRP, reboot into fastboot, boot the recovery (fastboot boot cwm.img), and flash the update. All the instructions are in the OTA Update URL thread.
[Samsung Galaxy Nexus] NCguy:
If I do option #1 would it wipe internal or the sd? Since you wouldn't be flashing userdata it would leave all intact wouldn't it?

BTW, for future reference what caused the OTA to fail?
[Samsung Galaxy Nexus] efrant:
Correct, it would leave all intact (except root, busybox, or whatever else you had installed in /system.

It's Chainfire's SuperSU that is causing it to fail. Read my post here. I edited the update file for the N4 for it to install properly, but I didn't have time to do if for the GNex. In any case, if you "unroot", the update should flash properly.
[Samsung Galaxy Nexus] NCguy:
Thanks for all the help. I read your link on SuperSU and that is in fact what I'm using so that explains it. Does superuser have similar issues?
[Samsung Galaxy Nexus] efrant:
I haven't tried the latest Superuser by Koush yet.
[Samsung Galaxy Nexus] kaushikd:
Even I was also facing the same problem. My ota was giving error on my rooted Gnex. I unrooted it and restarted the phone. After that the ota got installed smoothly. Now I've rooted again.

Tapatalked via Galaxy Nexus!
[Samsung Galaxy Nexus] mikka005:
go back to stock

Hi all,

Please help me, becouse my USB port going wrong (charging problem) and I have to send beack my for for warranty repair.

A used this method to go for yakju edition. The phone was originally a yakjuxw.

After a OTA updatest I was used WugFresh nexus toolkit to root the phone. I think this software changed the recovery to TWRP.

So I have to flash back the system, and recovery. Is there anything else what I have to flash to stock? Where can I find the stock roms? How to flash it?

Really thanks for the help!

Regards,

M.

---------- Post added at 12:54 PM ---------- Previous post was at 12:31 PM ----------

also note, i have the original build backup, followet this guide: http://xdaforums.com/showpost.php?p=21266325&postcount=239&nocache=1&z=5212931896094233

So i have the following files:

boot.img

cache.ext4.tar

data.ext4.tar

nandroid.md5

recovery.img

system.ext4.tar

what shall I do?

Thanks,

M.
[Samsung Galaxy Nexus] efrant:
Boot back into CWM (like in the post you linked to) and instead of backup, restore.
[Samsung Galaxy Nexus] mikka005:
Thanks for the help mate. I'll give a try.

It will restore recovery and everything?

M.
[Samsung Galaxy Nexus] 3rdstring:
If you flash all the image files, yes, it will be completely stock.
[Samsung Galaxy Nexus] NCguy:
I just wanted to close the loop. I was planning on doing this procedure today but in the mean time I noticed that the OTA showed up again automatically and so did an update to superSU. I believe the superSU is version 1.55. Anyway superSU said that it was updated for 4.3 and OTA survival mode. So I backed everything up, ran the superSU update, turned on OTA survival mode, and then ran the 4.3 update OTA that was queued on the phone. It seemed to update without a glitch this time and I retained root after the update.
[Samsung Galaxy Nexus] chikito-rikiyano:
JWR66V to JWR66Y no root/no flash ?

Hi,

Is it possible to update from JWR66V to JWR66Y without root/flashing ? Or some way to get rid of the update all together ?

I've gone from yakjuxw to takju thanks to the guide posted in this thread, which is great, but the latest OTA is starting to get annoying.

I just get "error" after reboot when trying to do the OTA for JWR66Y

Thanks !
[Samsung Galaxy Nexus] efrant:
Just grab the JWR66Y system and boot images and flash them in fastboot as per the instructions in the first post. You will get updated with no data loss if you only flash those 2 images.
[Samsung Galaxy Nexus] OrangePeeled:
Issues flashing the lte radio

Hi all,

I am trying to get my Galaxy Nexus (toro) back to stock. However, every time I try to flash the LTE radio, the device just freezes. When I finally pull the plug, fastboot gives a too many threads error. I have to battery pull the I've let it sit for 30 minutes thinking I just wasn't waiting long enough.

Any thoughts?

Thanks,

Brandon
[Samsung Galaxy Nexus] teh-android-guy:
simple

cant you just use the nexus root toolkit? download the stock .tgz file then it will automatically do everything?:good:
[Samsung Galaxy Nexus] efrant:
If it won't flash using fastboot, it won't flash using a "toolkit". How do you think toolkits flash things? They just automate and hide all the commands so that those who use them stay ignorant.

Have a read of the thread by El Daddy on "The dangers of using toolkits" for additional info.
[Samsung Galaxy Nexus] aparnaaparna85:
Galaxy Nexus-South Korean Variant

Hi Erfant,

I'm new to this process and i want to try ur method to get the future OTA. I went through ur post twice, but still i have some doubts. Please clear me out.

I'm using South Korean variant of GNex (SHW-M420S) for SKTelecom carrier. Following are my phone details :

Variant : yakjukr

Baseband : M420KRLB1

Build Number : JRO03C.M420KRLI1

Android Version : 4.1.1 (Stock)

Doubts:

(1) Can i install 4.3 takju image straightaway, using ur method ?

(2) I have Samsung USB Drivers installed (through Kies) and Fastboot mode recognize my Gnex (after installing Universal Naked Driver 0.7), so can i move forward without any problem ?

(3) I heard, this Gnex radio has been tuned for SKTelecom carrier, so is there any problem flashing 'radio-maguro-i9250xxlj1.img' ?. Actually i'm using this phone in India. Will this baseband work in India? (Current Baseband no issues)

Hoping to hear from you soon.. Thanks in advance

Aparna
[Samsung Galaxy Nexus] efrant:
1) Yes

2) Yes

3) The XXLJ1 should work fine. You can always try out different radios if you'd like (from here).
[Samsung Galaxy Nexus] aparnaaparna85:
Hi Efrant,

Thanks a lot, i converted my Nexus to takju variant using your method, Thanks :good: :D

So I have a couple questions :confused: ...First of all sorry for the "silly" questions, just want to clarify thats it :o

My questions are :

1) Why unlock the boot loader? Any kind of advantages?

2) Difference between Unlock the boot loader and Rooting ?

2) Is it possible to remove the "unlocked booting icon" by re-flashing the old boot loader ? (I assume it came after unlocking the bootloader)

3) If try to re-flash the old bootloader what will happen ?

4) I tried to open Google Wallet. I got some error and after that it got disappeard. How can i get back?

Any advice is highly appreciated. Thanks. Once again Thank you for this great post :good:

Aparna
[Samsung Galaxy Nexus] Natakranta:
HiAparna. You will find answers you your questions 1-4 in other eftant's masterpiece guide here: [REF] efrant's "Android for Galaxy Nexus" 101 & FAQs. It's a must read for any nexus user.

1) with unlocked bootloader you can use fastboot flash and fastboot boot commands. That's what you need to manually flash stock image as you did.

2) see the guide from link above.

3) no. To get rid of the icon you would need to relock bootloader. No point in doing it. Having open bootloader have too many advantages over the icon. I'd advise - learn to live with it :)

4) flashing old bootloader will give you old bootloader not compatible with your new takyu image. The only way I know to remove the unlock icon from booting screen is to relock bottler by fastboot OEM lock command.
[Samsung Galaxy Nexus] aparnaaparna85:
Could you please re-check the link you have mentioned ? Its redirecting me to some other page

And one more doubt, if i re-lock the boot loader using fast-boot OEM lock command , Can i receive future OTA updates from Google ?

Thanks
[Samsung Galaxy Nexus] Natakranta:
Link corrected. Please check now.

Locked / Unlocked bootloader has nothing to do with OTAs.

To get a future OTA (KitKat) you have to be on full stock image (including stock recovery, so no CWM recovery) and NOT rooted.
[Samsung Galaxy Nexus] pilotn:
Once you are rooted you can use BootUnlocker to unlock / lock bootloader when you want.

With locked bootloader rooted stock rom and cwm i always got ota.

And preventing flashing of stock recovery i usually keep root also.
[Samsung Galaxy Nexus] Natakranta:
But was this OTA self installing? Or did you have manually install it on CWM?

OTA topic is full of posts of people complaining how the OTA is not self installing on their phone.
[Samsung Galaxy Nexus] pilotn:
After reboot appear cwn that ask to install unsigned.zip after installation of zip file cwm ask to prevent stock recovery