yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] chubiprince:
Can anyone help me? Fastboot devices is not recognized by the command prompt. Somebody help me this please? :(
[Samsung Galaxy Nexus] efrant:
That is probably because your command prompt is not opened in the same directory as your fastboot.exe file. If fastboot.exe is in C:\me\myjunk, you need to cd c:\me\myjunk
[Samsung Galaxy Nexus] Theshawty:
If one has correctly set up environmental values, you can use fastboot commands from anywhere, directly when launching a CMD process.
[Samsung Galaxy Nexus] Baguett:
No OTA's for Yakjuxw yet? still on 4.0.1 here :(
[Samsung Galaxy Nexus] efrant:
I haven't seen any, but i you do come across a link, please post it here.
[Samsung Galaxy Nexus] aspot72:
go to Market and download GNex updater...
[Samsung Galaxy Nexus] julienrl:
THANK YOU!!!!!!!!!! I have been having such a hard time with this!
[Samsung Galaxy Nexus] AWDSM:
Could someone confirm if you can downgrade say from 4.0.2 to 4.0.1 using these zip files and this method? Or would I need to do a full install to 4.0.1?
[Samsung Galaxy Nexus] luffyp:
I believe the zip files in the first post are incremental updates, i.e. they contain only the updated or new files from the difference 4.0.2 - 4.0.1. So you can't use that to revert to 4.0.1.
[Samsung Galaxy Nexus] efrant:
luffyp is correct. You CANNOT downgrade with these files. The only way to downgrade is to either flash the stock images from Google's image page, or restore nandroid backup of an earlier build.
[Samsung Galaxy Nexus] PaulCayard:
IMHO this thread should be a sticky one.
[Samsung Galaxy Nexus] AWDSM:
Ok, thanks for clarifying that for me guys.
[Samsung Galaxy Nexus] FormelLMS:
Sorry, I was in holidays. This here is the updater script without the assert checks. So I've made the update to the newest version.

http://db.tt/VQk5x6rI

Send from my iphone 5s
[Samsung Galaxy Nexus] kms108:
I think the oficial 4.0.2 ota should come any day now, just today I was playing with a engineering sample and it had this rom in it, in settings/about the phone where it states Galaxy Nexus, it states engineering model in brackets, this is the hong kong model.
[Samsung Galaxy Nexus] efrant:
Do you still have it? Can you tell us the version of the bootloader? Can you dump the bootloader?
[Samsung Galaxy Nexus] jonathan3579:
Just curious but have the updates been paused or are they still rolling out? I'm still on 4.0.1 build ITL41F. (And I have yakju.) I haven't taken the plunge on rooting or any mods on the phone yet. :o
[Samsung Galaxy Nexus] efrant:
Not sure. I think they paused the 4.0.2 update. But if you are on yakju 4.0.1 and you follow the directions in this thread, you'll be on yakju 4.0.2 and you won't be rooted or have any mods. Just pure, stock, official Android OS. :)
[Samsung Galaxy Nexus] David Horn:
Got to say it's quite amusing that the Asus Transformer is now on a newer build of ICS than the Google Nexus. :-)
[Samsung Galaxy Nexus] luffyp:
Just updated to 4.0.2 via the incremental update and used the phone for a day. The battery drain seems good. But I felt that the rom is in general more laggy than 4.0.1 especially when swiping through the widgets list. Anyone else noticing more lags than 4.0.1?

