Develop Bugs

[Updating Pixel XL] After unlocked bootloader and rooted

So some might remember me awhile back ago... https://forum.xda-developers.com/pixel-xl/help/unlocking-verizon-bootloader-t3557290
I got tired of not having a unlocked/rooted device since I just dropped so much money on a new phone for my 27th bday sooo I took it back to verizon and swapped it for a new one. I was having the battery problems where my phone would hit 30-15% and just die on me OR the screen would die on me but the phone stayed on no problems.. I'd be in a phone call and the screen would shut off and I couldnt get it to turn back on without plugging in a charger or battery bank.
I've got my new phone now and everything is working flawlessly.. It's unlocked, has twrp installed and rooted just fine..
Now I remember seeing something about once I unlock/root the device my OTA becomes disabled so where do I get the OTA update for the device so I can go to 7.1.1 or later this month 7.1.2? I found this https://developers.google.com/android/ota and I see the 7.1.1 update but it's 800mbs which means I'm guessing if I flash that i'd be completely reinstalling a new copy of android and lose all of my data and have to go through setting up my phone again etc..
How do I just get the update itself and flash that? When I use the OTA on my Pixel XL the download is only like 200MB it doesn't install though just says it failed. Still new to all of this but I'm learning and how else am I gonna learn if I don't ask questions
a point in the right direction would be great.

https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk

wyrdtrtle said:
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?

[QUOTE=
If you go to that link in the post above you can download the newest firmware. Unzip it and open the bat file with note editor or something like that and remove the -w and it will update without losing your data.

Dimmizer said:
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
Click to expand...
Click to collapse
You use your original link and sideload it with TWRP.

TonikJDK said:
You use your original link and sideload it with TWRP.
Click to expand...
Click to collapse
Thanks

Upper left corner Link to OTA's smaller
Sent from my Pixel XL using Tapatalk

Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?

Dimmizer said:
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Click to expand...
Click to collapse
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.

Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?

Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
You did not decrypt it. That isn't currently doable.

TonikJDK said:
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Click to expand...
Click to collapse
Doing what you said now

[
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
I wouldn't unroot with that, doesn't work all the time just flash the newest firmware and you will be unrooted. You are going to have a bad time if you do.

mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..

lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.

Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Hit the link below, it explains it well and you will see it worked for others.
https://forum.xda-developers.com/pixel-xl/help/rooted-twrp-recovery-how-update-ota-t3524279
If you ever bootloop don't freak, its an unlocked google phone. Flashing back to stock is easy.

The only thing that was in question was the bootloader unlock, once its unlocked your safe. It wont relock unless you lock it. But, if you do lock it, its locked for good. Afaika
Sent from my Pixel XL using Tapatalk

Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Dimmizer said:
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
Click to expand...
Click to collapse
I flashed OTA with twrp on my buddy's pixel for the Feb update worked just fine. Just make sure it's the OTA and not the factory image. But the best way would be using fastboot

Most anything you flash (stock updates, custom roms, will overwrite recovery. But not a problem, you just re-boot it to flash it, or just boot it and flash su and reboot device.
Sent from my Pixel XL using Tapatalk

awesome , thanks again everyone for your time and the help, very much greatly appreciated.

Anyone received the Oreo ota

Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???

ttocs99 said:
Hi has anyone received the Oreo ota on non rooted nexus 5x and without signing up for the beta program???
Click to expand...
Click to collapse
Not yet. I'm on T-mobile.

mrpink10 said:
Not yet. I'm on T-mobile.
Click to expand...
Click to collapse
Same I spoke to Google support and they claim it's Al read available via ota

Haven't got it yet I bought my phone from Google.
Sent from my Nexus 5X using Tapatalk

Are you rooted? If so just get the ota from google and flash it with flashfire

jd1639 said:
Are you rooted? If so just get the ota from google and flash it with flashfire
Click to expand...
Click to collapse
Flashfire doesn't fully support Oreo yet so that's a no go, same with TWRP. ADB sideload might work.

I just flashed it this morning and had no problems.

I flashed a couple of hours ago official OTA package via ADB. No problems till now.

I took the plunge and flashed the 8.0 stock factory image the done a factory reset after to make sure and it been great ever since turned off animation and it's nippy just wish battery was about better but I'll give it a few days see if that goes

jd1639 said:
I just flashed it this morning and had no problems.
Click to expand...
Click to collapse
Did you use Flashfire?

Does anyone know why the battery drains so fast on Oreo even after fresh clean install

Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.

jd1639 said:
Yes, Pro v0.60. I also maintained root and twrp. I had supersu 2.82-sr3 installed at the time so make sure you have that.
Click to expand...
Click to collapse
Well then, I guess it's just when coming from the beta that it doesn't work. Thanks for the heads up.

ttocs99 said:
Does anyone know why the battery drains so fast on Oreo even after fresh clean install
Click to expand...
Click to collapse
Enable dev options and disable always keep mobile data on.
I just noticed that for some reason that is checked in oreo and it shouldn't be unless you are never on WIFI.

ttocs99 said:
Same I spoke to Google support and they claim it's Al read available via ota
Click to expand...
Click to collapse
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.

I can confirm that jd1639's method works for people rooted with TWRP.
- download OTA (https://developers.google.com/android/ota)
- run Flashfire 60.0 (free version is OK)
- when asked "A system update has been detected", cancel
- Flash ZIP or OTA
- uncheck "restore boot and recovery images"
- press "EverRoot" and select "Inject SuperSU" and "Preserve recovery"
- Flash
- wait patiently
I tried flashing the modem FW using "Flash firmware package" on the OTA zip file. It rebooted and the screen went black for many minutes. I had to hard reset.
Can anyone confirm the 8.0 baseband? I have M8994F-2.6.39.3.03. I know that's the baseband for the 8.0 developer preview, but I wanted to make sure it was the final.

Billys20 said:
It is true that the OTA is out there. I confirm it because I signed-up to beta program to get the update and two days later I opted out to see if this is the latest official OTA ROM and I didn't get the update. So if you don't want to wait you can do the same it's safe. You can check the latest OTA here: https://developers.google.com/android/ota
The version is the same I have. 8.0.0 OPR6.170623.013.
Click to expand...
Click to collapse
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?

tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
Nope
Sent from my Nexus 5X using Tapatalk

tallgrasshawk said:
Probably a stupid question, but this OTA file- since it's ~1gb-, does it wipe the device like the full image?
Click to expand...
Click to collapse
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).

Billys20 said:
No. There is no such problem.You can do it with any of the two ways if you didnt get the OTA until now. 1) Sign-up for the beta program install the update and then opt-out of it. 2) Flash the OTA files from Google to your phone. Or 3) But these are rumors and I can't be sure: An update will come at 11 of September with new Version of Oreo 8.0.1 with better support for Carriers (it is 8.0.0).
Click to expand...
Click to collapse
6p here, downloaded ota (NOT factory), ran Tibu, ran Flashfire 7.0 pro as described and after three reboots and a while of booted finishing, was cleanly updated to 8.0.0. took < 20 min. [emoji2]
Sent from my Nexus 6P using Tapatalk

