yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] vermaekansh:
need help urgent

I just received ad update for Android4.4 but the downloading has not been started, it stays on waiting to download 238.9 MB via WIFI only until Nov 28th Nov" .

How do I make this download to my nexus 4, Please need help urgently.

I don't want to sideload this.
[Nexus 4 General] sordna:
Get the latest fastboot. Put the phone in boot loader mode, and try "fastboot devices". You should see a device id, and then you are good to go, you will be able to flash the KitKat factory image using fastboot.
[Nexus 4 General] illingd:
Just had a thought --

I have Avast anti-virus/anti-theft installed. Could this be upsetting my attempt to upgrade to 4.4 ?
[Nexus 4 General] RealiZms:
No. It shouldn't matter.

After reading the several bogus articles posted by a Google employee to NOT clear Google Services Framwork data I did it any dam way and guess what? I got the OTA immediately with no issues. It's an old trick but a Google troll scared people away from doing it recently.

Go to Apps>All>Google Services Framwork>Clear data>back out>Check for updates>BAM! you have an update!>Win!:good:
[Nexus 4 General] filthykid:
Same here. But when i turn vpn on, it starts downloading. As soon as vpn disconnects, download also disconnects. Weird.
[Nexus 4 General] ykumar00:
If your phone is rooted, download via pc and copy to /cache. Reboot, update has downloaded notification will show.
[Nexus 4 General] filthykid:
Unrooted
[Nexus 4 General] daddlefan:
Get a wifi-connection, maybe internet-cafe or with friends. Doesn´t take that long
[Nexus 4 General] Mol86:
Thanks for the reply. Turned out I had a developers build on my phone for some reason, which explains why I didn't get the OTA updates. The problems with connecting to the PC were due to Windows 8.1. I managed to flash the image with my old laptop though.
[Nexus 4 General] PauCore:
Daydream something.
[Nexus 4 General] K2sInteg98:
So I had the OTA update, unrooted my phone, relocked bootloader and with factory recovery. I got an error when installing the OTA update. I believe this could be because I am on the .33 radio. Can anyone point me in the right direction on how to get the latest .84 radio with everything stock on my phone.
[Nexus 4 General] daddlefan:
Foolow efrants guide.Link: http://xdaforums.com/showthread.php?t=2010312
[Nexus 4 General] Azstynger:
Just completed the 4.4 OTA following Efrant's guide but root is gone. Can someone give specific steps how to regain root access again. I had latest TWRP and SuperSU prior to OTA. Thanks.
[Nexus 4 General] efrant:
Did you look at "Part E" in the same link?
[Nexus 4 General] Prez1:
thanks for the info and links :cyclops:
[Nexus 4 General] Azstynger:
Thanks for the reminder. I did read through that part before starting the update process but just forgot about it after I was done. Thanks for all the good work.
[Nexus 4 General] pizzadragon:
So I'm having trouble re-rooting.

I was stock + root + TWRP no changes so I followed option B instructions. I dled the proper image, flashed, it then rebooted and prompted me to fix root binary, which I did.

It booted fine and upgraded no problem, but still no root. So I tried to reboot into recovery but got am error trying to get to TWRP.

OK, so I fastboot and installed latest CWM recovery (worked) and flashed SuperSU 1.80 (no error messages) But SuperSU app still says I have missing binaries.

Thoughts anyone?
[Nexus 4 General] ykumar00:
There appears to be a problem with supersu 1.80, try flashing an older version, because that's what happened to me. I tried flashing the latest version, but supersu didn't show up in the drawer. Flashed older version (I think 1.51) worked.
[Nexus 4 General] The1Shark:
No problem here with supersu 1.8

Stock KRT16S + franco r195
[Nexus 4 General] midasize:
I can't update OTA due to a build.prop error. I'm rooted but the only modification I have is the LTE radio.

From 4.2 > 4.3 I had the same error and just replaced the build.prop with a stock version using ES File Explorer and the OTA worked fine. I'm trying to do this again but can't find a stock JWR66Y build.prop anywhere. Also have no idea how to extract it from the 4.3 factory image on a Mac. Can anyone advise a solution?
[Nexus 4 General] Mr.Symbol:
I'm getting this error wile I'm trying to update my tablet from 4.3 to 4.4 :

"Verifying current system....

/system/app/Chrome.apk has unexpected contents.

E:Error in /data/media/0/file_name.zip

Status 7

Installation aborted"

Looks like Chrome.apk was modified

1)How can I make the update without loosing my data and settings?

2)Can I take the stock Chrome.apk from( i don't know where) and replace the one I have now (and looks like modified by I don't know who)?

