yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] crazyykw:
Hi guys !! I have a galaxy nexus which is rooted , unlocked and had a clockworkmod recovery. It was yakju build IMM76I . I had kept it completely stock with no patches for gps, themes or anything/ Yesterday i downloaded the zip file for JB update freom this thread for yakju build. it flashed fine without any problem. But i didnt wipe anything.Everything was working fine since 12 14 hours . Today morning i tried to connect to my hospital wifi and my phone rebooted. now its not booting into android/ ive tried removing the battery and all. i tried to get ito recovery but it shows a red android with exclamaion mark and nothing. Kindly help please!!! tell in such a way that a noob like me can understandd...:crying::crying:

Can i try this?? try to fastboot clockwork mod recovery temporarily and then restore my backup of 4.04 yakju build??
[Samsung Galaxy Nexus] hboyer:
thanks for your support! The only issue is that I already installed a different kernel.

can anybody extract that boot.img from a nandroid backup of the latest 4.1.1 for me?
[Samsung Galaxy Nexus] xxdadragon:
Can't Upgarde My device even on OTA

I just got OTA update on my device and It starts downloading 8.5MB of Zip file after that It reboots and starts to install the updates, but mid way while wiping the Cache it hangs and shows a dead android with red triangle.

I had a ICS 4.0.2 after which I flashed Jelly bean 4.1 from xda-source. Now I am on 4.1 Kernel 3.0.31-ge8deOe2 ....Build no. JRN84D. My phone is rooted and I have CWM.

Please help me to update my deivce.... and yes I am semi n00b...:D
[Samsung Galaxy Nexus] efrant:
You must have changed the ApplicationsProvider.apk file. You will need to get a copy of the original and copy it to your device. (Instructions on how to do this yourself are in the first post.)

The Internal Storage folder that you see in MTP is /sdcard.

You shouldn't have to wipe when updating, so that was not the problem. You probably have an app that is not compatible with JB. For me it was LBE Privacy Guard that cause bootloops.

The red android with exclamaion mark is the main stock recovery screen. Android re-flashes the stock recovery on every boot unless you delete the responsible file.

So, yes, boot into fastboot mode, plug into a PC, and boot CWM. Then you can restore your 4.0.4 backup. If you know what app is causing the problem, you can uninstall it and then upgrade again.

I will try to get one for you if you need it right now. Otherwise, the JRO03C factory images will be posted here soon, so you can easily get it from there.

Download the correct update from the first post and apply it using CWM. That way we can see where it fails, and fix it.
[Samsung Galaxy Nexus] efrant:
I have no idea what could be causing those issuses. Did you restore anything from a backup? Did you restore anything from Titanium Backup?

As for how to easily fix, if you've tried fix permissions from within CWM, then I don't know what else to suggest. Prob best to wipe and start again.
[Samsung Galaxy Nexus] tailsthecat3:
Thanks for this. Since Android's inception, I've never used local search but I gotta have the latest sw. Thanks again.
[Samsung Galaxy Nexus] efrant:
I've attached the stock 4.1.1 kernel, as well as an insecure version (for anyone who is interested).

