Database Develop

Will Nexus 6 get OTA updates if rooted and custom recovery is installed?

I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
shelooga said:
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well
Click to expand...
Click to collapse
sheloga is correct. You'd have to revert back to full stock or wait for someone to make a flashable zip.

Can't you just flash the stock recovery and take the OTA? Or do you have to fully unroot and reflash the factory image?

I would like to pay close attention time to this thread because that is one is the main questions that I have. I hear so many different solutions towards this. I usually wait for a flashable zip but I would want to see someone either wrote a write up or make a video. Subscribed.

My understanding (from looking at the lollipop OTA updater-script) is it checks EVERY file for changes, including other partitions. You must be 100% stock with nothing extra in system (SuperSU apk or busybox etc).

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.

BLUF: wait until OTA is made available in a recovery flash method. 90% of the time the OTA updates are patching security holes and other less important features.
Having been with a handful of different android devices in the past several years, I've always gone the route of flashing from recovery vs. OTA.
The LG G3 for example had an OTA just recently that broke rooting. It was fixed by a Dev, but that's the only update found in OTA.
Sent from my Nexus 6 using XDA Free mobile app

Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.

simms22 said:
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.
Click to expand...
Click to collapse
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?

wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
no thoughts.
i just flash aosp hours after it appears there. or just wait for @rascarlo to add it to his rom, then i flash

HyperM3 said:
Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
After Android 5.0, you can't sideload the OTA file if you have made any changes to the system partition. You need to be completely stock to take OTA. You can just download the new factory images and extract the various img files from it and just flash those manually in ADB, thereby overwriting your modified system partition with the new factory system image (you can skip overwriting the userdata if you want to preserve your data). No need to revert back to stock (old image) and then take OTA - unnecessary step.

HyperM3 said:
Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?

gwojo22 said:
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?
Click to expand...
Click to collapse
From google
https://developers.google.com/android/nexus/images

hlxanthus said:
From google
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately

waqar.qu said:
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately
Click to expand...
Click to collapse
You need to install ADB and fastboot. After that, you can use the 'fastboot' command directly from Terminal. I've found that the easiest way to update Lollipop on my Nexus 6 is to:
Download image from Google
Decompress the archive, AND the second archive which was contained within the first one. Note: The recovery, boot, and system images are in the second archive.
Open Terminal, change directory to the extracted folder, and run these commands (they skip overwriting the userdata partition):
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader (VERY IMPORTANT TO DO THIS STEP)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
You need to restore root at this point; you can use these instructions if you're unfamiliar with the procedure.

Rooting

My 64gb n6 is coming on the 14th and I read if I root I won't get any ota... Is this true

PunishedSnake said:
My 64gb n6 is coming on the 14th and I read if I root I won't get any ota... Is this true
Click to expand...
Click to collapse
The ota checks if everything is stock before flashing and being rooting will cause it to fail.

papi5120 said:
The ota checks if everything is stock before flashing and being rooting will cause it to fail.
Click to expand...
Click to collapse
People usually modify the update script to remove all asserts and then the ota flash able zip will work.
Sent from my Nexus 6 using Tapatalk

Causes it to fail, but you can still get updates just as easy.

KingMarkous said:
Causes it to fail, but you can still get updates just as easy.
Click to expand...
Click to collapse
How?

PunishedSnake said:
How?
Click to expand...
Click to collapse
Flash a modified zip with the assert disabled.
Sent from my Nexus 6 using Tapatalk

zephiK said:
Flash a modified zip with the assert disabled.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I cant seem to find it can you link me?
Rooting here I come.....
Does anyone run ADAWAY on their n6?

PunishedSnake said:
I cant seem to find it can you link me?
Rooting here I come.....
Does anyone run ADAWAY on their n6?
Click to expand...
Click to collapse
You'd have to download the ota then edit it. OTA is not the only option either. There are full ROM.zip available to flash from recovery too or even fastboot flash the system and boot images.
One problem removing the asserts can cause is if you modify your ROM in any way besides root, you can be patching with the ota, mismatched code...

I've been searching for ages on how to receive the OTA update while rooted with TWRP recovery.
To add on to the difficulty, I have a mac so all the directions and steps I've seen are for windows users (the whole fast boot everything except user or something).
Can anyone link me to the stock ROM that someone mentioned in this thread or at least give a or give me a link to a step by step instruction on how to update on a rooted Nexus 6 running twrp? encrypted as well.