I'm rooted /stock .

Thank you
[Nexus 4 General] spicediablo:
Flash to 4.3 using efrant guide without flashing user data.img

Sent from Mako⁴
[Nexus 4 General] ykumar00:
If that's the only mod you have, why don't you try flashing stock radio with fastboot?
[Nexus 4 General] El Daddy:
Because the build.prop is modified as well.
[Nexus 4 General] bala2289:
2 OTA's but still build KRT16O

Hi,

I sideloaded KRT16O sometime back. Got an OTA update last week for 9 or 12 mb. Today i got another OTA for 9 mb. Updated it but still the build number KRT16O. Take a look a the screenshot. I have Twrp bootloader and rooted. The kernel seems to be from KRT16S.

Kernel Version: 3.4.0-perf-g6aa1c72 :confused::confused::confused:
[Nexus 4 General] The1Shark:
I think the kernel is the same between the 2 builds
[Nexus 4 General] bala2289:
That means the ota update was not successful? Is there anyway to find whether it has failed? While updating with twrp i didnt see any error or failure messages.

Nope. Not same kernel.

4.4 KRT16O

Stock Kernel - 3.4.0-perf-g249a6da

4.4 KRT16S

Kernel Version: 3.4.0-perf-g6aa1c72
[Nexus 4 General] The1Shark:
Sorry

My bad
[Nexus 4 General] efrant:
There's no benefit to flashing 4.3 and updating to 4.4. It's just an extra step. Best is to flash the 4.4 images directly (except userdata.img of course).
[Nexus 4 General] Mr.Symbol:
Thank you.

I'll try this when I have time.
[Nexus 4 General] sordna:
I had the same problem with 1.75, I kept flashing it but when booting, the SuperSU app kept complaining that something was wrong. Flashing 1.69 solved it for me and I was even able to update it via the play store later without issues after that.
[Nexus 4 General] pizzadragon:
So I tried v1.65 and v1.80 again (I couldn't find any others to download and test) and I keep getting the error:

Can't open <file name>

(bad)

Installation aborted.

I've downloaded a number of times and checked the MD5 with no error. Do I need to somehow remove supersu first? I'm not able to find an "uninstall" or "uninstall updates" option anywhere.

Or should I try to switch back to TWRP? I think earlier I might not have been on the latest version when doing the update so maybe the newest version of TWRP will work better?
[Nexus 4 General] ykumar00:
You need to be in latest twrp, try with supersu 1.69, update later from play store. Cwm isn't currently working I think, the toolkits say that, and I also read it in a thread. Just Google it to find the appropriate zip.
[Nexus 4 General] RASTAVIPER:
Correct versions are:

TWRP> 2.6.3.3

Supersu> 1.75

Both worked fine for me in order to update through OTA zip from 16O to 16S.

Root got lost anyway (othertimes I remove it myshelf before flashing zips )and then after flashing both ota and supersu zip, just needed to download supersu also from play store.

Then root was working fine.
[Nexus 4 General] pizzadragon:
Thanks to you and all the other commenters, but still no dice.

I updated to TWRP 2.6.3.3 using fastboot. No errors. Still boots up fine. Enters TWRP fine.

I tried installing SuperSU-v1.65, v1.75, and v1.80 and every time i get "Error flashing zip '<filename>' "

Should I try to wipe cache/dalvik? fix permissions? I don't want to tinker too much as much last Nandroid was done through CWM and it listed an error message when it was finishing creating that backup. My next project will be to wipe the space where that erroneous backup was saved (it's taking up like 4gbs on my 16GB phone) so I can make a proper Nandroid throu TWRP which never gave me an error when making backups.

I just don't know where CWM backups are stored. most advice on XDA says to look in /mnt/shell/emulated/clockworkmod/backup but my folder is empty. but my disk usage definitely shows about 4GB used where it was free before.

Unless the backup was stored elsewhere, I suspect the backup error is the culprit, but now how to fix it... sigh, every upgrade turns into a chore...

Thoughts?
[Nexus 4 General] mrlad:
Was running on rooted stock OTA 4.3 (Koush SuperUser) and no custom recovery. The upgrade failed. When the phone reboots, it reports no command.

I tried to flash the stock 4.4 OTA with TWRP but that reports E:Error executing updated binary in zip.

