yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] chrone:
please read the post #1, #2, and #3. it's written very clear how to to the OTA update manually.

or just flash the whole 4.2 ROM via fastboot command line using efrant's guide here.

make sure you download the right OTA or Factory Image build for your devices.

hope this helps. :)
[Samsung Galaxy Nexus] cristiandeives:
Status 7

I have a rooted Galaxy Nexus with stock Android 4.1.2 and I'm having problems to update it to Android 4.2. Two days ago I received an official OTA notification, but when I restarted the device, I got a "status 7" error. After googling, I tried flashing the stock system image to my phone and then I tried updating it again (by clearing the data of that "Google Services" app). No luck. I just tried updating using a zip file in the SD card but I still get the same error. What should I do?

My phone features are:

Model Number: Galaxy Nexus

Android version: 4.1.2

Baseband version: I9250XXLA2

Kernel version: 3.0.31-g4f6d371 android-build@vpbs1 ) #1 SMP PREEMPT Mon Sep 10 13:41:13 PDT 2012

Build number: JZO54K

CWM 6.0.1.0

The error I'm getting is:

Veryfing current system...

assert failed: apply_patch_check("EMMC: /dev/block/platform/omap/omap_hsmmc.0/by-name/radio: <big number>:<big hexa number>:<big number>:<big hexa number>")

E:Error in /sdcard/fdf06e8d71c7.signed-yakju-JOP40C-from-JZO54K.fdf06e8d.zip

(Status 7)

Installation aborted.
[Samsung Galaxy Nexus] Winesnob:
You have the wrong radio. You need to be on XXLF1. The assert failed statement gave you the answer that the radio was the problem. Pull the correct radio from the factory image and flash though fastboot.
[Samsung Galaxy Nexus] osm0sis:
All system files, kernel and radio must be stock in order to flash an OTA. Read what the assert failed says and you can figure out what you have that isn't stock which is making it fail.
[Samsung Galaxy Nexus] thephantom:
You mentioned flashing stock but your radio is old. That's the problem
[Samsung Galaxy Nexus] ahmadtrabulsi:
if i flash the victory image will I loos my data and apps?

my device information are:

android V: 4.1.2

baseband V : I9250xxlf1

kernal V :3.0.31-g4f6d371 android-build@vpns1

buid number :Jz054k

and it is yakju

I did the method 1 after gave me update completed I reboot and still on 4.1.2

in method 1 step2(2) Open the archive and delete the recovery folder; EDIT: Do NOT do this step if it you are using any Jelly Bean update, i.e., JRN84D or newer.)HOW TO DO THIS STEP??i miss it but I dont know how to find this archive,would you explain it for me
[Samsung Galaxy Nexus] cristiandeives:
Thanks, guys! I flashed the radio image and now the update worked!
[Samsung Galaxy Nexus] chrone:
i assume you have already flashed CWM recovery since you are using method #1.

it's best to backup all your data and apps to PC before doing a factory image reset. assume you have to unlock your bootloader first using the "fastboot oem unlock" and flashing the userdata.img using "fastboot flash userdata userdata.img" will wipe your data off.

efrant did wrote on method #1 this:

have you tried the "revised" Method 1 by Revoked yet?

but if you have your bootloader unlocked and still using stock recovery, then using method #2 is the easiest method to flash an OTA update. the archive for yakju coming from a 4.1.2 build should be this as mentioned on post #1.

i wonder what kind of message appeared in the CWM recovery mode when you flashed the OTA update, was it succesfull or failed? i supposed the message would be "failed" since after reboot you're still in 4.1.2, or you downloaded the same 4.1.2 OTA update package and flashed it ontop of your 4.1.2 hence produce the same build after reboot. hehe :P

i could think of a work around using efrant's guide on how to return to stock here in order to flash the ota update without loosing your data:

download the right OTA update package for yakju.

download the right CWM image.

download the 4.2 factory image for yakju,

extract all the packages inside the factory image using 7-zip.

flash back the stock recovery using "fastboot flash recovery recovery.img"

use method #2 of this thread to flash the OTA update.

