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?
Related
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Capture the URL for it ?
Here is the link: https://ota.googlezip.net/packages/ota-api/google_marlin_marlin/d872269d3aff80d3b7f81d28c972d1d59f36f8f6.zip
(I'm not allowed to link to it directly due to my account age - sorry!)
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
This happened to me. I have a Verizon version dePixel8 and sideloaded E build a few days ago. Today I got the update message and it upgraded to K in about 2 minutes.
Gather this is for the Verizon models?
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
It's an update specifically for the Verizon Pixels. It contains a number of bug fixes and improvements according to the release info. A simple Google search will locate more info including the specifics of the bug fixes and improvements.
So this OTA will update my Google store device to the Verizon build? Weird. I'll just flash the whole build later.
So, after applying this update - what build does it show?
Just flashed the OTA. It does indeed update Google Store devices to the Verizon build of 7.1.2, NHG47K. Looking in the OTA zip, the update may only affect the system and vendor partitions.
I had this happen after I flashed the January build I think it was. I have a play store pixel on vzw and it was trying to update my regular stock rom the vzw-specific version. It sounds like if you're on vzw service then you'd benefit from their improvements. I'm waiting for beans to update his rom before I update from 7.1.1. I just hope it includes these vzw changes.
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
alsip1023 said:
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
Click to expand...
Click to collapse
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
hub1 said:
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
Click to expand...
Click to collapse
I was referring to the difference between the 7.1.2 builds, not the phones.
alsip1023 said:
I was referring to the difference between the 7.1.2 builds, not the phones.
Click to expand...
Click to collapse
So was I.
TonikJDK said:
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
Click to expand...
Click to collapse
Thanks for playing the guinea pig. Good to know nothing obvious was added in terms of bloat.
With that being said, that Pixel update is handed to Verizon to "test and certify". Then it is sent to the Pixels. Verizon only promised to not delay updates. They may still add apps, bloat, etc... Should they so choose.
Added information:
Google Store Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the right (as in enabled) but is overall greyed out after "K" update.
Verizon Purchased Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the left (as in disabled) but is overall greyed out after "K" update.
Not sure what this means. If anything, I found it interesting. Once it's unlocked, unless I submit a relock, it can't be relocked by OTA right?
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
gordonlw said:
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
Click to expand...
Click to collapse
Hello,
You bought a Google version, you are fine. You can sideload Verizon's OTA if you are on Verizon's network. Otherwise, no benefits...
Even true Verizon's unlocked Pixel owners, as long as they don't lock bootloader, it will stay unlocked, no matter what they flash FYI.
You can install SU with fastboot boot twrp as well.
Cheers...
Worked great thanks!
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.
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
I will start this thread by saying I f*****up, recently my pixel 3 xl is giving me various issues like system glitches, so many app reloads , Trash battery, so what a person in right mind will do UNLOCK THE BOOT LOADER and install other rom.
Then when i boot up in new room, i got to know I cant use google pay of which I am a huge fan of.
Then I flashed back the stock rom from googles website using FLASHH-ALL.BAT still the google pay doesn't work.
I want to completely make my pixel 3 xl stock, and lock the boot loader and get rid of it as there are too many tradeoffs in performance.
Can someone please give me a guide how to completely make it stock and lock the bootloader ?(WITHOUT BRICKING IT):crying:
Panda1213 said:
I will start this thread by saying I f*****up, recently my pixel 3 xl is giving me various issues like system glitches, so many app reloads , Trash battery, so what a person in right mind will do UNLOCK THE BOOT LOADER and install other rom.
Then when i boot up in new room, i got to know I cant use google pay of which I am a huge fan of.
Then I flashed back the stock rom from googles website using FLASHH-ALL.BAT still the google pay doesn't work.
I want to completely make my pixel 3 xl stock, and lock the boot loader and get rid of it as there are too many tradeoffs in performance.
Can someone please give me a guide how to completely make it stock and lock the bootloader ?(WITHOUT BRICKING IT):crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117/
Read #3
You should try stock rom with custom kernel before locking.
Sent from my SM-P205 using Tapatalk
Panda1213 said:
I cant use google pay of which I am a huge fan of.
Click to expand...
Click to collapse
Take a look at this thread for instructions on getting GPay to work. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950. There are two methods. One is manual (the OP), and the other is using a Magisk module. https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176. I have been using the manual method since the day this was posted over 6 months ago. It has worked fine on Pixel 3, Pixel 3 XL and 3XL on various custom ROMs. All have worked on Pie and "Q."
I don't want to do anything related to root and magisk, i have a factory warranty but does brick cover in warranty if it happens after locking?
Flash full image and take one ota before locking. If ota fails you are not stock.
Sent from my Pixel 3 XL using Tapatalk
How to know I am 100% stock?
How to know if my phone is 100% stock, there are part a and b for rom or something, then there is boot loader. How to make it return to stock a 100%?
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 ??