yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] deusfaux:
I don't like that this is the second update in a row I've had to manually work and fix, even though I run stock + root.

OTA update didn't seem to work, build wasn't reported as the newer one in about phone,

had to fastboot and update system.img myself.

What's the deal? Why aren't OTAs working for me with this phone?
[Nexus 4 General] hgmichna:
It patches a whole range of files. It is small because it does not contain all those files. Instead it contains only the patch instructions.

"Significant" is up to interpretation.
[Nexus 4 General] kzakhar:
I just got the update today. A bit late, but anyway :)
[Nexus 4 General] hgmichna:
Same for me. The cause is most likely that one or two of your programs with root rights modify the system such that the next OTA fails. The OTA patch first checks all system files to be patched. If just one is modified, the patch fails and does nothing.

In my cases the culprits were StickMount (altering debuggerd) and SuperSU (introducing and making immutable the file install-recovery.sh). Not sure if StickMount is actually OK and I made some mistake, but both come from the same author: Chainfire. I believe he is actually a fine programmer, but now he is running the risk of becoming notorious for blocking OTA patches.

Let's see how the next one will go, possibly the update to Android 5, and that will probably not be a small patch, but a full-size new software package.
[Nexus 4 General] deusfaux:
So why did all my past OTA's across the previous 2 Nexus phones even when rooted, work just fine?

p.s. only root programs I use are SuperSU and TitaniumBackup
[Nexus 4 General] Blockberd:
It is a "small" security patch only. That's it.

Yes, it is the stock build.prop. Unfortunately you cannot flash my ZIP. You have to unzip it and replace the file manually, reboot, flash update and maybe flash LTE enabler again (no knowledge about the LTE enabler).