At this point, is my only recourse to install the full stock factory image using these instructions (http://xdaforums.com/showpost.php?p=34552123&postcount=1)?

---------- Post added at 10:54 PM ---------- Previous post was at 10:05 PM ----------

I installed the factory stock image. I know the first boot should take an extended amount of time, but its been showing the rotating circles for about 8 minutes now. What is a reasonable amount of time for the initial boot?
[Nexus 4 General] El Daddy:
8 minutes is too long. Boot into recovery and wipe data. That should fix it.
[Nexus 4 General] mrlad:
Wiping the cache and the Dalvik cache from TWRP solved it. I'm rooted again and things appear to be back to normal. Thanks for your help!
[Nexus 4 General] bala2289:
Guys seriously no one to reply?? :crying:

I tried downloading the ota update from this forum and flashed it in twrp. This time i got errors. Check the screenshot.

No errors when flashing with the system downloaded ota but was not updated to KRT16S.
[Nexus 4 General] ykumar00:
Best way, most stable is to just flash the KRT16S factory image directly. Flash twrp and root later.
[Nexus 4 General] RASTAVIPER:
Your answer is a few posts before.

As I see you have TWRP 2.6.0.0 and you need latest 2.6.3.3

Then you will flash the OTA with no problems.

Unleashed by my Nexus 4
[Nexus 4 General] bala2289:
Ah thanks :laugh::laugh::laugh: will try when im home.
[Nexus 4 General] bala2289:
Flashed twrp 2.6.3.3. Flashed OTA like a charm :good::good::good: Thanks a lot.
[Nexus 4 General] midasize:
Thanks for the replies - does anyone happen to have or know where I can find a stock build.prop from 4.3 JWR66Y?
[Nexus 4 General] midasize:
So I went ahead and replaced the modified build.prop with the one from this thread and now my phone is stuck in a boot cycle. Tried factory reset with TWRP and CWM to no avail. Is it bricked or is there another way around this problem?
[Nexus 4 General] efrant:
No where near being "bricked".

You probably didn't set the correct permissions on the build.prop file. They should be 644 if you want to change them.

The easier method to update to 4.4 is to flash the 4.4 factory images (excluding userdata.img). Much easier than trying to get the OTA update to install if you have messed around with your system files.
[Nexus 4 General] sordna:
CWM stores backups in /data/media/clockworkmod/

At least it did when I used it earlier this year. You can delete that entire folder if you are rooted.
[Nexus 4 General] KE-35:
Update to 4.4 for Nexus 4

I have Nexus 4, when i click on system update, it shows "waiting for download" for 4.4, but download actually never begins. What can be the issue? Can any one help me out? Its currently running 4.3, I have no issues of WiFi or internet.
[Nexus 4 General] ykumar00:
Rooted/ any modifications made? Anyway, if you have any issue, the best solution is to just sideload the OTA, or flash a 4.4 factory image.
[Nexus 4 General] Mr.Symbol:
No problems with the update ....and keeping my data...

Thank you
[Nexus 4 General] pizzadragon:
Thanks but I didn't find anything there either. I looked in (root) /data and /sdcard/data, but no dice.
[Nexus 4 General] KE-35:
Nexus 4 update to 4.4

I haven't made any modifications neither have I rooted it!
[Nexus 4 General] RASTAVIPER:
You can proceed then with any of the proposed ways.
[Nexus 4 General] nikhil381:
I flashed the what's app art fix . I have unlocked bl and root . which method I ll have to use for ota for 4.4.1
[Nexus 4 General] redsmith:
http://www.reddit.com/r/nexus4/comments/1s6x25/android_441_ota_link_official/
[Nexus 4 General] El Daddy:
OP updated with 4.4.1 OTA link.

I don't have the N4 anymore so I cannot confirm the 4.4 bootloader and radio versions. If they are wrong please let me know!
[Nexus 4 General] Sturdy_99:
help....getting error set_metadata_recursive: some changes failed

E:Error in tmp/update.zip (status 7)

i have flashed stock fatory image of 4.4 and downloaded ota of 4.4.1 but cant flash....what to do...i flashed twrp n cwm but both failed..
[Nexus 4 General] Vintos:
I'm on the same boat here...:confused:
[Nexus 4 General] El Daddy:
Searching the only solution I've seen is to use the latest versions of twrp or cwm.

Have you tried side loading with stock recovery?
[Nexus 4 General] Vintos:
I was rooted and on the latest version of TWRP. System was stock.

Just flashed stock system, bootloader and recovery from 4.4 and I will try sideloading the update.

Edit: Sideload method worked
[Nexus 4 General] shadowx360:
That's for the HTC One....

On that topic, the previous dropbox link of the Nexus 4 KitKat 4.4 build.prop is dead. Can anyone send me theirs?
[Nexus 4 General] d3xt3r:
M trying to flash the ota via twrp but its failing saying system/bin/app_process has unexpected contents and its failing. Please help
[Nexus 4 General] thiago.albertodesouza:
Hello guys. I need someone help with the browserproviderproxy.apk for the KRT16S build on Nexus 4. After installing the AOSP browser, maybe it have change something on this file and now, I'm having problems applying the 4.4.1 update.

There's someone who can post this file?

Thank's in advance.
[Nexus 4 General] hughfollett:
Hi [MENTION=962867]El Daddy[/MENTION] ! Followed your guide after flashing stock krt16s factory image and I thank you so much because it was really useful:good: However, just for reference: I was on stock rooted+twrp+franco+modified framework-res.apk to get transparencies in lockscreen. Does it flash the ota zip with modified framework-res.apk?

Thank you again:)
[Nexus 4 General] :
No. Because before it flashes, it checks first for whatever modification you made.
[Nexus 4 General] efrant:
I suspect this is due to using an older version of SuperSU.

