yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] Blockberd:
Or just flash system.img in fastboot if already on 4.3. Else flash boot.img, radio.img and kernel.img, too.

Sidenote: If the *.img files are taken from JWR66Y factory image you won't need to fiddle around with the OTA update for JWR66Y anymore as you already flashed the complete JWR66Y system.
[Nexus 4 General] sordna:
For flashing recoveries without a computer, I use apps like: Recovery Tools and Flash Image GUI. Both work from within android as long as you have root.
[Nexus 4 General] RickyBO89:
so basically we JDQ39 users have to unroot and launch the OTA zip from the custom recovery? but does this mean that we'll lose the recovery too? so it's again the "flash recovery" "flash supersu" thing...
[Nexus 4 General] Blockberd:
You won't lose recovery... Just unroot (to be sure), apply OTA, while still in custom recovery flash SuperSU app and reboot. Done.
[Nexus 4 General] RickyBO89:
nice to know, i was sure the recovery would have been replaced. I suppose I'll still get the message when rebooting asking to prevent stock recovery to be flashed, do I assume right?
[Nexus 4 General] ronn88:
I was curious if I'm under Scenario #3? I'm root 4.3 JWR66V with LTE radio hybrid on Tmobile.
[Nexus 4 General] Blockberd:
Yes, you are. Read section C and replace JWR66V with JWR66Y. Normally the easiest and cleanest way is to follow option 1 in section C.
[Nexus 4 General] ronn88:
Thank you it worked!
[Nexus 4 General] rcoliveirajr:
I'm stock running 4.3 JWR66V, but I flashed AOSP Browser via CWM, should I go to section B??
[Nexus 4 General] CatsAreGods:
Me too, I just found the factory image, unzipped to get boot.img and system.img so as not to disturb my precious data (I had TWRP recovery flashed already) and used a toolkit to flash them after doing an extra backup. It's easy and pretty much foolproof!
[Nexus 4 General] Blockberd:
I'll just leave this link here as a sidenote:

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

A thread about why someone should learn to use fastboot and adb before tinkering with toolkits. :)
[Nexus 4 General] CatsAreGods:
"Someone" knows how to use fastboot and adb. This particular someone has been working with computers since the mid-60s, when he used to sneak into a very large university and pretend to be a student so he could use their FORTRAN IV compiler via punch cards. And, just as I didn't like to retype my JCL but preferred to keep copies of the cards so I could reuse them, I don't see any necessity to manually type (and possibly mistype) commands when I have a nice little engine that doesn't leave out commands at random when he's tired. And just because I know how to drive a manual transmission car doesn't mean I have to punish myself by doing so in 2 hours of heavy traffic. And just because I know how to write device driver code in assembly language doesn't mean I have to avoid using other people's device drivers. And just because I know how to write a kernel doesn't mean I should avoid using Franco's, or think of myself as a wimp because I use his updater instead of downloading it by hand via modem signals powered by lunar cells backed up by a hand-cranked generator.

TL,DR: you may have to suffer if you want to sing the blues, but feel free to use all the labor-saving devices that people invent, as long as you know how to take the long route as well as the shortcut.
[Nexus 4 General] DecypherT:
delete
[Nexus 4 General] sunshinekhan:
CF-Auto-Root OTA Error

Which category does a Nexus 4 with Unlocked bootloader, Stock ROM and CF-Auto-Root fit in?

OTA update fails, can the update be applied manually?

I am on JWR66V, my phone downloaded a 1.8Mb file OTA but fails to update with an Red Triangle ! and Error.

Thanks and regards,

sunshinekhan
[Nexus 4 General] Blockberd:
It will fail. Head over to section C, option 1 and replace JWR66V with JWR66Y and you are good to go.

Just 2 things:

1) You say exactly the same as the people in the other thread and as I did.

2) I did not mean to **** you off. Just saying that someone (whoever that may be) should know the manual way before using toolkits in order to help themself if they bricked their phone.

Section B.

Error message? But I assume it was something along the line of "set_perm: some changes failed...".

Unroot, apply OTA through notifications or flash manually in recovery, while in recovery flash root app again and reboot.
[Nexus 4 General] sunshinekhan:
CF-Auto-Root OTA Error

No specific message, at least I didn't see one..

Only the Red Triangle like the file attached.

Will try your recommendation.

Thanks,

sunshinekhan
[Nexus 4 General] Blockberd:
Looks like you have stock recovery. Try pressing power button and/or volume up/down to bring up the text.

