yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Right. Regional variants don't get a factory image. I just sent you there so you could see the build numbers that correspond to build codes.

Yes, you can dirty flash to takju or yakju using the respective factory image and the method you describe. But I recommend you backup your userapps+data with Titanium Backup and then after you flash system.img and the radio of your choice go into a custom recovery like CWM or TWRP and format data and cache to avoid any possible incompatibilities between your regional variant and yakju/takju. Once you've done that and rerooted you can just boot up, install Titanium Backup and restore all your userapps+data and all you have to set up again are your system app settings. This isn't quite clean or dirty, but it's closer to clean so let's call it "semi-clean" flashing. ;)
[Samsung Galaxy Nexus] syspanic:
Can't update

Hello, I'm having problems to update to 4.2.

Actually, I'm using 4.1.1 since the 4.1.2 OTA simply doesn't work for me.

So I was trying to manually update to 4.1.2 then update to 4.2, without success. I'm always receiving this error when I try to flash:

"assert failed: apply_patch_check("EMMC:/dev/block/plataform/omap/omap_hsmc.0/by-name/boot:4470784:bce1a69286de41cc4a372bf3bb17131b708c2a60:4472832:2aadadd4d29644b56f078e074ca3a85123229fb6")

E:Error in /sdcard/06fa1976791d.signed-takju-JZO54K-from-JRO03C.06fa1976.zip

(Status 7)

Installation aborted.

I'm using a takju maguro JRO03C with I9250XXLF1 and stock kernel (3.0.31 - ge8de0e2).

Any ideas to fix it?

Thanks!
[Samsung Galaxy Nexus] osm0sis:
The assert is failing on your kernel, so whatever you're running it's not stock kernel. Reflash stock kernel from the takju 4.1.1 Factory Image at randomphantasmagoria.com and you should get past that assert.
[Samsung Galaxy Nexus] HinotoriBR:
You won't be able to apply the OTA that is meant to be applied from 4.1.2 to 4.2.0 when your phone have 4.1.1... If you have issues applying the ota from 4.1.1 to 4.1.2, best bet is to apply the 4.1.2 factory image (read carefully efrant instructions, you can do it and not loose your data, if you don't read it carefully you will erase all applications, data and everything in the virtual sdcard) then applying the 4.2 OTA... I'm not a big fan of applying the 4.2 factory image over a 4.1.1 or .4.1.2 data (no wipe) since the update script moves a lot of things to /sdcard/0 and I'm not sure what happens when you just apply the factory image (some people say it works).
[Samsung Galaxy Nexus] syspanic:
Well, I've used the Efrant tutorial to convert to takju I guess, and used the factory images, so I didn't modified anything.

Anyway, I don't even know how to reflash the stock kernel. I've already downloaded the 4.1.1 factory image but I don't know which files should I flash. Ah, just I question: Is it possible to reflash to stock kernel without lose my config/data?

I know is not possible apply the OTA to 4.2 from 4.1.1. I'm having problems to apply the 4.1.2 OTA from 4.1.1!

So that's why I trying to manually update to 4.1.2 to finally update to 4.2.

Is there any way to update to 4.2 from 4.1.1, using for example the factory image, but without lose any config/data?

Thanks in advice guys!
[Samsung Galaxy Nexus] osm0sis:
1) Well I don't know how but the JZO54K from JRO03C OTA is definitely failing on your kernel so you should try reflashing it. boot.img is the kernel image in the Factory Image package. So you'd just need to fastboot flash boot boot.img again to get it going and try again. No data is lost unless you flash userdata.img.

2) You can technically flash 4.2 Factory Images over 4.1.1 without losing config/data but like Hinotori mentioned, it's not recommended to do that "dirty flashing" in case there is some incompatibility between the versions. Best bet are the instructions I included for safer "semi-clean" flashing above since that won't wipe your sdcard and you can restore all your user apps+data/config from Titanium Backup, leaving only your system settings you'd need to redo.
[Samsung Galaxy Nexus] Moz007:
Hi,