flash back CWM recovery and your done.

hope efrant or other senior member could correct me if i'm wrong here. but if you have read the efrant's guide on how to return to stock and the methods provided in this thread, flashing ota package would be easy.
[Samsung Galaxy Nexus] ahmadtrabulsi:
I notice something that may help advising me:

-each time i try to flash the update I am loosing the CWM

-after CWM give me :install from sdcard compete and I do go back to reboot I am getting the message : ROM may flash stock recovery on boot.fix? no or yes:disable recovery flash,(in both choices update is not done)

did I do something wrong?
[Samsung Galaxy Nexus] osm0sis:
That would mean the update worked correctly if it pushed the files CWM is bringing up that dialog for.
[Samsung Galaxy Nexus] ahmadtrabulsi:
but it is not done I still have 4.1.2

regarding methods 2,3 on command prompt my device is no recolonized,and my device driver is working
[Samsung Galaxy Nexus] efrant:
1) The command is "adb devices", NOT "abd devices"

2) Please don't ask questions in this thread if you are using a toolkit to do anything -- ask in the toolkit thread please.

Thanks.
[Samsung Galaxy Nexus] ahmadtrabulsi:
thank you but it was wrong typing only
[Samsung Galaxy Nexus] chrone:
Dude, seriously, you are using toolkit instead of efrant's guide on how to return to stock. That's why the methods in here didn't work on you. Hehe

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ahmadtrabulsi:
thank you all but it seems that is too much for me I need to learn moor of this things

whatever I am sorry for wasting your time with me

I only have one last question : if i have the stock rom and before I have got the official updates why this one is failed? would you explain for me

thanks
[Samsung Galaxy Nexus] osm0sis:
You are doing something wrong, somewhere down the line. That's why, but we can't explain it because you are unable to explain it yourself. :(

Go to efrant's sig. Read "What matters is understanding the journey" and then start with 1) Basics. Then read 2). 2 should get you acquainted with fastboot and adb and then you should be able to get rid of the toolkit and come back here for 3).
[Samsung Galaxy Nexus] chrone:
No worries, dude. We all learning something new everyday here. Kudos for other members who share their knowledge. Gotta read here, read there, and practice. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ahmadtrabulsi:
there is something that I can not understand how to perform it correctly I am sure about,what is that thing,I am trying to find out I I will let you know my results

thanks all

---------- Post added at 11:40 PM ---------- Previous post was at 11:05 PM ----------

here I am again

assuming I have the correct factory img

first thing I can not perform this step in thread 2 (5) For those of you that don't know, every OTA update places two files on your system (that are not there on a non-update stock ROM) that re-flash the stock recovery on EVERY boot. The two files are /system/recovery-from-boot.p and /system/etc/install-recovery.sh. You need to make sure that these files are either deleted or renamed, or else CWM will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, if you've recently gotten an OTA and applied it, your CWM is gone... Use something like Root Explorer, delete them, and re-flash your CWM recovery. root explorer gave me can not delete the file system is read only

and now if i want to perform the method 2 I dont understand this(3) Download CWM from here and place it on your computer in the same directory as your fastboot binary)where exactly is that fastboot binary,and also if command prompt dont see my device what can I do?

I think that is exactly my problem...any suggest ??

hop I explained well

thanks all
[Samsung Galaxy Nexus] thephantom:
You aren't rooted yet so root explorer can't modify the files you are mentioning.

You downloaded the platform tools and extracted them in a folder. The cwm you have needs to be in the same folder where you have your fastboot files
[Samsung Galaxy Nexus] ahmadtrabulsi:
my device is rooted and unlocked
[Samsung Galaxy Nexus] ahmadtrabulsi:
finally I did it

but I used the method here : Samsung Galaxy Nexus > Galaxy Nexus General > Updating Android or switching from yakju to takju with Mobile Odin, and keep data

I have the 4.2 with all of my data and apps

thank you all for your help
[Samsung Galaxy Nexus] aniket.sananse:
Error 7 aborted

