It's been a while since I did this or even worked on my phone so my memory is foggy.
Plus I have used dPixel8 to unlock my bootloader for my Verizon Pixel XL and put on Pure Nexus... but that hasn't been updated since July
Anyway, can anyone tell me exactly how to return my Pixel XL to stock.?
I honestly don't have the time or energy to fiddle with it anymore and it's been so long since a PureNexus update, I just don't care to wait any longer for Oreo.
fsuagentsmith said:
It's been a while since I did this or even worked on my phone so my memory is foggy.
Plus I have used dPixel8 to unlock my bootloader for my Verizon Pixel XL and put on Pure Nexus... but that hasn't been updated since July
Anyway, can anyone tell me exactly how to return my Pixel XL to stock.?
I honestly don't have the time or energy to fiddle with it anymore and it's been so long since a PureNexus update, I just don't care to wait any longer for Oreo.
Click to expand...
Click to collapse
Jist install 8.1 factoy image .No need to relock your bootloader none of that bull****. As an unlocked bootloader will not void warranty
fsuagentsmith said:
It's been a while since I did this or even worked on my phone so my memory is foggy.
Plus I have used dPixel8 to unlock my bootloader for my Verizon Pixel XL and put on Pure Nexus... but that hasn't been updated since July
Anyway, can anyone tell me exactly how to return my Pixel XL to stock.?
I honestly don't have the time or energy to fiddle with it anymore and it's been so long since a PureNexus update, I just don't care to wait any longer for Oreo.
Click to expand...
Click to collapse
First, update your ADB tools to today's version.
Then, go here and get the December Marlin zip. https://developers.google.com/android/images
Info on setting up ADB and how to flash newest Oreo on this page as well as the download.
Open up and expand the zip contents in your ADB tools folder.
In Windows Explorer, double click on flash-all.bat and it will make your phone like new.
It will wipe your phone, so backup whatever you need before.
Related
With pixel xl bought say pixel store, when does ota usually Côme for 7.1.1?
GCbard said:
With pixel xl bought say pixel store, when does ota usually Côme for 7.1.1?
Click to expand...
Click to collapse
OTA updates roll out in phases. Can be as little as a couple of hours after release, or as much as 10 days to 2 weeks.
You can speed up the process by just sideloading the ota. I gave up on it coming automatically (I'm impatient) and went ahead and installed manually and running great.
xxfwmxx said:
You can speed up the process by just sideloading the ota. I gave up on it coming automatically (I'm impatient) and went ahead and installed manually and running great.
Click to expand...
Click to collapse
Need an unlocked bootloader for that?
GCbard said:
Need an unlocked bootloader for that?
Click to expand...
Click to collapse
Nope not at all I am completely stock and locked. I used the skipsoft Unified Android toolkit and was very easy to do.
GCbard said:
With pixel xl bought say pixel store, when does ota usually Côme for 7.1.1?
Click to expand...
Click to collapse
The first week of each month is when security updates are usually released.
That doesn't mean you'll get it the first week (unless you manually sideload the update).
But that's when updates are released.
Kind of like Microsoft releasing updates every second Tuesday of each month.
Except those get applied a lot faster, to more devices at a single time.
Hello guys,
This is my first post but this has been frustrating me for a while.
Just a little background info:
I've had in order a Nexus 4, Nexus 5, Nexus 6p and now the Pixel XL.
It's been a while since I've fiddled around and rooted my phones... maybe my last rooted phone was the nexus 5.
Anyway, I've been wanting to use android pay for a while now on my XL.
My Pixel is a pre-order and stock out of the box I was getting the "your phone might be rooted or bootloader is unlocked" error.
At first, I thought maybe it is because I had copied my data and settings from the nexus 6p which had the bootloader unlocked and maybe that affected the pixel? unlocked the bootloader by default or smthg...
So I went ahead and put the pixel into fastboot and tried to lock the booloader... I got that the bootloader is already "LOCKED"... So what now?
Bassem9 said:
Hello guys,
This is my first post but this has been frustrating me for a while.
Just a little background info:
I've had in order a Nexus 4, Nexus 5, Nexus 6p and now the Pixel XL.
It's been a while since I've fiddled around and rooted my phones... maybe my last rooted phone was the nexus 5.
Anyway, I've been wanting to use android pay for a while now on my XL.
My Pixel is a pre-order and stock out of the box I was getting the "your phone might be rooted or bootloader is unlocked" error.
At first, I thought maybe it is because I had copied my data and settings from the nexus 6p which had the bootloader unlocked and maybe that affected the pixel? unlocked the bootloader by default or smthg...
So I went ahead and put the pixel into fastboot and tried to lock the booloader... I got that the bootloader is already "LOCKED"... So what now?
Click to expand...
Click to collapse
I had a similar issue. It appears that the latest OTA has broken this for some users. I ended up wiping and flashing the full factory image to solve this.
dsmitty166 said:
I had a similar issue. It appears that the latest OTA has broken this for some users. I ended up wiping and flashing the full factory image to solve this.
Click to expand...
Click to collapse
That's weird because I was on 7.1 out of the box and hadn't updated. And now on 7.1.1 and I still have the same issue.
This is just really annoying... Are there any trusted alternative apps for mobile payments?
I'm fairly new to the XL 2, coming form a Nexus 6P this is quite the learning curve.
I'm looking to update to Oreo 8.1 now that it's live. I'm currently bootloader unlocked (not critical), twrp not installed, November update, rooted with magisk, stock kernel. What would be my best course o f action to update to 8.1? Thanks in advance for the help.
Triscuit said:
I'm fairly new to the XL 2, coming form a Nexus 6P this is quite the learning curve.
I'm looking to update to Oreo 8.1 now that it's live. I'm currently bootloader unlocked (not critical), twrp not installed, November update, rooted with magisk, stock kernel. What would be my best course o f action to update to 8.1? Thanks in advance for the help.
Click to expand...
Click to collapse
Former 6p guy as well. The learning curve isn't that bad, just takes a lot of reading is all. As far as updating, you'll need to unlock critical so you can update your bootloader. Unfortunately, it'll wipe your phone. After that, since your phone has been wiped, might as well flash the new 8.1 with the flash-all.bat script in fastboot mode. Then, after you set up your phone, go ahead and root it again :good:
I am a bit confused by all the posts about this subject
I would like to unlock my phone, for future rooting, when everything is more stable, meanwhile I want to get OTA updates on the phone "automaticaly", is that possible
You can definitely unlock the bootloader and still receive OTA.
And for your first point, rooting is plenty stable already, so no need to wait for that. Though if you aren't well versed in fastboot or root upgrade processes, you should definitely read all the most recent guides on it to make your transition smoother.
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
melorib said:
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
Click to expand...
Click to collapse
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
wtherrell said:
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
Click to expand...
Click to collapse
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
melorib said:
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
Click to expand...
Click to collapse
There's issues with Magisk and some other phones, but topjohnwu has a Pixel 2 I believe, so he tests on that.
Magisk for our phones is perfectly stable, the only issue is people don't like the dtbo image being edited to remove AVB 2.0/dm-verity.
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
canemaxx said:
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
Click to expand...
Click to collapse
Strange, there was at least an update in January
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
canemaxx said:
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
Click to expand...
Click to collapse
Why? I want OTA updates...
I'm not sure why they just have not come to my phone.
canemaxx said:
I'm not sure why they just have not come to my phone.
Click to expand...
Click to collapse
You only unlocked the bootloader? Maybe because it is Verizon, the bootloader is supposed to to be locked!
I can't see that being the reason as I bought the phone from the Google store
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
Sounds strange, maybe you updated before OTA was available for Verizon...
In 2 weeks I get mine, going to unlock before any update, it was bought December, so it has at least one update missing...
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
v12xke said:
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
Click to expand...
Click to collapse
Thanks I know how to sideload or flash the full image but just was hoping I wouldn't have to again and again
Are your phones enrolled on the Android Beta Program ? My P2 was and I never got the Jan. Update till I Unenrolled from the beta program. Immediately afterwards I checked and Jan update was available.
Anyone been able to successfully receive an OTA to the beta yet? Enrolled my device last night the moment I got it home and nothing so far.
Disclaimer: I'm using a carrier and bootloader locked T-Mobile version; still hoping I can eventually get TForce to carrier unlock this for me sooner rather than later otherwise i'll just return it and get one direct from good old El Goog.
Did they get magisk for the 3XL yet; last I read over there they didn't have it for Q on the XL.
This true. I spent a couple hours on this last night and it does not work. I went back to pie.
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
That's pretty much what I figured, but wasn't certain. Good to have some feedback from others; sounds like we can pretty much confirm that it isn't being pushed to the 3a devices yet.
I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?
DanRyb said:
I got my Pixel 3a XL Wednesday (from the Google Store) and I got the OTA for Android Q beta immediately after enrolling the device. Stupid question, but did you go into System updates and check there?
Click to expand...
Click to collapse
Yep. It's possible they are withholding the OTA from carrier devices...
P$udo said:
I think it may not be specific to your TMobile branded Pixel. I've bought one straight from Google and have opted in but have yet to receive the update.
I've tried flashing the Q Beta 3 image from Googles dev site, but get an error when flashing system so haven't been able to flash it. Doesn't help that the latest version in for March.
Click to expand...
Click to collapse
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.
alphahere said:
By 3aXL came from bestbuy and had no problem flashing the Q-Beta 3. It was really nice but could not root the phone with canary Magisk, so I went back to pie.
Click to expand...
Click to collapse
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.
P$udo said:
If I may, what was your flashing environment? When I initially tried to flash the Q beta 3 I was told that to flash system.img I needed fastbootd. I have tried using linux as well as minimal ADB and fastboot on windows.
Click to expand...
Click to collapse
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Looks like Pixel 3a and 3a XL were removed from eligible devices on the beta sign up page.
I wonder what's up?
if anyone is looking for the download you can find it here
alphahere said:
I had trouble but got this error and got the latest version then fastboot worked. I saw the fastbootd come up on the phone while q-beta was flashing.
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Wow. Thanks for that. I thought fastbootd was a mistype when they were compiling. I didn't know that it was a whole other thing. Seems to be more akin to what recovery previously was on some older devices.
I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.
elpindian said:
I'm curious to how you guys got the OTA update for Q. When I try to enroll this is what I come across.
Click to expand...
Click to collapse
I did not get the OTA. I downloaded the firmware image and flashed it.
Android q beta isn't ready for the pixel 3a/3a xl until June
An FYI... I just wandered over to Papajohnwu's Twitter and he is saying he'll be ready for Q.That's some good news, hate to be stuck on Pie forever.
If you have a 3a (xl) from a carrier like T-Mobile where to boot loader is locked, if you're able to use adb/fastboot to flash beta 3, you very well may not be able to revert the phone to Pie. I'm stuck as I got mine on the day TMO put them on sale, then opted in to the beta expecting to be able to opt out, well considering they removed that option, I'm now stuck on Q..
Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.
I'm curious how you got it unlocked from T-Mobile. I picked mine up on release day and when I got around to checking, OEM Unlocking was greyed out. Did you do this before installing a SIM?
Thanks!
PhoenixPath said:
Got it on my P3aXL.
Got the device SIM-unlocked from carrier (T-Mobile).
Toggled OEM Unlocking in Developer Options.
Downloaded new adb/fastboot (If you have not done this in the last week, do this now.)
Rebooted to fastboot mode.
Ran "fastboot flashing unlock"
Let it reboot to welcome screen
Booted back into fastboot.
Ran flash-all from Q Beta 3 Full Image download (Still available from Google).
No issues so far. Disabled Digital Wellbeing, enabled full-gesture control, enabled Dark mode override in developer options, and it is so nice.
PM me if you need any help or clarification on the steps I used.
Click to expand...
Click to collapse