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.
Related
My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!
Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Misread OP.
ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all
thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.
My phone prompted me today that an update to 4.2.2 was available.
Its a takju Nexus running with an unlocked bootloader and rooted but otherwise stock rom.
I've tried to get it to do the update, however it reboots to a screen saying "applying system update" then after a few seconds flicks to a screen with an android with an exclamation mark, and the word Error below.
Is this because i'm rooted? or is there something else going on?
Thanks
Kevin
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.
chelseaeuro said:
I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.
Click to expand...
Click to collapse
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.
reysonance said:
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.
Click to expand...
Click to collapse
I did that and my update is gone lol. Guess I'll have to wait for a few hours.
I had to force stop the frameworks and then try updating, which worked. Thanks!
reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Thanks
Just to confirm, if i flash the system.img over my current system, will that delete all my installed apps/data? Which system.img should i be flashing? the one from 4.2.1?
Is there a list somewhere of the version numbers for the various parts (recovery, radio, kernel and bootloader) so i can check they are correct?
Also, is there a way i can flash the OTA update with some error logging or debug output turned on, so i can see what its actually failing at?
Cheers
Yes, the one from 4.2.1, check under Maps > Settings > About, it should gives you the version you're currently running, download it from the factory images page if you haven't already, and no, it should not wipe any apps+data, but back it up anyway if you're worried, better safe than sorry, I'm generally paranoid about data so I always backup, but no it shouldn't wipe anything. You'll lose root and that's it.
And for the bootloader and all that, it all should come all packaged on the factory image, so if you flash 4.2.1 via toolkit, or manually and haven't installed any radio or kernel you should be safe. IIRC, the bootloader version is PRIMELC03, the radio is XXLH1.
reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Very thanks for this explanation. It help me a lot and I finally could update via OTA.
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:
Hi,
Is it possible to be on stock android while being rooted and keep getting ota? I was on 4.4.4 and was rooted, and when I got the ota I got an error and would not let me install.
Also, since im on cm11 now, is it possible for me to throw on Franco Kernel? Because I heard you could not use that for some reason.
Thanks.
Being rooted on stock firmware will not prevent OTAs from being pushed to you. It will likely prevent you from installing the updates due to changes to the /system and (probably) /recovery, which it seems like you experienced before on 4.4.4. The OTA will start to install but will have an error and abort when it detects that things are changed in your /system partition.
To get around this, one option is to do a full factory reset to get back to 100% stock (removes root/custom recovery AND user data). Some folks back stuff up by various methods, others just reinstall everything, it's up to you. Take the OTA and then root again with Chainfire Autoroot (CFAR).
You can also flash a stock /system and /recovery only, then take the update. Once you have the update, run CFAR.
Lastly, you can use the Factory Images and go straight to the version you want. I went from 4.4.4 to 5.0 and then from 5.0 to 5.0.1 with factory images and NO DATA LOSS. After downloading the image, unzip and edit the flash-all.bat file to remove the -w flag near the end. This tells the script to wipe the partitions before flashing them. Removing it will prevent the wipe, and preserve all your apps/data. Save the .bat file, put the N7 in bootloader and run the batch file. Once it runs (takes like 1-2 minutes), you can run CFAR to get root back on 5.0/.1.
As for the CM11 Kernel question, I have no idea. Someone else can touch on that.
Edit: also, you don't need to go from 4.4.4 to 5.0 to 5.0.1 with factory images, you can go straight from 4.4.4 to 5.0.1. Since you already flashed CM11, I'm guessing you wiped your data, so I would just use the factory image to 5.0.1 without editing the batch file and get a fresh install from there. The same methods described should work for future updates beyond 5.0.1, root methods pending.
Or you can do what a few of us have done--go to this thread:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
Follow the instructions to update your bootloader, make sure you're using TWRP 2.8.1.0 or newer, copy the ROM to your internal storage and flash with TWRP. (I wiped cache and Dalvik before and after flashing, but it apparently isn't necessary.) No data loss, working fine for 3 weeks now.
I checked about your last method, removing the w, and many have said that will mess with your android and you SHOULD NOT do it. Is that true?
Removing the "w" forces the install to not wipe. It could cause issues, but it also might not.
Hi...
I would like to upgrade my phone which has the systemless root.
I tried flashing the current stock recovery to see if OTA goes thru, but it doesn't. (It's a shame, since the OTA is only 11mb and I tend to like conciseness... but oh well.)
Since the OTA didn't go thru, I'd like to flash the upgrade myself - I have downloaded it.
It has the following images - is the following right if I want to upgrade stock ROM, without erasing my data -
radio-bullhead-m8994f-2.6.30.0.68.img - Flash
bootloader-bullhead-bhz10k.img - Flash
userdata.img - Do not flash - Will erase user data.
vendor.img - Flash? - I have Project Fi. Does it matter?
recovery.img - Do not flash - But it's okay if you flash, reflash TWRP.
cache.img - Flash? - Is it same as erasing cache?
boot.img - Flash - And reroot from TWRP.
Edit: There are a couple of threads which are on similar lines, but they are all about some other objective and not specifically on upgrading, e.g. "unroot and rever to stock", etc.
Yes. I usually flash recovery, wipe cache, then flash twrp image, and re-root via TWRP.
https://www.androidpit.com/how-to-get-android-m-preview
You forgot to flash the most important partition: system.
For manually updating to the latest build without losing your data or having to reinstall everything you will pretty much always be able to get away with doing the following:
flash radio, vendor, system and boot.
reflash supersu (and every other module you flashed in twrp)
wipe cache/dalvik
reboot.
Works like a charm and you will not even have to setup anything again. Should take you max 15 minutes total.
I do reccommend starting with a nandroid backup beforehand just in case.
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
vypinoy said:
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
Click to expand...
Click to collapse
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
peltus said:
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
Click to expand...
Click to collapse
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
vypinoy said:
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
Click to expand...
Click to collapse
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
pankaj554 said:
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
Click to expand...
Click to collapse
think you posted in the wrong forum, this is the 5X forum not the 5. Also, 5.1 is old...
peltus said:
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Click to expand...
Click to collapse
Got that "could not allocate ____bytes" error again when trying to flash system again. So just did it thru wugfreshs advanced utilities.
Other than that. It worked. Twrp was still there too. Which was weird. Installed SuperSU. And back and running again. Thanks!