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.
Related
After getting the phone, I right away flash it with google's 4.1.1 ROM. After that I rooted it and fastboot enable with unlocked.
Since 4.1.2 came out in OTA, I have been unable to update it successfully.
I did get prompt asking me to update and when I agree, it will try to update and then reboot to update. However, the update will fail and I will still get stuck in 4.1.1. The failed update has not affected the phone in anyway. So I continue using it at 4.1.1.
Anyone can provide simple instructions on how to update to 4.2.1 without erasing all my data? Especially contacts and emails. I have read there are numerous ways like nandroid and titanium and so on. Then there are mention that I will need to root the phone again after updating and so on. This is really overwhelming for me. Too much information and not sure which direction to go.
Previously I used nexus toolkit to convert the phone to yakjuw (or something) and updated to 4.1.1. Can I use this nexus toolkit again for it? Or OTA is a better way to preserve DATA?
Very sorry if there is already a thread for this cause I can't find it. I am new to this forum and the amount of information especially in galaxy nexus section is overwhelming but at the same time AWESOME!. Great phone with great community support.
Do you have the stock recovery or clockwork?
ironside2011 said:
Do you have the stock recovery or clockwork?
Click to expand...
Click to collapse
I don't think I have the stock recovery. But that can be easily downloaded, right?
As for CWM, I don't think I have it installed. I tried to keep the phone as vanilla as possible. However, I have tried CWM on other android devices before and wouldn't mind installing this.
First off, check your accounts settings. Sync should be set up for both contacts and emails (you should have a gmail account, right?). So that's of no concern. Turn your phone off. Now hold both volume buttons and press power [fastboot mode]. Use volume keys to scroll so top says recovery, then press power. Now you'll see what recovery you have, either android or cwm. If it's android, then you can hold volume up and press the power button to get the menu, which includes reboot now. If it's stock recovery, perhaps the update failed because you're rooted. Try OTA Rootkeeper, hide your root, then clear google services framework, and try the update again, and see if it sticks.
You should find out what version you have, btw, yakju, takju, etc.. You can do this by opening maps, settings, then about.
O, and OTA will preserve data, toolkit will likely wipe all in order to flash whole rom, not just update. I'd say that the common wisdom is skip the toolkits until you fully understand what, how, and why they work in such and such a way.
bodh said:
First off, check your accounts settings. Sync should be set up for both contacts and emails (you should have a gmail account, right?). So that's of no concern. Turn your phone off. Now hold both volume buttons and press power [fastboot mode]. Use volume keys to scroll so top says recovery, then press power. Now you'll see what recovery you have, either android or cwm. If it's android, then you can hold volume up and press the power button to get the menu, which includes reboot now. If it's stock recovery, perhaps the update failed because you're rooted. Try OTA Rootkeeper, hide your root, then clear google services framework, and try the update again, and see if it sticks.
You should find out what version you have, btw, yakju, takju, etc.. You can do this by opening maps, settings, then about.
O, and OTA will preserve data, toolkit will likely wipe all in order to flash whole rom, not just update. I'd say that the common wisdom is skip the toolkits until you fully understand what, how, and why they work in such and such a way.
Click to expand...
Click to collapse
Ok..let me summarize:
1) Check whether phone is stock recovery or CWM.
2) If stock recovery then install OTA rootkeeper and try update OTA again.
3) if CWM recovery then .....restore back to stock recovery???
The easiest thing you can do is backup your phone. Get a toolkit for your phone. Download the factory image for your phone from Google and flash it. You will have 4.2.1 in a jiff.
Sent using xda premium.
[email protected] said:
The easiest thing you can do is backup your phone. Get a toolkit for your phone. Download the factory image for your phone from Google and flash it. You will have 4.2.1 in a jiff.
Sent using xda premium.
Click to expand...
Click to collapse
backup using? titanium? a bit troublesome when nexus does not have sdcard. Storage is almost full.
Platform
android:samsung-maguro-Galaxy Nexus
Device
samsung yakju
ClockworkMod Recovery v5.8.0.2
What's the best way to update now without losing data?
exactly.
abubin said:
Ok..let me summarize:
1) Check whether phone is stock recovery or CWM.
2) If stock recovery then install OTA rootkeeper and try update OTA again.
3) if CWM recovery then .....restore back to stock recovery???
Click to expand...
Click to collapse
3) fastboot flash recovery *recovery.img*, then you'd try the OTA.
Have you consulted: http://forum.xda-developers.com/showthread.php?t=1419170
and http://forum.xda-developers.com/showthread.php?t=1626895 ?
these two threads should be able to teach you almost the exact processes...
btw, just found this: http://forum.xda-developers.com/showpost.php?p=36050897&postcount=9
Even though that's takju, it should be identical to yakju.
And if confident that you havent modified anything other than recovery and root, id still try to flash the stock recovery and ota first.
abubin said:
After getting the phone, I right away flash it with google's 4.1.1 ROM. After that I rooted it and fastboot enable with unlocked.
Since 4.1.2 came out in OTA, I have been unable to update it successfully.
I did get prompt asking me to update and when I agree, it will try to update and then reboot to update. However, the update will fail and I will still get stuck in 4.1.1. The failed update has not affected the phone in anyway. So I continue using it at 4.1.1.
Anyone can provide simple instructions on how to update to 4.2.1 without erasing all my data? Especially contacts and emails. I have read there are numerous ways like nandroid and titanium and so on. Then there are mention that I will need to root the phone again after updating and so on. This is really overwhelming for me. Too much information and not sure which direction to go.
Previously I used nexus toolkit to convert the phone to yakjuw (or something) and updated to 4.1.1. Can I use this nexus toolkit again for it? Or OTA is a better way to preserve DATA?
Very sorry if there is already a thread for this cause I can't find it. I am new to this forum and the amount of information especially in galaxy nexus section is overwhelming but at the same time AWESOME!. Great phone with great community support.
Click to expand...
Click to collapse
OTA update will not work on a rooted phone. You will have to flash the actual 4.2.1 ROM.
It should work with OTARootkeeper, and hidden root, I've done it myself. (read above)
bodh said:
It should work with OTARootkeeper, and hidden root, I've done it myself. (read above)
Click to expand...
Click to collapse
I will use this method. I can find OTARootkeeper. But can't find hidden root apps.
Not sure which is the one:
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot&hl=en
https://play.google.com/store/apps/details?id=com.troy1103.hideyourroot&hl=en
I guess i used the wrong words.. Open OTA Rootkeeper, select backup su, then temp un-root. You can download a rootchecker after this to check if your system shows as rooted or not rooted.
I tried to OTA update but failed.
First, I use OTA rootkeeper to hide root. After that I tried to update but the phone boot up to CWM and show update failed. So I then use nexus toolkit to change back to stock recovery. However, after doing that...when I check for update in the phone, it says no update.
After doing some reading, I try to update using manual method. Which is to boot into stock recovery and then choose update from cache. I have checked the update zip file in cache folder. Then I boot into stock recovery. But in stock recovery, I do not see any option to update from cache. I only see update from ADB or update from SDCARD (or USB...forgot). Tried both and it doesn't work.
The Nexus Toolkit must have restored my stock recovery back to the GSM phone that have SDCARD. Mine does not have SDCARD slot. I do not dare to restore from other recovery.img file. Anyone can point me to the right direction for a recovery.img that will not screw up my stock recovery or the phone at all?
Thanks.
The 'SDCARD' is the onboard storage, nothing wrong there
Easiest thing is to backup your data using Titanium Backup, flash the factory 4.2.1 image, reroot and then restore the backup
EddyOS said:
The 'SDCARD' is the onboard storage, nothing wrong there
Easiest thing is to backup your data using Titanium Backup, flash the factory 4.2.1 image, reroot and then restore the backup
Click to expand...
Click to collapse
So much hassle just for OTA. I guess now my only choice is to use this method. Thanks.
Ultimately, if you want the OTAs stay 100% stock. If you wanna root, go custom
Since you now have stock recovery, which is probably why the OTA failed [though there could be many reasons], Have you tried to clear Google services framwork data (under applications, all), to get the update notification and try again? If it stills fails, then at this point the others are right. Titanium backup method..Just skip the system apps in the backup, right guys?
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
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,
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!