It is not working because of SuperSU (does anybody even read the thread? :rolleyes:) which changes a file permission. You simply unroot in SuperSU, apply the update, install SuperSU again and you are good to go. (Did somebody count o how often I gave this exact instruction? ;()

I assume that Chainfire wasn't aware of the problem he causes with his permission changes of the one file. I would bet that he is scratching he head already on how to solve that. There were some significant changes in 4.3 reg. root.

Because the changes to root which forced Chainfire to change permission of a file came with 4.3. So they are not even half a year old.
[Nexus 4 General] Rusty!:
Root in 4.3 isn't like root in previous versions. The SELinux changes mean that su now has to be run as a daemon, and the only way to call that on a stock handset is to modify the install-recovery.sh script that is run on start up. As this file is not what the update expects it to be, the install will fail.

Except on CWM it seems, as that installed it just fine for me (I use CWM superuser and recovery).
[Nexus 4 General] Kendaihou:
I received the OTA update a couple of days ago so I don't know if it is just me or not but my battery somehow has gotten way better than it was when I updated to 4.3 and phone is running way smoother. I know the update was just security fixtures but did it have anything to do with the battery and such?

Sent from my Nexus 4
[Nexus 4 General] Blockberd:
Do you know your previous build by any chance? The JWR66V to JWR66Y update only did security related changes. Some people mentioned that the update from JDQ39 (4.2.2) to JWR66V (4.3) improved battery life. That could be possible because a new radio and kernel got flashed.
[Nexus 4 General] papachango:
At the end I flashed the full image!

Thank You very mutch!
[Nexus 4 General] vishal007:
Wasn't this thread itself an assumption till yesterday. He is true read some news out there!
[Nexus 4 General] ceejay83:
The freezing problems exist on AOSP built roms which are JSS. Unless AOSP is JWR now, I don't see how this fixes the bug :confused:
[Nexus 4 General] Fatherboard:
OMG, new update!
[Nexus 4 General] hp420:
what??? tmobile's page isn't reliable enough for you?? this was, after all, the original source!

http://support.t-mobile.com/docs/DOC-5034
[Nexus 4 General] SinisterSHO:
So, I'd I'm rooted, will I get this ota?
[Nexus 4 General] BadarChaudhry:
I got RMA yesterday and it was shipped with 4.2.2 but i received notification few min after i switched on and i didn't install right way because Google back up was installing my data, But after like 2 hours when i clicked on restart and install update. nothing happened and it disappear and now when i check for update. all i get is i'm on latest update which is 4.2.2.
[Nexus 4 General] scandalousk:
I think he was referring to the fact that he said that the new build fixes the freezing issues while there's no proof of that.
[Nexus 4 General] akshayguptaus:
Not even related to this thread. Read man.
[Nexus 4 General] fernandezhjr:
I'm not questioning if the update is real or not. I'm trying to get specifics of what fixes are included and what devices are getting it that are not speculation.
[Nexus 4 General] hp420:
ahhhhh, ok. My mistake :D
[Nexus 4 General] kzoodroid:
It says "security" fix with no other information given. Speculation is that it's a fix for the bitcoin bug and nothing more.
[Nexus 4 General] fernandezhjr:
That is what I also read. It doesn't seem to make sense to me that we would get a new version number for a small security patch if that is the case.
[Nexus 4 General] BadarChaudhry:
It is related because i'm not getting 4.3 update so i quoted the guy who says maybe Google is holding 4.3 in favor of 4.3.1 so in that case it may be same thing for me. Its open forum and you need to understand what the post was about.
[Nexus 4 General] eng.Colombo:
Wooow seems nice !, does anyone already received this update ?
[Nexus 4 General] bozzykid:
Only one person in this thread has and they didn't provide any details so it is likely no one has. It seems Galaxy Nexus users are the only ones to actual report the update so far.
[Nexus 4 General] FlorinXstyle:
I receive it ! But i lost it after i restart my phone :(
[Nexus 4 General] OnlySkills:
I received this update yesterday at around 8PM. It is very small (1.8MB). The version now reads JWR66Y. It is Android 4.3 still. No other noticeable changes.
[Nexus 4 General] SmXtrem:
Screens please than :)
[Nexus 4 General] maddoggin:
anyone have a link to stock deodex rom? the latest one? not factory images but stock deodex!
[Nexus 4 General] Minker17:
So I'm on Stock (JWR66V) + Root and getting prompted for an update. I'm assuming running this will either update and break root, or fail because of root? Is this correct?

What is the preferred method of doing this, then, as I thought rooted phones didn't get prompted for OTA's?
[Nexus 4 General] Chochiwpg:
If your phone is rooted but has the stock recovery than you will get prompted for the OTA and it will update and install.

I would assume that after install you will lose root though.
[Nexus 4 General] Blockberd:
*cries a river*

Some may think that we already covered every possible scenario (and we did).

As people tend to be lazy reading all the posts, I am also being lazy and just forward you to this: http://xdaforums.com/showthread.php?t=2145848

Head over to section B there. That should do it.

And yes, it will "break" root. Simply flash SuperSU again right after update is flashed.

---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------

If he is using SuperSU (and I think he does) the OTA will fail without unrooting first.
[Nexus 4 General] Chochiwpg:
Ah ok, good to know.

I downloaded the factory image and with Ubuntu I flashed the flash-all.sh file that comes with the factory image. Flashed my device and then flashed a custom recovery and SuperSU and I was back up and running on 4.3 with root and custom recovery. Pretty simple. :good:
[Nexus 4 General] Blockberd:
There are different ways to achieve the goal.

Coming from a previous 4.3 build with root:

1) Simply unroot, apply OTA, root again; keep data and apps

2) Flash system.img from factory image in fastboot; keep data and apps

3) Flash everything (except userdata) from factory image (but why?!); keep data and apps

4) Flash full factory image; lose data and apps - cleanest way

Coming from 4.2.2 and earlier with root:

1) Execute OTA; keep data and apps

2) Flash system.img, boot.img, kernel.img and radio.img from factory image; keep data and apps

3) Flash complete factory image; lose data and apps - cleanest way

Keep in mind that I did not consider any custom ROM or kernel here. Some OTA may be successfull if custom kernel is applied and some may not. It depends on which files the OTA actually patches or flashs.
[Nexus 4 General] sordna:
doesn't flash-all delete your apps and data ?
[Nexus 4 General] Blockberd:
If it flashs the userdata.img, yes. That's why I usually suggest one of the ways posted above.
[Nexus 4 General] Kendaihou:
If that's the case then it's starting to make sense. I'm pretty sure I was on the JDQ39 build not exactly positive but pretty sure. Ya my battery got way better. From 2-3 hours SOT (3 hours if lucky) to close to 5 hours SOT. Thanks for clearing it up.

Sent from my Nexus 4
[Nexus 4 General] Chochiwpg:
Yes it does, it's a complete and fresh install. But I have all my pics and videos backed up on G+, all my music backed up on Google Music. All my apps are backed up on Google Play so I just have to redownload.

