Database Users

Will custom recovery prevent ota updates?

First let me apologise if this is in the wrong section. I could not decide if this was the best place for it or q a&a. As the title sais. If i flash twrp will it prevent me from receiving ota updates from Google. I have an HTC sensation XE and if i flash a custom recovery i know from past experience that it prevents ota updates. This nexus 7 however is my first "Google" device you could call it and as such i do not know that.
Can any one inform me on this issue. Also if it will an ota cause loss of root on this nexus like it did on my smartphone or will it stay? If it is gone i suppose it will simply be a matter of using chainfires root tool again when it gets updated for it.
Thanks in advance.
Sent from my Nexus 7 using Tapatalk 4

Q&A would be the best place for the post, but I can offer some insight. Any time you flash a custom rom you will forfeit the option of an ota update from your carrier or Google. This doesn't affect your play store apps as they will update when needed. The information that gets sent to your carrier identifies it as being non-official software so only a few custom ROMs that are well maintained will point the ota updates to its own servers. If you wish to receive official ota updates you should perform a nandroid backup of your stock rom to have a restore point for when a new release comes out. Aside from that, you would have to flash everything back to stock (probably stock recovery too) in order to be seen by the carrier as an eligible device.
Sent from my SGH-I727 using Tapatalk 2

Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4

Ch3vr0n said:
Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
If you install a custom recovery like twrp, you wouldn't be able to install an OTA from Google. You need stock recovery for OTAs.

now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?

Ch3vr0n said:
now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?
Click to expand...
Click to collapse
This has already been brought up many times e.g.
http://forum.xda-developers.com/showthread.php?t=2404833

I thought as much. I'll stick with stock recovery then until i need a custom recovery for some specific reason. For now root access is enough. And if an ota comes out and i lose recovery well I'll just wait for chainfire to update his root tool

i received the jss15j -> jsl36c update on my razorg with twrp recovery installed.
after the update stock recovery was back.
you can boot every recovery or kernel image without flashing it using fastboot:
fastboot boot nameofrecovery.img

I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.

HowardZ said:
I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.
Click to expand...
Click to collapse
Good to know.
Sent from my Nexus 7 using Tapatalk 4

I've taken OTAs using custom recoveries before on any number of devices. If you're not careful you can lose your recovery and have to reflash again, but sometimes you don't even lose that.

Well, there might be complications installing an OTA with custom recovery if it comes with a newer bootloader version/radio. Sometimes it works, but there were also reported problems.

Well i just had an ota update to jss15r and lost root as kinda expected. Now ill just have to find out if rerunning the root tool will be enough. Since it is already OEM unlocked i suppose i can simply modify that bat file and remove that line and run it again?

[Q] Updating from 4.2.2 to 4.3 failing repeatedly.

Hi everyone, I'm having a hell of a time trying to update my phone from 4.2.2 to 4.3 (stock rom). I have searched the forums (or tried to) and have done general Google searches, but nothing with my problems came up. I rooted my phone a while back, lost root when my phone updated to 4.2.2, then used wugfresh's Nexus Root Toolkit to get it back. Ever since 4.3 came out, I have been unable to update. I was using TWRP, and when updating through the phone it would simply dump me back there and not continue. I was then instructed to manually flash through TWRP, which I tried to do, but halfway through the flash it simply stops. I believe it said "signature verification failed". Someone had me try using the NRT to push the update as well, but that hasnt worked either. It just fails.
After asking around some more, I was instructed to flash the stock recovery, which I have now done. Now when I try to update (through the phone), it takes me to stock recovery, starts installing the update, and (yet again) halfway through the android guy just has an X on it and it says "failed". With Kit Kat supposedly coming out in two days, I really want to be ready to get the update asap. Could anybody help me out?
Also, if possible I would like there to be a way to do so without losing the data on my phone. But its not necessary.
I am sorry if this same problem has come up before. I tried going through other threads and the ones suggested after typing in the thread title.

Why don't you just use the toolkit to bring you back to stock and unroot? Once that is done you will get the update OTA