I did not compile the insecure one myself; I got it from bigxie and I just packaged it up for CWM.
[Samsung Galaxy Nexus] bishop41466:
Yeah I have restored a bunch of stuff from Titanium Backup, adb backup. Sigh.. guess I will have to wipe the data again :( Thanks for answering my question!
[Samsung Galaxy Nexus] efrant:
When switching ROMs, it's usually safe to restore user apps and user app data with TB, but not system apps and system app data.
[Samsung Galaxy Nexus] sabhain:
Update (both OTA and CWM) fails with status 7

Thanks for your help. I've deleted my question because I was wrong about what version of ICS I was running, and didn't want to send others down the wrong path.

Thanks very much for all of your efforts here.
[Samsung Galaxy Nexus] efrant:
Are you using CWM 5.5.0.2 as stated (in red) in the first post?
[Samsung Galaxy Nexus] segv11:
Anyone have any feedback on the stability of:

CWM 5.5.0.4 (the most current version of the non-touch CWM)

TWRP 2.0 (a really nice recovery for Nandroids, but I don't know how it fares for flashing ROMs/OTAs)

I keep several recoveries handy for different purposes, but I'm curious if some of the newer recoveries like TWRP are stable enough for flashing.
[Samsung Galaxy Nexus] efrant:
CWM 5.5.0.4 is fine - it is the same as 5.5.0.2, but for toro. Sorry I wasn't more clear before. I'll make the change in the first post.

Can't comment on TWRP.
[Samsung Galaxy Nexus] deutscher.bund:
First off, thank you soooo much OP for this truley amazing :D

Secondly I appologize if you've answered this above, i read through 10 pages and I'm running out of time, have a flight in the AM tomorrow :*(

I'm both rooted and have an unlocked bootloader, I followed steps very carefully and applied my respective update zip (yakjuux ICL53F), problem is when I reboot no jelly bean is there :( do you know what I'm doing wrong?

Cheers,

Deutscher
[Samsung Galaxy Nexus] efrant:
There is no Jelly Bean for yakjuux -- it is only for yakju and takju at this point. You need to flash takju/yakju IMM76I by following this, then apply the JRO03C update.
[Samsung Galaxy Nexus] deutscher.bund:
on it now, and I apologize for that. Thank you once again!

---------- Post added at 09:43 PM ---------- Previous post was at 09:01 PM ----------

I love you I could cry :*(

Thank you soooooooooo much for all your hardwork
[Samsung Galaxy Nexus] Technical:
OTA update failed

I'm with a Samsung Galaxy Nexus 4.0.4 IMM76I root and with CWM and could not update using any OTA methods posted here.

I've used yakju JRO03C from IMM76I: http://android.clients.google.com/pa...I.f946a412.zip

I've tried with Bootloader locked and then unlocked.

I'm not at USA, so, I did not have Google Wallet in my stock Google ROM.

Error:

assertfailed: apply_patch_check ("/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869 ..."

Status 7

Whatever this means...

By the way, I was offered the OTA by the system itself twice. One with Bootloader locked and the other with it already unlocked.

Both official OTA failed.

I can't understand why the OTA is officially offered and I could not apply it.

At both situations I was plugged on, battery full, wifi connected.
[Samsung Galaxy Nexus] sabhain:
Yes, I was using 5.5.0.2. My problem was much more basic than that.

While my recollection was that I had gone from yakjuxw to yakju back in April, I had in fact gone to takju. Once I got the right update file from your update post (for takju), the upgrade (via CWM 5.5.0.2) went smoothly the first time. I'm not certain why the OTA update didn't take, but I wasn't able to grab the error message prior to figuring this out.

Thanks again for your help.
[Samsung Galaxy Nexus] Matt08642:
you cannot apply the OTA if you don't have stock recovery.
[Samsung Galaxy Nexus] Mitchenjeep:
OTA Failed

Verifying current system...

file "/system/app/Gmail.apk" 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/app/Gmail.apk", "21177453e64d114f4c208720a0f57d9765665a1d", "8c4ca9a52a3849b20f12219e7fc5a29b4ebe1ad1")

assert failed: apply_patch_check("/system/app/Gmail.apk", "21177453e64d114f4c208720a0f57d9765665a1d", "8c4ca9a52a3849b20f12219e7fc5a29b4ebe1ad1")

E:Error in /tmp/sideload/package.zip

(Status 7)

Installation aborted.

Just Busybox is installed in /system/bin.

Thank you for help.
[Samsung Galaxy Nexus] ibraheeemz:
i am using 4.1

I tried to force update using "clear data" for google framework and then checking system update... I received notification for the system update... and download started automatically... checked in the logcat and below is the source:

http://android.clients.google.com/p....signed-takju-JRO03C-from-JRN84D.edfff6d3.zip

download completed successfully and it also said "verified" ...after I confirmed to restart the update... it booted into recovery... but installation aborted itself, saying verification failed...... I am using CWM... I think thats the reason for the upgrade to abort...and I should be on the stock recovery... any suggestions???
[Samsung Galaxy Nexus] tailsthecat3:
Flash the stock recovery then try running the update again? /system would need to be stock.

-----------

I replaced all the stuff I deleted in /system then flashed the update with cwm. Then I had to disable/rename the 'install recovery on boot' file and flash cwm again.

Can't wait to get the toro update file to JB and upgrade this way, so easy.

Thanks again.
[Samsung Galaxy Nexus] efrant:
From post #2:

The has been address many times in the thread.

That's not what he was doing.

You must have modified your Gmail.apk file. Replace it with the stock one as per the instructions in the first post. As well, if you have busybox installed in /system/bin, you will have the same issue with other files (like mentioned above), so you will have to replace though.

Yes, for the update to install OTA, you need the stock recovery -- if you want to install it, you need CMW. This was discussed in post #2.
[Samsung Galaxy Nexus] mulder21:
Hi,

I had an similar problem, but with "assert failed: apply_patch_check("/system/bin/iptables"...."

I solved my problem with the method from Revoked in his post i ignored the first steps and started at step 4 but I chagend step 7 in "Remove the line saying: assert(apply_patch_check("/system/bin/iptables"......." or for you the line with GMail.apk. Then I updated my System and it works fine (using it 10minutes ;) ) I know this might not be a professional way of solving the problem, but it works. ANd in case this solution won't work you can do a factory reset.

Greetings

Jan
[Samsung Galaxy Nexus] efrant:
A factory reset won't do anything. Factory reset erases /data. It doesn't not do anything to /system. (An easy way to get /system back to stock is to flash the factory system.img from the same build your are using, but it will replace any changes you made to /system.)

As I stated before. Updates require all the files in /system. If you change them, fine: you either have to replace them, or do as you say and remove the assert check. However, by removing the assert checks, you could potential be cause issues, as the update may patch the existing files thinking they are stock files.
[Samsung Galaxy Nexus] mulder21:
Oh I thought a factory reset would change everything to stock, sorry.

How do I flash the factory system.img? I now have 4.1.1, do i have to go back to 4.0.4? because it seems it wasn't really clever to ignore the message with iptables, i have some problems with switching between vpn and wifi and i think these problems are caused by the iptables file.... (I used a vpn app which edited the iptables file i tink, now i have a app for vpn without root)
[Samsung Galaxy Nexus] Thorgoth:
hmmmm......after about 3 months i decided to re- unlock the bootloader from my gnex in order to finaly apply the IMM76I update and then the JB one...

(just as a heads up i originally was on yakjuxw and used efrant's guide to switch to yakju ... this time i only unlocked the bootloader did not root the phone.. )

so unlocking was ok through the cmd commands..also installed the 5.5.0.2 cwm non touch version and for start i used the yakju IMM76I from IMM76D to get into the latest 4.0.4 update...that was done in one go no probs at all...

after rebooting the phone i connected with my wi-fi router and got a notification for 4.1 update (140ish mb i think)..

now this time the installation failed (i did not see the cwm menu!?) so i download it manualy copied to my gnex reinstalled the cwm recovery and tried to do it the same way as the IMM76I patch....but it failed..the error i got is

" installing : /sdcard/f946a4120eb1.signed.yakju-JR003C-FROM-IMM76I.f946a412.zip

finding update package

opening update package

installing update

verifying current system

assert failed : apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/radio12583168:8b7209e8c3a6d73254as92069aabe693beffd6bd:12583168:47b1799049e32ef2c0746ca716f5277a83768b96")

E:error in /sdcard/f946a4120eb1.signed.yakju-JR003C-FROM-IMM76I.f946a412.zip

(status 7)

installation aborted "

i mean...come on...

it worked with the "small " patch why not with the JB one...

and again i did not touch anything in my gnex....no root not modified any file/folder..

is there any jb stock rom to try and install?

damn i miss my nexus s..was so much easier.. :(
[Samsung Galaxy Nexus] efrant:
Right now there is no factory system image for 4.1.1. Which assert checks did you delete? If it is only one or two files, I can pull them from my /system, post them here, and you can you can just replace what you have.

As is stated in the second post, you need to have the stock recovery for the update to install OTA. If you want to flash it yourself, you need CWM.

The reason you are getting that error, is because you have the wrong radio flashed. (You probably did not flash it when you switched to yakju, as I had labeled it optional. However, there was a note a the bottom, saying that if you do not do the optional steps, you will need to do them before the update will install...)

Flash the XXLA2 radio and then you should be able to flash the update in CWM.
[Samsung Galaxy Nexus] Mendeleev:
This all worked fine for me (method 2)

I'm just wondering, is it possible to flash these updates using the "fastboot update" command too?
[Samsung Galaxy Nexus] efrant:
Although I have never tried that, I do not think that is what the fast boot update command is used for. Just logically, it would not make sense that fast boot would be able to flash an update file made for recovery.
[Samsung Galaxy Nexus] Thorgoth:
well once again you were right efrant..

that optional command was not that optional afterall for me :)))

thank you for the your help...

from now on i will not skip any optional commands....hahahahaha

p.s.

i miss the lwp i see in youtube vids...help??hahahahahahah
[Samsung Galaxy Nexus] nwadams:
In case any one cares it is possible to flash the update from stock without root or a unlocked bootloader or a custom recovery. I was able to put the patch file on a usb drive, and plug a usb drive into the galaxy nexus (using a micro male to usb standard female cable) and then go to recovery and select apply update from USB drive and then select my zip.
[Samsung Galaxy Nexus] mulder21:
That sounds good, i deleted the asset check for /system/bin/Iptables only. If you post it here i would be grateful. For the next OTA the system will think everything is stock when i replace my file with yours?
[Samsung Galaxy Nexus] efrant:
That is only possible with the new Jelly Bean stock recovery. So if you are updating from JRN84D to JRO03C, then yes, that works. It doesn't work otherwise.
[Samsung Galaxy Nexus] efrant:
File attached. And yes, the next OTA should see that you are stock, assuming you make no other changes to system files. (Make sure when you copy my file over to your /system/bin that the permissions are correct (like the other files in /system/bin).
[Samsung Galaxy Nexus] Technical:
But the first post says I need to have CWM (custom recovery) not touch (but also not the stock recovery).

I've installed the stock recovery with Android Root Toolkit 1.5 and it just does not boot on recovery...

ROM Manager does not have an option to flash the stock recovery again...

How can I do it?
[Samsung Galaxy Nexus] osm0sis:
That means you can't just let the phone apply it itself, you have to update from zip via CWM if you don't have stock recovery.
[Samsung Galaxy Nexus] efrant:
I don't think you fully read everything:

there is a difference between getting the ota notification and installing it vs using the file and updating it yourself. The former requires the stock recovery if the build you are using, the latter requires cwm 5.5.0.2 or 5.5.0.4.

Edit: what osm0sis said. :)
[Samsung Galaxy Nexus] Technical:
And of course I've tried it and it fails with the same error...

That's the problem.

I've also uninstalled avast! anti-theft if this could bring any trouble.

Thanks for the support.

Anyway, I've tried with both CWM and the stock recovery and both failed.

But seems that I'm not being able to proper flash the stock recovery back again.

I've tried also Galaxy Nexus Toolkit (v 7.4 option 6). When I boot in Bootloader the flash start and never stops...
[Samsung Galaxy Nexus] efrant:
If you are using a toolkit, you should ask in the appropriate toolkit thread. I do not condone using toolkits until you've figured out how to do things manually.

The problems you are having could easily be resolved if you flash or boot CWM manually.
[Samsung Galaxy Nexus] mulder21:
Thanx for this. I changed the files and Thema permissions are set like the other system/bin files. Is there a possibility to check whether everything is fine now? For example installing the update again?
[Samsung Galaxy Nexus] Mitchenjeep:
Tk you very much for your help. I spared lot of time with you.

OTA is installed but I have no boot animation, just a cross.
[Samsung Galaxy Nexus] efrant:
The glowing cross is the new boot animation.

Seriously? These updates are for the Galaxy Nexus...
[Samsung Galaxy Nexus] gabster21:
Anyone else having a problem with maps keeping the phone awake all the time? This wasn't the case in ICS.. maybe it has something to do with google cards or google now. I tried killing the maps process but it still comes back to wake my phone.

Any ideas?
[Samsung Galaxy Nexus] efrant:
Let's try to keep this thread on topic. For bug issues, please post in a thread like this or this. Thanks!
[Samsung Galaxy Nexus] Technical:
Efrant, sorry to be a pain, but I AM booting into CWM (not Touch version) but I'm not being able to apply the OTA saved in my disk (.zip file). The error is always the same. Other functions of CWM works (backup, restore...).
[Samsung Galaxy Nexus] efrant:
If you are getting this error:

Error:

assertfailed: apply_patch_check ("/system/bin/gzip", "afdda757b27b444f525a0f41726d2c1a83012869 ..."

Status 7

Then, as has been mentioned numerous times in the thread, it is because you installed busybox into /system/bin. You either need to re-flash the IMM76Isystem.img file, or get the 3 files that were changed by your busybox installation and replace them with the stock ones from the system.img. (The three files have been mentioned, as was the instructions on how to extract the files from the stock image. Everything is in this thread. If you can't be bothered to read the thread, then I suggest you backup up your data off your device, follow the steps in the first post of the "flash" link in my signature to flash yakju or takju IMM76I, and then apply the yakju or takju JRO03C-from-IMM76I update from this thread. That is the simplest way.

For future reference:

- If you want busybox, install it in /system/xbin, NOT /system/bin

- Do not use toolkits
[Samsung Galaxy Nexus] highvista:
I had the same error message when trying to update via either the OTA or the ZIP file. The problem was that I had BusyBox installed, which replaces the stock "/system/bin/gzip" program. I had to use fastboot to flash the stock "system.img" file from IMM76I to restore the /system/bin directory before the update would work. I tried uninstalling BusyBox, but that didn't work properly, so I wouldn't recommend it.
[Samsung Galaxy Nexus] mercilessauce2:
I've the 4.1 version, and trying to update to 4.1.1, the kernel, radios, etc is untouched, only the recovery is cwm 5.5.0.2, now I go into cwm recovery and try to apply the takju 4.1 to 4.1.1 update and it fails to flash, it gives me an error, I'm not sure what I'm doing wrong, and that's why I'm here, trying to figure it out.
[Samsung Galaxy Nexus] efrant:
Saying "it gives me an error" does nothing for us. If you want us to help, you need to write out the full error...
[Samsung Galaxy Nexus] mercilessauce2:
yes, here it goes:

assert failed: apply:patch_check("/system/app/ApplicationsProvider.apk","08db09578758c61cf5c8ec895b1331a5fa4cc349", "512784ba869d55f3cf2d291baaa5f6a0aa90b960")

E:Error in /sdcard/edfff6d328f1.signed-takju-JRO03c-from-JRN84D.edfff6d3.zip

(status 7)

installation aborted
[Samsung Galaxy Nexus] efrant:
So that means that either you, or one of your root apps, modified your /system/app/ApplicationsProvider.apk file. Replace it with the attached and try the update again.
[Samsung Galaxy Nexus] efrant:
By the way, I hope you are not trying to install that update on a non-stock ROM...
[Samsung Galaxy Nexus] mercilessauce2:
It's just the Jelly Bean version from I/O that was released last week or so, it must have been a root app modifiing the file or something, I'll try with that file.
[Samsung Galaxy Nexus] efrant:
Just as long as you weren't using any ROM by bigxie... He had the 4.1 ROM posted and labeled as stock, but he deodexed it, so it is NOT a stock ROM.
[Samsung Galaxy Nexus] mercilessauce2:
ah, I think that's the problem then :X

http://xdaforums.com/showthread.php?t=1737849

should I use this thread then?
[Samsung Galaxy Nexus] irha:
Spot on! Is there a separate update package for the deodexed rom, or do we need to flash the full package?
[Samsung Galaxy Nexus] efrant:
I guess. You will still not be stock though (although it will look like a stock ROM).

What do you want to do? If you want a deodexed but otherwise unmodified ROM, yeah, flash the link quoted by mercilessauce2. If you want to be on a stock ROM, follow the instructions in the "flash" link in my sig, then apply the update from this thread.
[Samsung Galaxy Nexus] mercilessauce2:
so if i follow bigxie thread I've to constantly flash new updates manually, while if I follow your guide I'll get them from google via OTAs but have to wipe the device?
[Samsung Galaxy Nexus] efrant:
If you flash/flashed bigxie's ROM, you are not stock, which means that there are NO updates. When the next stock update is released, bigxie will put together a new ROM, and you flash that.

If you follow the steps in the "flash" link in my signature, you will be on a stock ROM, and updates can be flashed either: a) when you get them OTA, or b) as soon as it becomes available here on XDA (which is usually much sooner than most people get it OTA).
[Samsung Galaxy Nexus] BlueBagodah:
Hi Efrant (or whoever has any ideas for me.)

I have an yakju device (GSM), Unlocked bootloader, on 4.0.4, non-root, with stock recovery.

I want to keep the stock recovery, but flash this OTA, as my OTA hasn't come through yet...

If I follow the instructions in your method 2, then used fastboot to flash the recovery that came with 4.0.4, would that still work?

---Alternatively---

If I do get the OTA update, if I do a factory reset, will it reset to 4.1, or 4.0.4?
[Samsung Galaxy Nexus] efrant:
Use method 2 AS IS. It does not flash CWM - it just boots it. Once you reboot (after flashing the update), the 4.1.1 stock recovery will automatically be flashed for you.