If it still fails, you should go to section C, option 1 and do the steps mentioned there but use the JWR66Y factory image.
[Nexus 4 General] x_Mischka_x:
Thank you for this post, I was unaware of this, and just installed TWRP and rooted my N4 the other day. I used the "full unroot" option in SuperSU, and /system/bin/su, /system/xbin/su, and /system/app/Superuser.apk are now gone, and I believe this means I am completely unrooted, correct? I still do have TWRP installed.

Will I be able to receive OTA updates? I really want to keep the stock Android experience and receive OTAs, so if I have to reflash stock recovery and everything I probably will, since I basically just installed custom and rooted because I was bored (and because I was intending on removing the requirement of WiFi for Hangouts video calls, but didn't feel like paying for a decent SQLite editor so ended up not doing so).

Thank you in advance, I've missed frequenting XDA as much as I used to in my GNex days <3

Edit: I suppose I was just confused as to what "unroot" in quotes meant, I guess it means to completely revert to stock? As, since I have TWRP, I do not have /system/etc/install-recovery.sh. I assume any OTA will fail since that file does not exist? If so, will simply flashing stock recovery restore that file?

Final Edit: Okay, so I think I've answered my own question. According to this thread, TWRP uses another method to maintain recovery status, it's the "full unroot" option that deletes that file. However, the OTAs themselves extract it, so the fact that I don't have one should cause no issues.

I could just delete my post entirely, since I've answered my own question, but it may prove useful to someone else so I'll just leave it. Thank you all and sorry for the pointless notification.
[Nexus 4 General] CatsAreGods:
I wasn't mad, just felt a little talked down to. Just a little. But we're cool now.
[Nexus 4 General] Blockberd:
Hey everyone. Chainfire pushed an update for his SuperSU app. He mentioned he reworked OTA survival and changed the permission of that one file back again.

[MENTION=962867]El Daddy[/MENTION]:

Maybe you take a look and update the first post... again. :D

Edit:

For reference: http://xdaforums.com/showpost.php?p=23427824&postcount=3
[Nexus 4 General] Slymobi:
OK maybe been asked but......

I've got the notification for the latest Y version saying its downloaded and ready for install, ( it will fail I have tried )

Now my point is that I don't want it ( I have a nandroid with everything up to date so I'm not interested in this update )

so where on stock is this download located so I can just delete the files/update so the notification will disappear and clear the 1.8 mb its using ??

Please note I don't want this update or methods of how to get it to work, I just want its downloaded location.

Kindest regards in advance.

NeXuS⁴
[Nexus 4 General] Blockberd:
With stock rom it will come back every time. Why not simply update and be done?
[Nexus 4 General] Slymobi:
As I've said this is not needed and it will fail because I've modded my system apps and some other mods. I've already got a full updated version as nandroid.

When I attempt it and it fails the notification stops which is good but then the file ( update ) is still somewhere so I just want to delete it .

All I want is the location of where its stored/downloaded to.

NeXuS⁴
[Nexus 4 General] Blockberd:
I got that. The update notification will come back.

But you can check /cache/ folder to get rid of 1.8mb which you will never be able to use in the userdata partition.

Tl;dr: you can save time by either just leave it or apply update+your changes.
[Nexus 4 General] Slymobi:
OK, so when I apply and it fails the notifications stop but my version remains as V ( this I've done previously so I can confirm no more notification on update )

so your saying if I located the downloaded update and deleted it then I would keep getting the notifications anyway ?

So for my need its best to apply and let it fail and keep the files so I don't get the notification again and the 1.8 mb is in a non usable path anyway ?

Cheers.

NeXuS⁴
[Nexus 4 General] Blockberd:
The notification will come back regardless of the file and if it's deleted or not. As long as your version is not up-to-date.

I also tried to apply the update from N to V several times and the notification came back.
[Nexus 4 General] Slymobi:
Not for me, the only time I get the notification is when I restore this nandroid backup. I then go ahead and try the update which boots into recovery but then does nothing, I then reboot and the notification never returns. Which is why I was asking about where the leftover update files were. I've run it like this for a week, never getting the update notification again. Yet my version is still V.

Never mind, I've decided to just root The Y version and do all my mods again then totally remove root again ( I do this because I have apps that don't run on root )

Thanks anyway.

NeXuS⁴
[Nexus 4 General] Blockberd:
You could also check out the /cache/ folder on your device for the 1.8mb file...
[Nexus 4 General] Slymobi:
Empty folder !!

NeXuS⁴
[Nexus 4 General] sunshinekhan:
CF-Auto-Root OTA Error

This is how I did it:

1. SuperSU has an inbuilt Unroot, unrooted the device from there.

2. Forced an OTA update check by Google Services Framework > Clear Data button and then Force Stop.

Will try CF-Auto-Root to root again and post an update.

CF-Auto-Root doesn't seem to be working as of now!
[Nexus 4 General] Blockberd:
Where you able to run the update from JWR66V to JWR66Y after unrooting? Why not simply flash SuperSU 1.55 ZIP in recovery after successfully unrooted?

You could also update from SuperSU 1.51 to 1.55 first and then run OTA update. Maybe a reboot after SuperSU update but before OTA update could be required.

To everyone using SuperSU:

It is highly recommended to update SuperSU 1.55 before doing any OTA update or to avoid troubles in the future.

Thanks [MENTION=631273]Chainfire[/MENTION] for his continous work on that. I knew a new version will come up soon which handles the problem.
[Nexus 4 General] zizo222:
Hi guys

I want update my phone but when i unroot the device and try to install from recovery

it say

installation aborted

Any help ??
[Nexus 4 General] Blockberd:
More details please. Our crystal balls (to see into the future and stuff) are broken (by design). ;)

Assumption:

You have a modified stock app/file. Still you need to try to flash the update again to find out which file it is.

Easiest way would be to flash system.img through fastboot. If you are coming from 4.2.2 you also need to flash kernel.img, radio.img and boot.img.

Note:

I assume you are working with a custom recovery.
[Nexus 4 General] wizardwiz:
Did any of you guys managed to update to 4.3 with the new 1.55 SU? I read somewhere that only Su 1.55 Pro has the survival mode to allow updating while still rooted
[Nexus 4 General] Blockberd:
As far as I understood the OTA survival mode is just for keeping root after OTA update. Without pro you should still be able to OTA update and then flash SuperSU again for getting root back.
[Nexus 4 General] wizardwiz:
Thanks on that one.
[Nexus 4 General] Garymeister:
No success on my end, that is with v1.55 going from JWR66V to JWR66Y :/

Update: Got it to work! I had my softkeyz modded so I recovered the stock ones. The first update link from OP downloaded the zip file which directed me to Flashify where I used TWRP to run the installation of JWR66Y. Great!

*This was with SuperSU v1.55 installed and rooted.
[Nexus 4 General] Garymeister:
Update: Lost root and recovery. I now get an android with a red exclamation mark. Tried fast boot flash twrp but it did not fix the issue. Help?
[Nexus 4 General] spaceman860:
What command did you use to flash the custom recovery? The android with red exclamation is stock recovery

BLACKED OUT LTE N4
[Nexus 4 General] Garymeister:
fastboot flash recovery openrecovery-twrp-2.6.1.0-mako.img

---------- Post added at 04:04 PM ---------- Previous post was at 04:01 PM ----------

I will try cwm, but since I already have stock recovery theres no need to request it. I did clear cache through it. Is there suppose to be an alternate command to flash a recovery image? I hope the update did not patch it.
[Nexus 4 General] spaceman860:
That's the right command and no the update didn't patch the way you flash the recovery. When you flash it does the command prompt say it was successful

BLACKED OUT LTE N4
[Nexus 4 General] Garymeister:
Yes, it says okay.
[Nexus 4 General] efrant:
This has been mentioned before: all OTA updates place files on your device that automatically flash the stock recovery on every boot. (Maybe have a read of the 101 thread which is linked in the sticky roll-up thread.)

Boot into the bootloader and flash TWRP using fastboot as you have done, but do NOT reboot into Android. Boot directly into TWRP and flash your superuser zip.
[Nexus 4 General] Garymeister:
It was USB debugging. I must have turned it off at some point but I got everything going, thanks.
[Nexus 4 General] efrant:
That's strange. Fastboot does not require USB Debugging to be enabled.
[Nexus 4 General] Garymeister:
That's exactly what I thought. Even after I figured it out someone over in another thread suggested it. Learn something new everyday.
[Nexus 4 General] efrant:
Well, just an FYI, I can guarantee you that it was not USB Debugging that was the issue. The fastboot protocol interfaces with the bootloader only. USB Debugging is an Android setting. You can even have no ROM (i.e., no Android) on your device, and fastboot will still work.
[Nexus 4 General] Garymeister:
That's the strange thing. Everything was recognized and processed via fastboot. Yet the multiple times I told it to flash recovery.img it would not stick. I guess it was luck or coincidence that it worked after enabling USB debugging. I cannot recall altering anything else about the phone or files on my computer.