hi every1 .. i am on takju version and jelybean 4.1.2 (JZ054K) firmware...and unocked bootloader & CWM installed...

everytime i m trying to install the jellybean update 4.2 -- by method 1....i m gettin ERROR 7 ABORTED error..!!

please please help..!!
[Samsung Galaxy Nexus] chrone:
Have you checked the md5 of your ota zip yet? Just to be sure your downloaded ota zip is not corrupted. :P

Also, are you using the same cwm build as in method 1? There's warning above the method 1 to avoid specific cwm build.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] goldygopher:
Hey all - welcome your thoughts. I did a 4.2 upgrade, using the full system image, basically following all the instructions in post 1505. I didn't like the performance of 4.2 however, but mainly, one of the apps I wanted for an upcoming trip (sixaxis) was incompatible. So I tried to flash down to 4.1.2 (again, using the instructions in post 1505, but now my GSM Nexus is hung at the X screen at startup (the one that oscillates the colors. It still has unlocked bootloader (unlocked padlock before I get to the X screen).

Any help would be appreciated.
[Samsung Galaxy Nexus] caro23:
I have a problem with Avast AntiTheft after updating to 4.2.

When I try to reinstall it to the system partition, I get an error message "Could not write to /system".

According to Titanium Backup, I still have root permissions...

Thanks in advance!
[Samsung Galaxy Nexus] efrant:
Flash the boot and system images again, erase the cache again, and reboot. If that still doesn't work, then you will have to boot into CWM and wipe /data.

Are you sure you have root? If you are using ChainsDD's Superuser, it is not fully compatible yet with 4.2. Use Chainfire's SuperSU until ChainsDD updates his app.
[Samsung Galaxy Nexus] chrone:
avast antitheft is not fully compatible with android jellybean 4.2 yet, especially for the hard reset protection in advance settings. i have emailed the developer and they said they're working on this for the next update. there's an option for unrooted phone to use avast antitheft when the first time you set and download the anti theft app inside avast! mobile security app.

i got force closed everytime i tried to rewrite hard reset protection using the advance custom recovery method on jelly bean 4.2, but the direct write method wrote the hard reset protection flawlessly though it could not verify the written hard reset protection due to the incompatibility issue. :)

i've tested avast antitheft on android jelly bean 4.1.1/4.1.2/4.2 that gnex didn't have to be rooted to use the hard reset protection if again was initially set and downloaded the appropriate avast anti theft for unrooted phone.

now, let's get back to the original Google OTA thread topic. :D
[Samsung Galaxy Nexus] samersh72:
try google site for nexus images
[Samsung Galaxy Nexus] bozint:
Hey efrant, I just got my 4.2 OTA. I would like to know whether you want me to find the URL? I have yakju GNex after flashing using your guide. I live in Macedonia (South-East Europe) if it means something for the update.

Let me know, as I am still hesitant whether to update.

BTW, any chance of doing a nandroid on non-rooted GNex?
[Samsung Galaxy Nexus] efrant:
The yakju 4.2 update has already been posted, but thanks anyway.
[Samsung Galaxy Nexus] telnet05:
I have a Yakzu 4.1.1 nexus and i haven't received anything, either 4.1.2 or 4.2. Any ideas???
[Samsung Galaxy Nexus] efrant:
That is what the whole purpose of this thread is for: so you don't have to wait for the update. Just grab it from the first post and flash it.
[Samsung Galaxy Nexus] specially_foru:
TOUCH CWM Recovery causing OTA Flashing Problem

I was on 4.1.2 Yakju

Downloaded the OTA to update to 4.2

Tried to flash the.zip file using CWM