Edit: Ok it looks like I'm not alone http://xdaforums.com/showthread.php?t=1397968
[Samsung Galaxy Nexus] efrant:
Yup, I believe everyone is noticing a bit of lag compared to 4.0.1. However, for me, being able to use Chainfire's StickMount and Google Wallet makes the update worthwhile. As everyone has been say, "I hope the lag gets fixed in the next update." :)
[Samsung Galaxy Nexus] luffyp:
So I heard that GSM phones are now getting OTA for 4.0.2. Will their update.zip be exactly the same as the ones in the first posted? My understanding is that the updates in the first post are taken from people with verizon phones and maybe the GSM variant will be slightly different? I updated to 4.0.2 with .zip from the first post and now I notice that in my gps.conf the server is north-america.pool.ntp.org. Not sure if it was already there before the update though.
[Samsung Galaxy Nexus] efrant:
Yes, it is the same update as the one posted in the first post. THE UPDATES IN THE FIRST POST ARE FOR GSM DEVICES ONLY, NOT FOR VERIZON DEVICES. They were NOT "taken from people with Verizon phones". They were taken from people on GSM devices with the respective builds. Don't forget, not everyone gets the updates at the same time. That is why people who get it first, grab the URL and post it, so that we all can have the update without waiting for it to get pushed to our devices. We could be neighbours with the same device and carrier, but I may get the update hours, days, or even weeks before you.
[Samsung Galaxy Nexus] FormelLMS:
How can we grab ;)
[Samsung Galaxy Nexus] dwd3885:
I bought my phone from the Play Store two weeks ago. I reverted back to the original 4.0.4 system images. However, when I try to update via Method #2, it gives me a status 7 error. Assert Failed: file_getprop...........

I have downloaded the takju OTA from here. What gives?

EDIT: I Think I may have figured it out. Since I went back to stock ICS, I need to flash the original JB preview build before flashing the latest update. I'll re-post here if it works.

Ok I got it. Thanks
[Samsung Galaxy Nexus] tmxda:
Updated radio to XXLA2 but now get an error with build.prop

Where can I find a stock build.prop for 4.0.4?
[Samsung Galaxy Nexus] mattlehrer:
Does anyone have the extracted gzip, ping and ip files from 4.04 so I can fix what Busybox changed?
[Samsung Galaxy Nexus] chubiprince:
I did. First, I downloaded the OTA and then put it in the 'Jelly Bean' folder that I created. Then, with cwm.img. Then, right clicked the jelly bean folder and clicked 'open command prompt here'. There I typed fastboot devices... and it doesnt recognize.

I think I did followed the steps, but it was not working for me. Is there a problem with my laptop or something? I have done this before with ICS 4.0.4 and it was working fine.
[Samsung Galaxy Nexus] efrant:
So you have all of these three things in the same directory:

1) A command prompt open;

2) The fastboot.exe file;

3) cwm.img.

And you have the fastboot driver set up properly, right?
[Samsung Galaxy Nexus] DevilishSerpent:
I'm constantly having an issue where after booting, or flashing cwm, it will say that nothing can be mounted. When the phone restarts, I have to redo set up. Anyone had this issue and knows how to resolve it?
[Samsung Galaxy Nexus] tjex:
I'm having the same issue.

unlocked, rooted, "radio-maguro-i9250xxla2" and "recovery-clockwork-touch-5.8.0.2-maguro".

It did the verification and started to update the system. I then got a "installation aborted" and a system 7.

I bricked the phone and wouldn't load. Currently doing a system recovery image... it's slowwww

Use: yakju JRO03C from IMM76I (but deleted the recovery folder as suggested)

Any ideas?
[Samsung Galaxy Nexus] chubiprince:
The fastboot.exe is missing. So that is what is causing all this trouble. Sorry sir for the inconvenience. And thanks for the time. I'll just have to look up for that file in my previous 4.0.4 update folder. :D
[Samsung Galaxy Nexus] krlosgarces:
Status 7 Error + No reboot

hi, i've got the same "status 7" error. After that i rebooted the phone from CWM menu but now is "freeze" and it does'nt pass the Google booting image. i've tried several times but i can't find the way to reboot the phone at least. I'm really worried about that :( . i'll appreciate your help.

I used "yakju JRO03C from IMM76I" deleting the recovery folder.

My baseband is XXLA2

CWM 6.0.
[Samsung Galaxy Nexus] tjex:
Did you delete the recovery folder?

Did you make a recovery image before updating?
[Samsung Galaxy Nexus] krlosgarces:
-I deleted the recovery folder (as suggested)