Everything else is just setting up your homescreens and logging into your apps again. Same thing you would do when flashing a new ROM after a factory reset.

You just have to re-root afterward, if you want root that is. It's not necessary if you don't want it.
[Nexus 4 General] cloney:
I had previous 4.3 build with root and i did step #3 along with the hybrid LTE modem flash after regaining root and custom recovery. Now All i am getting is 2g/EDGE ! Do you have any clue why I am only getting edge??? Please help if anyone has any idea.

Thanks,
[Nexus 4 General] Blockberd:
You flashed radio, too? AFAIK the radio .33 is required and not .84 (or was it .83?) for LTE. You may want to flash the radio .33 again.
[Nexus 4 General] cloney:
I flashed to the .84 radio and then after gaining root and CWM, i flashed it back to the .27 hybrid LTE radio. I tried just the .27 and .33 radio also. No dice.
[Nexus 4 General] Blockberd:
Sorry. I am out. That's pretty much all I know about LTE enabler. Maybe you need to look out for another way to enable LTE on the N4.
[Nexus 4 General] cloney:
It's only part of the problem... I'm not even getting HSPA+ anymore...
[Nexus 4 General] Blockberd:
Try to just flash system.img, radio.img and kernel.img again from factory JWR66Y and leave the LTE enabler away.
[Nexus 4 General] sordna:
Ok, for most people losing apps & data is a big deal, so better put a big disclaimer "YOU WILL LOSE YOUR DATA" when talking about the flash-all script :)

Btw, is there any way to backup and restore just the homescreen setup? Asking cause that's probably the most time-consuming task when setting up fresh; so far I rely on screenshots (if I remember to keep them up to date) for how I set up my shortcuts and widgets.
[Nexus 4 General] Chochiwpg:
I use Nova Launcher, it has a backup option. So if you ever decide to flash ROMs in the future, just install Nova and your apps then restore your backup in the Nova settings and you got all your homescreens back. But if you do a fresh install (meaning a full clean wipe of the device) then your backup will be wiped as well.

You will lose your data by using the flashall. It's like buying your phone and opening the box for the first time and turning it on. Fresh and clean.

If you are worried about your apps and data, you can have them backed up to the cloud as I do. Or you could also use ADB and run an ADB backup of your device first. Then download the factory image and run the flashall and after that is complete you can ADB restore and restore what you backed up. You don't even need root to do this, it's a built in Android feature. Here's how.

http://www.howtogeek.com/125375/how...kup-without-rooting-or-unlocking-your-device/
[Nexus 4 General] mrlad:
After applying the OTA, is it safe to reinstall the superuser.zip file from TWRP when it reboots or should I let it reboot with stock OTA and then reboot to TWRP and install the superuser/re-root?
[Nexus 4 General] Blockberd:
Should be save to directly flash SuperSU zip again while in recovery and after OTA update.
[Nexus 4 General] sordna:
Safest is to flash stock recovery, then apply the OTA and let the device boot, then flash TWRP, then boot into it to re-root.
[Nexus 4 General] Blockberd:
Why do one need stock recovery? At least the updates from JWR66N to JWR66V to JWR66Y could be flashed through custom recovery (at least CWM).

