Can't update from 4.3 Using stock kernel ( swapped from franco to install the ota)
Tried CWM and TWRP, both fail.
here what happens: https://www.dropbox.com/s/6a1oesuwa3zgk1h/2013-11-14%2004.12.43.jpg?m
the same problem, the same CWM version
Not sure if it helps, but I followed this guide and now I am on KitKat
Download the JWR66Y factory image, extract everything and flash the system.img in fastboot mode, which should restore any changes made to the system partition. Try again after that
I'm having the same issue. I was on JWR66V and tried to update to 4.4 in cwm but it wanted me to be on JWR66Y... so after much hunting around I finally found a working JWR66Y flash able zip and was able to update to that.
However, I noticed that supersu got screwed up in the process, saying it couldn't find binaries. I downloaded and flashed the latest supersu, but that had no effect. I figured I would go ahead and try updating to 4.4 anyway and fix the root issue later...
The 4.4 update seemed to be going OK in cwm until I hit that same issue you did at about 75%. I've seen elsewhere that certain versions of supersu have been causing update problems. My only other thought is maybe I need to update my cwm to a newer version.
Eregoth said:
Download the JWR66Y factory image, extract everything and flash the system.img in fastboot mode, which should restore any changes made to the system partition. Try again after that
Click to expand...
Click to collapse
Why not getting directly the kitkat-image and flash boot.img and system.img in fastboot mode? No further update needed ...
Sent from my Nexus 7 using xda app-developers app
Related
Hey guys,
I am having an issue flashing the stock android 4.2.2, coming from factory 4.2.1 only rooted. I downloaded the factory image from http://www.androidpolice.com/2013/0...us-7-3g-android-4-2-2-update-jdq39-right-now/ when I try to flash the zip file in TWRP i get an error assert failed: apple_patc h_check ("system/app/browserproviderproxy.apk
E: Error in /sdcard/"name of zip file" error flasing zip
the files that it is trying to patch do not exist in the file system. I attempted temp unroot to see if that would do it. The official OTA came through, rebooted recovery but did nothing.
Any suggestions?
Had the same issue with TWRP. With the ClockWorkMod Recovery this part works. If you made any modifikations like camera resolution, enabling of wifi tethering or what else, extract the system.img file from the factory image and flash this first to make sure that you really are on stock 4.2.1 ...
And thats it have fun with the new version 4.2.2
Best regards ...
Ah I did not think of that with the wifi tethering, how do I flash the system.img file, using ADB?
affiaff said:
Had the same issue with TWRP. With the ClockWorkMod Recovery this part works. If you made any modifikations like camera resolution, enabling of wifi tethering or what else, extract the system.img file from the factory image and flash this first to make sure that you really are on stock 4.2.1 ...
And thats it have fun with the new version 4.2.2
Best regards ...
Click to expand...
Click to collapse
I'm having an issue here as well.
I'm stock, except I did enable wifi tethering.
I can't update via CWM or OTA, because I get an error during the process.
I tried to pull the system folder out of 4.2.1 and flash that through CWM, but I also get an error when it checks the current system.
EDIT: I finally got updated. It was serious scare for a bit though. The toolkit really messed things up at first. I had to flash back to 4.2.1. After using the toolkit and having failed attempt after failed attempt, I realized I had to reflash the stock recovery first. I was then able flash the stock 4.2.1 image, reflash CWM recovery, and use CWM to install the update. There are still things that are screwy, and I've lost root (the root restore app isn't seeing it as being recoverable, but I'm tired and probably missing something). Anyways, most of my data is in tact, aside from a couple odd issues, so the rest I'll deal with tomorrow. The device does feel more responsive, so I suppose it was worth the bother, but I definitely will not be installing that tethering mod again.
I installed factory image KRT16O and rooted it and also installed CWM touch recovery. Will i get the OTA to KRT16S ? Will i lose root afterwards ? Will the custom recovery cause problems ?
+1
Sent from my Nexus 4 using Tapatalk
+1
---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------
I guess an ota zip will be very helpfull.
You will not get OTA with custom recovery, but you can download the OTA package and flash it using custom recovery. You will lose root, but you can either hide root or reflash it. edit: CWM is not compatible with OTA, it will soft brick the device.
sent from tapatalk
for the custom recovery part. I'm running KRT16S with TWRP 2.6.3.3, works just fine. Earlier try it with latest CWM touch, works fine too.
But I'm doing manual install (adb and image). So I can tell you anything about flashing rom.zip through custom recovery. I think it won't cause any problem by flashing rom through custom recovery.
Forgive me if I'm wrong. thanks
Thanks eksasol but can you give us a link for the OTA package(KRT16S)?
you can lose root,, you have to re flash after installing to krt16s
im sorry for my english
other way,,, you can install zip version of factory image..
If I flash back to stock recovery will I be able to get this new KitKat build OTA?
+1
CWM, root, KRT16O. Id rather just a .zip update so I dont have to go through the whole rig-a-ma-role again (other than re-rooting).
You can get the OTA through custom recovery contrary to what others are saying. The KRT16S OTA arrived for my KRT16O, and it proceeded to automatically reboot and flash through TWRP.
Custom recovery and root is wiped after that OTA update, so you will need to re-flash both.
I will try the OTA as soon as I get it. I'm on CWM but I think that if you did it on TWRP there is no reason it won't update on mine. Thanks!
what to do if I Dont want to get the O T A ? flash fota killer for 4,3 will it work,?
Sent from my nexus 4 running 4.4 kit kat
no OTA for my stock KRT16O...
I updated my N4 to the Google factory image KRT16O via fast boot through stock recover using ADB, from previous 4.2.2 stock - I chose to avoid 4.3 due to all the issues. The phone is completely stock, but no update is available yet? Could it be because I manually updated to KRT16O using fastboot? I don't see why this would stop the latest update being pushed since the phone is pure stock with zero changes to recovery or root.
Globespy said:
I updated my N4 to the Google factory image KRT16O via fast boot through stock recover using ADB, from previous 4.2.2 stock - I chose to avoid 4.3 due to all the issues. The phone is completely stock, but no update is available yet? Could it be because I manually updated to KRT16O using fastboot? I don't see why this would stop the latest update being pushed since the phone is pure stock with zero changes to recovery or root.
Click to expand...
Click to collapse
That is technically impossible, fastboot only work in fastboot mode (aka the bootloader menu). So you must have flashed it in fastboot mode, not stock recovery. You can download the OTA package from the thread in the general section and sideload it in stock recovery, or use fastboot to flash the KRT16S firmware, since you said you did it already, shouldn't be an issue.
Salty Wagyu said:
You can get the OTA through custom recovery contrary to what others are saying. The KRT16S OTA arrived for my KRT16O, and it proceeded to automatically reboot and flash through TWRP.
Custom recovery and root is wiped after that OTA update, so you will need to re-flash both.
Click to expand...
Click to collapse
Half true.
Updated yesterday the S version normally through OTA and my TWRP recovery is still there.
Only thing neeeded after was to reroot and flash custom kernel again, which I had remove to make the update.
Sent from my NookColor using Tapatalk 4
eksasol said:
That is technically impossible, fastboot only work in fastboot mode (aka the bootloader menu). So you must have flashed it in fastboot mode, not stock recovery. You can download the OTA package from the thread in the general section and sideload it in stock recovery, or use fastboot to flash the KRT16S firmware, since you said you did it already, shouldn't be an issue.
Click to expand...
Click to collapse
Thanks. Yes, my mistake, of course it was just fastboot.
I would have thought that the new build would show up OTA, but maybe it looks for 4.3 to initiate as KRT16O never actually was pushed OTA.
I guess I could update to new build via fastboot like before, but had hoped to get it OTA.
Cheers.
Globespy said:
Thanks. Yes, my mistake, of course it was just fastboot.
I would have thought that the new build would show up OTA, but maybe it looks for 4.3 to initiate as KRT16O never actually was pushed OTA.
I guess I could update to new build via fastboot like before, but had hoped to get it OTA.
Cheers.
Click to expand...
Click to collapse
You can flash image without wiping data, links in my signature. There is a KRT160 to KRT16S OTA package as well, I was hoping you could find it yourself, but I guess I'll do a bit more work: http://forum.xda-developers.com/showthread.php?t=2145848
eksasol said:
You can flash image without wiping data, links in my signature. There is a KRT160 to KRT16S OTA package as well, I was hoping you could find it yourself, but I guess I'll do a bit more work: http://forum.xda-developers.com/showthread.php?t=2145848
Click to expand...
Click to collapse
Cheers! I may wait a few days to see if the OTA comes since phone is stock untouched... But if nothing in next 2 days I'll fastboot the image.
Can someone help me with me problem?
I have a Nexus 4, its currently running 4.3 & want to update to 4.4 without loosing my data.
Its a stock 4.3 ROM, but my device has the bootloader unlocked, rooted & has Franco kernel installed along with TWRP recovery.
Recently, I've been getting the notification that 4.4 update is ready to install. I click ok & the phone re-boots into TWRP, after a few seconds the screen goes back to the main TWRP menu without installing the update.
So, I downloaded the latest factory image from here: https://developers.google.com/android/nexus/images (Android 4.4 (KRT16S)) & extracted the 'image-occam-krt16s.zip' file from the 'occam-krt16s-factory-2006f418.tgz' download. I then booted into TWRP > Advanced > ADB Sideload.
and ran the following command from adt sdk tools: 'adb sideload image-occam-krt16s.zip'. This sent the zip file to the phone (took about ~1 minute) & the update started but failed almost straight away.
This is the error message I got:
Can anyone point me in the right direction why 4.4 wont install?
Thanks.
Thats not how it works. The factory image zip is not flashable...it contains the imgs for flashing via fastboot, not a recovery.
You can get the flashable ota zips from here: http://forum.xda-developers.com/showthread.php?t=2145848
The ones found on that thread can be adb sideloaded.
Thanks for the update.
So, according to the link you provided I need to wipe everything & revert back to stock.
So, there's no way to install 4.4 if I have TWRP & custom kernel installed?
cmberry20 said:
Thanks for the update.
So, according to the link you provided I need to wipe everything & revert back to stock.
So, there's no way to install 4.4 if I have TWRP & custom kernel installed?
Click to expand...
Click to collapse
No there is a way. Download the ota zip from that page and flash via TWRP. It should work, assuming that you are currently on 4.3 JWR66Y.
Chromium_ said:
Thats not how it works. The factory image zip is not flashable...it contains the imgs for flashing via fastboot, not a recovery..
Click to expand...
Click to collapse
Not saying your wrong but theres a ton of links showing you how to install the factory image via adb sideloading.
http://phandroid.com/2013/11/21/dow...d-4-4-kitkat-krt16s-ota-directly-from-google/
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
http://www.androidpolice.com/2013/1...16s-ota-manually-root-or-unlock-not-required/
What gives??
Chromium_ said:
No there is a way. Download the ota zip from that page and flash via TWRP. It should work, assuming that you are currently on 4.3 JWR66Y.
Click to expand...
Click to collapse
Thanks, I'll give that a go.
cmberry20 said:
Not saying your wrong but theres a ton of links showing you how to install the factory image via adb sideloading.
http://phandroid.com/2013/11/21/dow...d-4-4-kitkat-krt16s-ota-directly-from-google/
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
http://www.androidpolice.com/2013/1...16s-ota-manually-root-or-unlock-not-required/
What gives??
Click to expand...
Click to collapse
The links are not installing the factory image image by adb sideloading. They are using an ota zip (what i have provided you with above) and sideloading that.
Thanks.
Someone lead me down the wrong path with the OTA image. They told me to use the factory image one. Sorry about the dumbness!!
I've tried updating via TWRP install & adb sideload with the image from the link & it fails each time.
Seems that theres something not quite right with my phone. My phone is definitely running 4.3 JWR66Y with 3.4.0 Franco Kernel.
Is my version of TWRP ok - I have 2.6.3.0. I didn't know if this had any issues with flashing 4.4? I've tried updating it through Goomanager but i doesn't seem to want to download the latest version.
edit, just manually install 2.6.3.3 & update is still failing.
cmberry20 said:
I've tried updating via TWRP install & adb sideload with the image from the link & it fails each time.
Seems that theres something not quite right with my phone. My phone is definitely running 4.3 JWR66Y with 3.4.0 Franco Kernel.
Is my version of TWRP ok - I have 2.6.3.0. I didn't know if this had any issues with flashing 4.4? I've tried updating it through Goomanager but i doesnt seem to want to download the latest version.
Click to expand...
Click to collapse
You are definetly using this right?: http://android.clients.google.com/p....signed-occam-KRT16S-from-JWR66Y.d1b99704.zip
Instead of sideloading try pushing it to the phone manually then flashing it.
Nope, not working. It just doesnt want to know.
I wonder if its the custom kernel? I'll try flashing the OEM one see if it makes a difference.
it will not work, otas check for fils remember?.
hes using custom kernel so no work.
to upgrade to 4.4 download factory images of 4.4. extract and then u open image-occamikrt16s.zip(or whatever the name is), delete userdata.img and recovery.img, then u restart your n4 into fastboot mode, connect to pc, and run flash-all.boom, but u will need to re flash the kernel with a krt16s compatible one.
I am currently running stock 4.4 on my Nexus 4. FTP doesn't work with 4.4 and I don't like that, I use my FTP a lot. Now did I get a notification about half an hour ago that there was an update (4.4.2) available. I chose to update and pressed the restart an install updates button.
But my N4 didn't install the update, it simply booted into TWRP recovery. So I chose reboot > system and my phone just booted. Just not to 4.4.2, but to 4.4. When I check for updates in the settings it says that there are no updates available. Does anyone know how to fix this?
Sent from my Nexus 4 using xda app-developers app
thedjdoorn said:
I am currently running stock 4.4 on my Nexus 4. FTP doesn't work with 4.4 and I don't like that, I use my FTP a lot. Now did I get a notification about half an hour ago that there was an update (4.4.2) available. I chose to update and pressed the restart an install updates button.
But my N4 didn't install the update, it simply booted into TWRP recovery. So I chose reboot > system and my phone just booted. Just not to 4.4.2, but to 4.4. When I check for updates in the settings it says that there are no updates available. Does anyone know how to fix this?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Download the update to your pc from here. If you are running 4.4.1, then download from here.
Copy the update.zip to your phone
Boot into TWRP recovery. Choose install zip from sdcard, navigate and select the update.zip and flash. Re-flash the SuperSU/Superuser binaries if you want to keep root (not flashing this, might replace twrp with the stock recovery ). Reboot.
If you have modified ANY system file, then this won't work and you will have to revert to stock first.
Ibrahim.Rahman said:
Download the update to your pc from {I am not allowed to post links yet}.. If you are running 4.4.1, then download from {I am not allowed to post links yet}.
Copy the update.zip to your phone
Boot into TWRP recovery. Choose install zip from sdcard, navigate and select the update.zip and flash. Re-flash the SuperSU/Superuser binaries if you want to keep root (not flashing this, might replace twrp with the stock recovery ). Reboot.
If you have modified ANY system file, then this won't work and you will have to revert to stock first.
Click to expand...
Click to collapse
Didn't work but i've found a solution myself.
To update to 4.4, I've flashed the factory image without wiping the cache.
I used the following command lines
fastboot flash bootloader bootloader*.img
fastboot reboot-bootloader
fastboot flash radio radio-*.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Maybe that is the reason why it doesn't work. I've downloaded the 4.4.2 factory image now and flashed it like this, it worked.
Hi,
I have a rooted Nexus 4 with android 5.0 lollipop build LRX21T.
I have TWRP recovery installed version : v2.8.0.1
The device id rooted via placing the zip file in the device and flashng it via TWRP recovery.
But i am not able to update to android 5.0.1 via google OTA update.
Everytime i try to install the 5.0.1 OTA it goes to TWRP recovery.
I found that the downloaded OTA update file is placed in /cache folder , so i try to update it manually but failed as it shows some update partition error.
"E: error executing updater binary in zip '/cache/e93b********************.signed-occam-LRX22c-from-LRX21T.e93b****.zip"
update partition details.....
I think i am getting this error because the device is rooted.
Can someone guide me how to update my device..and if this because of the rooted device how to unroot without going back to stock.
Thanks in advance....
You can't flash the ota in twrp. You have to be 100% stock recovery, system, kernel, and radio. Flash the stock recovery with fastboot then try the ota.
Sent from my Nexus 9 using XDA Free mobile app
I flashed the stock recovery the OTA update continued in the stock recovery , then it showed a error....and i had to restart the phone ...now the ota update has disappeared with the phone still in android 5.0 ...Can you tell me how to get the OTA update back...?
1)Does the error came because the phone is still rooted ?
2) If so how do i remove the root with returning stock .?
3) also if i root and return to stock will it wipe my phone apps and their data...
Now i got the OTA update downloaded manually on my laptop and and booted into stock recovery to try to sideload the zip it gave me the error
"package expects build fingerprint of google /occam/mako:5.0/LRX21T or google /occam/mako:5.0/LRX22C user release keys; this device has google/occam/mako:4.4/KRT160 user release keys .....
This is weird as i am running android android lollipop 5.0 LRX21T and not android kitkat....
Did you flash mods while rooted?
Sent from my Nexus 4
arkangel72 said:
Did you flash mods while rooted?
Sent from my Nexus 4
Click to expand...
Click to collapse
Tried both...with and without Root....same error....
Try flashing factory image.
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
sachin.parmar100 said:
The OTA will flash only on the stock recovery it won't work in any modified/custom recovery. So flash stock recovery first then you are good to go.
Edit: You may also try flashing the factory image, u may lose your data while doing that
Head to https://developers.google.com/android/nexus/images and download the latest image, flashing procedure is explained there too.Its not compulsory to lock bootloader afterwards BTW, its personal preference.
Click to expand...
Click to collapse
Actually i dont want to flash stock as i will lose all the data in the process....
Any other way....?
If there is no other way could you please suggest any tool kit which will backup all data including sms ,contact, call logs and all app data and /data/media folder. in one go ...?
use advanced backup from twrp backup menu and select data only to create a nandroid backup of data only
you can also use titanium backup to backup to choose what to backup and restore it afterwards but it will need root again.
sync your contacts with google server
Flah rom in fastboot
Download factory image, flash system, bootloader and recovery manually. You won't lose your data.
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
sachin.parmar100 said:
You need stock recovery to proceed flashing the OTA, custom recovery won't flash the OTA, i don't think being rooted is the issue Just flash the stock recovery to solve the problem.
Click to expand...
Click to collapse
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Yaz75 said:
Rooted IS an issue. You can't be rooted and apply the OTA file, it will fail every time. As a previous poster has said, the phone MUST have stock bootloader, recovery and be not rooted for the stock OTA's to apply. If they see any modification during the process, they abort. It's been discussed many times.
Click to expand...
Click to collapse
thanks for pointing out i was so wrong