Installing android 6.0.1 on nexus 6 (problem) - Nexus 6 Q&A, Help & Troubleshooting

I am currently on stock android M rooted and unlocked bootloader
Want to upgrade to 6.0.1 anyone please guide me how to do it?
If i do it will the bootlader lock again?
Will the root access go away
someone please guide me with proper steps
advance thanks

MD0038 said:
I am currently on stock android M rooted and unlocked bootloader
Want to upgrade to 6.0.1 anyone please guide me how to do it?
If i do it will the bootlader lock again?
Will the root access go away
someone please guide me with proper steps
advance thanks
Click to expand...
Click to collapse
just flash the latest 6.0.1 factory image. yes, you will lose root and will have to reroot(flash twrp then supersu which takes a few minutes). bootloader will only relock if you relock yourself, manually. if by now you dont know the proper steps, and yet you are modifying your nexus 6, then there is no help for you, sorry.

simms22 said:
just flash the latest 6.0.1 factory image. yes, you will lose root and will have to reroot(flash twrp then supersu which takes a few minutes). bootloader will only relock if you relock yourself, manually. if by now you dont know the proper steps, and yet you are modifying your nexus 6, then there is no help for you, sorry.
Click to expand...
Click to collapse
directly flash 6.0.1 over rooted M????
should i not get back to 6.0.0 make the phone stock and then flash 6.0.1 over it?
or thats not necessary?
btw do i lose data if i directly flash over present one?

MD0038 said:
directly flash 6.0.1 over rooted M????
should i not get back to 6.0.0 make the phone stock and then flash 6.0.1 over it?
or thats not necessary?
btw do i lose data if i directly flash over present one?
Click to expand...
Click to collapse
flashing a factody image will wipe out your partitions first, so affectively, youre flaahing on top of an "empty" device. you will lose data, but wont if you only flash the system.img.

MD0038 said:
I am currently on stock android M rooted and unlocked bootloader
Want to upgrade to 6.0.1 anyone please guide me how to do it?
If i do it will the bootlader lock again?
Will the root access go away
someone please guide me with proper steps
advance thanks
Click to expand...
Click to collapse
Sorry to butt in but only flashing userdata.img in fastboot or performing a manual data factory reset (in recovery or settings) will wipe all data on your device.

gee2012 said:
Sorry to butt in but only flashing userdata.img in fastboot or performing a manual data factory reset (in recovery or settings) will wipe all data on your device.
Click to expand...
Click to collapse
Am thinking of taking backup and then flashing 6.0.1 and re rooting again

MD0038 said:
Am thinking of taking backup and then flashing 6.0.1 and re rooting again
Click to expand...
Click to collapse
Sure, but only backup userdata (apps) and no system data.

Related

Error on update

Updating from 5.0 to 5.0.1 I got a message that said "error" during the reboot and install phase. I had to manually shut down the phone and reboot. After the reboot, I noticed that there was no update available and my phone is still on 5.0. I've only unlocked the bootloader and does with CF. No custom recovery or rom.
Sent from my Nexus 6 using XDA Free mobile app
You used CF so if you rooted it wont work.
As stated in the other threads, you cannot update if you have root. You need to unroot. The update notification will eventually pop up again,
Hand76 said:
You used CF so if you rooted it wont work.
Click to expand...
Click to collapse
PaisanNYC said:
As stated in the other threads, you cannot update if you have root. You need to unroot. The update notification will eventually pop up again,
Click to expand...
Click to collapse
Ah okay I didn't realize that. Thanks for the info!
Sent from my Nexus 6 using XDA Free mobile app
I'm not rooted, I just have decrypted and I get the error.
Aston Martin said:
I'm not rooted, I just have decrypted and I get the error.
Click to expand...
Click to collapse
Same issue - any change to the kernel or system files is going to cause this issue. You need to be completely stock (having the bootloader unlocked is not an issue)
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
TheLegendary87 said:
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
Click to expand...
Click to collapse
Unroot relock boot loader which will while everything again and apply update
ryuken11221 said:
Unroot relock boot loader which will while everything again and apply update
Click to expand...
Click to collapse
Did you mean "...which will wipe everything again..." ? If so, that's really not what I wanted to hear, haha.
TheLegendary87 said:
Did you mean "...which will wipe everything again..." ? If so, that's really not what I wanted to hear, haha.
Click to expand...
Click to collapse
yeah lol i know its hard to hear
ryuken11221 said:
yeah lol i know its hard to hear
Click to expand...
Click to collapse
Found this thread which walks you through the update process without having to wipe your data. Worked perfectly.
TheLegendary87 said:
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
Click to expand...
Click to collapse
You need to get stock before taking any OTA (bootloader being unlocked doesn't cause any issues with update). You can either download factory images for 5.0 and flash those (skip userdata.img if you don't want to lose data), and then take OTA, OR, do it the easier way - download factory images for 5.0.1 and flash those (skip userdata.img to avoid losing data)
ryuken11221 said:
Unroot relock boot loader which will while everything again and apply update
Click to expand...
Click to collapse
huh? why relock bootloader? And that's not going to fix the issue with the modified system files
jj14 said:
You need to get stock before taking any OTA (bootloader being unlocked doesn't cause any issues with update). You can either download factory images for 5.0 and flash those (skip userdata.img if you don't want to lose data), and then take OTA, OR, do it the easier way - download factory images for 5.0.1 and flash those (skip userdata.img to avoid losing data)
Click to expand...
Click to collapse
Exactly what I did following the guidence in this thread: http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924