I am on stock, and I am getting the update OTA. It is just failing to install every time I try to install the update.

Your did something wrong when going back to stock. Did you unroot and relock the boot loader?
Sent from my Nexus 4 using XDA Premium 4 mobile app

Or you can just flash all the .img file of the 4.3 using adb.

To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.

To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.

I did same thing without any problems after I unrooted and installed stock kernel.
Just use Wug toolkit and factory 4.3 image.
Now open image and extract radio, bootloader and system img.
Now use Wug and flash only these img.
Then reroot and start flashing custom kernel or roms.
Sent from my NookColor using Tapatalk 4

If everything else fail, do it manually.. Seek this thread.. http://forum.xda-developers.com/showthread.php?t=2010312.
Never do anything using toolkits.. Manual way is always the best.

this tool may help you:
Have you ever get into a situation where you have a custom recovery on a stock rom and then get a OTA update then you find out that you need to flash the stock recovery to flash?, well this Nexus 4 Stock Recovery Flasher will sort it all out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2413550

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4

Your build.prop isn't standard, get the original one, or just use the factory image to update.

Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..

Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.

inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?

CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app

inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?

CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app

I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.

After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk

Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?

[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.

Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.

[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).

I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?

[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.

charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!

mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.

charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...

Never mind

[Q] Cannot upgrade Nexus 4 to Lollipop or do a factory reset without USB

This is my first post here because I usually find answers on my own but this seems to be an unsolved issue everywhere so please excuse me if I do not follow a proper format.
My Nexus 4's USB is broken (not the wire, but the actual microUSB) so I can charge fine but cannot connect to the computer. It is unlocked and rooted and I do not mind losing my data (everything is backed up) but I cannot get the update without a PC.
A way to get the update very easily and without losing data was to flash the OTA zip using TWRP 2.7 but it gave me an error saying it cannot install zips from sdcard. So I flashed the latest CWM which can do it but it gave me an error saying "package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or googleoccam/mako:5.0/LRX21P/1570855:user/release-keys; this device has google/occam/mako:4.3/JWR66Y/779366:user/release-keys." but my phone has 4.4.4 KTU84P and I know that. I am wondering if it is because of the weird looking kernel I have due to my use of Wug's NRT in the past so I flashed stock recovery to factory reset but when I found out my phone was going to be locked again, I flashed CWM using Flashify again. I'm attaching the screenshot of my 'about' below.
Since I do not mind losing data by flashing a factory image, is there any way I can do it without connecting it to the PC? Because I really want this phone to return to stock? (I know with Flashify you cannot) but I'm apprehensive of locking the phone again because I'd really like to root and install custom recoveries etc.
Thanks in advance!

NishkarshChugh said:
This is my first post here because I usually find answers on my own but this seems to be an unsolved issue everywhere so please excuse me if I do not follow a proper format.
My Nexus 4's USB is broken (not the wire, but the actual microUSB) so I can charge fine but cannot connect to the computer. It is unlocked and rooted and I do not mind losing my data (everything is backed up) but I cannot get the update without a PC.
A way to get the update very easily and without losing data was to flash the OTA zip using TWRP 2.7 but it gave me an error saying it cannot install zips from sdcard. So I flashed the latest CWM which can do it but it gave me an error saying "package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or googleoccam/mako:5.0/LRX21P/1570855:user/release-keys; this device has google/occam/mako:4.3/JWR66Y/779366:user/release-keys." but my phone has 4.4.4 KTU84P and I know that. I am wondering if it is because of the weird looking kernel I have due to my use of Wug's NRT in the past so I flashed stock recovery to factory reset but when I found out my phone was going to be locked again, I flashed CWM using Flashify again. I'm attaching the screenshot of my 'about' below.
Since I do not mind losing data by flashing a factory image, is there any way I can do it without connecting it to the PC? Because I really want this phone to return to stock? (I know with Flashify you cannot) but I'm apprehensive of locking the phone again because I'd really like to root and install custom recoveries etc.
Thanks in advance!
Click to expand...
Click to collapse
For the ota to work you need the stock recovery and no system files modified or deterred. I would flash the stock recovery in flashify and try the ota again
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
For the ota to work you need the stock recovery and no system files modified or deterred. I would flash the stock recovery in flashify and try the ota again
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
This post may help you http://forum.xda-developers.com/nexus-4/development/rom-flashable-stock-rom-radio-kernel-t2527806

pm_dsp_ra said:
This post may help you http://forum.xda-developers.com/nexus-4/development/rom-flashable-stock-rom-radio-kernel-t2527806
Click to expand...
Click to collapse
Thank you! This is a working solution, got the sweet OTA on my phone!
Requesting the mods to close this thread. Thank you!

Same problem for me (but to go to 5.0.1 from 5.0)
I re-flashed stock kernel and radio, but still the same message.
Why this 4.3 message??
Edit : wait, I forgot to flash stock recovery

Unable to install 6.0.1 OTA

Everytime I try to install 6.0.1, when it restarts my phone, I get an error message during boot. I am unable to install 6.0.1 OTA.
My phone has bootloader unlocked and rooted. I have tried restarting the phone and clearing out the cache. Can someone give me any pointers how to resolve this issue?
Thanks

JayRyu said:
Everytime I try to install 6.0.1, when it restarts my phone, I get an error message during boot. I am unable to install 6.0.1 OTA.
My phone has bootloader unlocked and rooted. I have tried restarting the phone and clearing out the cache. Can someone give me any pointers how to resolve this issue?
Thanks
Click to expand...
Click to collapse
Your rooted and wondering why you cant take an OTA?
Hint....your rooted.
Sent from my Note 5, Nexus 6P, Note 4 or Nexus 6

If you want to take the OTA you need to flash stock recovery and reflash /system first. To not lose your data, you can flash the 6.0.1 factory image withe the "-w" removed from the flash-all.bat batch file, or flash the individual components one by one, skipping userdata.img. You will then need to reflash TWRP and root, and Xposed (if you have it), but you won't need to setup all your modules again, just flash the framework and everything will work as it did.
Note: if you used traditional root in the past (flashed modified boot.img) this won't work on 6.0.1, it breaks the camera. I switched to systemless root which modifies the boot image on the fly as it installs and everything works fine.

force70 said:
Your rooted and wondering why you cant take an OTA?
Hint....your rooted.
Sent from my Note 5, Nexus 6P, Note 4 or Nexus 6
Click to expand...
Click to collapse
Force, lol thanks.. I jumped from kit kat to Marshmellow. I didn't realized I can't update OTA when rooted on 6.0
fury683 said:
If you want to take the OTA you need to flash stock recovery and reflash /system first. To not lose your data, you can flash the 6.0.1 factory image withe the "-w" removed from the flash-all.bat batch file, or flash the individual components one by one, skipping userdata.img. You will then need to reflash TWRP and root, and Xposed (if you have it), but you won't need to setup all your modules again, just flash the framework and everything will work as it did.
Note: if you used traditional root in the past (flashed modified boot.img) this won't work on 6.0.1, it breaks the camera. I switched to systemless root which modifies the boot image on the fly as it installs and everything works fine.
Click to expand...
Click to collapse
Fury, thanks

JayRyu said:
Force, lol thanks.. I jumped from kit kat to Marshmellow. I didn't realized I can't update OTA when rooted on 6.0
Fury, thanks
Click to expand...
Click to collapse
Yeah alot has changed, and its not getting easier that's for sure lol
Sent from my Note 5, Nexus 6P, Note 4 or Nexus 6

ive relocked bootloader, completely factory recovered device and flashed vendor image. still getting error when trying to update too 6.0.1

Are you trying to OTA or flashing the img files using fastboot? I highly recommend flashing the individual img files from the factory img using fastboot. It takes like 2 minutes and you're up and running and keep your data.
Just make sure you don't flash the batch file without removing the -W. Best to just do the individually.
Sent from my Nexus 6P using Tapatalk