It might not be possible if the update contains recovery files (but that's been mentioned earlier already...).

Kinda agree on the SuperSU but at least it is fine to flash directly without reboot this time, though.
[Nexus 4 General] sordna:
I think this OTA patches your stock recovery, but you are right, custom recoveries can flash OTA update zips, I've done it that way before.

This thread is very useful by the way:

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

For the record, I flashed this OTA (JWR99Y) through TWRP and without unrooting, but I used this modified zip:

http://xdaforums.com/showthread.php?p=44886292
[Nexus 4 General] Blockberd:
The jwr66v to jwr66y update does not do anything really to the recovery. Stock recovery wont help you if you are rooted (at least with supersu) and trying to flash ota update. It. Will. Fail. Period.

Why i am so sure? I tried it more then once. Only [MENTION=2909590]CrazyPeter[/MENTION]'s tipp with unrooting helped me.

The modified zip worked for you because [MENTION=1566190]efrant[/MENTION] removed the unnecessary line regarding the one file whichs permissions got changed by supersu. As far as i know the file is not even required if you run stock recovery.
[Nexus 4 General] jack8daniels2:
Does applying [MENTION=1566190]efrant[/MENTION] zip affect the all in one LTE enabler? If so, how do I revert it back?
[Nexus 4 General] hgmichna:
I hope somebody ([MENTION=1566190]efrant[/MENTION]?) has checked the "unnecessary" line carefully before removing it. In theory you could be missing information that way, if that "unnecessary" line does something that may be required for some function or for the next OTA update.

I have not looked into it. I am only happy when I see that the original, unaltered OTA update runs perfectly, which is not too difficult to achieve in this case.
[Nexus 4 General] sordna:
I looked into it, and even posted a diff of what exactly he changed, take a look:

http://xdaforums.com/showthread.php?p=44896115#post44896115

efrant's zip does the right thing and simply avoids from the recovery to be messed with by the OTA, so after this investigation I used it and endorse as the quickest / simplest way to get this particular OTA if rooted and on custom recovery.
[Nexus 4 General] Blockberd:
Thank you. I was about to do the same. :)

---------- Post added at 08:42 AM ---------- Previous post was at 08:38 AM ----------

Yes, it should. You have to apply LTE enabler again. You can only apply efrants ZIP if you are coming from JWR66V. But I think even the ZIP from efrant will fail in your case. You have to revert LTE enabler before you apply OTA. If you don't have a revert zip, you better go by flashing system.img (and if coming from 4.2.2 you also flash boot.img, kernel.img and maybe radio.img) in fastboot.

Take them from the factory image of JWR66Y.
[Nexus 4 General] hgmichna:
I continue this discussion out of general interest in the basic problem. This particular case is only a weak example, but it may still serve as a case in point.

I don't understand diff. I'm not a Linux person. The diff file you link to is apparently relatively long and complex, not just a line that is commented out.

The question is, can you prove that the result of the modification that is now not happening is not needed or checked by the next OTA update? I have doubts that this can be proved.

If it cannot be proved, then the modified OTA file contains the risk of killing the next OTA update. Since it is relatively easy to circumvent this and let the original OTA update run, I see no need for a modified one.

Another question is that every user would have to check the modified OTA script for mistakes and for malware, which many users cannot do, due to lack of technical expertise. If they cannot check, trust comes into play. They have to trust the original mod author. They have to trust you.
[Nexus 4 General] rpudner:
Google Now Different Behaviour

Has any one else noticed that with the JWR66Y if you long press your headset button with the phone locked an announcement of unlock the device is made, I am sure this did not happen before.
[Nexus 4 General] Xoib:
Like your title say, it's Google Now specific behavior.
[Nexus 4 General] efrant:
If you have applied the "LTE enabler" patch, then ANY OTA update won't work until you revert your build.prop back to stock. Grab the stock build.prop file and replace the one you currently have.

Ok, let's clear some things up:

1) I have owned almost every Nexus device since the Nexus One, and I have been pulling apart OTA update files since that time, so, while I may not be an expert, I do have at least a little bit of knowledge to share.

2) OTA update files do NOT patch the stock recovery, so you can have whatever recovery on your device you want to apply the OTA update.

3) EVERY OTA update file places two files on your device (which otherwise would not be there if you flashed the factory images). These files are a) /system/recovery-from-boot.p and b) /system/etc/install-recovery.sh. What these two files do is re-flash the stock recovery EVERY time the device boots into Android. They are not used for anything else, and those files are not checked by any OTA update.

4) Since JWR66N, the new security measures in Android have required a change to the way the root is implemented in Android. Both Chainfire and Koush have changed the way their Superuser zips work, and they make use of install-recovery.sh. Chainfire's zip has also "chattr'ed" that file, which prevents it from being modified. <== this is why the latest OTA update fails. The OTA update file tries to replace the install-recovery.sh file and change permissions on that file, but it can't, so it fails.

5) The only modifications I made to the OTA update file was the following: a) delete the two files mentioned above, and b) delete the line that changes the permissions on said files. As stated before, these files are not part of the stock ROM, and are not checked by any future OTA updates. That being said, if you continue to use Chainfire's zip package for root, you will continue to have issues with future OTA updates (unless he changes it). But those issues are easily resolved by either removing root before you update, or flash an OTA update file with the same modifications I mentioned above.

