I'm on a Galaxy Nexus takju, and I'm trying to install this update. http://forum.xda-developers.com/showthread.php?t=2144568
But as you can see in that thread, I get an error7.
I guess it might has something to do with my gps.conf that I've edited, and even if I edit it back, there are still some changes done to the date and stuff..
I wonder if there are any way to see why the update fails. Like a log file or something.
Also, what is the easiest way to restor that part then, without wipeing to phone?
EDIT: Also I got the right drivers installed for my win8 computer, but with both Galaxy Nexus toolkit and Nexus Root Toolkit, I can't install the update with adb sideload...
/Söder
you will never be able to update with any method because you modified a system file. you need to completely revert it back to stock (pull it from one of the images).
also, it will tell you in the error 7 message why it failed.
Zepius said:
you will never be able to update with any method because you modified a system file. you need to completely revert it back to stock (pull it from one of the images).
also, it will tell you in the error 7 message why it failed.
Click to expand...
Click to collapse
Do you mean gps.conf or my /system?
And, how do I pull the gps.conf from a image file and push it still intact?
When I get the error I can't see the complete message. But it say something about /system/lib.
If it is my /system, can I then in some way restore just that?
/Söder
AW: [Q] Check what fails a OTA update?
soder said:
Do you mean gps.conf or my /system?
And, how do I pull the gps.conf from a image file and push it still intact?
When I get the error I can't see the complete message. But it say something about /system/lib.
If it is my /system, can I then in some way restore just that?
/Söder
Click to expand...
Click to collapse
The last time it was enough for me to reflash only the system partition. Use fast boot for it and you are on the safe side. The stock Google images are linked in the general and q&a section. The reflash should convert the main and important part back to stock and the ota is possible.
Sent from my Nexus 7
if you are on stock 4.2.1, just flash the rooted 4.2.2 bigxie rom in the dev section and u are ok, no need wipe
u will need to flash also the new radio that u can find in that thread too
Today when I was at schooI I was not able to flash OTA update even with my OTA ROM or Bixgie's OTA ROM so what I did was this:
When I went to home I donwloaded takju 4.2.1 factory images!
I opened CMW and I wiped cache and dalvik cache and then via Fastboot I flashed JB 4.2.1 Takju system and boot and then I flashed old custom recovery 5.#.#... and I was able to update to JDQ39 without losing files from my Nexus..
manumanfred said:
Today when I was at schooI I was not able to flash OTA update even with my OTA ROM or Bixgie's OTA ROM so what I did was this:
When I went to home I donwloaded takju 4.2.1 factory images!
I opened CMW and I wiped cache and dalvik cache and then via Fastboot I flashed JB 4.2.1 Takju system and boot and then I flashed old custom recovery 5.#.#... and I was able to update to JDQ39 without losing files from my Nexus..
Click to expand...
Click to collapse
I extracted the system.img from takju-jop40d-factory-e4d13f14.tar and then did a fastboot flash system system.img
After that I could update. Will boot back and restore my custom system files then, and restore root.
Thanks.
/Söder
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
Hey guys,
So I used the GNEX tool to update my GSM Galaxy Nexus to the latest 4.0.4, all smooth, all perfect, I now have a rooted 4.0.4 but without clockwork RecoveryMod.
I read somewhere that OTA patches remove the modded recovery (obvious) and also each subsequent reboot it flashes stock recovery back. I had read I must delete the file from /system called "recover-from-boot" and another one that seems to be missing, however I have "recover-from-boot" and "recover-from-boot-old" is it cool if I just delete these two and flash CWM recovery again and it should be fine or should I take any sort of precaution and find the other file (which I can't recall) and then go ahead with the flash.
Thanks
I think it would be fine to delete those files and permanently flash CWM (since google has the stock recoveries on their website). But flashing a custom recovery will not allow you to receive the next OTA fyi...
anton2009 said:
I think it would be fine to delete those files and permanently flash CWM (since google has the stock recoveries on their website). But flashing a custom recovery will not allow you to receive the next OTA fyi...
Click to expand...
Click to collapse
really? I did not know that, thanks for that information - but as long as I can manually flash to the next OTA that should be cool I guess !
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 just got the 4.2.2 system update notification on my phone from Verizon. Before I install it, I wanted to make sure the 4.2 camera/gallery I installed a while back (installed from zip using CWM, renamed old cam/gallery files if I remember right) wouldn't cause the update to error out. I'm rooted and on stock 4.1.1 Build JRO03O other than the newer camera/gallery. Thanks.
you wouldnt be stock since you installed a mod, therefore the OTA would error.
Zepius said:
you wouldnt be stock since you installed a mod, therefore the OTA would error.
Click to expand...
Click to collapse
Thanks, that's what I figured. I'll try to find the site that outlined what I did to install the new camera/gallery so I can reverse it.
Well, I can't find any info on how to get the old 4.1 camera/gallery back.
What I did for the 4.2 camera back in December was download the "camera.zip" file, reboot into recovery, install the zip, then reboot. Then it force closes the gallery so I used root browser to go into system>app and renamed gallery.google.odex to gallery.google.bak and then moved that file to the system folder.
I assume I need to find a 4.1 camera zip and install it, then move the above file back to system>app if the install doesn't create a new gallery.google.odex file?
Is this correct or am I way off? Anybody have a link to the 4.1 camera zip download?
Your main issue is also having a custom recovery (CWM). If you want ota (not sure why) you need to go back to stock recovery also.
good day.
chopper the dog said:
Your main issue is also having a custom recovery (CWM). If you want ota (not sure why) you need to go back to stock recovery also.
good day.
Click to expand...
Click to collapse
I've always used the OTA update in the past with CWM without issue, I just never had a custom camera (or anything else) for previous updates. I don't really care "how" I get 4.2.2 as long as it's the official version so it's got the least chance of being buggy. What's the easiest way to get the official 4.2.2 release when rooted with 4.2 camera without loosing any phone data?
So is there nowhere to download just the camera/gallery from 4.1 to re-install?
What's the fix here so I can go to 4.2.2 without clearing phone data? Thanks.
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
http://tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond
chopper the dog said:
Your main issue is also having a custom recovery (CWM). If you want ota (not sure why) you need to go back to stock recovery also.
good day.
Click to expand...
Click to collapse
this isnt true. you can still complete the OTA with a custom recovery. ive done it the past 2 OTAs. the problem happens when you have flashed a mod or modified a /system/ file.
Sandman-007 said:
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
http://tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
Thanks. Because it's 4:30 am and I wanted to see if I could get a quick fix, I tried pulling out the gallery.apk, moving it to the app folder and it worked perfect after I renamed the 4.2 gallery.apk to gallery. The camera and gallery are back to the "old" versions and working fine.
Went ahead and ran the OTA, it failed (cache error) so I cleared cache/dalvik, rebooted and it went into "Android is upgrading...". After it was done, I went into settings to see what version it was and it was still on 4.1.1. Tried to force the system update a few times by clearing/stopping framework services and then checking for updates and finally got it to download the update.
It rebooted to install the update and TWRP opened up. I told it to install the file and it failed. Errors say:
assert failed: apply_patch_check (' /system/app/GalleryGoogle.apk.....(can't read the rest, it's off the screen).
E: Error in /cache/5939ff985946.signed-mysid-JDQ....(can't read the rest)
(Status 7)
It appears there is still "something" wrong with the gallery/camera but it's beyond skills. It's too late to mess with it any further so hopefully someone will have a suggestion to try when I wake up. If not, I guess I'll try to apply the whole 4.1.1 OTA first and see if that fixes it.
Thanks for the help thus far.
It would only take a minute or two to flash the whole file. Is like flashing a ROM
Toro | Xylon | AK Diamond
Sandman-007 said:
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
I'm in the same position. Rooted, 4.2 camera. Putting the 4.1 apk back didn't help me. Thanks for the OTA, I'm hoping that flashing with this and then with the 4.2.2 will get me upgraded without a full wipe. H/W died a few weeks ago and it's finally back to having everything loaded.
Thanks!
Leithal007 said:
I'm in the same position. Rooted, 4.2 camera. Putting the 4.1 apk back didn't help me. Thanks for the OTA, I'm hoping that flashing with this and then with the 4.2.2 will get me upgraded without a full wipe. H/W died a few weeks ago and it's finally back to having everything loaded.
Thanks!
Click to expand...
Click to collapse
No problem. Please let me know if it works.
Sandman-007 said:
Here is the 4.1.1 stock rooted OTA. It is a flashable zip. Flash in recovery. Wipe cache/dalvik only. Reboot then update to 4.2.2.
tinyw.in/FbcF
Edit: you could just pull the apk out if you wanted but I suggest just flashing the whole system.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
I Flashed the Full/Stock 4.1.1 you posted. However I still can't install 4.2.2. I get the following error (image attached).
I'm completely stuck at this point, the only thing I had done was install the 4.2 camera, and superuser, and thought that the 4.1.1 install would have "fixed" this.
Any ideas?
Leithal007 said:
I Flashed the Full/Stock 4.1.1 you posted. However I still can't install 4.2.2. I get the following error (image attached).
I'm completely stuck at this point, the only thing I had done was install the 4.2 camera, and thought that the 4.1.1 install would have "fixed" this.
Any ideas?
Click to expand...
Click to collapse
Fastboot the Google Stock image
Sandman-007 said:
Fastboot the Google Stock image
Click to expand...
Click to collapse
Flashed, then recovered CWM, Superuser etc.
Now to start with Apps, etc...
Thank you for the help and pointers... Couldn't have got here without you and the resources you, and this site, pointed me to...
Leithal007 said:
Flashed, then recovered CWM, Superuser etc.
Now to start with Apps, etc...
Thank you for the help and pointers... Couldn't have got here without you and the resources you, and this site, pointed me to...
Click to expand...
Click to collapse
No problem dude. Glad u got it all figured out. I forgot to tell you and I an sure you did this since you had to reinstall CWR but make sure you have the updated version of your recovery BEFORE you update to 4.2.2
Toro | Xylon | AK Diamond
Sandman-007 said:
No problem dude. Glad u got it all figured out. I forgot to tell you and I an sure you did this since you had to reinstall CWR but make sure you have the updated version of your recovery BEFORE you update to 4.2.2
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
Can you explain this so I can be sure to do it before I end up in the same situation as the other guy? What do you mean by "updated version of your recovery"? I did a Ti Backup of all user apps + system data and saved it to the sd card before I messed with going back to the 4.1 camera. I also backed up the current ROM in CWM which rebooted into TWRP and did a Nandroid backup. Is this sufficient or is there something I need to do to make it 4.2.2 compatible? Thanks.
This is a good reminder why I shouldn't run a "custom" anything on this phone. I don't have time to keep up with how to do all of this stuff and it ends up being a mess in the end. Only reason I did the 4.2 camera was I was going on vacation and wanted to be able to take some great photosphere photos while I was there (which I did).
Stinger2300 said:
Can you explain this so I can be sure to do it before I end up in the same situation as the other guy? What do you mean by "updated version of your recovery"? I did a Ti Backup of all user apps + system data and saved it to the sd card before I messed with going back to the 4.1 camera. I also backed up the current ROM in CWM which rebooted into TWRP and did a Nandroid backup. Is this sufficient or is there something I need to do to make it 4.2.2 compatible? Thanks.
This is a good reminder why I shouldn't run a "custom" anything on this phone. I don't have time to keep up with how to do all of this stuff and it ends up being a mess in the end. Only reason I did the 4.2 camera was I was going on vacation and wanted to be able to take some great photosphere photos while I was there (which I did).
Click to expand...
Click to collapse
CWM is called a recovery. You need to get the updated version from ROM Manager or Koush's website. I recommend TWRP over CWM. You can get TWRP from Goo manager. Either way make sure you update your recovery or your will have a headache.
Sent from my Nexus 7 using XDA Premium HD app
I am having a similar issue with the OTA update since I have the 4.2.2 camera installed as well. Is there a way to flash the update manually with CWM that will work with the camera installed?
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.
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!