yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tigrato:
so my only problem could be to have some old app that with the root rights has modded the standard build.prop JWR66V into a non standard build.prop
[Samsung Galaxy Nexus] Shuvo_bd:
try a clean flash. flash yakju factory image using fastboot, after that flash only recovery. then from the recovery flash the ota update and then flash supersu. reboot. done.
[Samsung Galaxy Nexus] papinist:
/me too have problem with this update. Stock rom, only boot unlocked and rooted. Stock recovery.

Tried flixos method but I'm getting and error from twrp (temporarily loaded).

Edit: apparently trying to install this update broke root permission, twrp asked me to fix it
[Samsung Galaxy Nexus] str355:
i'm the same, stock recovery, only rooted.

do the following:-

1) go into the SuperSU app settings and press 'Full Unroot'

2) boot into Team Win Recovery

3) Flash the stock update file

4) flash the SuperSU1.51 zip

5) Reboot
[Samsung Galaxy Nexus] staud:
It would be awesome if someone could confirm that.
[Samsung Galaxy Nexus] tigrato:
understand...

i take a look in the ota downloaded file in \cache ... and WTF ... i have a yakju... but my ota file automatically downloaded is a takju !!

so i don't know why but my yakju gnex want a takju JWR66Y ......it's funny because i flashed two days ago !! :confused:

however... all ok

just copied the latest supersu to be flashed.. the update that i found in \cache .. reboot in recovery .. flashed the update..than without reboot flashed supersu.. that's done
[Samsung Galaxy Nexus] dasansi_13:
Hi flixos, where have you downloaded the update.zip for yajku? I don't find it... Thanks!
[Samsung Galaxy Nexus] wisefreakz:
Would you guys post the updated zip file?

Thankssss
[Samsung Galaxy Nexus] papinist:
worked! Thanks man :)
[Samsung Galaxy Nexus] Daniol71:
Full unroot with SuperSU won't affect data or anything, right?
[Samsung Galaxy Nexus] Peach1200:
Thank you, worked like a charm! :)

Just done it: data and everything else are untouched! :)
[Samsung Galaxy Nexus] pvkiniyan95:
not working with cwm

