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
I have a nexus 7 2013 on android 4.3 and twrp 2.6.3.1. Because of twrp I can't upgrade my Nexus 7 2013 to Android 4.4.
What are the steps to do it manually?
I upgraded to 4.4 using TWRP 2.6.3.1 just fine.
I clean flashed a stock JSS15R image from Google, flashed TWRP and then flashed the 4.4 OTA update zip with no issue.
Please explain
iPWNtehNOOB said:
I upgraded to 4.4 using TWRP 2.6.3.1 just fine.
I clean flashed a stock JSS15R image from Google, flashed TWRP and then flashed the 4.4 OTA update zip with no issue.
Click to expand...
Click to collapse
Fine to know that it works.
But could you please tell what are the steps I have to do because I have never upgraded Android in combination with twrp?
I used this on mine... Worked perfect
http://www.androidbeat.com/2013/11/install-android-kitkat-rom-nexus-7/
This belongs in Q&A, not the general forum.
Secondly, many people have updated to 4.4 using a variety of methods. If you aren't going to read, I submit you'd probably be better going to the stock recovery, updating via adb sideload & then using a basic root method (if you really need root) like Chainfire's CF-AutoRoot.
Sent from my Nexus 7 using XDA Premium HD app
cx1964 said:
Fine to know that it works.
But could you please tell what are the steps I have to do because I have never upgraded Android in combination with twrp?
Click to expand...
Click to collapse
You should literally be able to just flash the OTA zip file through TWRP.
Failing that, download the KRT16O stock ROM from here, extract that to your platform-tools folder, then run:
fastboot flash boot boot.img
fastboot flash system system.img
Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Tinfoil Hat Tom said:
Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Flash the complete 4.4 KRT16S factory image. Download from here and extract the zip to your adb/platform tools directory. Make sure your drivers are working properly. If you don't want your data wiped, edit flash-all.bat and remove -w. Connect your phone and boot into the bootloader (you can do this by opening cmd in adb directory and entering "adb reboot bootloader"). Now simply run the flash-all script and wait for it to complete. You are now on KitKat 4.4
Flash TWRP and anything else you want to flash. Download and flash the 4.4.2 update if you want.
Thanks a lot for the quick reply. I managed to get root and twrp back using wugfresh's kit. It seems to me that twrp is not good with OTAs(there is a page on their site re. this) which might be the reason for this mess.
So now instead of flashing the zip using adb, can i do it with twrp? I dont have much experience with adb since i have always used twrp. (I am not averse to using cmd but the 480 mb download for the sdk just to get adb and stuff puts me off).
Do I necessarily need to wipe my data to install the kitkat update?
Sent from my Nexus 4 using xda app-developers app
Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!
dragancla said:
Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!
Click to expand...
Click to collapse
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?
Razor is the 2013 model. You might want to mention that before people here download your link and ruin their grouper or tilapia....
Why wouldn't you just download the stock images straight from Google? You didn't need to downgrade anything and you don't use Odin with a nexus....
Sent from my Nexus 5
dragancla said:
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?
Click to expand...
Click to collapse
Possibly...
Any modifications you may have made to your Nexus 7 (other then rooting and a Custom Recovery installed) will almost certainly cause an OTA to fail... as an OTA first runs a checksum verification test on all system files to ensure they are the original system files.
If they've been modified by the user, they cannot be 'patched', ie. updated... so the OTA aborts with no changes made.
Anyway... you really should be posting your question(s) here...
http://forum.xda-developers.com/nexus-7-2013
...as the Razor recovery you posted clearly identifies your device as a second generation Nexus 7(2013), and as @Pirateghost points out, posting that recovery in this forum could potentially mess up other peoples devices, if they were to flash it.
Rgrds,
Ged.
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
UPDATE 1: Possible Solution
So, turns out you should be completely stock, means you should have stock recovery and NO ROOT. Stock Recovery can be Installed through 'Wugfresh' and unroot through SuperSu Setting. BUT, if you have modified even a single thing, YOU WILL A FACE ERROR as shown in the second screenshot. SO you will have to 'Fastboot Flash' the system.img from Factory image. I'm downloading The 5.0.0 Factory image right now and it will be downloaded by 2 hours.
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
You can get the stock recovery from the nexus factory images here . I would suggest just flashing the factory 5.0.1 image (don't flash userdata or cache and you should be fine).
I think OTA is only from 5.0.0 to 5.0.1.I'm having the same problem too and nobody seems to have an answer so I'll just get the factory images, flash all except user data
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember
You mean bringing silent mode back, getting a hold on the countless graphical glitches (yes, mine were all clean flashes) and maybe even grace us with a 3.10 kernel?
I was hoping on that as well, but it looks like we really are the rearmost wheel on the Google cart.
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps
parkourz said:
So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember
Click to expand...
Click to collapse
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...
matiamb said:
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...
Click to expand...
Click to collapse
I think it was something with security... but good to know that nothing has changed before flashing it
did we get a new kernel with 5.0 update?
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
EDIT: Recovery update did not help, still getting 4.4.2 fingerprint.
VinceCZ said:
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
Click to expand...
Click to collapse
I don't think I will work. Starting from lollipop, the update process is not like previous versions. It needs the system partitions to be completely unmodified. That includes the recovery partition and root to be hidden (temporary unroot in the supersu app). I tried to flash ota file with adb sideload and twrp and also cwm (both newest version) and failed. It can only be flashed successfully with stock recovery.
I heard what you are saying from more guys so I will try that.
EDIT: I made unroot and flashed stock recovery but getting error 7, which is basically the same as with custom recovery.
hk.happy said:
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps
Click to expand...
Click to collapse
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?
There is no solution yet.
VinceCZ said:
There is no solution yet.
Click to expand...
Click to collapse
Guys, for the ota to work you need to be unrooted and 100% stock recovery, system, and kernel.
Sent from my Nexus 5 using XDA Free mobile app
veketash said:
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?
Click to expand...
Click to collapse
I'm not sure but I think it will break root no matter how you update from 5.0.0 to 5.0.1, and you will have to flash supersu zip again, but again, i'm not sure....
Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.
VinceCZ said:
Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.
Click to expand...
Click to collapse
Flash the system, recovery, and boot images from 5.0 in fastboot. Then try the ota
Sent from my Nexus 5 using XDA Free mobile app
I suppose it will delete user settings and all, will it not?
VinceCZ said:
I suppose it will delete user settings and all, will it not?
Click to expand...
Click to collapse
no, it won't delete anything.
Sent from my Nexus 5 using XDA Free mobile app