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.
I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?
There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
savi0 said:
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
Click to expand...
Click to collapse
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
5.1 said:
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
Click to expand...
Click to collapse
To clarify your meaning... The May Verizon OTA does or does not break root?
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
savi0 said:
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.
Click to expand...
Click to collapse
Hello,
If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...
savi0 said:
Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
5.1 said:
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
Click to expand...
Click to collapse
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Hey,
As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.
Cheers...
5.1 said:
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
Click to expand...
Click to collapse
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
sliding_billy said:
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...
Normally, we won't have to wait too long to get back TWRP/Root.
Cheers...
sliding_billy said:
I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
Hello,
I don't understand what you mean when you say:
alluringreality said:
That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update
Click to expand...
Click to collapse
If you have issues, just sideload the latest OTA from Google here:
https://developers.google.com/android/ota
Instructions are available on this page.
Good luck...
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.
Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
PrettyPistol555 said:
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
Click to expand...
Click to collapse
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
shagbag913 said:
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
Click to expand...
Click to collapse
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
PrettyPistol555 said:
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
Click to expand...
Click to collapse
Yep.
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Not yet available on my nokia 6.1. I think we are a couple of weeks away from the update.
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Which TA....?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
EricH7001 said:
Which TA....?
Click to expand...
Click to collapse
TA-1045
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I'm on the June 1st level
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Mobe1969 said:
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Click to expand...
Click to collapse
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Ozonethegreat said:
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Click to expand...
Click to collapse
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
prg318 said:
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
Click to expand...
Click to collapse
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Ozonethegreat said:
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Click to expand...
Click to collapse
Nope - don't think its Chinse - it appears to be a "global" or international version. I don't really notice a difference from my original stock.
I got it from here: https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
And was able to flash the "extracted version" with fastboot. I used some fastboot instructions that I found for a chinese rom and changed the filenames to match the worldwide filenames and it worked without the OST tool
Ozonethegreat said:
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Click to expand...
Click to collapse
Can you locate the downloaded OTA and post it here?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Were you able to update to Android pie?
Danny1976 said:
Were you able to update to Android pie?
Click to expand...
Click to collapse
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Can you check under system partition and look for Data/OTA
---------- Post added at 04:37 PM ---------- Previous post was at 04:14 PM ----------
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
Check system partition under data/ota.
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
You should have pulled the OTA link from a logcat so the rest of us can download the update files and upgrade ourselves :/
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Danny1976 said:
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Click to expand...
Click to collapse
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
neowlchaz said:
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
Click to expand...
Click to collapse
I got the July update in July and then I got the August update on August. I don't know why yours took a while to update. Mine and other that I know, get the update for the month the same month.
Hi, recently I bought my Moto Z2 Play (XT1710-09).
I really wanted to root my phone, but because of some weird bug, it soft-bricked it. Fortunately I had Absolute backup of whole internal storage so I have Original files.
Also I have not flashed TWRP, I have only fastbooted TWRP (Which is propably why I soft-bricked my phone)
So my question is very easy. Is it possible to lock bootloader if I have recovered back whole system and all it's files by stock files with which it (Moto Z2 Play XT1710-09) arrived?
Also the phone is fully functioning at the moment, with original files mantionet above, but it can't make working OTA updating process. And it's pain in ass, because the update manager is still apearing with new update...
So I have decided to lock bootloader even if it means to wipe all personal data and factory reset. Just for sake of getting rid of that stupid OTA updatete fullscreen pop up, that I have a new update waiting to be downloaded and installed.
You may ask as well "Why do you want to lock bootloadert insted of buying Titanium backup pro and freezing that update manager". The reason is simple. I'm afraid of rooting my phone again, because last time, it soft-bricked it and next time, it may full-brick it.
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Surely there is a fastboot command somewhere (which I think I saw in another thread) without having to flash some firmware?
https://forum.xda-developers.com/showpost.php?p=77270030&postcount=9
So that does mean. As long as I have 100% of stock files with which it come to me, it will lock?
julesism said:
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Click to expand...
Click to collapse
Every firmware I try fails to lock my bootloader, validation fails because non of them are above the security level of my device before I unlocked. Is there any newer firmwares ?
I finally got a pixel phone, the 2 XL. got a question about the romming process
if i install a custom rom, then decide to go back to stock using the images that google provides, and relock the bootloader and all that, will i still be able to get OTA updates?
i have a moto z3 play that if you go back to stock and lock it, it says the phones using a different OS and requires Motorola to reprogram the phone in order to get OTA updates again.
xSpartacusx said:
I finally got a pixel phone, the 2 XL. got a question about the romming process
if i install a custom rom, then decide to go back to stock using the images that google provides, and relock the bootloader and all that, will i still be able to get OTA updates?
i have a moto z3 play that if you go back to stock and lock it, it says the phones using a different OS and requires Motorola to reprogram the phone in order to get OTA updates again.
Click to expand...
Click to collapse
You should be fine. While I haven't done it personally, I've seen several that have ??