I try to update my 4.1.2 Gnex to 4.2 but i have an error :

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

Any ideas ? :crying:
[Samsung Galaxy Nexus] artkrz:
Yes, read this thread.
[Samsung Galaxy Nexus] Moz007:
I'm sorry, i'm not sure what to do...
[Samsung Galaxy Nexus] artkrz:
That's fine but it was mentioned meny times and even on the page your post appeared. You just have to scroll up. Remember, search the forum, then post :)
[Samsung Galaxy Nexus] Moz007:
I don't find someone with the same error than me... :confused:

Can you tell me what i have to do please ?
[Samsung Galaxy Nexus] artkrz:
Try to flash the system and boot images using fastboot. I think that worked for some people.
[Samsung Galaxy Nexus] Paul22000:
So I decided to make the jump again to 4.2 today. (I'm quoting my previous post in case anyone else has the same issues that I did.)

Here's what I did from the above point:

Power off phone -> Hold Volume Up + Volume Down + Power -> Wait for Bootloader -> Select Recovery

Backup

Flash CWM-SuperSU-v0.92-mod.zip -> Reboot and I am rooted once again

Download, install, and use OTA Rootkeeper

Download and tranfer to phone bigxie_maguro_OTA_JOP40C_odexed-signed.zip from: Android 4.2 JOP40C: Rooted Busybox Odexed

Recovery again -> Wipe cache -> Wipe dalvik cache

Install ROM

OTA Rootkeeper: tried to restore root but useless once again

Go back into recovery and re-flash CWM root file

Hope that helps someone else out there!
[Samsung Galaxy Nexus] Flitschi:
Hi Guys,

can anybody help me, gut much trouble the last time with flashing.

On my Phone right now.:

4.1.2

3.044-franco.Kernel-Milestone6

Codename-Android-3.8.0

JZ054K

Can i flash the update with out problems ??
[Samsung Galaxy Nexus] thephantom:
No you can't. You have a custom rom and kernel. You need to be on stock to update
[Samsung Galaxy Nexus] Flitschi:
Thx
[Samsung Galaxy Nexus] Dutch2005:
I just tried to update.. and I got the error from below...

I think its because i installed a TimeSync app, and one needed root access... (i reckon this program altered the file... )

any idea's how to fix it without fully re-flashing my nexus...

p.s. ignore the screen damage already ordered a new glass (as the touchpart still works...)

installed apps were "TimeZone Fixer (ROOT)" and "ClockSync"

---

assert failed: apply_patch_check("/system/usr/share/zoneinfo/zoneinfo.dat"

E: Error in /sdard/......signed-takju.....zip (status 7)

Installation aborted.

------

Can any one supply me the zoneinfo.dat from takju version 4.1.2, as i have my phone rooted i can "just" replace my file with the correct version...
[Samsung Galaxy Nexus] efrant:
The instructions on how to extract the file are in the second post of this thread.

Or, you would always just flash the takju 4.1.2 system image, which will ensure that all the system files are stock.
[Samsung Galaxy Nexus] Paul22000:
I think you have the same problem that I did? See post #1605 above
[Samsung Galaxy Nexus] NCguy:
Efrant, I understand that superuser is broken for 4.2 and I've seen others advise using supersu until superuser is fixed.

I'm on 4.1.2 and superuser was apparently installed to /system/apps. I guess I need to deal with the superuser issue before I run the OTA. Is there any way to resolve this and be able to run the 4.2 ota or am I looking at installing a new 4.2 stock rom?
[Samsung Galaxy Nexus] efrant:
Not sure what you are talking about. (And I didn't know that superuser was up to version 4.1.2.)

Superuser 3.2 works just fine for me on JOP40C.
[Samsung Galaxy Nexus] NCguy:
Sorry, I meant android 4.1.2.

There are lots of reports about superuser and android 4.2.

Here is one

https://plus.google.com/108126763150092079408/posts/9twCAtqB5Dq

---------- Post added at 10:20 AM ---------- Previous post was at 10:10 AM ----------

Here is another problem report from mskip

The Android 4.2 build adds a cool new feature called MultiUser. Unfortunately for users this update brings a world of trouble in regards to rooting and a few other things. Superuser 3.1.3 will not root and SuperSU 0.97 will look like it worked but it didnt and busybox wont go on properly. Chainfire has updated SuperSU to 0.98 to bring a temporary fix until he sorts it out properly but with SuperSU only the primary user can have root access. The SDCard is also now in /data/media/0 so if looking for your sdcard on clockworkmod or twrp you will have to look in the "0" folder as a legacy folder and another folder have been created in /data/media. Im not sure how this affects Internal Storage backups as the the files go back to the correct location but you may have to set permissions and owner rights manually to see the files/folders.

The good news is that I have updated all parts of the Toolkit relating to do EVERYTHING you need to. I have temporarily blocked Superuser being used to root 4.2 as it wont work so just use SuperSU and you will be fine.
[Samsung Galaxy Nexus] NCguy:
Efrant, are you still if the opinion that I won't have any issues with android 4.2 and superuser?
[Samsung Galaxy Nexus] osm0sis:
Superuser hasn't worked well since Jelly Bean in general, SuperSU is really the way to go from here unless ChainsDD decides to get back in the game.
[Samsung Galaxy Nexus] NCguy:
Thanks for that confirmation. I'm currently on android 4.1.2 with superuser installed to /system/apps. I don't think superuser can be uninstalled and I would like to install the 4.2 OTA with root. So is my only good option now to install the whole stock 4.2 rom with supersu since I can't get rid of superuser?
[Samsung Galaxy Nexus] osm0sis:
You should be able to install SuperSU from the market. It will use the Superuser su binary to replace it with itself, then you can just go in with a file explorer of your choice and remove the superuser.apk.
[Samsung Galaxy Nexus] NCguy:
Thanks for that tip. I'll do a nandroid before I start as a fallback. This will save me a lot of time.

Does ota rootkeeper work with supersu?
[Samsung Galaxy Nexus] osm0sis:
Haven't tried the root keeper. CWM 6.x makes sure you keep root now too.
[Samsung Galaxy Nexus] efrant:
Based on what koush is saying, it seems that it won't work. I don't have my gnex with me at the moment, but I will test it out later. The reason I haven't had any issues is that I haven't installed any apps that require root after updating to 4.2. All my apps that previously had root access still have root access. If you like superuser, try it. If it doesn't work, just replace it with supersu. Too easy.
[Samsung Galaxy Nexus] NCguy:
Thanks for talking a look at it. Looks like I will be trying osm0sis method in the prior post for replacing superuser with supersu. It sounds like you two are on the same page. Do you happen to know if OTA rootkeeper will work with supersu like it does with superuser?
[Samsung Galaxy Nexus] osm0sis:
Chainfire said SuperSU's built-in OTA survival mode worked for him, I didn't try it though since CWM 6.x just kept my su privileges intact anyway.
[Samsung Galaxy Nexus] NCguy:
I think I found the answer in the play store description for rootkeeper. The answer is no because supersu apparently has the same type of rootkeeper functionality already built in.
[Samsung Galaxy Nexus] NCguy:
Guys, the installation of supersu went without a glitch. I then ran the OTA and it its now permanently stuck on the google boot screen.

Sounds like I'm not alone. Lots of reports now of people stuck like this who installed supersu just prior to the OTA.

http://xdaforums.com/showthread.php?p=34164146

No one has a good suggestion on how to recover. I did an nandroid before I started and I can boot into clockworkmod but when I try to select the folder that contains my backup it says "no files found". Does this on an earlier backup folder also. I did also try to mount the SD and that didn't help.

BTW, I also copied the nandroid backup to the PC before the OTA and supersu install but I dont think that helps since I can boot into android.

Any suggestions on how to get past this? Anything worth trying before I load a new factory image (assuming that I can do this)?

EDIT: out of things to try. ended up installing a stock image, lost all data
[Samsung Galaxy Nexus] osm0sis:
Upgrade to the newest cwm and move your clockworkmod folder from /data/media/0 to /data/media/ where it used to be. 4.2 just moved all your stuff for multi-user support. As for the SuperSU thing, that's really weird. I updated to 0.98 right before applying the OTA in CWM with no problems.. :(

You could try manually removing supersu and su through adb shell?

Edit: Ah poop, just saw your edit. 4.2 factory image I hope? All you needed was system.img and all your data would be intact, you'd just need to reroot and install busybox, etc.
[Samsung Galaxy Nexus] efrant:
So I can indeed confirm that, if you are using Superuser and update to 4.2, only those apps to which you had previously granted root will have root. Any new apps that request root will not get it.

Hopefully ChainsDD will sort this out quickly.

When flashing the factory image via fastboot, if you skip the userdata and recovery images, you will not lose any data, and will still have your custom recovery. (You may experience a bootloop, but just wipe data in your custom recovery, and it will fix it. You will lose your installed apps and data, but not anything on /sdcard)
[Samsung Galaxy Nexus] ajstyles69:
Havnt recieved any update yet :(

Hi folks...

M kinda new to this forum.. can some1 guide me how to update my gnex to 4.2. And if possible without flashing or rooting..

I havnt yet recievd ne OTA for 4.1.2 or 4.2.

My firmware ver is 4.1.1 and its not rooted ..

M a noob.. so pls any help is really appreciated.

Thank you
[Samsung Galaxy Nexus] thephantom:
If the update is not ready for your build version, there's no way to update it. If you are open to flashing, read page 1 of this http://xdaforums.com/showthread.php?t=1626895. No need to root if you don't want to
[Samsung Galaxy Nexus] NCguy:
Thanks to you and osm0sis for those tips and next time it will come in handy. Fortunately I had a current titanium and most of the sd data. Just lost a few pics.

BTW, what exactly is the relationship between /data/media, /data/media/0 and /sdcard? Is there a virtual link from one of these media folders to /sdcard. I migrated all my sd card data to /sdcard via mtp. I hope that was the preferred thing to do? It seems to be working.

---------- Post added at 07:17 AM ---------- Previous post was at 06:52 AM ----------

I actually installed CWM touch on the new stock 4.2 and the folder is in /data/media. Rom manager wants to update CWM. I suppose I should let it? Also where do you go to tell CWM not to use the new blob format?
[Samsung Galaxy Nexus] efrant:
Hmm. I haven't really looked at it before (I've been extremely busy at work over the past week or so), so someone else may be able to answer better, but this is what my device is showing as symlinks:

/sdcard ---> /storage/emulated/legacy
/storage/sdcard0 ---> /storage/emulated/legacy
/storage/emulated/legacy ---> /mnt/shell/emulated/0 (which is /data/media/0)
[Samsung Galaxy Nexus] osm0sis:
If you know how to use adb pull/push it's actually a lot faster than MTP.

dup (blob)/tar format option is under backup/restore :)
[Samsung Galaxy Nexus] NCguy:
Great. Thanks for that. What do you use to access that area?

Does it look to you like /sdcard maps to /data/media/0? The contents of those folders are the same on my JB 4.2 after I copied my old sdcard data into /sdcard using MTP. Since that's what mtp is still showing as the default location I hope its still ok to copy to /sdcard. There isn't new mtp drivers for JB 4.2 is there?

---------- Post added at 11:03 AM ---------- Previous post was at 10:49 AM ----------

Since I don't backup all that frequently its just easier to use mtp. The way things are going I may start using adb.

On the format options I was looking for it in the backup launch from rom manager. I should have thought to go into the recovery itself. Thanks for that. The old format was tar correct?
[Samsung Galaxy Nexus] osm0sis:
Correct sir. And to directly access the /data/media/ and structure is through adb shell again. ;) Once the OS is booted it mounts them to emulated/legacy, etc and doesn't give you access to anything else under /data/media/.
[Samsung Galaxy Nexus] evil_penguin:
I have switched to takju 4.2 ( from yakju)

what is taking so long for yakju to get ota ?

no factory images for yakju.

It must be due to bugs.:rolleyes:
[Samsung Galaxy Nexus] osm0sis:
My thoughts exactly. Forgetting to have the month of December in the calendar seems a pretty glaring oversight, plus I'm getting weird little audio artifacts with the music in Temple Run where I didn't in 4.1.2. "takju" apparently means "beta test" now. ;)

