Related
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.)
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
EDIT: Just got the OTA for the N preview, so I guess it's just a roll out thing then. Just want to leave this here for anyone else who's new to nexus devices and was wondering the same.
AnrgKrshn said:
Hi I just wanted some confirmation that unlocking bootloader doesn't block me from getting OTA updates from Google, since I haven't gotten an OTA for the latest build yet (The May update). I'm hoping this is only cause I'm in India and it hasn't pushed to us yet. I've enrolled in the Android Beta Program to test if OTA is really broken (since it sends an OTA with the Android N image.
I haven't modified anything, I tried flashing TWRP but it didn't stick cause I didn't know I had to go into the recovery and modify the system/boot, so I still have the stock android recovery.
Any confirmation will give me a lot of peace of mind, cause I value getting OTAs and not having to manually flash it. If it has indeed been broken, I want to know if relocking would fix it and if relocking would wipe data again. Thanks for your help
Click to expand...
Click to collapse
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
brholt6 said:
Simply having an unlocked bootloader won't stop you from receiving OTAs. I don't believe they've even began pushing the OTA for the May update.
Click to expand...
Click to collapse
Just saw this after I posted my edit lol. Thanks for the confirmation
Will the ota work with systemless root?
94SupraTT said:
Will the ota work with systemless root?
Click to expand...
Click to collapse
You need to flash stock boot and recovery images to receive it or alternatively use chainfires flashfire app.
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk
Hi, hoping I could get some help.
I just got a huawei watch and cannot get it to update. It is on version 1.3xxxx. When I try to update it, it says it's already the latest version. Hopefully I'm just overlooking something very obvious as right now I feel stuck in the mud. Thanks for your help in advance!
Same issue here! Own the watch from 4 days now.
Same for me
An idea ?
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
jainanshal said:
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
Click to expand...
Click to collapse
The issue with flashing the stock image is that you have to unlock the bootloader, and after that it seems that you loose the warranty.
Better flashing OTA if you want to stay stock. I bought my refurb from newegg.ca too.
ndompierre said:
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Click to expand...
Click to collapse
Same problem.
Then I took your advice and it worked out great, and without changing the bootloader, thank you so much ndompierre :good::victory:
I got my newegg refurb yesterday and could not force the OTA despite resetting and checking multiple times. This afternoon it updated to marshmallow.
Each time time it reboots, I check for updates. I am currently receiving my fourth update of the day.
I guess each security patch has to be downloaded separately. I'm up to August so far..
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
bjoostema said:
Anyone gotten this build via OTA? I got impatient and flashed the factory images. Just curious about that weird build number...https://www.reddit.com/r/GooglePixe...nyone_seen_nhg47k_in_the_wild_might_or_might/
Click to expand...
Click to collapse
I thought I was the only one, I didn't get the OTA yet either, I'm still waiting even though it's supposed to be out and Verizon normally has it ready to download immediately when they say it's ready on their software update page.
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Well that helps, I have a play store phone but Verizon service and I haven't been able to get OTA yet even when I tell it to go look. I guess I will have to wait until Verizon gets going on this. Taking the sim card out and rebooting does not help.
Sent from my BTV-W09 using Tapatalk
bjoostema said:
I haven't heard anyone on Verizon getting an OTA yet, which is odd like you implied. I wonder what they're holding off for. It also didn't mention the Android version bump in their notes.
Click to expand...
Click to collapse
I got the OTA, it's 7.1.2 and definitely the NHG47K
LaosPerson said:
I got the OTA, it's 7.1.2 and definitely the NHG47K
Click to expand...
Click to collapse
Are you able to grab the link?
rozyman17 said:
Are you able to grab the link?
Click to expand...
Click to collapse
Link for what? Sorry I'm confused lol.
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Any time there is an update I just grab it from https://developers.google.com/android/images. I haven't tried flashing the OTA from the page since I usually grab the full factory image (I don't mind starting over lol). I am on Verizon and my build number after I flash the factory image is N2G47E. There are no Verizon apps on the images , but during set up it will prompt to download all that Verizon crap-ware, which you can cancel or uninstall.
As of last night, Verizon has released the K build, which is not up on the developer site. Must be something in there that is better than the E build on their network. Just an FYI.
rozyman17 said:
Link for the OTA. I sideloaded the E build, but wouldn't mind putting on the K build
Click to expand...
Click to collapse
I did the same thing earlier this week. Just checked for updates and nothing. Hope I am not hosed lol.
I ended up with the Verizon version OTA last night (non rooted, google play phone on Verizon service). I did not notice any Verizon-ware installed on the phone, at least not yet. Seems pretty flawless so far.
Sent from my Pixel XL using Tapatalk
Anyone able to upload the OTA?
I would be concerned with the Verizon firmware locking the bootloader on Google Play store Pixels
I don't think that's how it works.
After the frustration it took for me to get stock 7.1.2 on my PXL, I'll wait to see how people like the K build before I consider going back to 7.1.1 so I can be recognized and offered the OTA.
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Trooper27 said:
No one has the OTA file yet? Assume that I can't to back to 7.1.1 to get this OTA? I sideloaded the E build earlier this week.
Click to expand...
Click to collapse
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
It seems to bounce back and forth, sometimes there is a Verizon specific firmware sometimes there isn't, but it would be nice to know before side loading how many branches of the firmware there will be.
Sent from my Pixel XL using Tapatalk
destruya1 said:
There's always loading the 7.1.1 factory image back, but you can only do that when unlocked. I just hope this is a one-off, because over time it might become 'a thing' if people who sideloaded are on a different release track as others'. It would be nice to know if this is just 7.1.2 with VZW branding, or if it gives better performance on Verizon's network, but evidently we're too dumb to understand exactly what's different between stock 7.1.2 and their version.
Click to expand...
Click to collapse
I am not unlocked so I have no option of doing that. I had no clue there would be a Verizon specific build or what I have not sideloaded earlier this week. Guess I have to learn patience LOL.
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
awarman said:
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
Click to expand...
Click to collapse
are you rooted?
Yes but I have removed root and tried, same thing. Cleared dalvik cache, same thing.
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
hallo dare said:
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Click to expand...
Click to collapse
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
awarman said:
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
Click to expand...
Click to collapse
You won't get incremental if rooted, only full updates.
hallo dare said:
You won't get incremental if rooted, only full updates.
Click to expand...
Click to collapse
So in theory, if I unroot then run OnePlus updater I should be able to get the update. Then reboot after. Correct?
Maybe I did something wrong, but I tried unrooting for the last OTA and still received the same error. I had to wait until the full version was on the OnePlus site, I think OnePlus updater grabs the zip from there too. It also took a month longer for the full zip to hit the OnePlus site.
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
I have global unlocked varient and when I first received it I just flashed BA/EU on both slots(local upgrade twice) and I've been able to get all full zip updates(via system updates and/or O2 updater app) staying rooted the whole time. I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Initially I was getting that error. Then I ran the uninstall in Magisk and chose to RESTORE IMAGES. I then just hit retry on the OTA from the phone settings (NOT Oxygen Updater) and the update installed. Initially this did not for 11.2.3.3 as it would still give the error after unrooting by uninstalling Magisk, then it worked for 11.2.4.4 and 11.2.5.5. So YMMV. You can look here for my update process as I was having an issue post-OTA:
No cell service after update to 11.2.4.4AA while keeping root
I'll try to keep this short. Global OP9 Pro on 11.2.2.2AA, bootloader unlocked, rooted w/Magisk. Been trying to find the best way to update. Decided on trying this: 1. Un-rooting by going in to Magisk and doing UNINSTALL->RESTORE IMAGES 2...
forum.xda-developers.com
jammin6996 said:
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
Click to expand...
Click to collapse
This worked, btw. Never had to do this with my OP8P. Hopefully this isn't a regular occurrence.
Shooter7889 said:
I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Click to expand...
Click to collapse
Not knowing that the AA variant would have dog**** updates from the start, and already having restored my old phone's data and not wanting to go through setup and restore again.
Edit: The goal is also to eventually get on crDroid anyway so it's whatever. I'm not resetting until there's an official crDroid build out.