still doesnt work for me with cwm. does only twrp work???:(
[Samsung Galaxy Nexus] samersh72:
Yes, wifi re-connect issue is fixed :good:
[Samsung Galaxy Nexus] crazykool9:
It just works

My phone is rooted and with CWM.

I just carelessly accepted the ota notification, the phone rebooted, the ota zip auto installed and i chose to fix (mantain) custom recovery when prompted by CWM, voilà, updated, kept root and anything is fine.
[Samsung Galaxy Nexus] :
Hi, inspired by crazycool above i also am on 4.3 rooted with cwm...so when i got the ota, i chose to install.Now when cwm tookover..it said fail in file signature verification...so i chose go back and aborted the update. Any ideas guys?? On d way forward
[Samsung Galaxy Nexus] bcook75:
Update but no update?

Galaxy Nexus running stock Android 4.3 YWR66V, rooted, bootloader unlocked. Just received OTA update notification. Accepted that, applied that. Watched the reboot, app updates, etc., as expected for an update. However, About Phone is still showing build number JWR66V, not Y. Any idea what that is about?

Update: I decided to uninstall ReKey (patch for the security flaw) and then run Bluebox. Bluebox says all is well and patched, so I assume the update did actually install. Just curious about the build number.
[Samsung Galaxy Nexus] staud:
Unfortunately I still have the wifi reconnection issue.

GNex AOSP JSS15Q on Fancy Kernel.
[Samsung Galaxy Nexus] Gbcue:
You have to unroot, install the OTA (sideload or other methods), then re-root.
[Samsung Galaxy Nexus] bcook75:
Does that mean the update didn't install, despite the appearance that it did, or that unrooting and reinstalling would just update the build number?
[Samsung Galaxy Nexus] samersh72:
I think it is caused by the custom ROM, maybe it is still based on the old build of 4.3

sent from my Galaxy
[Samsung Galaxy Nexus] staud:
Seems you're right though I thought that the AOSP rom I flashed yesterday night was based on the newest sources. Today I made a clean flash of JWR66Y via Fastboot and voilà, my first test about the wifi reconnection issue was successful. It auto reconnected when I unlocked the screen.
[Samsung Galaxy Nexus] Daniol71:
I have a problem. My Nexus is stock everything, rooted, unlocked bootloader. I followed these steps:

Go into SuperSU settings and press full unroot

Reboot into CWM

Apply the update zip

Apply SuperSU 1.51 zip

Reboot

The update was installed correctly however when I rebooted SuperSU was gone from the app drawer. Now all my apps that require root are crashing. It's like the phone is "half rooted". I have a simple Root Checker app and when I click "Verify Access" it starts checking but never completes. Anybody have an idea? Should I try to reflash SuperSU? Should I install it from Google Play? Or do I need to re-root my device?

Sorry, found the solution. I had to download SuperSU from Google Play again. My GNex was still rooted but there was no SuperSU to grant access which is why some apps crashed. Everything is working flawlessly now :D
[Samsung Galaxy Nexus] nemesi54:
My question also guys...

Does the update you all refer to is the one from the very first post of this thread?
[Samsung Galaxy Nexus] sakis_the_fraud:
I got the notification for the OTA update.

My GNEX is rooted, i have removed some system apps (gmaps email etc) and installed CWM recovery.

What should i do to install it?

thanks in advance for your help!! :D
[Samsung Galaxy Nexus] hgmichna:
Good idea.

Or into any other good recovery, like one of the ClockworkMod recoveries. But TWRP will certainly work.

That's the point.

Bad idea. Why reintroduce the thing that caused the problem in the first place? It will only kill all future OTA updates too.

Several postings indicated that the OTA update will not work on rooted phones. That is not true. It will only fail on phones that are rooted with SuperSU.

Flash something better. Superuser by ClockworkMod comes to mind, which is open-source. Quite desirable for a program as security-sensitive as this. Just flash this ZIP file: http://download.clockworkmod.com/superuser/superuser.zip

Technical background: What the SuperSU programmer did is write /system/etc/install-recovery.sh and then set its ext partition immutable attribute, a truly remarkable thing to do. It kills each and every OTA update and makes me wonder what else the guy might come up with. Bury landmines in children's playgrounds?
[Samsung Galaxy Nexus] papinist:
[MENTION=2893530]hgmichna[/MENTION]: will Superuser by ClockworkMod act different and allow this OTA update?

[MENTION=1919835]nemesi54[/MENTION]: yes, the OTA update for yakju is the one posted in the very first post.
[Samsung Galaxy Nexus] hgmichna:
I checked whether it uses the immutable attribute, but of course it doesn't. I could not find any other transgression either, so I would bet that it will generally not get in the way of OTA updates. But I could not try it.

But then I have not seen any complaints here or anywhere else by people using Koush's ClockworkMod Superuser. Those who asked for help because of the failing OTA update were running Chainfire's SuperSU, with the exception of those who ran into unrelated causes, like having done other operating system modifications.
[Samsung Galaxy Nexus] papinist:
Since I have my friends' galaxy nexus to update, I could try to install Koush's Superuser instead of Chainfire's one.

Should I simply proceed to full unroot from supersu and then install the new superuser.zip from recovery?
[Samsung Galaxy Nexus] hgmichna:
That would be my recommendation, and please report here how it went.

After you are unrooted, you might as well flash the update before rerooting by flashing superuser.zip.
[Samsung Galaxy Nexus] Vingelstad:
Will I lose root if I ota?
[Samsung Galaxy Nexus] ruben46_:
You will loose gps as everyone hére :)

Enviado desde mi TAB-PROTAB2XXL(4) usando Tapatalk 2
[Samsung Galaxy Nexus] kaushikd:
I was getting error while installing the OTA, was fully on stock but rooted. Finally I managed to install after unrooting. Now I'll have to root again.

Tapatalked via Galaxy Nexus!
[Samsung Galaxy Nexus] sakis_the_fraud:
none???
[Samsung Galaxy Nexus] hgmichna:
Nothing. You cannot install an OTA update to a non-stock phone.

I think it was not a good idea to remove system apps. You could simply have disabled them instead.

If you want the new version, you have to download and flash it completely, which will also bring back the removed system apps.
[Samsung Galaxy Nexus] sakis_the_fraud:
i have freezed them with titanium so it's not a big problem ;)

i read here that some have unrooted their phones in order to install it. should i do the same?

what about the recovery?
[Samsung Galaxy Nexus] papinist:
Ok this morning I tried this on a gnex with the update notification pending:

- from supersu app, do the full unroot

- copied CWM superuser.zip into internal memory

- temporarily boot into twrp

- flash superuser.zip then reboot

- check if root access is working, yes it's working!

- go with the system update, reboot

all is ok, update is installed keeping root access!

So the end of the story is: USE SUPERUSER FROM CWM INSTEAD OF CHAINFIRE'S ONE
[Samsung Galaxy Nexus] flixos:
I've named the file update.zip just to be more clear, the file you have to flash is in the first post of this thread.
[Samsung Galaxy Nexus] hgmichna:
That's better. Perhaps it is safer to unfreeze them before you try the OTA update.

