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
Related
Received 4.2 ota so I protected root and proceeded to install.
Device rebooted and went straight to android with red exclamation mark then booted back to 4.1.2 with no option to try again?
I am stock rom, rooted and unlocked, but without cwm installed. Can someone tell me what I have to so next so I can try again.
I never had this problem last time when updating to 4.1.2
Many thanks.
Sent from my Nexus 7 using Tapatalk 2
exactly the same problem here
same here and im not rooted
You have to have STOCK BOOT, STOCK RECOVERY & the device MUST BE BOOTLOADER LOCKED (>fastboot oem lock).
Boot loader doesn't need to be locked and you can have a custom recovery, too. But this will be removed during the OTA install. The same for root, I.e. after the update fastboot flash recovery again and then flash superSU and you are done.
Sent from my Nexus 7 using xda app-developers app
If you flashed the 720p camera mod that might be the problem. I had the same issue till I restored the original media_profiles.xml
Sent from my Nexus 7 using XDA Premium HD app
Same here. I got the notification and whent it rebooted it was still 4.1.2. I tried to upgrade manually through recovery (TWRP) but the installation failed, so no 4.2. Are you sure the bootloader needs to be locked? When I upgraded to 4.1.2 i installed the update normally and had to re-root and re-install custom recovery. Anyone has solved this issue?
+1 rooted, cwm and uninstalled all blotware.. when i try to install ota 4.2
it gets me some errors and dosent install...
Dont wanna lose my data and dunno what to do :s
Not sure if y'all are still stuck on 4.1.2 or prior, but turns out it was the 720p camera mod after all, as AntiPhotonz pointed out earlier.
Using these instructions, I restored the old media_profiles.xml in the /system/etc/ folder. To be safe, I renamed the current (modified) media_profiles.xml to media_profiles.xml.new. I then rebooted, and tried to update OTA. My OTA updater didn't recognize that I was not on the latest version, so I downloaded the signed zip directly to my internal sd card, and then rebooted into CWM and flashed it that way.
I then updated to 4.2.1. via OTA. I may flash the new 720p profile zip when I am able. The zip did not exist when I first tried to apply the mod; let's hope this will be much less messy.
Hi guys, I noticed a problem with the ota upgrade from 4.4 to 4.4.2 .
When I had the notification of the upgrade, i skipped it because I have root and I need it. Finally I decided to upgrade, but when I did it and the device rebooted, it gave me error and the version of android remained 4.4 .
I tried to flash the occam KOT49H from KRT16S zip with custom recovery but it gave me error again.
Anyone knows how to help me or the only way is flashing the factory image? And if so, can I restore a backup from different version?
Thanks all.
P.S. These are my specs:
LGE Nexus 4
Unlocked Bootloader
Root + Busybox
ClockWorkMod Recovery 6.0.4.3
Franco Kernel r197
Android 4.4 KRT16S
Don't update from 4.4 to 4.4.2, if you ask me!
With 4.4 I had everything working fine, but 4.4.2 gave some bugs.
So I wouldn't hurry if I would you, maybe a new bugfix will come shortly.
To do OTA upgrades your device must be completely stock - that is, you need to get rid of root privileges, restore the stock kernel and probably flash back the stock recovery as well.
To unroot, simply flash the system.img file from the 4.4 image via fastboot (fastboot flash system /path/to/system.img).
To restore the stock kernel: fastboot flash boot /path/to/boot.img.
To restore the stock recovery: fastboot flash recovery /path/to/recovery.img.
Finally, you might want to format cache as well: fastboot format cache.
Once you're done with the steps above, OTA upgrade should work without issues.
Sent from my Nexus 4 using Tapatalk
antofiasco said:
Hi guys, I noticed a problem with the ota upgrade from 4.4 to 4.4.2 .
When I had the notification of the upgrade, i skipped it because I have root and I need it. Finally I decided to upgrade, but when I did it and the device rebooted, it gave me error and the version of android remained 4.4 .
I tried to flash the occam KOT49H from KRT16S zip with custom recovery but it gave me error again.
Anyone knows how to help me or the only way is flashing the factory image? And if so, can I restore a backup from different version?
Thanks all.
P.S. These are my specs:
LGE Nexus 4
Unlocked Bootloader
Root + Busybox
ClockWorkMod Recovery 6.0.4.3
Franco Kernel r197
Android 4.4 KRT16S
Click to expand...
Click to collapse
You can't update when you've rooted your phone if you want to update it so badly you could restore back to stock android.. Hope it helps.. ?
Sent from my Nexus 4 using XDA Premium 4 mobile app
As was said previously, OTA requires stock recovery.
Solved
I have had the same problem, try this.
Yes I wrote it by my self.
Update android 4.4.2 fail/error7
http://forum.xda-developers.com/showthread.php?t=2571534
I hope it helps for you, but you have to use android adb from the sdk of something like that.
Thanks everyone for your help
Sent from my Nexus 4 using xda app-developers app
Do you have problems updating Nexus 7 from Jelly Bean to Kitkat? Well I did, since the day got my hands of N7 device, it was unlocked and rooted.
Somewhere is Sep the News of Kitkat has been rolling out. In Oct my N7 device notified on the new Kit Kat upgrade. I have been trying using OTA update but each time came to "FAILED" installation and so decided to give up the idea since JB 4.3 was working fine.
Now Kit Kat rolled out 4.4.2 version and still I had the same problem, did some researched on XDA forum and tried each of their suggestion but still did not work out. I was always stuck with "KoreanIME.apk" error on recovery, perhaps something I deleted earlier on.
Using Nexus Root Toolkit Ver 1.8
Finally decided to use the Nexus Root Toolkit (NRT). The last time used it was rooting the brand new N7. Run NRT and it started gathered information and upgraded to latest NRT ver 1.8.
With the new NRT version I decided to Flash Stock + Unroot, hoping I can do the update by going back to stock. To my surprise NRT found the latest Kitkat 4.4.2 and installed on Nexus 7. Most of the data was lost but had earlier done a backup. After which just like a brand new device, log in my account and immediately all the previous Apps started to download back to the device.
Once that was done, Root the device using NRT included Custom Recovery check, the rest just follow NRT instructions to install BusyBox and all is Done!!
Apps like Watsapp had to be installed manually since it does not support tablet version. Other data were also done manually.
I would not recommend this method unless you are prepared to wipe everything clean, so do a backup first. There were no other options and this was the only method.
Hope this helps and if anyone can point out the mistake I have done, do share for others.
OTA update doesn't work with custom recovery if I'm not mistaken
OTA can work with custom recovery, I've done it several times, though the custom recovery was overwritten by the update.
Sent from my SGH-I747M using xda app-developers app
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
clienttrace said:
Yes, OTA in the form of .zip file can be flashed via custom recovery.
But it seems that OP's problem occurs when he's trying to update from official OTA notification, from my understanding if you try to update from official OTA notification with custom recovery installed it will fail.
Please correct me if I'm wrong since mine was done through adb sideload
Click to expand...
Click to collapse
Just for clarification, besides using auto OTA update, I did tried it manually using razor and SuperSu zip files. Also as you mentioned ADB sideload. It did not work out.
Somehow using NRT was much easier, just sit back and let NRT do all the job. The only setback were the missing data. Not a big issue, anyway was nice to see the file structure cleaned up.
gc84245 said:
I did it through the official OTA (not a zip file) with a custom recovery. There seems to be a myth out there that it's not possible, but I can say from experience that it is possible.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
thanks, that's clear it up for me
Ok so currently running a rooted VS980 on 12B with CWM 6.0.x.x non touch. I have attempted to flash both CM10.2 and a 4.4 kitkat absed rom (pa_g2-4.0-ALPHA-20131205-vs980). In both cases I get the same error,
asset failed: run_program("/system/bin/loki.sh") == 0
E: Error in /data/media/o/ (filename of rom in zip format)
(status 7)
installation aborted
My current steps are a backup of rooted 12B,
wipe/factory reset
wipe cache partition
wipe dalvik
format system.
I also attempted to install a GAPPS .zip to see if it was happening with all zip files, the GAPPS installed with no issues.
phone also will take a restore from CWM so at least im not bricked in the meantime
Now that that is all out of the way can anyone tell me what is happening here? Only my second rooted phone first being a droid 4 and by the time I rooted it there was a lot out in the form of auto runs and apps to take care of all the steps to root/flash roms. So my knowledge level is pretty novice on this.
UPDATE: so after my reading im coming across random issues with CWM on the LG G2. going to attempt to push ASOPA 4.4 with GAPPS after I switch to TWRP.
Get same thing on trwp
Sent from my VS980 4G using XDA Premium 4 mobile app
Make sure you are on the latest versions. Darker ones will not install kitkat. Roms
Sent from my LG-D800 using Tapatalk
UPDATE 2:
Ok, so after following the guide below and face palming myself about a thousand times through the process, I've come to another snag..... I get all the way to the end in both options 1 and 2, then get the error below. Option 3 (GooManager) states that there is no recovery for my phone.
http://forum.xda-developers.com/showthread.php?t=2449670
[+] loki_flash 2.1
[-] loki aboot version does not match device
looked around through the thread and cannot find a definitive answer on what im doing wrong or what I may have done wrong in rooting or with already running CWM.
I want to attempt to go back to stock. Completely unrooted and start from scratch but not sure the path to take on this. I've factory reset via CWM but the phone is still rooted and the apps i removed via titanium backup are missing as well.
Is there a way to pull a stock firmware and somehow push it to the phone so that everything i have done thus far is erased? ( excuse the terminology here) like erasing and reformatting a computer's hdd and re installing windows.
update:
http://forum.xda-developers.com/showthread.php?t=2432476
Hopefully this stock firmware guide works...
Goo doesn't work either lol. Use freegee to install recovery. Will take you about 2 minutes to complete and you will be rooted and have a custom recovery installed
Sent from my LG-D800 using Tapatalk
Thats how I got CWM onto the phone after I rooted. After all my reading though, I want to go back to stock and start all over again. I still haven't got a chance to start the proccess yet, been pouring through the thread about reverting back to stock firmware to see what issues have come up. From mwhat I can tell the issues were all related to people not fully reading the directions provided by the OP. Will update once I have attempted. FreeGee worked like a charm for getting CWM on though
Ok, so using the thread listed above i was able to revert back to 11a!!!!!!! now, onto IORoot and see if i can loki twrp 2.6.3.2 and then flash 2.6.3.3.
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
corrsea said:
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks for clarifying that!!!!!
So as of now I have re flash stock 11A per the guide (showed unrooted once done), Rerooted via IORoot 22 and then adb flashed twrp 2.6.3.2, Now I am going to flash the 2.6.3.3 .zip via TWRP and then try to flash A ROM and Kernel.
Back up and running!!!!
IORoot22
TWRP 2.6.3.3
ASOPA 4.4 BETA (updating as daily releases come out)
Slim GAPPS (might switch to regular due to the speech to text function being missing from keyboard but need to do some reading to figure out if running the full GAPPS will fix that or if it is something with the ROM ) EDIT: as i typed this i got a text and as i replied I noticed the icon is there now on the keyboard.... FACEPALM....
Thanks for all the information that was provided guys. Probably could have cleared this all up without the thread and just reading, Thanks for not flaming me and turning me away with a statement to use the search function.
To anyone reading this to find a fix for an issue they are having here are the links in order of what I did to get back up and functioning.
1. Went back to stock
http://forum.xda-developers.com/showthread.php?t=2448960 ( how to go back to stock )
http://forum.xda-developers.com/showthread.php?t=2141817 ( how to set up SDK )
2. ReRooted
http://forum.xda-developers.com/showthread.php?t=2448887 ( IOROOT how to )
3. TWRP
http://forum.xda-developers.com/showthread.php?t=2449670 ( TWRP how to )
All these guides worked the first time through for me, make sure you take the time and read all the directions in them.
I got the 4.4.3 update notification and downloaded it. When it rebooted for the install, it went into TWRP recovery. Not sure what to do with that, I rebooted. Now I am still on 4.4.2 and getting the "up to date" when I check for updates.
I am rooted running stock ROM. Does being unlocked and rooted with custom recovery prevent an OTA install of updates?
I vevs
Sent from my Nexus 7 using XDA Premium 4 mobile app
I'm also looking for help updating to 4.4.3. I uninstalled Xposed and tried to flash the update zip with TWRP but the install failed. Does the update need to be installed via adb sideload?
Sent from my Nexus 7 using Tapatalk
When my n7 was on 4.3.1 stock rooted with unlock bootloader i updated via ota and twrp can handle it. I dont know about 4.4.3. There is a thread discussing this matter but i dont remmember where, i think is in the general. I never used side load but im using nrt nexus root toolkit for udpating to 4.4.3 and it work fine.
vs980
Same problem!!
Exactly same has happened to me. I got the notification for update than i downloaded it, it was about 70 mb , then rebooted my device, goes to TWRP recovery than what ?? I just restarted my device and in settings its still on 4.4.2 what to do Now ????
Hey all
What does TWRP stand for please?
I also got the notification to update to 4.3.3 but after downloading, when the installation began I got an error screen with the android dude lying on his back. I switched my nexus off and on again and I'm still on 4.2.2.
Now I get the same message when I check for updates.
How can I get my tablet to update again please?
My nexus is a regular unrooted tablet with the stock ROM that was installed via the previous ota update.
Many thanks
Sent from my Nexus 7 using XDA Free mobile app
hmmmm, sounds odd. same thing happened to me.
maybe TWRP(Team Win Recovery Project) cant handle it, or we should have updated it first. Or maybe we should have used CWM or Stock Recovery.
but the strange thing is that the tablet cannot find the update again!!
i'll try to update NRT (Nexus Root Toolkit) and see if i can update using that.
Don't install it, until there's an answer in http://forum.xda-developers.com/showthread.php?t=2786758 - a couple of us did install it, and we've lost root, but more importantly, recovery has been wiped, and I've been unable to reflash CWM with fastboot.
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
GrillMouster said:
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
Click to expand...
Click to collapse
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
hamid_valad said:
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
Click to expand...
Click to collapse
Flashing stock recovery.img and stock system.img does not wipe all my data. Everything was still there: all my media, files, apps, and app data.
I think you're right about the Stickmount app. I did have it on my son's tablet, and I had to flash system. Last night I updated my wife's tablet. She did not have Stickmount, so the OTA installed without me having to flash system. Just to be safe I did flash stock recovery first. I put TWRP back on and re-rooted after the OTA.