got an error getprop ("ro.product.device) == getprop ("ro.build.product")

Not sure of the exact wording since i did not note it down

i thought maybe i have updated some system files which is giving me error.

So i reflashed 4.1.2 yakju factory image (which was already available with me) using Nexus Toolkit kit

All stock

again tried to flash the OTA of 4.2 yakju and same error.

All this time i have touch CWM

Read somewhere that it

Touch CWM Recovery may cause problem.

So installed non-touch CWM using ROM Manager.

And tried to flash the OTA YAKJU 4.2 using CWM Recovery.

And SUCCESS.
[Samsung Galaxy Nexus] AArmin88:
Widget missing

Guys, I used rom manager and have now 4.2

but looking over some other posts, I noticed that others have the music widget on the lock screen (that means 5 of them) and I only have 4, the music widget is missing? Do I have to enable it somehow or what?

Also, is this 4.2 or some app/widget in Kaisan1's post --> http://xdaforums.com/show...989045&page=63

"last post on page 63"

thx in advance
[Samsung Galaxy Nexus] evil_penguin:
4.2.1 is Rolling out for nexus 4.

OTA size is only 1.1 mb

hope it fixes bugs in galaxy nexus:)
[Samsung Galaxy Nexus] efrant:
If you are not in the U.S., it is disabled by default. Use Package Enabler to re-enable it.
[Samsung Galaxy Nexus] fireb33:
Or disable Google Partner Set Up :)
[Samsung Galaxy Nexus] thitto:
status 7

Guys I need some Help, I'm getting status 7 error.

My Nexus:

Android Version: 4.1.2

Baseband version: I9250XXLF1

Kernel:3.0.31-g4f6d371

Build Number:JZO54K

Product:Yakju

I'm using CWM 6.0.1.5, also I tried to update the version JRO03C to check if something of my system is different but also I got the same error.

Someone could help?

Thanks
[Samsung Galaxy Nexus] dmapr:
Just got the 4.2.1 on Galaxy Nexus. Since I can't post links yet...

HTTP android.clients.google.com/packages/ota/google_takju/1d62212ba0a9.signed-takju-JOP40D-from-JOP40C.1d62212b.zip
[Samsung Galaxy Nexus] osm0sis:
Nicely done! Welcome to XDA! You're off to a great start. :)
[Samsung Galaxy Nexus] rusco.morgan:
orestsgi

Can we flash it on android 4.2 yakju version? is it safe?
[Samsung Galaxy Nexus] oldblue910:
Fail. Disregard.
[Samsung Galaxy Nexus] osm0sis:
Got your OTA threads confused, blue. ;):laugh:
[Samsung Galaxy Nexus] oldblue910:
:o
[Samsung Galaxy Nexus] DJxSpeedy:
flashed the ota..atm no problems
[Samsung Galaxy Nexus] sachin6870:
Flashed, failed!

Now stuck at boot screen with "Google" label for last 15 mins.
[Samsung Galaxy Nexus] chntpw:
sweet.. now my phone's running android 4.2.1
[Samsung Galaxy Nexus] oldblue910:
Hopefully Google will start slowing down on the Android updates to give Verizon ample time to test and approve one. If they keep up this schedule of an update every few weeks, we are never going to see mysid get off of 4.1.1/JRO03O. haha
[Samsung Galaxy Nexus] Winesnob:
Really wondering what update Toro will see next. 4.1.2 and then to 4.2.1, or just straight to 4.2.1? I just hope they're testing SOMETHING.
[Samsung Galaxy Nexus] oldblue910:
When we get an OTA, it'll be to whatever the current version is at the time. You can take that to the bank. That's why this is so frustrating. Historically Verizon updates come two months after the GSM variants. So...every single time Google pushes an OTA, that two-month counter resets to zero. Ugh.
[Samsung Galaxy Nexus] Carlos_Manuel:
Can somebody create android 4.2.1 update of its OTA files for deodexed jelly bean 4.2?

Thanks.

Not needed if somebody have made ROM of it...

I'm not at home and I'm not going to mess my nexus again when I have modified ROM... :D
[Samsung Galaxy Nexus] samm1e:
Someone who updated to 4.2.1 with bluetooth\USB keyboard.

Could you please check does layout change on keyboard (CTRL-SPACE) causes system restart? This bug is awfull!

I cannot update untill it's fixed. Thank you.
[Samsung Galaxy Nexus] shadow_empire1:
Help - not booting anymore

Tried to flash "1d62212ba0a9.signed-takju-JOP40D-from-JOP40C.1d62212b.zip" from my stock (rooted) JOP40C with TWRP 2.3.2.1.

