I'm having some issues work the P Beta mostly around Bluetooth that others say they are not so I was thinking about flashing the beta with a clean flash instead of just accepting the OTA. Can anyone tell me how to do this. I can flash a normal system image but don't know if this is different. If I wanted to leave the beta could I just opt out online or would I need to flash the Oreo system image again? Where would I get the Beta files to flash that way?
I could have sworn I read that flashing the factory images would not get ota updates.
Edit for picture.
acheney1990 said:
I'm having some issues work the P Beta mostly around Bluetooth that others say they are not so I was thinking about flashing the beta with a clean flash instead of just accepting the OTA. Can anyone tell me how to do this. I can flash a normal system image but don't know if this is different. If I wanted to leave the beta could I just opt out online or would I need to flash the Oreo system image again? Where would I get the Beta files to flash that way?
Click to expand...
Click to collapse
Flash the factory images, and let it wipe user data. If you have to unlock the bootloader to flash, it will wipe during that process.
https://developer.android.com/preview/download
In the future of the P betas (if you wish to use them) you can sideload OTAs if you dont get them automatically.
I have a Pixel XL that has the bootloader unlocked, rooted via Magisk and on Oreo 8.1.0 with the June 18 security patch. Question is, can I accept the OTA download to upgrade to Pie? Screenshots with additional info attached.
I suggest you to consider upgrading via fastboot since this is the next os version.
Download the latest factory image, then edit the script removing the "-w" so it won't wipe during the upgrade, and then install from fastboot.
Then just reflash magisk and/or kernel and/or twrp
Flash the latest factory image...
I have learned that to avoid the heavy battery drain you got to do 2 things...
Use the chrome webview
Do NOT or atleast manually manage the Location
Hello, I have pixel 2xl with unlocked boodloader, and my security patch is stack on 05. September... When I check for updates it says that my software is latest... But in security settings it says that security patch is old...should I lock bootloader? Will I receive OTA updates normaly etc
In CPY Z says that my device is not rooted, thanks in advance...
markokrstic0507 said:
Hello, I have pixel 2xl with unlocked boodloader, and my security patch is stack on 05. September... When I check for updates it says that my software is latest... But in security settings it says that security patch is old...should I lock bootloader? Will I receive OTA updates normaly etc
In CPY Z says that my device is not rooted, thanks in advance...
Click to expand...
Click to collapse
You have a few options. You could factory reset, then see if you get your OTA. You could also lock the bootloader, which wipes your device as well, then, yes, you will get normal OTA's. Or, you can adb side load the OTA zip from October, then November, then December to be up to date. Or, you can fastboot the factory images to get up to speed. Or, you can fastboot into twrp, then flash the OTA zips. And there ya go
Badger50 said:
You have a few options. You could factory reset, then see if you get your OTA. You could also lock the bootloader, which wipes your device as well, then, yes, you will get normal OTA's. Or, you can adb side load the OTA zip from October, then November, then December to be up to date. Or, you can fastboot the factory images to get up to speed. Or, you can fastboot into twrp, then flash the OTA zips. And there ya go
Click to expand...
Click to collapse
Tnx for fast reply
@Badger50: He doesn't have to install all three, but only the December OTA. Since the OTA zips Google makes available for download are full images they include all the patches from previous months.
Strephon Alkhalikoi said:
@Badger50: He doesn't have to install all three, but only the December OTA. Since the OTA zips Google makes available for download are full images they include all the patches from previous months.
Click to expand...
Click to collapse
Roger that my friend. I've just seen some folks have trouble when updating after a few months :good:
@Badger50: Understood there. I should have known there was a reason for you mentioning it.
I had the same problem when i buy my used pixel 2 xl, i solved the problem by this way
visit: https://www.google.com/android/beta
and unsubscribe my device from beta program. After some hours i receive ota
I have done factory data reset and there is an update, but it can't install, instalation problem... And its trying every few hours but it cant... Bootloader still unlocked
markokrstic0507 said:
I have done factory data reset and there is an update, but it can't install, instalation problem... And its trying every few hours but it cant... Bootloader still unlocked
Click to expand...
Click to collapse
Have you flashed TWRP? If so, you cannot update via OTA. This only works with the stock recovery.
You have to flash a full OTA via TWRP or flash the factory image with fastboot if you are using TWRP.
And if you don't use TWRP, you still can update manually. Why are you waiting for the automatic update in the first place?
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
BabelHuber said:
Have you flashed TWRP? If so, you cannot update via OTA. This only works with the stock recovery.
You have to flash a full OTA via TWRP or flash the factory image with fastboot if you are using TWRP.
And if you don't use TWRP, you still can update manually. Why are you waiting for the automatic update in the first place?
Click to expand...
Click to collapse
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
markokrstic0507 said:
I have unlocked bootloader, my phone is not rooted, when I try to update my phone tru settings and Sysrem update it starts and than stops (couldn't install update)
Click to expand...
Click to collapse
This has nothing to do with root, but with TWRP. Have you flashed it or not?
You can try to flash the boot.img again, too. Extract it from the factory image and flash it with fastboot. Of course this only helps if you have messed around with it.
If this doesn't work you can try a factory reset or flash the update manually. See https://developers.google.com/android/images for instructions.
Anyone have issues doing ota updates after relocking bootloader? I unlocked my bootloader. Installed magisk for root. Did modifications to by pass wifi hot spot authentication. Installed squeeze gesture for different actions. And now I want to revert back. Was still on stock.
Uninstalled magisk. Factory reset. Relocked boot loader. Then tried to install ota which would sit at 0% downloading and eventually fail.
My method, because I can't wait for OTA notifications:
1. Tap on the Complete Uninstall of Magisk and reboot.
2. Download OTA full image and install it using adb sideload.
3. Reinstall Magisk and patch the boot image (Need to download new factory image and unzip file).
4. Use fastboot to flash patched boot image and reboot.
5. Finished.
I would flash the factory image (of course you have to unlock the bootloader again) before locking it
y2whisper said:
I would flash the factory image (of course you have to unlock the bootloader again) before locking it
Click to expand...
Click to collapse
Thanks. Noob question. Keep seeing people say its very easy to brick my phone when I try to relock bootloader.. Does factory image mean the very first version released? Pixel 3 xl -9.0.0 (PD1A.180720.030, Sep 2018). Then after I will be able to ota update to current version? Or are all crosshatched files considered factory image. So any image will work?
Nevermind, I got it to go through. First time I actually used the newest feb 05 2019 file to flash. After I relocked my boot loader, I loaded a backup from my google account. That seems to kick me back down to jan 05 2019 security update version. This first time the ota would get stuck @ 0% and not do anything. I redid the whole thing using a dec 2018 file. After I relocked my boot loader and reloaded my backup from my google account. I was back at jan 05 2019.. prob due to reloading a backup. Now the ota feb 05 2019 is actually installing. Might've been a fluke. Thanks.
ychongy13 said:
Thanks. Noob question. Keep seeing people say its very easy to brick my phone when I try to relock bootloader.. Does factory image mean the very first version released? Pixel 3 xl -9.0.0 (PD1A.180720.030, Sep 2018). Then after I will be able to ota update to current version? Or are all crosshatched files considered factory image. So any image will work?
Click to expand...
Click to collapse
...very easy to brick my phone...
It means if you relock the bootloader and you are not 100% stock (No Custom ROM, Custom Kernel, T.W.R.P, Magisk, etc., residual files remain on your phone). You run the risk of bricking your phone.
Two ways to return the phone to stock:
- flash-all with the -w
- Settings > System > Advanced > Reset options > Erase all data (factory reset)
Hi,
It would be best if somone with expirience, for example, when transition from Oeo to Pie happened, what happened with your unlocked bootloader.
Should i lock bootloader, remove magisk, etc
Or restart the phone to factory and erase, that sounds most likely to be safest.
Thanks
Well, u just have to update OTA if your system partition is untouched and if not flash 10.0.17 with MiFlash, update to Android 10 OTA and install Magisk with patched Boot. Thats all!
You could flash Android 10 directly but I doubt that fastboot ROM will be available directly.
Cappucinto said:
Well, u just have to update OTA if your system partition is untouched and if not flash 10.0.17 with MiFlash, update to Android 10 OTA and install Magisk with patched Boot. Thats all!
You could flash Android 10 directly but I doubt that fastboot ROM will be available directly.
Click to expand...
Click to collapse
Can you provide the link to 10.0.17 please?