I'm still pumped to be running it first though. :D:good:
[Samsung Galaxy Nexus] efrant:
To show the symlinks? I just use "ls -l".

Yes.
[Samsung Galaxy Nexus] NCguy:
Do I need access from the pc to any structures in /data/media with the exception of CWM?
[Samsung Galaxy Nexus] pafaisal:
Hi

Can anyone tell me the fastboot command for copying a file from my pc to mobile...?
[Samsung Galaxy Nexus] artkrz:
None.
[Samsung Galaxy Nexus] HinotoriBR:
You use adb for that, adb push and adb pull...
[Samsung Galaxy Nexus] pafaisal:
I need to do this in bootloader mode.. adb command will work in bootloader mode...?

Below is the situation....

My phone doesnt boot up.

but I can go to recovery mod.

I have the nandroid backup file, but it is in my pc.

In this situation I need to copy the backup file from pc to mobile...

please suggest any method to restore the nandroid backup in the above situation.
[Samsung Galaxy Nexus] osm0sis:
It's faster for moving files to use adb pull/push instead of MTP like I said before, but otherwise no, nothing else of interest for us. :good:
[Samsung Galaxy Nexus] efrant:
Start you phone in bootloader mode and then select "recovery". You are now in recovery mode, and you can use ADB commands...
[Samsung Galaxy Nexus] Snowknight26:
Obligatory 4.2 yakju build link: http://android.clients.google.com/p....signed-yakju-JOP40C-from-JZO54K.fdf06e8d.zip
[Samsung Galaxy Nexus] ilciumbia:
OTA link