If you used SuperSU, you have to unroot, using the complete unroot command in SuperSU, which also uninstalls SuperSU.

After that you can wait for the OTA update or flash it manually.

Finally you have to re-root. You could flash SuperSU again, but I personally prefer Superuser by ClockworkMod, because it will probably not hinder the next OTA update like SuperSU did. If you follow this line of thinking, flash the file http://download.clockworkmod.com/superuser/superuser.zip instead.

Use either the ClockworkMod recovery or TWRP. TWRP has some more functions and also more strange things, like not finding its own backups. I don't like that, so I use ClockworkMod.

A convenient tool to do all this quickly and easily is the WugFresh Nexus Root Toolkit (for Windows).
[Samsung Galaxy Nexus] sakis_the_fraud:
great info! thanks for your help [MENTION=2893530]hgmichna[/MENTION] !

As i said earlier i got the OTA update, and i am using SuperSU for root access. ;)

I will try it later and see what happens, my phone is on charger now, Fishing superstars drained my battery!! :P
[Samsung Galaxy Nexus] elhana:
Update fails because SuperSU does chattr +i on /system/etc/install-recovery.sh and set_perm(0, 0, 0544, "/system/etc/install-recovery.sh"); fails.

It works if you remove this line from updater-script.

Or you can remove immutable flag with busybox or /data/data/eu.chainfire.supersu/files/chattr.arm.png (this is actually a chattr binary), but I havent tried that.
[Samsung Galaxy Nexus] t3alc:
SuperSU write protects install-recovery.sh, thats why you cant't install OTA using superSU.

Superuser on the other hand don't, and allows OTA to be installed, but you have to reroot after OTA is installed.
[Samsung Galaxy Nexus] papinist:
I must disagree, I tried to unroot the supersu and install superuser, then do the system update.

root access kept.
[Samsung Galaxy Nexus] Quereller:
Unroot and flash earlier update

I have CWM and SuperSU installed and even after a full unroot I was not able to install the current update.

What has worked for me is to unroot, go to recovery, install the second latest update (JWR66V from JDQ39) and finally install this update.
[Samsung Galaxy Nexus] Nexusaurus:
I can gladly confirm that this minor update efectively far from fixing the Wifi Issue, it worsen it even more. Now my phone cant even connect in my home network nor my work network. Galaxy Nexus un rooted, all stock without any modification at all, just like Google intented. running 4.3 JWR66Y
[Samsung Galaxy Nexus] t3alc:
I don't know what you disagree about but are you sure that you have root access?

Superuser app will still be present but it's not sure that you will get root access.

When I installed the OTA i did it from cwm but had to re root and reinstall cwm, but i didn't use the zip in this thread i did it the normal way with OTA downloaded by phone.
[Samsung Galaxy Nexus] colonelcack:
This is what I did and it worked...however, now clockwork mod superuser is saying its binarys are out of date and I can't get it to update using the recovery method (only option it gives me)...

Ideas?

Also, I'm running Twrp 2.3.2.0 recovery...
[Samsung Galaxy Nexus] papinist:
I disagree with the sentence "you have to reroot after the update".

I changed supersu with superuser and then do the update. After phone rebooting, I have the superuser app AND when checked with Root checker, superuser opens and asks if I want to grant superuser access to root checker. And yes, I have root access.
[Samsung Galaxy Nexus] t3alc:
This message is because you don't have root annymore, you only have the superuser app.

You solve it by flashing superuser again.

Strange, because OTA normaly removes root or don't install with root at all.

The post by colonelcack (above) is the way i had it, and in that case root is gone even if it looks like it's still there.
[Samsung Galaxy Nexus] papinist:
yes I agree with you, normally I would have lost root access. All the past updates went ok but after that I have no more root access.

Probably CMW superuser uses some different method because with that, this update goes ok. Perhaps this is a tiny update that does not affect so much the system.

about the post by colonelcack: I have updated 4 nexus, and only one gave me this message. But, after cancelling that message I checked and root access is working. After rebooting, that message didn't show anymore.
[Samsung Galaxy Nexus] dude8383:
I've been having some difficulty flashing this on my nexus.

I'm stock, but rooted and I have unlocked the bootloader. I did this because I wanted to try enabling LTE but turns out its not compatible with Tmobile. Anyways, I received an OTA update for 4.3 because the I had to do a factory wipe. I installed 4.3 without issue, root access still intact.