-Unfortunately i did'nt :(
[Samsung Galaxy Nexus] shingojr:
If my phone is stock, I just need to put the update file in my sdcard, and go in recovery and select the zip file and update right?
[Samsung Galaxy Nexus] tmxda:
I extracted build.prop from system.img using linuxreader.

New error is

assert_failed: file_getprop() == ....maguro:4.0.4/IMM76I/... || file_getprop() == ...maguro:4.1.1/....
[Samsung Galaxy Nexus] tjex:
You might have to do a system reset, though to be honest I'm not an expert.Hopefully someone here can help you out.

I myself had the same problem with the phone locking on the boot screen. Had to do a img recovery. Would love to know what went wrong
[Samsung Galaxy Nexus] efrant:
No need to do a full restore. As stated in the first post, try re-flashing the update WITHOUT deleting the recovery folder...

As stated in the first post, try re-flashing the update WITHOUT deleting the recovery folder...

What's the full error? Are you sure you are flashing the yakju update on a yakju ROM (or the takju update on a takju ROM) and not mixing them up?
[Samsung Galaxy Nexus] chubiprince:
Sorry, I'm really dumb with this kinds of things. Sirs, after fastboot boot cwm.img. This thing appeared:

Cant find choose zip from sdcard from there.
[Samsung Galaxy Nexus] krlosgarces:
My issue:

set_perm: some changes failed

E:Error in /sdcard/f946a4120eb1.signed-yakju-JRO03C-from-IMM76I. f946a412.zip

(Status 7)

Installation aborted.