Hi everyone!

OTA for my yakju here in Italy just arrived! Operator Postemobile. Logcat recorded, link following:

http://android.clients.google.com/p....signed-yakju-JOP40C-from-JZO54K.fdf06e8d.zip

Hope it is useful!

Upgrade in progress right now... :cowboy:

Regards,

Paolo.
[Samsung Galaxy Nexus] efrant:
Thanks! But look two posts above yours... ;)
[Samsung Galaxy Nexus] ilciumbia:
:D Whoops... same link! Didn't notice... Well, at least we know it is a legitimate one! :p
[Samsung Galaxy Nexus] Murrzeak:
Hey guys. I get this error while flashing the 4.2

...apply_patch_check("/system/etc/audio_effects.conf...

But the thing is, I flashed 4.1.2 about two weeks ago and it went absolutely flawlessly and I didn't do anything with the system files after that. No volume mods, nothing. I have a DSP Manager installed, but it was there since day 1 and didn't prevent me from updating to 4.1.2 anyways. What's the easiest way to fix this? Cheers in advance!
[Samsung Galaxy Nexus] efrant:
Obviously DSP Manager changed something in that file. You have a couple of choices: 1) extract that file from the factory image (instructions in post #2) and copy it to your device then apply the update, or 2) just flash the full system and boot images using fastboot, and don't worry about the update.
[Samsung Galaxy Nexus] ahmadtrabulsi:
help plz

hello

I have yakju 4.1.2 build jz054k

I received the 4.2 update but got error ( as I remember it was around 64 MB ) is it the same of your update(16) if I want to flush it?

also I am not sure if this is the correct one for my device(yakju JZO54K from JRO03C: http://android.clients.google.com/pa...C.24a9a760.zip)??

would you please advice me?

thanks
[Samsung Galaxy Nexus] efrant:
Yes, that is the one.
[Samsung Galaxy Nexus] pranavhooda:
I m on 4.1.2 jzo54k... rooted and cwm installed.... so should i just flash it??

And I installed 4.2 camera installed on it will it create any problem?

Sent from Nexus.
[Samsung Galaxy Nexus] Androidin':
Thanks again to efrant for this post! Updated and re-rooted with no issues on jakju.
[Samsung Galaxy Nexus] pafaisal:
Hi

There was an issue in 4.2 takju that "December" month was missing in "people" app. The same error in yakju too...? Can anyone confirm...?

http://code.google.com/p/android/issues/detail?id=39692
[Samsung Galaxy Nexus] haxor:
Android yakju 4.2 !

Android 4.2 update rolling out to yakju Galaxy Nexus, factory image available :D

https://developers.google.com/android/nexus/images#yakjujop40c
[Samsung Galaxy Nexus] Androidin':
Yep it's still missing
[Samsung Galaxy Nexus] pranavhooda:
I m getting error while flashing..... it says "status 7"

Please help!!!

Sent from my Galaxy Nexus.
[Samsung Galaxy Nexus] ahmadtrabulsi:
help plzz

I tried to flush the update but got error would you help please
[Samsung Galaxy Nexus] efrant:
If you guys are getting errors, it means that you have something that is not stock. As stated in post #2, your kernel, radio and all files in /system need to be stock 4.1.2 files for the 4.2 update to work. A 4.2 camera is not a 4.1.2 file, now is it?

All the instructions are in post #2.
[Samsung Galaxy Nexus] ahmadtrabulsi:
I really only have the stock system and its update officially from google

4.1.2 yakjo jz054k kernel : 3.0.31-g4f6d371
[Samsung Galaxy Nexus] osm0sis:
How can we give you any help if you don't tell us any details, like, the exact error for example?
[Samsung Galaxy Nexus] tmxda:
efrant, in method 1 you modifying the update-script to remove "set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");"

if a user gets an assert error then could they modify the update-script and remove the relevant assert statement?

for example:

assert fails on "Calculator.apk"

then

edit update-script - remove the line with "assert(apply_patch_check("/system/app/Calculator.apk"...."

is that a possible work around?
[Samsung Galaxy Nexus] efrant:
Yes, assuming you also remove the corresponding line that patches the file. But I wouldn't recommend doing that. I would recommend what I said earlier : either flash the stock system image in fastboot or extract the stock file you need from the stock system image.
[Samsung Galaxy Nexus] ahmadtrabulsi:
recovery mood

hello again I think my brb is on the recovery mood ,when I tried to enter is even if I don't start the update I am getting the android logo with the red triangle above, I don't know how to fix this,the same situation I got when I received the update(4.2) also when I tried to flush it from CWM

I have the stock ROM with stock updates witch downloaded successfully before

any advice??
[Samsung Galaxy Nexus] osm0sis:
That's stock recovery. Plain and simple, you just need to flash back to CWM or boot to it to apply the OTA. Read the OP. :)

I recommend CWM 6.x since it will make sure you don't get flashed back to stock again, or lose root with an OTA.
[Samsung Galaxy Nexus] ahmadtrabulsi:
cwm

would someone please explain for me what should I do by steps,I don't understand exactly my brb

I want to update my device to 4.2

I have stock updated officially 4.1.2 yakjo jz054k

when i enter the recovery mood I am getting the android logo with the red triangle above

explain for me by steps plzzz
[Samsung Galaxy Nexus] osm0sis:
I did. Step 1) Read the OP. ;)

No but seriously, go read it. It has all the steps. All of them.
[Samsung Galaxy Nexus] ahmadtrabulsi:
I did the method 1 ,on CWM after finished all steps and it gave me update is completed ,i rebooted the device ,I didn't see any change my version stay on 4.1.2
[Samsung Galaxy Nexus] oldblue910:
The 4.2/JOP40C yakju update is now mirrored at randomphantasmagoria.com.
[Samsung Galaxy Nexus] ahmadtrabulsi:
still trying with no result

anyone can help?? i want the update