A while back I received the security OTA and I have been unable to flash it. I have TWRP. I tried the methods you guys listed above and I'm unable to get it to install. Fails each time. I tried unrooting it first, verified with root checker... rebooted into recovery... still fails.

I'm contemplating doing this however the instructions aren't absolutely crystal clear:

2. This is removing quite a bit of script from the file... is that correct? Also, finding the term "recovery" brings up like 5 results... Am I deleting every instance of it??

Any help would be appreciated... I would love to sideload this security update.
[Samsung Galaxy Nexus] hgmichna:
Which Nexus?

What is the error message? Check the log.

This is not very difficult and does not require overly complicated procedures. If you have SuperSU active, the OTA update will fail. If you have made other changes, like LTE enabling, the OTA update will also fail. In most other cases the OTA update will run just fine.
[Samsung Galaxy Nexus] dude8383:
Oh whoops, forgot to key in the "4" after nexus.

The error is:

file_getprop: failed to stat "/system/build.prop": No such file or directory

E: Error excuting updater binary in zip '/sdcdard/Download/1b0ac7dfb2907e5981f1af24b9e5b005712bd4ee.signed-yakju-JWR66Y-from-JWR66V.1b0ac7df.zip

Error flashing zip '/sdcard/Download/1b0ac7dfb2907e5981f1af24b9e5b005712bd4ee.signed-yakju-JWR66Y-from-JWR66V.1b0ac7df.zip

I read in the thread that you have to do full unroot first in order to get this update to work via sideload or OTA... looking over the instructions they say:

- from supersu app, do the full unroot

- copied CWM superuser.zip into internal memory

- temporarily boot into twrp

- flash superuser.zip then reboot

- check if root access is working, yes it's working!

- go with the system update, reboot

Seems like the wrong order of doing it... you need to be unrooted first to install THEN flash superuser... wouldn't that be the right way to do it?

I do not have any LTE enabling. I gave up because it wasn't compatible with TMobile networks.

Having said that, I removed superSU and now I have no idea how to unroot with superwipe... doesn't have the same option to "full unroot"

Thanks for the speedy response man.
[Samsung Galaxy Nexus] hgmichna:
My first suspicion is that you or some LTE enabler procedure mistakenly removed /system/build.prop . I suspect that, because the LTE enabler changes that file.

Possibly the only thing you have to do is to get the original version of that file and put it back in place.

This has been discussed in some threads here. You can use the global or Google search for the file name to find these discussions.
[Samsung Galaxy Nexus] dude8383:
Hey dude. Just to be clear, I made NO CHANGES to the phone after I unlocked the bootloader and gained root access. There is no change to the radio, no reflashes for the radio, nothing has been done.

Sorry to confuse you, I probably should have left that out my initial post here. I'll research how to unroot with superwipe and then trying installing the zip... and THEN flash superwipe again to gain root access.
[Samsung Galaxy Nexus] hgmichna:
No matter why or how the file disappeared, you will have to put it back to make the OTA update work. At least that is my current knowledge.
[Samsung Galaxy Nexus] sakis_the_fraud:
thanks for your help guys!

i finally updated my GNEX!

Although i have some google apps frozen the update worked like a charm!

here are the steps that i followed:

copy superuser to sd

full unroot from SuperSU

reboot

install the ota update

reboot

boot to recovery

flash superuser

reboot

and it works :D
[Samsung Galaxy Nexus] enzippo:
Could somebody provide a updater script file alrealy patched? Thanks.
[Samsung Galaxy Nexus] AndroidBob:
How do I "flash superuser" with stock recovery?

I'm running the stock rom and stock recovery, but want root access. I've been keeping stock recovery so I don't have proboems with OTA. Now I find out that superSU was killing the recent OTA, so I derooted superSU, got the OTA and now want to switch to the cwm su, but I don't see how to do this without a custom recovery. Can someone help?

Thanks.

Bob (Galaxy Nexus)
[Samsung Galaxy Nexus] hgmichna:
A convenient way could be the WugFresh Nexus Root Toolkit, which does it nearly automatically for you. It also allows you to boot into a custom recovery of your choice temporarily, so you could even keep the stock recovery, if you wanted to take it that far.
[Samsung Galaxy Nexus] AndroidBob:
this looks like a windoze package

Thanks for the suggestion, but this looks like a windoze package and I'm a linux guy. I'm quite comfortable with the linux command line, although I've never quite figured out exactly how the andrdoid boot/flash/process works (just need to translate all the terminology to linux). I tried adb pushing the cwm apk and su binary, but upon reboot, superuser tells me I need to update the su binary, but only gives me a recovery option to do so, which, of course I can't do. I downloaded the su 3.1.3 binary and pushed it directly, chmod'ed it to 06755, but superuser still tells me I need to update the binary. I'm close- but I know I'm missing some obvous little bit of knowledge here.....