Regardless I did not know how tedious doing all that for a tiny update was. Probably could have held off until the next major update haha. Thanks
[Nexus 4 General] efrant:
If you updated via OTA, there are two files that are place on your device that re-flash the stock recovery on every boot. You can flash TWRP as many times as you'd like, but it will not stick. It will get replaced by the stock recovery. The only way to get a custom recovery to stick, is either to deleted or rename said files. (If you flash a superuser zip, like SuperSU v1.5x, it will automatically delete them, and the custom recovery will stick.) CWM and TWRP also have the option to delete (or is it rename) those files, so if you boot into your custom recovery, before you exit, it will prompt you.
[Nexus 4 General] Garymeister:
Yes it indeed do that (prompt me for something) when I booted into recovery from bootloader menu after fastbooting recovery img. Prior that I believe I kept booting into system then into recovery, so the stock img was always there. Hm makes me want to do it again just to see. But it'd be nice to know of those files and where they're located. Thanks for clearing it up
[Nexus 4 General] efrant:
Have a read of the "Android for Nexus 4 101 & FAQs" thread linked in the sticky. All the details are there.
[Nexus 4 General] vukis:
Mine story: I was rooted and except that I was totally stock. And I noticed OTA update. Earlier OTA updates were working with no problem. Except it loosed stock. But this JWR66Y did not get pass even through stock recovery. I read that I had to unroot through superSu app. But app wanted superSu binnaries and gave me two ways instaling them: 1.Normal 2. Through custom recovery. First choose did not work. So I flashed TWRP through GooManager. After that SU updated binaries and I was able to unroot. Then I cleared android services data to obtain OTA notification again and this ota flashed through TWRP. After that TWRP was gone. No problem I booted to fastboot and loaded twrp.img from computer through fastboot. And I applied newest UPDATE-SuperSU-v1.55.zip from official site. After booting I noticed that there are no superSU app. So I downloaded it from market and that`s it.

My questions:

1. Why earlier OTA updates passed, but this did not?

2. How minor OTA update ~5Mb could overwrite recovery? I don`t know the size of stock recovery, but TWRP.IMG is 7.5mb. So android keeps a backup of stock recovery?

3. Why newest UPDATE-SuperSU-v1.55.zip from official site did not install superSu app?
[Nexus 4 General] sunshinekhan:
CF-Auto-Root OTA Error

Yes! Updated to JWR66Y.

I guess I got the 1.55 update from the PlayStore, just before doing the OTA update.

But after that when I try to apply CF-Auto-Root I get the following message and error:

----- CF-Auto-Root-mako-occam-nexus4 -----

Please make sure your device is in bootloader/fastboot mode before continuing.

***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***

We are going to run the "OEM UNLOCK" command on your device. If your device

was not previously unlocked, this will wipe all your data !

After the unlock, CF-Auto-Root will boot. You should see a big red Android

on your device's screen.

Press Ctrl+C followed by Y to cancel !

Press any key to continue . . .

The system cannot find the path specified.

The system cannot find the path specified.

It may take a minute or so for the red Android to appear. If it doesn't show up

at all, there may be a problem.

Press any key to continue . . .

What should I do to get rooted again without custom recoveries?
[Nexus 4 General] Blockberd:
1) All updates since the 4.3 branch have a new permission system. All SuperSU versions till and incl. 1.51 created problems with that. CF fixed it in 1.55 right after he came back from vacation!

2) It does not. It simply places a script again which flashs the stock recovery every time on boot. This behavior was there from the start. The stock recovery is around 6 to 6.5mb. And yes, there is a version of it on the device in the system partition. Deleting it will not bring you more space!

3) That I don't know. Normally it should work if you flash the latest desired custom recovery, flash from there and also apply the "revert to stock recovery" fix.

Did you have root before applying the OTA update? If so, why don't you simply flash the SuperSU 1.55 directly in custom recovery?

Note for all CF-Auto-Root users: You don't need to flash this if you are already on an unlocked bootloader device! What it does: Unlock bootloader (oem unlock) and flash SuperSU 1.55. That's it.

For details, please go to http://xdaforums.com/showthread.php?t=1980683
[Nexus 4 General] mefxes:
I was using Paranoid Android 4.2.2 when Android 4.3 was released, and since then the update section on options keep downloading the update all the time. Seems like it downloads the update, fail to install and then redownload it, and keep doing that over and over again. Over 3G, over Wi-fi, doesn't matter.

So I decided to go to PAC Man, wich gave me lots of restarts all the time (never happened before with my device) and then the newer ParanoidAndroid for 4.3. Everything seems to be perfect with PA 3.99 except the Titanium Backup not working. And I really need my backups.

