Database Develop

Updating to 5.1 without losing root nor system settings

Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.

LordGrahf said:
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.

Without a modified img, and using the google provided stuff, you can't keep root. Just re-root, it's not hard.

Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much

LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
Click to expand...
Click to collapse
If doing the fastboot way like I linked (I have not read through the procedure for sideload, so I don't know)
1) no
2) no if you only flash some of the IMG files. For your purpose it seems (I'm also assuming you don't have custom kernel) these are the ones to not lose data. Make sure you follow the links in how to flash this correctly with the appropriate order and spots where to fastboot reboot.
Bootloader image
Radio image
Boot image (kernel)
Cache image
System image
Recovery image
Then reroot with the cf zip like before then reinstall the su app.
4) no we flash the new stock recovery too
5) minimal, to not overwrite the user data, above. Yup we skip the user data image

LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
Click to expand...
Click to collapse
No.
LordGrahf said:
3. If I'm not losing my installed apps, what would happen to my root-required apps?
Click to expand...
Click to collapse
You'll have to install su since it was deleted by system.img but that's all. Note that last time I looked CF-Auto still said it was 5.0.1 but ...
LordGrahf said:
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
Click to expand...
Click to collapse
If you install a current TWRP it will install super-su for you when you request a reboot.
LordGrahf said:
5. What is the minimal set of the update's images can I use to get this update?
Click to expand...
Click to collapse
Everything except user.img. You can read or run flash-base to get the Google suggested initial ordering.

MunkinDrunky said:
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Click to expand...
Click to collapse
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?

Nikos2k said:
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Click to expand...
Click to collapse
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?

MunkinDrunky said:
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
Click to expand...
Click to collapse
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)

Nikos2k said:
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Click to expand...
Click to collapse
hmm yeah i really dont know why that happend. I guess as long as the new radio shows up as you say then it worked. I will actually be doing this shortly, since i am now at a computer

Just updated to 5.1
for those who will read later and more importantly in my same position.
I was on 5.0.1 BL unlocked, custom recovery+root, custom kernel- -wanting to go to->>5.1, root+custom recovery (cause flashing kernels is trivial) without any data loss (basically don't flash the userdata image) (also you could have left out the radio, I guess if you don't want newest radio, and the boot if you want to just keep your kernel--**not 100% about these two though)
I flashed via fastboot the: bootloader (then fastboot reboot-bootloader), the radio (then fastboot reboot-bootloader), then the boot (updated stock kernel), cache, system. Done, exit command prompt, then while in fastboot menu go into TWRP, whereby I choose system reboot and TWRP RE-ROOTS for me! Now I just kernel shop again

Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!

I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------
LordGrahf said:
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
Click to expand...
Click to collapse
That's all the latest versions yes...

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.

Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.

I tried using tge NRT to flash it back to stock but it didn't work.

I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.

http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1

When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...

celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!

Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!

You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.

prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.

rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again

kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

[Q] 5.1.1 stock update: Re-root and Unencrypt Q's

Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?

bovineyard said:
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
Click to expand...
Click to collapse
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.

cam30era said:
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
Click to expand...
Click to collapse
i think with root but encrypted will do the update

HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.

cam30era said:
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
Click to expand...
Click to collapse
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?

5.1.1 is NOT officially out for the nexus 6. it is in aosp though. thats two differing things. stock is on 5.1.

HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
The OTA package only looks at system.img and boot.img. Of course you need stock recovery to install it. And the "unroot" option inside SuperSU is insufficient. It leaves some traces around that will prevent the OTA from loading. Flash the stock system.img.
And afterwards, when unencrypting, you'll have to fastboot format userdata. Which will wipe your SDcard again.

HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
Bootloader status has no effect on the OTA.

I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?

ibraheeemz said:
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
Click to expand...
Click to collapse
As it says above, you cannot FLASH the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA

danarama said:
As it says above, you cannot receive the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
Click to expand...
Click to collapse
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,

ibraheeemz said:
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
Click to expand...
Click to collapse
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.

danarama said:
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
Click to expand...
Click to collapse
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?

ibraheeemz said:
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
Click to expand...
Click to collapse
No. Only factory reset or unlocking the bootloader loses data. System.img is the rom, flashing to /system. Boot.img is the kernel, flashing to /boot. if you flash these separately, userdata.img is not flashed to /data, so your /data partition remains in tact.
root doesn't touch /data either. Just /system

HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
How do you get root while leaving it encrypted?

Arfyness said:
How do you get root while leaving it encrypted?
Click to expand...
Click to collapse
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.

Evolution_Tech said:
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Click to expand...
Click to collapse
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?

Arfyness said:
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Click to expand...
Click to collapse
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.

edit - this was a duplicate. i can't delete it.

Evolution_Tech said:
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
Click to expand...
Click to collapse
Oohhh, wait, so flash from fastboot, except flash SuperSU from TWRP? (update.zip style?) Is only the data partition encrypted then? If that's the case why are folks decrypting? Unlocking the bootloader requires it, but what is that required for?
And thank you loads BTW! I'm so far behind! I'm coming off 3 years of rooted, stable SGS3 stock, last updated to 4.1.2. There were no further stock updates that I wanted, (too many bugs) and everything was working so I left well enough alone.
(I probably would have messed about with CM and other roms, if I had not initially bricked the thing trying to put TWRP on... and had to send it for somebody to JTAG reprogram it. Thought about it several times, but never wanted to chance it again.)
Thanks again!