If you are rooted and unlocked can you accept the update notification?

I haven't been offered it yet, but I know it's coming so wanted to ask, trying to stay on the official channel.
If you accept the update will I lose root and have to re-root?
I'm out of practice since the Nexus 6P tether worked out of the box.
Thanks in advance!

wonderrx said:
I haven't been offered it yet, but I know it's coming so wanted to ask, trying to stay on the official channel.
If you accept the update will I lose root and have to re-root?
I'm out of practice since the Nexus 6P tether worked out of the box.
Thanks in advance!
Click to expand...
Click to collapse
The OTA probably won't work because when you root with Magisk you flash a modified boot image. Process would be as follows before taking the OTA.
Flash stock boot image from the Image Version you are currently on (i.e. Flash the October Boot Image)
Reboot
Take OTA
Re-root using Magisk using the November Boot image to patch
add tethering line to build.prop or get the Magisk Module
Profit
You would need to repeat this for each monthly update to keep root.

I had always thought this was the best way to install OTAs. Someone correct me if I'm wrong?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

Cowbell_Guy said:
I had always thought this was the best way to install OTAs. Someone correct me if I'm wrong?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Normally yes but I'm not sure if the partition structure is identical on the new Pixels but you could always try @topjohnwu 's method and report back.

I didn't think you could do an OTA with an unlocked bootloader, is that true? If so, topjohnwu's method wouldn't work anyway.

Cannot flash official 8.1 OTA over 8.1 DP2

I am on 8.1 DP2 which is OPP6.171019.012, tried to install the official 8.1 OTA which is OPM1.171019.011 : obviously the latter is older that DP2, so now I am still on DP2.
Maybe I need to wait for the OTA for those that are on beta program?

Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data

skw5115 said:
Yes, you'll either have to wait for the official OTA for beta users or use the factory images to my knowledge. You can use the factory images and just remove the wipe command ( -w ) from the flashall.bat file to keep your data
Click to expand...
Click to collapse
I can confirm this, I have updated this way.

anyone has the OTA for those on DP2?

Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?

But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?

Mikulec said:
I can confirm this, I have updated this way.
Click to expand...
Click to collapse
I'm assuming you already had an unlocked bootloader?

Mr Patchy Patch said:
Curiosity, how can the final version be older than a beta? I've seen this posted a few times now, how can/does this happen?
Click to expand...
Click to collapse
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk

oxman said:
But after flashing the final, we're still enrolled to the beta. How to cancel the enroll without erase data ?
Click to expand...
Click to collapse
go to the website and unenroll.

imnuts said:
It isn't, but they probably put an unreasonable date stamp in on purpose to avoid any potential issues in the flashing process.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?

Usually an OTA is made to go from one specific build to another. Which would make sense on why you can't do it that way. If you have the unlocked bootloader flashing the factory image for 8.1 can be done.

thegios said:
So those on DP2 with unlocked bootloader when/how will be able to update to official/final 8.1?
Click to expand...
Click to collapse
If you have an unlocked bootloader, you can update now with the factory image. Otherwise wait until the OTA rolls or for beta users.
Sent from my Pixel 2 XL using Tapatalk

I just got the small ota to bump me from DP2 to final. So it's in the wild now. You can probably force the update at this point.

Like he said, I just got the official OTA bump yesterday to final. If you can't force it, it should come soon regardless.. This shows the December 5th patch.

hrkahn said:
I'm assuming you already had an unlocked bootloader?
Click to expand...
Click to collapse
yes

I have same problem with Nexus 5X.
Adb sideload breaks at 47%.
Now i can only wait, because i have the no-rpmb-bug.

TWRP & Root

I'm so confused with this phone. Google sent me a 128gb Pixel XL which I activated on my Sprint account. I'm fairly comfortable with rooting, flashing, TWRP, SuperSU, etc., however for the life of me I cannot get TWRP to stick.
Background...
Phone came to me straight from Google, and updated to 8.0 immediately (this was in August). Since, the phone doesn't appear to have been updated as I was still on 8.0 from August I believe
Here's what I did...
Unlocked the phone, using TWRP image, boot to it via fastboot, flash the installer TWRP zip, and then issues happen.
On 3.2.1.0-0 it reboots to system (even if I go back into TWRP's main setting and Reboot Recovery). If I use 3.2.0.0-0, it gives me an ERROR 1 code. I've tried using systemless root method (with the modified TWRP img, Aroma Installer for SU, etc.). I've tried using the 2 most recent TWRP images from their website. I initially started with this guide ([GUIDE] Pixel XL Android 8(OREO) Unlock/Install Stock Images + Kernels/Recovery +). I then tried this method using Systemless root ([Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU)).
I even tried flashing the OTA manually, which caused other issues, mainly bootloops. I finally got the most recent 8.0 OTA to work after multiple errors (which appear to be caused by outdated platform_tools). When trying to flash the OTA, only OPR1 would flash, OPR3 would always just hang or throw errors (sorry, no changelog, which I know is not helpful). Am I not correct that OPR3 is what is needed for a Sprint (US carriers) based phone? Regardless, everything is up, and running now in 8.0, however I can't take the OTA (it fails when trying to download), and I still can't get TWRP to stick.
Is there anything obvious I'm missing? I can boot to TWRP, but can't flash it, regardless of what I do. I've searched and most issues I've found in getting TWRP to stick either has to do with flashing the boot.img from an OTA or using 3.2.1.0 instead of 3.2.2.0. Funny thing, I don't see the 3.2.2.0 img file, just the flashable zip. Someone please help me, even if it is to tell me I'm in over my head and should stick to a stock rom.

I think you should simplify your life.
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file.
That will update your phone, but leave settings a data in tact. Again, remove the -w so you don't wipe user data.
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
I do it each month this way. It takes 15 minutes and I have zero problems.

To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.

TonikJDK said:
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file..
Click to expand...
Click to collapse
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
TonikJDK said:
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
TonikJDK said:
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
Click to expand...
Click to collapse
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?

vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
2 different methods, same result. Make sure to thoroughly follow instructions with whatever method you try and you'll be fine.

vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.

TonikJDK said:
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?
Click to expand...
Click to collapse
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.[/QUOTE]
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?

Chance Ill said:
I
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?
Click to expand...
Click to collapse
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....

TonikJDK said:
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....
Click to expand...
Click to collapse
Oh ok. I do remember coming across Chainfire's announcement awhile ago but was unaware that the new owners hadn't been active with the community. That's disappointing to say the least.

Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
Tried this, for some reason wouldn't work. Tried the TWRP and it wouldn't due to OpenSourceScript or something. Then tried rooting and installing busybox, it wouldn't do this either. It attempted to flash it to sd card, another place, and finally in the right storage for this device, and it wouldn't for some error. No specifics on the error were given.
TonikJDK said:
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
Click to expand...
Click to collapse
Tried this next, removed the -w, and used flash-all in fastboot. This worked, however after I upgraded to 8.1 OPM1, I left it alone. Will try again tonight to root, and attempt flashing magisk for the first time.
Thanks for all the advice!