thanks,

Bob
[Samsung Galaxy Nexus] andQlimax:
Extract the Superuser flushable zip, and look the commands in the updater-script.. The commands are Linux similar...You need push su binary, Superuser apk, and since android 4.3, you need to push also the modified install-recovery sh that has been modified to launch the su daemon.. Just look the Superuser zip

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] staud:
After some days of use I have to correct myself. The wifi bug isn't fixed. Sometimes the Galaxy Nexus reconnects automatically, but most of the time it doesn't. And why hasn't Google even acknowledged this issue? WTF. That totally sucks.
[Samsung Galaxy Nexus] Thadd:
Brain Dead Easy

I just wanted to provide a brain dead easy way to fix this issue.

After reading this thread y'all have figured out supersu is not letting the OTA upgrade to work.

I also remember seeing an upgrade for supersu. I had the issue of not upgrading from jwr66v to jwr66y and I had supersu 1.5 so I went ahead and upgraded to supersu 1.60 and forced the OTA upgrade, and it went perfectly.

So apparently the author of supersu is on top of this issue and has fixed the problem. I did lose root, but easy enough to fire up Wugs NRT and re-root.

Thanks for all your help and thanks to the author of supersu Chainfire.
[Samsung Galaxy Nexus] eric_22:
i have the same situation .

when i install the zip through recovery mode,

it told me that warning: no file_contexts assert failed "/system/build.prop"

and then it aborted

do you or anyone find the solution?
[LG Optimus G (International)] ahm12:
Whats up guys,

I bought this optimus G(at&t) few days ago on craigslist but never bother testing it.

now today i realized there is no sound from earpiece during phone calls. even if i turn on the speaker still no sound..The other person cant hear me either..

Then i tried using skype , and the calls are working absolutely fine both on earpiece and speakerphone..

So i feel like its some kind of software issue because the hardware itself is fine.

does anyone know how does warranty works on phones bought on craigslist??

or anyone else faced similar problem.. (i already did a factory reset , it did not solve the problem)

i am 100% sure this phone is not 1 year old..
[LG Optimus G (International)] GRG13:
Try to reflash stock rom or flash a custom rom(first root &unlock bootloader) to see if you still having this.problem.Otherwise send it back for DOA

Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
[LG Optimus G (International)] kimitza:
Try the at&t section..we can't help you much here..

Sent from LG E975 pwd by CM 10.2
[LG Optimus G (International)] ahm12:
Admins you can lock this thread..

I didnt even knew there was a at&t section..
[Android Q&A, Help & Troubleshooting] anoop18:
i have a gt-i9003 running on gingerbread.DDMF1 v2.3.6

:crying:my baseband version is unknown, imei unknown, imeisv is unknown..

search the phone for the efs file which is not to be seen... what do i do..pls help urgent..:crying:

P.S. i dont have the file efs..nor do i have a copy of it.. not even nav_data.bin my bad... im a complete noob.. please guide me step by step

maybe it may have been posted before..i did search i spend my 3 last days searching but couldn't find solution

.
[MDA II, XDA II, 2060 ROM Development] BraveDruid:
I am on O2 user and have just upgraded from 1.60.00 to 1.72.00.

Since upgrading I find that when I receive single alerts in the start bar rather than getting the correct symbol (e.g. a message symbol if I get a text or a phone symbol for a missed call) I get the multiple alert speech bubble symbol instead. What actually happens is at the point the event happens the correct symbol appears and then it merges with the O2 symbol and becomes the speach bubble symbol. Any ideas how I can sort this? If I have to I'm happy to lose the O2 symbol all together as I can see that I need it!

It's only a small issue but it's becoming increasingly annoying and I would be very grateful if someone could suggest a fix.

Many thanks

David
[MDA II, XDA II, 2060 ROM Development] Griffy wiffy:
go to the following folder on you PPC

"\Windows\Mobile Solutions\O2ActiveUI\Modules\Connections" and rename the connections.exe file (anythinig will do).

Then soft reset.
[MDA II, XDA II, 2060 ROM Development] BraveDruid:
Thanks for the help.

I don't actually have a 'Mobile Solutions' folder in Windows. I did find "Windows\V2R\O2ActiveUI" In that I renamed O2ActiveUI and sure enough when I reset it the O2 branding had disappeared :)

However, I now get a warning message when the phone boots up complaining of the missing file. Can I stop it trying to load the O2 UI altogether?