You need to uninstall the Xposed framework.
[Nexus 4 General] RASTAVIPER:
I can't install 4.4.1 over 4.4 with stock framework anyway.
[Nexus 4 General] efrant:
Then you have something that is not stock. Just flash the 4.4 system, boot and radio images using fastboot and then apply the update. That's the easiest way to get back to stock without having to mess around with individual files.
[Nexus 4 General] RASTAVIPER:
4.4 updated over 4 3 with no problem.

Also small update of KTR160S

Only this 4.4.1 gets failed.
[Nexus 4 General] efrant:
As I said, something is not stock. What is the exact error you're getting?

Also, if you had flashed an older version of Super SU in recovery (even if it was updated via the Play Store), it may prevent the update from applying successfully. (I've mentioned the reason for this earlier in this thread.)
[Nexus 4 General] RASTAVIPER:
Error is : Error executing updater binary in zip

About supersu I have version 1.80, but first installed from recovery and then updated groom Play.

Are you suggesting to completely remove supersu and try again?

Unleashed by my Nexus 4
[Nexus 4 General] pizzadragon:
I also still can't get supersu working either. Flashing any version produces an error.

My question to the forum is the same then, should I remove supersu completely and how would I do that since I don't have root?

Another option is just wiping the phone and starting from scratch. How would I do that? I just want stock 4.4.1 plus root...
[Nexus 4 General] efrant:
It's strange that is all it shows and no other details.

If it was root that was causing a problem, it would say something like "permissions could not be set" or "recursive error" or something. If you are seeing one of those, it's likely because you had an older version of SuperSU at some point. Open a terminal emulator and type the following commands:

su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p21 /system
chattr -i /system/etc/install-recovery.sh

Then try to apply the update.

Although I still suggest just flashing the images instead, as per my comment below. It's simpler, and no data loss, so there shouldn't be an issue.

See above.

If your bootloader is already unlocked, then as I mentioned earlier, just flash the 4.4 system, boot and radio images (as per this thread, but only those images) and then flash the 4.4.1 update in recovery.
[Nexus 4 General] RASTAVIPER:
After this how I proceed?

u0_a145@mako:/ $ su

chattr -i /system/etc/install-recovery.shchattr -i /system/etc/install-recovery.shroot@mako:/ # chattr -i /system/etc/install-recovery.sh

chattr: setting flags on /system/etc/install-recovery.sh: Read-only file system

root@mako:/ #

Unleashed by my Nexus 4
[Nexus 4 General] efrant:
Sorry, that was my mistake. I was trying to type too fast. Use this:

su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p21 /system
chattr -i /system/etc/install-recovery.sh
[Nexus 4 General] RASTAVIPER:
No, my mistake for not seeing this earlier.

More error info.

/system/bin/dexopt has unexpected contents
[Nexus 4 General] .:F@bio:.:
Error while updating

I have a problem with the file "dalvickvm". I've done the unroot but when i try to install the update i get this error:

Verifyng current system...

"/system/bin/dalvickvm" has unexpected contents.

E:Error in /tmp/update.zip

(Status 7)

Installation aborted.

Can i solve this problem without making a factory reset?
[Nexus 4 General] MersauX:
I flashed stock recovery, sideloaded the update using adb and flashed without issues.
[Nexus 4 General] efrant:
I would suspect it has something to do with deodexing, but not sure.

I would suspect it has something to do with deodexing, but not sure.

If your bootloader is already unlocked, then as I mentioned earlier, just flash the 4.4 system, boot and radio images (as per this thread, but only those images) and then flash the 4.4.1 update in recovery. No data loss.
[Nexus 4 General] .:F@bio:.:
Thanks very much, i'll try and i'll let you know if it work.
[Nexus 4 General] ibrahim52:
Don't do that, simply if you are using custom kernel that is why its happening i guess. Follow the steps.

1. Uninstall whatsapp if you had modified the libart.so

2. Then download the 4.4 image and restore boot.img and system.img so it will restore stock properly without deleting data.

3. Now try applying the update copied on your SD card and installing it through CWM or TWRP. Good luck.
[Nexus 4 General] grgana:
So if im on stock,rooted,CWM 6.0.4.3. Nothing is modified or deleted from system, only few apps i dont use are disabled in normal way in manage aplications.

Should be able to flash OTA via CWM??

Only thing that worries me is when i was rooting and installing CWM, i saw in toolkit something like " installing modified boot img." in order to have a custom recovery i guess, does that count as modification or not..cause is not system img. thats been modified?

Sorry my first nexus here, lack of expirience :o

Sent from my Nexus 4
[Nexus 4 General] sixaxis94:
I can't seem to change my recovery from TWRP to CWM through flashify.

Flashing CM11 from TWRP kept failing (Just like when I flashed the N5 stock port) so I tried to flash CWM's image zip through flashify. It worked the last time but it's not happening now.

Tried multiple times, and it's still stuck on TWRP. Any help?

EDIT : ROM Manager shows both CWM and TWRP as recoveries already installed. Is that even possible?

How do I delete TWRP or disable it or make CWM the default?
[Nexus 4 General] davidgs:
I was the same as you, all stock, rooted and with CWM, I successfully installed the OTA via CWM, BUT I lost root and ended up with stock recovery.

I'll have to get back to my PC to reinstall CWM and flash Supersu.
[Nexus 4 General] akiv:
Hi,

Does anyone have a backup of power.msm8960.so in /system/lib/hw .

Just flashing boot.img from the stock image did not work :(
[Nexus 4 General] efrant:
Every OTA update since the Nexus One has done that. The procedure to update also has not changed since the Nexus One: reboot into CWM/TWRP, flash the update, then flash a superuser zip, then reboot. You still have root and (if you are using a recent CWM/TWRP) and your CWM/TWRP installed.
[Nexus 4 General] efrant:
Flash the system from the stock image as well.
[Nexus 4 General] efrant:
Try flashing it using fastboot, not flashify.

And it is impossible to have both CWM and TWRP flashed at the same time. Don't trust what ROM manager is telling you.
[Nexus 4 General] grgana:
ok and if i proceed in CWM do i need to flash anything else? radio 98? or bootloader? kernel? or its all included in OTA? and do i need to wipe dalvik or data?

thanx [MENTION=1566190]efrant[/MENTION] : do i need to flash CWM along with superSU zip or it will stay i have CWM 6.0.4.3

greets
[Nexus 4 General] efrant:
Just flash the update in CWM, and before you reboot, flash the SuperSU zip in CWM. That's all you need to do. The radio is included in the OTA update, and there is no new bootloader. CWM will remain if you flash SuperSU BEFORE you boot back into Android. (At least it should anyway).
[Nexus 4 General] .:F@bio:.:
It works, i've successfully updated, thanks again.

I had not a custom kernel, i had all stock and root.
[Nexus 4 General] FunkiBluDawg:
4.4.1 update via twrp all ok

Rooted 4.4 => TWRP => 4.4.1 => success !

Installed update zip file via TWRP 2.6.3.3 recovery

No errors

and rebooted straight into 4.4.1

Everything seems to work.

Unbelievable ! (especially after the all grief I (and many) had with 4.4 update)

But lost root, but I re-rooted by installing SuperSU via TWRP (Yes, old recovery was still there after the update !)

Now to play with 4.4.1 goodies/bugs !
[Nexus 4 General] gialakias:
Correct me if I am wrong but when there is a new bootloader you have to reboot only from the custom recovery without flashing anything, because then the update continues through the new bootloader and stock recovery to complete the installation. I think that was the problem with bootloops in the update from 4.3 to 4.4. I assume this because I noticed the whole procedure and saw that after rebooting through cwm the stock recovery showed up and continued the installation.
[Nexus 4 General] grgana:
Well i flashed it via CWM a few minutes a go, it went fine for now, flashed superSU after OTA and got root..

It was a bit scary

first time i dowloaded OTA and SU zip, i wanted moved them from dowloads to root of sdcard(storage) and verry wierd i couldnt find them any more, does anyone knows where they are gone? (Really like to erase them to free some space)

Anyway i redowloaded OTA and SU and flash via CWM..

Sent from my Nexus 4