-> set_perm: some changes failed

E:Error in /data/media/0/1d62212ba0a9.signed-tak

(Status 7)

Error flashing zip '/data/media/0/1d62212ba0a9.s

Updating partition details...

Failed

Now it is stuck at the Google logo...

---------

Reflashed Stock google image with Nexus Toolkit 10.0 (without deleting user data)

I love this prog :)
[Samsung Galaxy Nexus] hasafly:
Still no update file for Yakju ?
[Samsung Galaxy Nexus] gokpog:
Yakju link for OTA 4.2.1: http://android.clients.google.com/p....signed-yakju-JOP40D-from-JOP40C.5f67f5ca.zip

Credits: Dirk64
[Samsung Galaxy Nexus] hasafly:
Thank you guys!
[Samsung Galaxy Nexus] oldblue910:
4.2.1/JOP40D updates for yakju and takju are both mirrored on randomphantasmagoria.com.
[Samsung Galaxy Nexus] jfrag:
http://android.clients.google.com/p....signed-yakju-JOP40D-from-JOP40C.5f67f5ca.zip

for yakju ;)
[Samsung Galaxy Nexus] Carlos_Manuel:
Hey!

When I try to update Takju JB 4.2 to 4.2.1 then the flashing fails and says installation aborted..

What causes that?

I use latest CWM Touch Recovery, does it cause the failing?

(I flashed stock odexed back to update my nexus..)
[Samsung Galaxy Nexus] WizardBGR:
Same here. Status 7 error. I'm starting to think that this is caused because of Xlouder patch... is says "error checking effects.odex" or sth. Any ideas, guys?
[Samsung Galaxy Nexus] efrant:
Both of you need to post the details of the Status 7 error in order for us to help you.
[Samsung Galaxy Nexus] Carlos_Manuel:
and how I can post details of it?

on Jet I modified init.rc files to give android.log and kernel.log but actually never used logcat..

I can try to flash older recovery and if that does not help the I flash factory image again..

I'm going to flash system.img and boot.img again, maybe that helps..
[Samsung Galaxy Nexus] bagl0312:
updated my Galaxy Nexus to 4.2.1 and everything is ok
[Samsung Galaxy Nexus] efrant:
You can post the contents of the log files in /cache, or, just post the error details from the CWM screen when it aborts -- that's all we really need.
[Samsung Galaxy Nexus] Carlos_Manuel:
OK!

I flashed factory system.img and boot.img and then CWM touch 5.# something and now it flashed it..

maybe SuperSU app on /system/app/ caused it or my modded files or then boot.img that maybe was rooted (insecured)

And thanks for the OTA update link..
[Samsung Galaxy Nexus] lexcyn:
Mine errors with status 7 as well on yakju update:

assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.2/JOP40C/527662:user/release-keys"

Running stock with root.
[Samsung Galaxy Nexus] efrant:
Are you using a touch recovery?
[Samsung Galaxy Nexus] lexcyn:
Yeah CWM touch, latest. If that is the issue I can just flash the non-touch.
[Samsung Galaxy Nexus] efrant:
That is the issue.
[Samsung Galaxy Nexus] osm0sis:
Worked fine with cwm touch 6.0.1.5 official.
[Samsung Galaxy Nexus] efrant:
I haven't quite figured out why some are having issues with CWM touch recoveries while others are not. Seems hit and miss. In any case, all non-touch recoveries work without issue.
[Samsung Galaxy Nexus] lexcyn:
OK so I installed the non-touch, now I am getting the following:

set_perm: some changes failed

(Status 7)

At least now it tries to install the update lol
[Samsung Galaxy Nexus] efrant:
Need more details please. Was there anything else on the screen, as far as errors/details go?
[Samsung Galaxy Nexus] lexcyn:
I'll give you exactly what the log said:

Finding update package...

Opening update package...

Installing update...

Verifying current system...

Removing unneeded files...

Patching system files...

Unpacking new recovery...

Symlinks and permissions...

