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:
Related
Hi, hope my exact issue wasn't discussed after page 10 of the help & troubleshoot forum, anyway my rooted, unlocked cwm recovery stock 4.2 yakju (if I remember well) Samsung GNEX started to behave strangely slower then usual less then a week ago, then a couple of days later I woke up after night battery recharge to the boot up animation which never gave way to the operating system starting up.
After the first moment of despair I tried reading something here and with the use of adb I was able to first see the device and, after backing up via recovery, to pull the files from the phone (backup included). Problem is the 0 folder is very light for all the data and apps that I had, and inside the DCIM folder there's nothing, no trace of the 1k+ picture I shot in the past couple years, only an igc file which should have been in another folder. But strangely enough the backup weights almost 6GB which is consistent with what was inside prior to the crash.
Before attempting the backup I fiddled with recovery and tried to wipe cache, dalvik and fixing permissions, with no apparent results.
So now I'm undecided whether to take the phone to a samsung job centre which will surely wipe all data and possibly find out I have a corrupt memory or partition table, which renders many files and folders unavailable to be adb pulled or to wipe data/restore factory by myself hopying, fingers crossed, that the backup actually saved all my files and that could be restored without hassle. I actually had hoped that, like for the desktop environment, there was the possibility to awake my phone with a linux live or whatever to check if all files were present and downloadable before actually restoring the phone.
Thanks for your interest and help.
https://drive.google.com/file/d/0B8Pbk0TslYN6cm1wWWZydVM2V0k/edit?usp=sharing
Have you tried dirty flashing your rom?
Sent from my Galaxy Nexus using XDA Free mobile app
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
berniefranz said:
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
mrgnex said:
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
Click to expand...
Click to collapse
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
mrgnex said:
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
Click to expand...
Click to collapse
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
ashclepdia said:
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Click to expand...
Click to collapse
small update, I managed to download the correct rom and I tried to adb push the .tar to the device (twice and attempting a third to /sdcard/ /sdcard/clockworkmod/ and now /sdcard/0/Download/) but still haven't been able to spot the uploaded file to choose for dirty flash. adb shows the file as uploaded , but again no sign of it with CWM Recovery. should I try to install TWRP recovery? with the nexus toolkit there is a function to flash a rom, but it says it will wipe the device first, so it's really not the option I was looking for. Another strange behaviour of CWM Recovery, or maybe my phone, inside mounts and storage menu, mount sdcard seems to be not working as it never changes to unmount after you click it. I think my memory went berserk and that's the reason why the phone rebooted and never woke up again. Maybe I'll take to the nearest job center to ascertain the damage...
thanks for all your help
berniefranz said:
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
Click to expand...
Click to collapse
installed TWRP and was able to see to rom.tar uploaded via adb in the download folder, but wasn't able to use to flash as probably both recovery wants .zip and not .tar, so I'll now untar and zip the stock rom and upload it again...
small steps...
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
berniefranz said:
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
Click to expand...
Click to collapse
Had to take it to the job center where, it was downgraded to 4.0.4 (have still to check which flavour) fixed something and Wiped everything. When I side about he post mortem backup and the intention to try a restore from there I was give an are you kidding look, it could crash again... sigh.
Anyway thanks everyone that spent some time to try and explain a noob how to try to solve this issue.. Now I've got a new galaxy nexus, so after a little grievance I'll start reading on how to flash a nice rom...
berniefranz said:
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
Click to expand...
Click to collapse
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
[email protected] said:
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
Click to expand...
Click to collapse
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
mdamaged said:
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
Click to expand...
Click to collapse
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
[email protected] said:
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
Click to expand...
Click to collapse
There are multiple ways to update, you asked about OTA, in order for OTA to work, the OTA expects the device to have certain files at a certain version, one of the things it checks, besides files in /system, when there is a change to it, is the kernel, so a OTA will fail if it checks the kernel and finds timur's in its place, which is why I suggested you just flash the stock boot and system (yes, you can always go back to timur's afterward assuming it is compatible with the new ROM, you will also have to reroot/redo changes to /system).
The OTA is downloaded into /cache, and if the cache is wiped the OTA file will not be there, so once it is downloaded, use a root filemanager, and copy it to your sdcard, then it won't get wiped.
The other way to update is to just flash the changed images individually from the factory images using fastboot, making sure not to flash the images which would wipe any boot, userdata, or custom recoveries...as long as you do not flash boot.img, you will keep timur's kernel, but you will have to reroot/redo changes to /system.
You can also use the factory image flash-all.bat to do this, BUT you must delete the -w option in the bat file, not doing so will result in your device being wiped, you will still have to reflash timur's kernel using this method as well as reroot/redo changes to /system.
Either way, when you update, wipe dalvik and cache before rebooting.
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
[email protected] said:
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
Click to expand...
Click to collapse
Yeah, you can use TiB to backup apps and appdata. I would also advise you do a full nandroid (no need to backup cache though). Save them all to your PC.
As for whether it's worth it, you'll have to read the changelogs for yourself and find out if it is to you or not. Really it's not much work at all to update.
You can always wait around for Android L.
D85120G-Untouched_Stock_Restore.zip
Flash Full Stock (system/kernel/modem/recovery) No Root, No Mods, 100% Stock
Thanks.
Since this is the full rom, not OTA, has anyone successfully twrp from stock rooted 20e and then SuperSU and kept root? Will TiBu frozen system apps stay frozen as well? TIA
What exactly is this rom?
cenwesi said:
What exactly is this rom?
Click to expand...
Click to collapse
The name of the zip file and first post tells you what it is.
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5
do we flash it through TWRP? or any other custom recovery?
Yes, just as you would w/ any other ROM. Perform a full wipe beforehand, excluding both internal and external storage. And if you want to retain root and recovery, make sure to flash those immediately after (add them to the queue in TWRP).
Just flash this rom.. Everything works fine..
Sent from my A1-840FHD using XDA Free mobile app
This may be a stupid question but I flashed this and it says I'm still vulnerable to stagefright, isn't this suppose to patch it.
Sent from my LG-D851 using Tapatalk
I flashed the same 20g ROM, and according to the Lookout Stagefright Detector app, my device is not vulnerable to Stagefright.
works but
Followed these instruction using twrp
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
I had to reset phone after flashing and setting up. Because the phone was no functioning correctly.
Unfortunately Stagefright CVE-2015-6602 is still vulnerable according to
Zimperium Stagefright detector app.
Lookout Stagefright Detector will not detect the latest Version 2.0 vulnerabilities of Stagefright and make it clear in there app description.
"This app does not support detection of Stagefright 2.0 vulnerabilities. "
So here we go again in the waiting game.
Wouldn't it be better if google took Stagefight out of the rom, so it can could be updated in play store?
painless
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Works Great
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
fc3211 said:
Thanks bro,
Did exact same steps as you suggest and it worked great. Just in case anyone needs them....
Here is Super Su:
https://www.androidfilehost.com/?w=...b6cc0224f97f975b25bd6fd089dffab48899dd59ac9fc
ANd here is TWRP:
https://www.androidfilehost.com/?w=...9a65ee4397109b889147c21f3bf0e48037fffad3bccb3
Click to expand...
Click to collapse
Thanks for the two links. Very helpful
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
skipaaa said:
Anyone do it dirty, no wipes? From 20e to 20g? -Cuz restoring apps and settings is "such fun". Thanks.
Click to expand...
Click to collapse
I landed here because I tried the 20e to 20g update and got the "unexpected version" error via twrp. Responding to my own post cuz I got bold and did it anyways.
...So, I had TWRP 2.8.7.0 D851 installed. Did full backups with Titanium paid version and TWRP. Started with STOCK rooted d85120e, left it rooted, and used TRWP to install
1) STOCK d95120g from top of this thread,
2) TWRP d851 2.8.7.0 found elsewhere (above link is 2.8.6.0), and
3) the SuperSU zip from link found just above.
Rebooted system without any wipes. A few minutes to update apps on first reboot and mostly good to go. Had to update SupserSU binaries via normal mode, and reinstall busybox. Busybox froze on black screen on multiple attempts during it's startup check, so on next attempt, I didn't let it finish the check, just told it to install, and has been bliss all day. So far, so stable. Better have the backups and not need them than need them and not have them. Settings show D85120G and Lookout shows NOT vulnerable to stagefright.
Sitting pretty. Hope this helps others who couldn't use the 20E to 20G update method to keep stock roms with optional root.
Wiped everything as stated and flashing reboots TWRP, anyone know why this happens?
Thank you! Works - rooted 20e to 20g
AndroidUzer said:
Wiped cache & Dalvik cache, flashed the OP update zip then flashed TWRP custom recovery and finally SupurSU.
Tested using Lookout Stagefright Detector and all is well.
side note: needed to regain writing privileges for my external SD
Thanks core720!
Click to expand...
Click to collapse
I was on rooted 20e and did what you said. Works like a charm, I have 20g now without any problems. Thank you everyone! :]
I finally came out of lurk mode to say thanks. This untouched ROM has saved me from 2 soft bricks. Works flawlessly.
it has no sound please help
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.
Hi there!
I'm using stock rooted phone on latest stock firmware. I would like to know how I can reflash stock firmware again using TWRP (Wich I have installed already) without loosing data or recovery if possible. Thanks a lot people!
marcomir said:
Hi there!
I'm using stock rooted phone on latest stock firmware. I would like to know how I can reflash stock firmware again using TWRP (Wich I have installed already) without loosing data or recovery if possible. Thanks a lot people!
Click to expand...
Click to collapse
Yes you can reinstall it using fastboot without losing data. You might have to install twrp again and SuperSU if you want root. If you use the flashall method take off the -w.
Tulsadiver said:
Yes you can reinstall it using fastboot without losing data. You might have to install twrp again and SuperSU if you want root. If you use the flashall method take off the -w.
Click to expand...
Click to collapse
Thanks! But I think you can do it right from TWRP. I think it was just wiping SYSTEM and one of the caches, leaving data and internal storage alone, then reinstalling it. I was following a guide once that did this, but can't seem to find it anywhere again. But I think I might go with the method you told me. Thanks for your reply!
marcomir said:
Thanks! But I think you can do it right from TWRP. I think it was just wiping SYSTEM and one of the caches, leaving data and internal storage alone, then reinstalling it. I was following a guide once that did this, but can't seem to find it anywhere again. But I think I might go with the method you told me. Thanks for your reply!
Click to expand...
Click to collapse
You can sideload an ota update thru twrp. Maybe that is what you were thinking about.
Unpack Factory Image and manually flash each .img in TWRP. Just switch from .zip flash to image flash mode in Install section.