[Q] Install 5.1 OTA if rooted and bootloader unlocked?

Hi guys !
I unlocked my bootloader and rooted my device, and i don't know if i can upgrade my Nexus 6 by ota (received this morning on the phone) without brick it.
Is it dangerous?
Thank you
EDIT : I'm on stock Lollipop 5.0.1
Unlocked is fine. If you have root or any other system mods, you'll need to remove them.
Oh thanks for the quick answer
So if I unroot it with Nexus Root Toolkit it will be ok?
Midsylen said:
Oh thanks for the quick answer
So if I unroot it with Nexus Root Toolkit it will be ok?
Click to expand...
Click to collapse
Nexus toolkit doesn't unroot. It reflashes the entire phone which also means root disappears. If you're going to do that, no point taking the ota. Just flash full update.
You can indoor via the SuperSU app.
Oh ok I just saw that.
So if I unroot via SuperSU it's ok i can install?
Midsylen said:
Oh ok I just saw that.
So if I unroot via SuperSU it's ok i can install?
Click to expand...
Click to collapse
As long as you do the full unroot and made no other modifications. Oh and everything must be 100% stock, including recovery
I've installed TWRP...
So, what is the best way for me to install 5.1 without losing my data?
Midsylen said:
I've installed TWRP...
So, what is the best way for me to install 5.1 without losing my data?
Click to expand...
Click to collapse
download the factory image that you want to update to.
extract the system.img, boot.img and radio.img
Fastboot flash them.
You could also flash the bootloader if you want though I dont see any point.
Ok, thank you for your quick answers

[Q] Upgrading from 5.0>5.1

Is it okay to flash the newest image (LMY74I) coming from LMY47O? I won't do any harm in skipping 5.0.1 will I?
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
mymusicathome said:
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
Click to expand...
Click to collapse
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Forerunner326 said:
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Click to expand...
Click to collapse
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
rootSU said:
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
Click to expand...
Click to collapse
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Forerunner326 said:
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Click to expand...
Click to collapse
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Is this because oem unlocking was unchecked for those people?
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Even if the device is rooted, all it will do is cause root to be lost correct?
Forerunner326 said:
Is this because oem unlocking was unchecked for those people?
Click to expand...
Click to collapse
See this post on relocking instructions:
http://forum.xda-developers.com/showthread.php?p=59699095
Forerunner326 said:
Even if the device is rooted, all it will do is cause root to be lost correct?
Click to expand...
Click to collapse
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
rootSU said:
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
Click to expand...
Click to collapse
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
theDXT said:
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
Click to expand...
Click to collapse
Flash everything from the factory image except the userdata.img

[Q] rooted, unlocked, TWRP recovery, stock, Verizon OTA help

I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.

Downgrade without loosing data?

Is there anyway to downgrade from 7.1.1 back to 7.0 without losing data. I sideloaded the OTA using Nexus toolkit and I have tried to go back using this method but it says no image for my device yet. Any other way?
Grab the full image from Google, and flash with fastboot. Don't flash data and you won't lose any. And from what I've read, DON'T downgrade the bootloader.
Thanks.
Thanks!
Larzzzz82 said:
Grab the full image from Google, and flash with fastboot. Don't flash data and you won't lose any. And from what I've read, DON'T downgrade the bootloader.
Click to expand...
Click to collapse
What else to flash
Do I flash the radio as well or just sys.img?
Larzzzz82 said:
Grab the full image from Google, and flash with fastboot. Don't flash data and you won't lose any. And from what I've read, DON'T downgrade the bootloader.
Click to expand...
Click to collapse

Categories

Resources