set_perm: some changes failed

E:Error in /sdcard/0/Download/1d62212ba0a9.signed-takju-JOP40D-from-JOP40C.1d62212b.zip

(Status 7)

Installation aborted.

I'm guessing it's a permission issue but I'm not sure why. Unless SuperSU is screwing it up.
[Samsung Galaxy Nexus] WizardBGR:
Here is the log file
[Samsung Galaxy Nexus] efrant:
Are you using the "protect root" feature of SuperSU? That is probably messing it up. Try updating without that feature enabled -- there is no need, as the latest CWM detects permission changes on su and fixes them for you if you want.

Are you running a deodexed ROM? You need to be running a stock ROM. Best thing to do is to flash the yakju 4.2 system image using fastboot. The update will work then.
[Samsung Galaxy Nexus] WizardBGR:
No, it's odexed stock 4.2 takju. Only thing that is different is that I applied volume Xlouder patch.
[Samsung Galaxy Nexus] efrant:
Then I guess the Xlouder patch changes some system files (including this one: /system/framework/com.google.android.media.effects.odex). The easiest way to solve it is to just re-flash the system image using fastboot and all will be fine. No data loss or anything.
[Samsung Galaxy Nexus] Hotshot205:
Has super user been updated to work with 4.2? I've been hearing that it's not granting root apps permissions.
[Samsung Galaxy Nexus] osm0sis:
Haha xlouder changes like 30 system files. ;)

That's why we've got a revert zip to get you back to stock. :good:
[Samsung Galaxy Nexus] efrant:
Not yet. ChainsDD is aware of the issue and is working on it: https://twitter.com/ChainsDD/status/271964267857727489.

Use SuperSU for the time being, and switch back to Superuser once the issues get rectified if you like.
[Samsung Galaxy Nexus] lexcyn:
Well it's something messed. I think I'm just going to flash back to stock, wipe & reset and then do the update.
[Samsung Galaxy Nexus] efrant:
All you have to do is flash the 4.2 system image, then apply the update... No wipe necessary.
[Samsung Galaxy Nexus] WizardBGR:
I am on Alpha 1 patch... Could you give me link to revert patch?
[Samsung Galaxy Nexus] osm0sis:
There is none for that alpha, as posted in the warning in that thread. Follow efrant's advice above.
[Samsung Galaxy Nexus] WizardBGR:
Darn... A little more info how to do it and not to lose my data? I am tired of reflashing and restoring all from backups...

Edit: Is that correct: I need factory takju image, extract system.img and do this - fastboot flash system system.img ?
[Samsung Galaxy Nexus] Baalzamon:
What are your experiences with 4.2.1 on yakju? Are there any bugs remaining?
[Samsung Galaxy Nexus] osm0sis:
Yes. That's correct.
[Samsung Galaxy Nexus] Hotshot205:
Okay thanks, do you have a link on how to switch over to supersu if not I can just wait until it's fixed.
[Samsung Galaxy Nexus] efrant:
Just flash the SuperSU zip package from here after you flash the update, but before rebooting.
[Samsung Galaxy Nexus] le_prof:
A question about Method 1.

Since I want to update to 4.2.1 (i.e. No step 2), can I download the file directly to my sdcard instead of my computer, or for whatever reason is it necessary to download it through my computer and then transfer it to my sdcard ?

And for verification purposes, how big is the file? Tried to download it, but was a very small file, so it seemed odd. Can someone give me the md5 for that file (takju version)? Tnx.
[Samsung Galaxy Nexus] efrant:
Correct, you can download it directly to your device.

The update is small (only 986 KB). It is not a major update.

You don't really need to worry about checking the MD5, but if you really want to, here it is: 0D8F85338BB9AF0C694AE528C76058B8

By the way, the first 12 characters of the file name are the first 12 characters of the SHA1 hash, so you can always check that way as well.
[Samsung Galaxy Nexus] le_prof:
Thanks!

This being said, I am not familiar with this SHA-1 hash thing. I have read it is similar to md5, but unlike the latter, I have no idea where to find it (I am using Root Explorer).