waqar.qu said:
I've been searching for ages on how to receive the OTA update while rooted with TWRP recovery.
To add on to the difficulty, I have a mac so all the directions and steps I've seen are for windows users (the whole fast boot everything except user or something).
Can anyone link me to the stock ROM that someone mentioned in this thread or at least give a or give me a link to a step by step instruction on how to update on a rooted Nexus 6 running twrp? encrypted as well.
Click to expand...
Click to collapse
The steps are easy,
1. New OTA?
2. Download zip (not the official OTA but a modified OTA script that removes asserts)
3. Flash the zip
4. You have new OTA.
Even easier because you wont have to wait for the OTA to come to you and can flash the OTA.
Its not really difficult

PunishedSnake said:
How?
Click to expand...
Click to collapse
Google publishes fastbootable images for all Nexus updates. Just do a google search for "factory images for nexus devices".
A little warning... they need some **very trivial** modification before being written, or they will wipe your phone's userdata.

zephiK said:
The steps are easy,
1. New OTA?
2. Download zip (not the official OTA but a modified OTA script that removes asserts)
3. Flash the zip
4. You have new OTA.
Even easier because you wont have to wait for the OTA to come to you and can flash the OTA.
Its not really difficult
Click to expand...
Click to collapse
Where does one find a modified OTA script that removes "asserts"?

[Q] ota update always failing

i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root

Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.

Same thing here, always installation failed

Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables

Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares

Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?

sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps

Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???

@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw

Removed Root on Costum FIrmware

As Mantioned in the title I accidentally removed my Root permission on my Amazon Fire . I'd tried to reeinstall busybox and after a reboot root permissions where gone :/
I also tried to use King Root again but with no luck. Flashed it with FireFlash
Model:KFFOWI
ROM:Cyanogenmod 12.1-20161122-UNOFFICIAL-ford

Unversed said:
As Mantioned in the title I accidentally removed my Root permission on my Amazon Fire . I'd tried to reeinstall busybox and after a reboot root permissions where gone :/
I also tried to use King Root again but with no luck. Flashed it with FireFlash
Model:KFFOWI
ROM:Cyanogenmod 12.1-20161122-UNOFFICIAL-ford
Click to expand...
Click to collapse
,
Assume you have tried re-enabling root under developer options to no avail (don't forget to reboot between attempts).
You will need to reinstall/sideload FireOS (same version that was on your device before installing CM 12.1) from stock recovery and start again. Be sure to keep device off WiFi except when running KingRoot; otherwise Amazon will push an OTA update that will block root and any hope of running a custom ROM.

Davey126 said:
,
Assume you have tried re-enabling root under developer options to no avail (don't forget to reboot between attempts).
You will need to reinstall/sideload FireOS (same version that was on your device before installing CM 12.1) from stock recovery and start again. Be sure to keep device off WiFi except when running KingRoot; otherwise Amazon will push an OTA update that will block root and any hope of running a custom ROM.
Click to expand...
Click to collapse
Is there a way to see what version of fireOS I had ? I installed CM12 a long Time ago.
Do I really need to install the same version ?

Unversed said:
Is there a way to see what version of fireOS I had ? I installed CM12 a long Time ago.
Do I really need to install the same version ?
Click to expand...
Click to collapse
If you go too low your device will brick. If uncertain sideload FireOS 5.3.1 which is the highest rootable build at present. You can find links in the index thread.
Do you recall using TWRP or FlashFire to install CM?

Davey126 said:
If you go too low your device will brick. If uncertain sideload FireOS 5.3.1 which is the highest rootable build at present. You can find links in the index thread.
Do you recall using TWRP or FlashFire to install CM?
Click to expand...
Click to collapse
I used flashfire. I have the stock recovery so no twrp
I guess this means installing stock firmware version 5.3.1.0 via sideload will work
I will try it

Unversed said:
I used flashfire. I have the stock recovery so no twrp
I guess this means installing stock firmware version 5.3.1.0 via sideload will work
I will try it
Click to expand...
Click to collapse
doesn't work. this is what I get:
loading: 'update-kindle-global-37.5.5.2_user_552153420.bin'
error: insufficient permissions for device.
See [http://developer.android.com/tools/device.html] for more information.

Unversed said:
doesn't work. this is what I get:
loading: 'update-kindle-global-37.5.5.2_user_552153420.bin'
error: insufficient permissions for device.
See [http://developer.android.com/tools/device.html] for more information.
Click to expand...
Click to collapse
Reboot both devices then follow instructions in this thread. Be sure to use the 5.3.1 bin, not the older one referenced in the video.

Davey126 said:
Reboot both devices then follow instructions in this thread. Be sure to use the 5.3.1 bin, not the older one referenced in the video.
Click to expand...
Click to collapse
ok my problem solved after sidloading with my windows partition
thanks for the huge help

[SOLVED] Pie october update failed

I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...

Same problem and I didn't find any solution yet.

Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli

It worked for me mate! Thank you

k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.

Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...

jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...

proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?

Worked for me too, thanks!

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader

wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.

Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse

I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.

whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...

Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse

I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.

Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse

whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.