[Q] 5.1.1. OTA Update Error

My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.

I downloaded the factory image and fastboot flashed the files.
Sent from my Nexus 6 using Tapatalk

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
What error? Also, have you unencrypted?

Evolution_Tech said:
What error? Also, have you unencrypted?
Click to expand...
Click to collapse
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.

Shift2win said:
Haven't unencrypted at all. The only "mod" has been the unlocking of the bootloader. Everything else is bone stock. And it just shows a picture of the Android robot laying down and it just says error underneath it.
Click to expand...
Click to collapse
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.

Shift2win said:
My stock T-Mobile, unlocked bootloader N6 says that the 5.1.1. update is ready to install and then when I try to install it, it gets about 1/4 done and gives an error. I can reboot the phone at that point but the update never installs. Any suggestions? I've tried the factory reset and I get the same thing.
Click to expand...
Click to collapse
Mine is doing the exact same, I'm also stock and on T-Mobile.

^same here...rooted and T-Mobile.

skipm said:
Mine is doing the exact same, I'm also stock and on T-Mobile.
Click to expand...
Click to collapse
n7plus1 said:
^same here...rooted and T-Mobile.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61119896

Evolution_Tech said:
Then as stated before, I recommend downloading the factory image, unzipping and flashing everything separately except userdata. Then you won't lose your data.
Click to expand...
Click to collapse
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?

neudof said:
I am rooted with stock recovery. Can I do this via ADB or do i need to install TWRP?
Click to expand...
Click to collapse
Fastboot. You need an unlocked bootloader.

I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.

robert_shipley said:
I have the same problem. I'm completely stock. Never done anything. I think it's a problem with the update. I've completely factory reset and wiped everything. I can't even get into the recovery mode. Just gives "no command" when I try.
Click to expand...
Click to collapse
That's exactly my problem, I'm completely stock and have to remain that way since I use my phone at work and they require the AirWatch MDM agent to be installed. I even tried deactivating AirWatch and uninstalling it and I still couldn't get the update to install. I hope there is some way they can either erase and download the update again or just overwrite the current one because this one definitely has problems.

Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.

bchildress said:
Error you get if you look at recovery messages is
"Verifying current system...
System Partition has unexpected contents
E:Error in /cache/update.zip
(Status 7)
read elsewhere that something has modified a system file so OTA won't work and you'll need to flash full image (erasing everything in process) - which is my next step unless I want to wait for OTA to address the issue in the install procedure. No one has figured out what that item is that caused the change in system - some uninstalled Amazon appstore without success.
Click to expand...
Click to collapse
Just flash the system image. No need to flash everything. If you've unencrypted, then flash boot image too.

I have the same problem totaly stock, not rooted, untouched! I have the same error. I have 64 gb nexus 6 build number LMY47D.

Ok Guys,
Here is the solution,
1. Download stock image from google developer page, https://developers.google.com/android/nexus/images
2. Flash with long way;' DONT USE FLASH-ALL SCRIPT' (I tried, update fails again)
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-shamu-XXXXXX/cache.img
(FOR FURTHER INFO PLS SEE THE PAGE; http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008)
3. Just turn on your N6 and it will find update and will be succesfull this time

Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.

Evolution_Tech said:
Why do all that then OTA? Why not just flash everything but userdata from the LMY28E image? Boom your updated and you didn't lose data.
Click to expand...
Click to collapse
Hey,
I am Rooted with TWRP Recovery and Elemental X custom kernel, still encrypted with unlocked bootloader. I got the OTA (LMY47Z) notification and I have got the Factory Image as well as the OTA Zip. Can you guide me as to how can I update my Nexus (currently LMY47I) to 5.1.1 without losing any data?
Thanks.

The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.

peerpower said:
The thing is which factory image for me?. Thats the reason i decided to do it via OTa. As u will see on developers page there are several versions,
5.1.0 (For T-Mobile ONLY) (LMY47M) Link 0469ca2018c923498cc603baae4fd648 5228e84a8a03609ead6b55df569057d5a4e28e0a
5.1.1 (For Sprint, USC ONLY) (LMY47Z) Link c8fe950ad9e861120a1074825b92cfba 33951732896055848d17b3876d8a39b79fb95301
5.1.1 (For T-Mobile ONLY) (LYZ28E) Link 9ea32a7ff1751afa2a16214ac23ef000 b542b88a0ad478110f9f111dd32b62a1cb65b9d5
So better to do it with the OTA.
Click to expand...
Click to collapse
Download the OTA Zip, Extract it and check the "\META-INF\com\android\otacert" file to find the version number for your phone.

LMY48I update error

Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?

OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.

KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.

OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.

OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot

Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.

OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.

prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.

OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img

danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.

OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.

OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.

danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.

OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.

OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.

danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.

OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals

Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...

imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot

Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!