Hope this clears a few things up.
[Nexus 4 General] SinisterSHO:
I guess I am lost because I am not sure how to replace my LTE modified build.prop with a the stock build.prop.
[Nexus 4 General] Draakhs:
Issue after update

Hi guys,

I'm having some weird behaviour. I updated from JWR66V to JWR66Y but at the end of the update I got an error. Of course this is related to the SuperSU issues which have been mentioned in this thread.

I didn't know that yet at that moment so I just restarted my Nexus, he booted and everything looks fine. However when I look at my version he's still reporting he's at JWR66V and there's no update available.

My question is is there a way to force him to re-apply the update for JWR66Y. I would like to un-root the device, apply the update, and re-root the device.

I've downloaded the patch from Google and am looking at the sideload method but isn't there a simpler method because I assume the update is already on my device as it has been downloaded before.

Thanks.
[Nexus 4 General] sordna:
This is a unified diff, the lines that start with - is what is removed, and the lines that start with + is what is added. The lines without - or + in front give you context to see whereabouts the changes are. So every pair of -/+ is 1 line change, and the rest is fluff.

diffs are a bit hard to read at first, but if you work with them regularly you realize how nice they are.

This is absolutely correct, if you want to be sure, you have to analyze yourself, or trust the provider of any code you use.

Not sure if people realize that by rooting your phone or even using a custom ROM, you potentially give your device data and even your keystrokes to whoever wrote the ROM or a rooted app you are using. Even if you use a 3rd party mail app, that app can potentially send your password over the network to the app author.

If you are serious about security, don't root your phone and keep it stock, and avoid 3rd party apps that deal with sensitive information. Then only Google can get to your data and share it with their affiliates :)
[Nexus 4 General] Blockberd:
First of all: thank you very much [MENTION=1566190]efrant[/MENTION]. I've been trying to explain the same. :(

Coming back to quoted issue: the update is not really on your device. You can either flash/sideload the update again or flash the whole system.img through fastboot again. You should not have any problems doing that. Good luck.
[Nexus 4 General] nextelbuddy:
i have been stuck on JWR66V and every time the JWR66Y OTA comes it kept failing.

finally i have stock kernel, stock recovery, all SYSTEM apps are proper now and nothing is different about my system directory.

the OTA wont come back though and its been several days.

is there anyway to sideload the OTA?
[Nexus 4 General] sordna:
Yes, the OTA Helpdesk has all the info you need:

http://xdaforums.com/showthread.php?t=2145848
[Nexus 4 General] Blockberd:
If you really flashed system.img from JWR66Y factory image through fastboot you should have JWR66Y. Check your phone info for the correct build.

How to sideload:

- Boot device into recovery

- Connect phone through USB with PC

- In recovery select the sideload flash option (naming may vary between recoveries)

- On PC with Android SDK:

-- Open command prompt

-- write adb sideload "path-to-updatezip"
[Nexus 4 General] hgmichna:
Yes, thanks!

There are still risks. What if the next OTA update attempts to patch /system/recovery-from-boot.p ? Why remove that file anyway?

I wonder if anybody comes up with a good idea on how to have root and OTA operation at the same time. Perhaps one way could be a "prepare for OTA update" function, which restores the original state just before an OTA update and allows to easily restore root afterwards.
[Nexus 4 General] efrant:
As I mentioned in my post, an OTA update will never patch that file because that is not a file that comes in a stock ROM. The file only exists if you have updated via an OTA update. Download the factory image from Google's developer page here, and see if you can find the two files I mentioned in there. You won't be able to. So, that is why future OTA's will not patch that file, because it is not part of the ROM. If future OTA updates would attempt to patch that file, then it would fail for everyone who flashed the factory images.

Again, as I mentioned, all that file does is flash the stock recovery every time you boot into Android. It is not needed for anything else. Not for running Android, not for future OTA updates, only if you want to automatically replace whatever is on your recovery partition with the stock recovery.

If you are using a custom recovery, it probably deletes/renames that file for you, otherwise, your CWM or TWRP would be overwritten by the stock recovery every time you booted your device.
[Nexus 4 General] hgmichna:
Thanks again! Yes, I see the point.

So the remaining problem is that the authors of either the superuser utilities or the custom recoveries or both will have to find a way to deal with OTA updates elegantly, if they want to make things easy for root users with stock Android. Perhaps Koush has done it already.