Related
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
goodboy1 said:
I am on a stock rom, rooted with twrp. I downloaded the 4.4.3 update ota but when rebooting it went to twrp and I did not know how to proceed so I booted to system. The update did not apply and I am still on 4.4.2
Now I cannot download the update again as it says I have the latest version.
Please tell me how I can get 4.4.3
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
First make sure you have the latest twrp, then boot into it, flash the ota zip from inside twrp, the ota zip is located in /cache...be sure to wipe cache and dalvik before restarting.
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Me too!
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
goodboy1 said:
Many thanks for the prompt response. Unfortunately, when I try and install the update I get a message
Unexpected Content in system/app/iWnnIME.apk
Many thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
brandypuff said:
I am having the exact same problem. I got a notice that an update was available but when i did the update via TWRP, it rebooted and i was still on 4.4.2. It thinks i already updated so say's I am already up to date when i check for updates again..
So i downloaded the 4.4.3 update zip file from somewhere and put in on my SDcard. Then went into TWRP to install it and it complains that /system/app.Videos.apk has unexpected contents - WTF??? Then aborts. Why is a simple update so damn problematic?
Am i out of luck? I don't want to have to wipe my tablet and start over.
James
Click to expand...
Click to collapse
Both of you modified /system, you must dirty flash your stock system.img then flash the ota. Additionally, if you are using a custom kernel, you will probably have to flash the stock boot.img as well.
And both if you, don't forget to do a nandroid first!
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
brandypuff said:
By dirty flash if you mean wipe Dalvik and cache, i did that and then tried reflashing the update but it failed again.
James
Click to expand...
Click to collapse
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Updated!
Bought my Nexus recently and it was android 4.3 [Dad bought it in US and forgot to check the version)
I got the OTA update to 4.4.2 a few days back but it didnt install though it finished downloading. After trying all methods, i decided to do it with Nexus Root Toolkit. But to my surprise, NRT had the 4.4.3 stock img already! I flashed it and my Tablet is smooth. No problems noted till now. If you want me to check whether a particular app is working in 4.4.3 properly or not, let me know. I will test it and tell you
mdamaged said:
No, what I mean is you need your system.img (and boot.img if you use a custom kernel) from the stock rom, then you need to flash that over your /system and /boot respectively, then flash the OTA, then wipe cache and dalvik.
And both if you, don't forget to do a nandroid first!
Click to expand...
Click to collapse
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
brandypuff said:
Hmm..I don;t remember removing video.apk but i may have done some house cleaning awhile back. i know i don't have a backup of it anywhere. Since I'm not running a custom kernel, i just need to flash razor-kot49h-factory-ebb4918e.tar, wipe dalvik and cache and then the update and then the update should work ok? will i lose any of my installed apps after flashing the factory image? I'm assuming this puts it back to the original out of the box OS.
Actually, if that's the case that I will lose everything, why can't i just flash the factory image 4.4.3 (KTU84L) directly?
James
Click to expand...
Click to collapse
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but any changes you made to /system will be gone, you will have to reapply those changes.
You did not ask, but I use MultiROM, and I will flash a new version to a secondary, then use titanium on app data, then boot into the new secondary, make whatever changes I need to, once I am fine with how it works, I then migrate my data to it, then use the swap ROM function in MultiROM. The whole OTA thing is a PITA when you modify too much of the system.
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
i.e.:
fastboot flash system system.img
...then flash the OTA, then wipe cache and dalvik.
This process will revert system to stock, thus allowing the update to work. It will not wipe data, but anychanges you made to /system will be gone, you will have to reapply those changes.
Click to expand...
Click to collapse
Thank you very much!
I will try this.
James
I fought with the Nexus 7 {2013} 4.4.3 update for a good day and a half. Tablet rooted with xposed modules , etc. Same messages you got.
Found that this method works very easily and preserves all data. Takes a few minutes to accomplish, then just one minute to reroot. Try this, it works:
http://nexus5.wonderhowto.com/how-t...ndroid-4-4-3-without-losing-any-data-0155334/
sucess
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
brandypuff said:
OK, I was able to update successfully.
I copied down the factory razor 4.4.2 kot49h image from google and extracted the tar file using cygwin's tar because winzip was giving me errors reading the tar file. Once i extracted the contents, i used ext4_unpacker to extract the system folder. I then copied videos.apk to the system\app directory using a the File Manager App and provided the correct RW attributes.
I tried the upgrade again but got an error this time about system\bin\app_process. I searched the web and realized that i need to uninstall the Xposed framework. Then i tried the upgrade again. this time it worked. I wiped dalvik/cache and rebooted. However, now I've lost root and need to remember how i rooted initially.
Thanks all.
James.
Click to expand...
Click to collapse
Just download the newest SuperSU and flash it from recovery. Then install busybox from playstore.
I had to uninstall xposed, re enable all apps. Recovery, install update in cache, wipe cache dalvik, reboot, reboot to recover flash su, boot, install supersu, reboot to TWRP and boot then reinstall xposed.
Yep if you're unlocked and rooted it can be done without a computer but it's way slower!
Sent from my Nexus 7 using Tapatalk
Thank you everyone. I used the nexus toolkit suggested a few posts back and everything works.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
mccartad said:
I am having a similar issue where the error that pops up for me says "/system/bin/app_process has unexpected contents". I tried uninstalling xposed and gravity box but that didn't help. Help?
Click to expand...
Click to collapse
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
mdamaged said:
How did you uninstall xposed? If you did so the way you normally uninstall apps, you did it the wrong way. You should have uninstalled it from within xposed. I think you can still fix it by reinstalling xposed and doing it the right way.
Click to expand...
Click to collapse
Holy shnikies it worked! Thanks so much!
mdamaged said:
No, no, no, extract system.img from this zip, then fastboot flash them.
Click to expand...
Click to collapse
can anyone please confirm that this is a flashable .zip of a full stock Kit Kat 4.4.3. or can anyone point me to one. - thanks :cyclops:
Idk what i did to my phone lol but all my Google apps force close and idk how to fix it any help?
Darkness2147 said:
Idk what i did to my phone lol but all my Google apps force close and idk how to fix it any help?
Click to expand...
Click to collapse
If you want help, you will have to give more info than that. What ROM are you running specifically? Did you make any changes before this problem occurred? Is this a fresh install?
Killa357 said:
If you want help, you will have to give more info than that. What ROM are you running specifically? Did you make any changes before this problem occurred? Is this a fresh install?
Click to expand...
Click to collapse
It's the factory TouchWiz rom and yes it was a fresh 4.4 kk install and I did root it could it be the host file? Cause I did another fresh install and all the apps work fine now except Google play store I've tried uninstalling it and then downloading the new version and putting it in system/apps giving full permissions for install then restarting my phone and nothing seems to be working. I did mess with the host file awhile ago but I did a fresh install again.
Darkness2147 said:
It's the factory TouchWiz rom and yes it was a fresh 4.4 kk install and I did root it could it be the host file? Cause I did another fresh install and all the apps work fine now except Google play store I've tried uninstalling it and then downloading the new version and putting it in system/apps giving full permissions for install then restarting my phone and nothing seems to be working. I did mess with the host file awhile ago but I did a fresh install again.
Click to expand...
Click to collapse
I don't see what a host file would have to do with all of your apps crashing, but then again doing a full wipe and reinstall should fix it if it was something you did with a file. Maybe you have a bad image? Could always just try going to your recovery doing a full wipe without reflashing and see if that fixes anything. Is the play store just force closing or what?
Killa357 said:
I don't see what a host file would have to do with all of your apps crashing, but then again doing a full wipe and reinstall should fix it if it was something you did with a file. Maybe you have a bad image? Could always just try going to your recovery doing a full wipe without reflashing and see if that fixes anything. Is the play store just force closing or what?
Click to expand...
Click to collapse
Yeah its just the Google play store and I've already done a full wipe first it was all the Google apps force closing literally now it's the playstore
I'm trying to update my E975 to v20A (kitkat) using software update app on the device. 1st try, I get notification that my phone is rooted and installation cannot continue, so I use Framaroot to unroot my phone, then I tried again to update my phone and I get, "installation error" msge and not knowing what cause the error.
what should I do?
frans3q said:
I'm trying to update my E975 to v20A (kitkat) using software update app on the device. 1st try, I get notification that my phone is rooted and installation cannot continue, so I use Framaroot to unroot my phone, then I tried again to update my phone and I get, "installation error" msge and not knowing what cause the error.
what should I do?
Click to expand...
Click to collapse
You should either flash back to original stock from your region or root your phone again, install CWM and install artmod - I suggest the latter.
http://forum.xda-developers.com/opt...om-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
nchc said:
You should either flash back to original stock from your region or root your phone again, install CWM and install artmod - I suggest the latter.
http://forum.xda-developers.com/opt...om-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
Click to expand...
Click to collapse
means you suggest I should use the artmod?
well, I used CM11 before, but I think 4.1.2 stockrom is better, and I use QSlide a lot. Then I flash using KDZ back to my original stock ROM. (that my current ROM, 4.1.2 stock rom)
then I read about official Kitkat release and I think the v20a official update will included all previous LG feature so I decided to try it.
But now I'm experiencing a lot of problem, the software update didnt works, so I download the .zip from this thread : http://forum.xda-developers.com/showthread.php?t=2784649 but it didnt work, and I'm having a bootloop.
I dont know, should I re-lock my bootloader before trying to update / flashing the official ROM?
I had try flashing CM11, and no problem.
Try again and if you didn't before do a very clean install i.e. factory reset,clear cache and dalvik cache, format system. Stock KitKat has a different partition setup compared to stock jb,I'd say that's what's causing errors.
nchc said:
Try again and if you didn't before do a very clean install i.e. factory reset,clear cache and dalvik cache, format system. Stock KitKat has a different partition setup compared to stock jb,I'd say that's what's causing errors.
Click to expand...
Click to collapse
thx. looks like I need a very clean install... software update method still wont work, but installing .zip from CWM work was working.
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Seattleweather said:
I have rooted firetv 1 with latest rBox pre-rooted ROM. I have noticed if I put the box in sleep mod for a while, it will change to TWRP recovery screen when wake it up. I have to reboot it every time in order to back to normal. Anyone has the same problem?
Thanks.
Click to expand...
Click to collapse
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Y314K said:
Most folks that have had this problem is because they did not block updates properly. And you have an update in the hopper. And TWRP being your last line of defense is blocking the installation of that update since it is not a PreRooted ROM. So each time your device is idle it tries to install the update. And TWRP stops it at reboot.
Luckily there are solutions.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
And at the very least do Method 1. But both Method 1 & Method 5 are what is recommended to stop this from happening in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Click to expand...
Click to collapse
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Seattleweather said:
Thanks you very much. I believe I did one BEFORE flash to new pre-root ROM. I tried to do it again this morning, found the superuser is not there anymore after flash to pre-root ROM from rbox. I am confused since I rooted firmware and unlocked bootlocker. I does not me to install superuser anymore. Please help me:crying::crying::crying:
Click to expand...
Click to collapse
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Y314K said:
If you are able to still go into TWRP. I would try to flash the latest PreRooted ROM using a USB Stick. Also make sure you include a MD5 for safety. DO NOT WIPE anything but Dalvik Cache & Cache. See if that restores your PreRooted FW back to normal. This is just a guess since it has never happened to me before.
Maybe someone with this problem the fixed things can chime in. Others that this has had happened to did not have access to TWRP.
Click to expand...
Click to collapse
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Seattleweather said:
FIXED!!!
I tried to install superuser apk , but failed. Since I still have access to TWRP, I installed with flashable superuser. Then I cleared OTA and blocked the updates again with your suggestion. I did Method 1 before, but forgot to do it again after update. Thank you very much!!!
Click to expand...
Click to collapse
np, glad it is back to normal.
Method 1 helps when you flash a new PreRooted ROM. And Method 5 helps to make sure your FW version is never low enough to think an update would apply to your device. Method 5 needs to be redone when ever you flash a ROM. And Method 1 must be redone when ever you factory reset thru TWRP or clean more then the Dalvik Cache & Cache thru TWRP. NEVER do a factory reset from FireOS 5. Only use TWRP for that.
Forgot to add. NEVER INCLUDE SYSTEM IN ANY OF YOUR WIPES. Flashing a PreRooted ROM will take care of System. So leave it alone. Most bricks happen because folks wipe SYSTEM & they do not Flash a PreRooted ROM before doing a reboot.