When you say "system reset" do you mean a "wipe data / Factory reset" via CWM?
[Samsung Galaxy Nexus] xreflection:
I would double check this, tmxda. I made a similar mistake and it looks like your error is the same as mine that I had when I tried flashing the yakju update onto a takju rom. If you have google wallet, chances are you are running takju (takju = yakju + google wallet from my understanding)
[Samsung Galaxy Nexus] str355:
yes, if your system files are all stock it's that easy :good:
[Samsung Galaxy Nexus] krlosgarces:
Thanks, I thought so, but i'm not an expert, i don't know how to add the "NonDeletedRecoveryFolder" file to the sd card, my phone is "locked" in the boot screen. :(
[Samsung Galaxy Nexus] iurylima:
Done with success (via CWM) on a Brazilian Galaxy X, formerly yakjuvx, converted to yakju!
[Samsung Galaxy Nexus] aygriffith:
I took a picture and attached it...
[Samsung Galaxy Nexus] WakkiPakki:
I am having the same issue :(

I am not able to extract files from the system.img in my windows OS.

Can anyone please provide the stock files from the system/bin/gzip image

Thanks
[Samsung Galaxy Nexus] tjex:
Tried again, kept the recovery folder, all is good now, thank you! :good::good:
[Samsung Galaxy Nexus] tmxda:
Sorry not providing enough info the first time.

I found the recovery log files

Installing: /sdcard/Download/4.1 OTA/original/f946a4120eb1.signed-yakju-JRO03C-from-IMM76I.f946a412.zip
Finding update package...
I:Update location: /sdcard/Download/4.1 OTA/original/f946a4120eb1.signed-yakju-JRO03C-from-IMM76I.f946a412.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
installing samsung updater extensions
Verifying current system...
file "/system/build.prop" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/build.prop", "85c927ec74fd416ae64c60e3047ac0270c1f7cf8", "b0cd51bb45cd47b4822101841a15b76b83f197a8")
assert failed: apply_patch_check("/system/build.prop", "85c927ec74fd416ae64c60e3047ac0270c1f7cf8", "b0cd51bb45cd47b4822101841a15b76b83f197a8")
E:Error in /sdcard/Download/4.1 OTA/original/f946a4120eb1.signed-yakju-JRO03C-from-IMM76I.f946a412.zip
(Status 7)
Installation aborted
[Samsung Galaxy Nexus] tjex:
What radio are you using?
[Samsung Galaxy Nexus] beefyt:
Play Store GNex recieved, 4.0.4 takju IMM76I

Rooted w/ CWM via NexusRootKit.

When trying to flash the zip (both w/ recovery removed, and then redownloaded w/ recovery included)

assert failed: getprop("ro.product.device" == "maguro" || getprop("ro.build.product") == "maguro"

E:Error in .../sdcard/update.zip

(status 7)

Installation Aborted

Searching isn't giving me much help with the above error - any thoughts?
[Samsung Galaxy Nexus] aygriffith:
It was my impression that I was stock YAKJU. The phone was one of the Polish models that came from 1saleaday.com months ago and I immediately changed it to YAKJU. Its there a link to the stock radio that I can flash just to be sure that I have the stock radio? The device is unlocked but not rooted w/ SU.
[Samsung Galaxy Nexus] tjex:
Check to see if you have XXLA2 installed
[Samsung Galaxy Nexus] efrant:
You need to flash the XXLA2 radio before trying to apply the update.
[Samsung Galaxy Nexus] qdhd99:
OR an easy way

Download Fix-Recovery.zip and upload it to phone

1. download OTA zip

2. DO NOT remove recovery

3. reboot in recovery mode

4. flash OTA zip with CWM

5. right after flash root fix zip (otherwise u'll loose root, and u'll need root)

6. flash Fix-Recovery

7. reboot phone

If you were to lose CWM recovery, flash directly from ROM Manager.

Keep the Fix-Recovery.zip file for future OTA updates.
[Samsung Galaxy Nexus] NCguy:
Can someone enlighten me on the MD5' for the posted OTA's? I didn't see them posted on the first post?
[Samsung Galaxy Nexus] efrant:
No need to worry about it. The links are directly from Google, and they won't flash if they are corrupt.

EDIT: the numbers in the file name are the first numbers of the SHA1 hash.
[Samsung Galaxy Nexus] Nikos_s3:
ok, dear efrant my turn :p

stock 4.0.4 , cwm 5.5.0.2, yakju....put the update file in sdcard, chose it via recovery and the following error appeared:

assert failed:apply_patch_check ("/system/bin/gzip"....)

status 7

installation aborted

what is this gzip? I don't remeber changing something...radio is stock 4.0.4 XXLA2 and bootloader too...unlocked bootloader and rooted.

thanks...
[Samsung Galaxy Nexus] NCguy:
Efrant I just successfully updated to 4.1.1 thank you but after I upgraded I installed busybox and I noticed that by default it went to system/bin. Everything is working but kinda concerned about future OTAs. Should I uninstall/reinstall? Not sure how safe that is?
[Samsung Galaxy Nexus] jhuynh:
Do you have busybox installed? It messed up some of your files. I had the same issue. What I ended up doing was download the stock 4.0.4 image from google, extract it. Use fastboot to only flash system.img which will re-write your /system folder with the correct files(you will lose root and need to re-root). Then did the update and it went through fine.
[Samsung Galaxy Nexus] Nikos_s3:
actually yes...I have busybox (ericsson) installed in /system/bin..:worry:

flashing system.img is safe? Do I lose any data? Do I lose cwm? Can I just uninstall busybox?

thanks
[Samsung Galaxy Nexus] jhuynh:
Someone else might be able to better answer this since i'm no expert. I did it and didn't seem to lose anything because I believe your user data is stored elsewhere. All my apps seem to work fine. I don't think it affects cwm either but i'm not sure. Worst case is you just need to reflash cwm after re-rooting.
[Samsung Galaxy Nexus] krlosgarces:
When i try to push the file i get "device not found", the adb drivers are properly installed. when i check adb devices the list is empty. to be honest i think i didn't set the USB debugging on, i know, i'm a fool.. but know i'm stuck on google boot screen after. there's a way to fix this? :(
[Samsung Galaxy Nexus] aygriffith:
That was totally it, I flashed XXLA2 in fastboot and then the JB update in Clockwork and its all good now. As always you guys are the tits!
[Samsung Galaxy Nexus] bagl0312:
Hi Efrant,

I don't understand how re-flashing superSU may fix the access right of the /sdcard partition.

Can you please explain something more ?

However I did some mistake trying to reflashing superSU and my phone was not booting anymore.

So I had to factory reset my phone with fastboot, using a stock IMM76I image,

then I did the update applying the JRO03C with CWM recovery, and finally rooted again my phone (with standard Superuser.apk).

I am now trying to recover my settings and apps from an old backup of Titanium Backup done via Google Drive.

This was a quite painful update :(
[Samsung Galaxy Nexus] Nikos_s3:
dear jhuynh:

I uninstalled busybox( did not fix the problem), then flashed 4.0.4 system.img .

I lost root (probably due to busybox uninstallation) but managed to boot into recovery using power button and volume buttons.

I flashed SU.zip (just to be sure), then the 4.1.1 update(went fine) ....then SU.zip again (:p) and everything seems fine...:)

JB 4.1.1 rooted is here!

million thanks mate...appreciate it..;)

well...just found out that now I have both superuser and superSU...any ideas to get rid of the superuser?
[Samsung Galaxy Nexus] hboyer:
success here - gsm maguro yakju - coming from imm76i

flashed back to stock kernel

flashed back to stock radio

followed instructions method 2 (cwm touch recovery)

rerooted with gnex toolkit 7.4

reflashed cwm touch recovery (using gnex 7.4) after deleting the two files from the system partition as suggested by efrant

thanks to all here!! specifically to efrant & mskip!!
[Samsung Galaxy Nexus] jhuynh:
Quick question for everyone that has updated. In Google Now there were videos that showed you can just say "Google" and then you say the rest of your search. When I just tried it, it doesn't do anything when I say Google. Does this work for anyone else or is it only broken for me?

**edit: I figured it out, it only works under English US
[Samsung Galaxy Nexus] efrant:
I don't know, maybe try uninstalling it. The problem with installing busybox in /system/bin is it overwrites some of the system files. Installing it somewhere else is a better option. You should always check the directory before installing. Not sure if the Stericson installer gives you the option, but I know Busybox Installer does.

Is your device booted in CWM? It needs to be...

And CWM has "USB Debugging" enabled by default -- don't forget, that is a setting in the Android, not on your device...

I was making an assumption that there may have been something wrong with the su binary. I've seen it before where some root apps worked, but others did not after a flash.

The update should not be so painful. Yes, we had some issues with removing the recovery folder, but even if that failed, the ONLY thing that had to be done was to re-flash the untouched update file. That's it.

This is not addressed to you in particular, but the main problem here is that people are so anxious to get the update, they just jump in head first without reading.

I'm almost temped to pull the first post, because there are way too many people just blindly following the instructions there. That was not my intent with this thread. I was hoping that people would go through it and try to understand what each step is doing and what it is for, and maybe get a clearer picture of how updates work, and maybe learn a bit about troubleshooting.

I understand that sometimes thing go wrong, but we shouldn't try to fix them immediately (even though most of us want our phone working immediately). If we took a bit of time to figure out what went wrong before fixing what we think is wrong, in most cases, the fix is quite simple. We have an incredibly open device, and it is extremely difficult to screw it up <== we need to keep this in mind.

And if you don't have the drivers for fastboot and adb set up on your PC, and don't know how to get fastboot and adb to recognize your device, you shouldn't be in this thread -- you should wait for the OTA update to come to you, or you should be in one of the many "toolkit" threads.
[Samsung Galaxy Nexus] krlosgarces:
attached CMD screenshot, i hope you can help me, to be honest i think i didn't set the USB debugging on, i know, i'm a fool.. but know i'm stuck on google boot screen. there's a way to fix this?

i used CWM touch because i already have istalled it.
[Samsung Galaxy Nexus] jhuynh:
add .zip to the end of the filename and it will push the file.
[Samsung Galaxy Nexus] d33k:
First time I tried to update using the takju JRO03C from IMM76I file I got an error while "checking current system." The error was pretty cryptic but I remember seeing "Status 7" and one acronym stood out, RIL. I booted back into ICS, opened GetRIL and noticed that the XXLF1 RIL I had previously flashed wasn't installed anymore and I had an RIL/baseband mismatch. Oddly enough, the XXLF1 RIL wasn't available in the dropdown list until I closed GetRIL and relaunched it. Then two entries for XXLF1 were present... "XXLF1 (JB, 4.1)" and "XXLF1 (JB, 4.1.1)." I chose the "XXLF1 (JB, 4.1.1)" RIL and installed it, I was then able to use fastboot to load CWM bootloader and flash from .zip.

Not sure if anyone else had this issue and already posted, I searched this thread for the keyword RIL but there were no results. So I'm tossing it out there in case it may help someone.
[Samsung Galaxy Nexus] efrant:
Like jhuynh said, add .zip at the end of your file name. Pretty basic stuff...

As well, why are you using the touch recovery? Did I not link the NON-touch recovery in the first post? There are issues with touch recoveries, so please don't use them if you want support from me. And why the hell does someone need touch support in a recovery anyway? A recovery is so that you can go in, backup/restore your data, and flash updates -- you hardly spend any time with recovery booted, no? I will take stability and compatibility over aesthetic features like touch and theming support any day.
[Samsung Galaxy Nexus] krlosgarces:
i did it, does'nt help, i tried also changing the file name for a shorter one. just in case

---------- Post added at 06:21 PM ---------- Previous post was at 06:14 PM ----------

Is your device booted in CWM? It needs to be...

And CWM has "USB Debugging" enabled by default -- don't forget, that is a setting in the Android, not on your device...

efrant, yes, my phone is in CWM mode when trying to push.

I'm using CWM touch 6.0, i already have installed it, i tried to apply an older version via fastboot but i could'nt, i dont know if is that the problem,. i dont know what to do. if you need more info about my phone just ask me. i really appreciate your help bro.
[Samsung Galaxy Nexus] Guto ViP:
My Yakju 4.0.4 JRN84D is rooted with locked bootloader... i´m try to use method 3.c (now i have CWM Recovery) but i stay getting Status 7 on update.... What is the problem?
[Samsung Galaxy Nexus] efrant:
Flash the recovery I linked to in the first post.

You need to tell us what the error is. Status 7 just doesn't cut it...
[Samsung Galaxy Nexus] krlosgarces:
i did it. does not help.

efrant, yes, my phone is in CWM mode when trying to push.

I'm using CWM touch 6.0, i already have installed it from last week, was the first time using CWM so i installed the last version, i didn't know that have somw issues, i tried to apply an older version via fastboot but i could'nt, i dont know if is that the problem,. i dont know what to do. if you need more info about my phone just ask me. i really appreciate your help bro.
[Samsung Galaxy Nexus] JuliantoS:
I'm on 4.0.4 version.

Should i upgrade it to 4.1 and then upgrade to 4.1.1 or is it ok to upgrade 4.1.1 with your steps on 1st post?
[Samsung Galaxy Nexus] d33k:
Status 7 was also provided as an error during my first attempt... read the rest of the message and see if it says something about RIL, then go that route. I'm unsure if "Status 7" is related to RIL only, or just a generic status number for a failure, but its worth looking into.

Efrant has a good thread regarding RIL vs baseband here.

EDIT: Can I please be verified, waiting 5 minutes between posts is torturous. ;)
[Samsung Galaxy Nexus] Guto ViP:
Something about: "system/bin/gzip"

P.S.: Now i cant back to CWM Recovery, i will try reinstall again.
[Samsung Galaxy Nexus] efrant:
Yes, it is ok to go from yakju/takju IMM76I to JRO03C.

As was mentioned many times already in this thread, that file relates to you using Stericson busybox. Have a read of the post in this thread to see what others have done. As well, the first post clearly states that if you (or any of your root apps) modifies any of your system files, you will need to put back the original. It even tells you in the first post how to get the originals...