So I decided to revert back to 4.2.2 due to a friend who told me I can block the download installing an app from Google Play, but he couldn't remember the app's name. I searched a lot but couldn't find it.

Is there anyone who can help me? Maybe with the solution to the download loop, maybe with a working backup app on 4.2.2 and 4.3 so I can backup everything and then revert to 4.3.

Please! Thanks!
[Nexus 4 General] HeyyMyNameIs:
i recieved the OTA update for a long time now and i still have not applied it since i have custom fonts boot animation(done through rom toolbox) custom glowdots, lockring(thanks to candyshop) all done using zipthemer, is it possible to just install the stock font and boot animation through rom toolbox and just apply the undo from zipthemer and i will be able to update through OTA?

Sent from my Nexus 4
[Nexus 4 General] efrant:
It would be easier to just grab the JWR66Y system.img and flash it using fastboot.
[Nexus 4 General] HeyyMyNameIs:
is that all i have to do? how about the already downloaded update from OTA, will it delete itself? will this keep my root? wait im running the old 4.3 will flashing the new 4.3 cause problems?

Sent from my Nexus 4
[Nexus 4 General] efrant:
So, to answer your questions in order: yes, yes, no, no.

To get root again, just re-flash a superuser zip package.
[Verizon Samsung Galaxy Note II] WyoSi:
I have a problem when using vpn (JunosPlus from Juniper networking) I can't seem to get to host names directly. I can access them by using the IP Address, but not with host names.

In Linux I normally edit the /etc/resolve.conf file, but on Jedi_r1 I don't seem to have the file.

Anyone know how android looks up host names? And preferably how to add a new search domain suffix to it.
[Verizon Samsung Galaxy Note II] WyoSi:
Bump, anyone have any ideas?

I've tried a couple things, but no dice.
[Verizon Samsung Galaxy Note II] WyoSi:
So it appears that resolv.conf isn't used, but that dns is handled with with the getprop / setprop of net.dns.xxxx. And in this case net.dns.search. Except that even when I change the property to include my domain I can't do direct host resolution. Works fine with host.domain.edu calls though on my vpn connection.

Anyone have more familiarity with setprop and getprop of the network stuff?
[Verizon Samsung Galaxy Note II] WarlockLord:
Is there a dhcp server on the other side giving you an ip address on the internal network? Is it handing out internal dns addresses and the correct dns suffix?
[Verizon Samsung Galaxy Note II] WyoSi:
There is a VPN DHCP server. But add in just an employee and not an IT guy I don't know about anything else it does.

On my Bionic though I could use SetDNS and add my domain suffix through it for searches and all was fine. Can't seem to now on my N2
[Sprint Samsung Galaxy Note II] mackentosh:
Im back on the scene with a New Build. This is an entirely new build which doesn't include the 15 toggle mod its strait up LJC with a ton of Mods if you have to have the 15 toggle mod just flash MacksUpdater from the Morphology thread and you can theme away so no Modinstaller here folks, I couldn't stay away :highfive:

Feature's

75% trans statusbar

Notification Shade removed

Camera shutter sound option

Resizable Popup browser

Battery Full Notification removed

AOSP LockScreen

AOSP Notification sounds added

Multi App mod

MMS screen on removed

Keyboard switch added Back

Transparent Multi apps

Custom Keyboard

Custom S Pen sound

Wifi Tether

Carrier Branding Removed

Volume Boost

Bravia Engine 2

Sony Xperia Z Launcher

Nova Launcher

Themed a Little

Animations

No CRT

Morphology Friendly

Bloated [Remove your own apps]

4 in 1 Reboot Option

Bootanimation sound removed

Custom Bootanimation

Transparent Popup Menu's

Real Statusbar Icons

Much More
​

Bugs

You tell me

I would like you guys to do a full wipe SORRY im starting over from stock

I AM NOT RESPONSABLE FOR YOUR DECISION'S AND ALWAYS DO A BACKUP

DOWNLOADS

MacksROM Revived! http://www.team-veritas.net/forum/index.php?topic=7.0

Ill add the Credits Later im not finished
[Sprint Samsung Galaxy Note II] mackentosh:
Mods & Fixes

FIX'S

Multi App fix
[Sprint Samsung Galaxy Note II] DJ IZZY:
Re: [ROM] [Team Veritas] MacksROM Revived! 2/12/13

Finally FIRST!! I knew you would be back homie!! :beer::beer::beer::beer: