Related
Because the Google Store is so back-dated to get a pixel xl, can I just go to Verizon, pay cash for a pixel xl, then flash the stock ROM to it and then get the factory updates?
The way I understand it Verizon updates will come the same time as Google's. Also the only are like 3 apps from Verizon, and they are uninstallable.
Sent from my Pixel XL using Tapatalk
I pre-ordered from Google, got 5 WEEK wait notice 2 weeks after ordering so, I cancelled the order. I went to a Verizon store picked up a pixel XL, while walking out the store uninstalled anything with verizon and put my AT&T Sim card in. Simple as that, No "Unlocking", No regrets.
evoschecter said:
I pre-ordered from Google, got 5 WEEK wait notice 2 weeks after ordering so, I cancelled the order. I went to a Verizon store picked up a pixel XL, while walking out the store uninstalled anything with verizon and put my AT&T Sim card in. Simple as that, No "Unlocking", No regrets.
Click to expand...
Click to collapse
Did you get the latest update? I'm on AT&T also and did not get the OTA, so I side loaded it.
Sent from my Pixel XL using XDA-Developers mobile app
The VZW bootloader can only be unlocked via depixel8 once that is done you can flash the Google factory image, which will also flash the Google bootloader, this way all your updates come from Google vs VZW. But hurry this will be patched in November security patch which is nov 7th.
Has anyone actually been successful in flashing the factory image? I was reading the unlock thread earlier and people were saying the flash was failing
Sent from my Pixel XL using Tapatalk
DualSportDad said:
Has anyone actually been successful in flashing the factory image? I was reading the unlock thread earlier and people were saying the flash was failing
Click to expand...
Click to collapse
Yes I flashed every image available. And the failures were due to having the wrong drivers. Including myself having the wrong drivers
treIII said:
Yes I flashed every image available. And the failures were due to having the wrong drivers. Including myself having the wrong drivers
Click to expand...
Click to collapse
Did you flash them 1 by 1 or use the flash all.bat? I looked inside the image zip folder and my god, there are a lot of files in there. I'm used to the Nexus which has the boot.img, system.img, userdata.img, recovery.img and cache.img. The Pixel folder has 19 IMG. Files.
Sent from my Pixel XL using XDA-Developers mobile app
jaxenroth said:
The VZW bootloader can only be unlocked via depixel8 once that is done you can flash the Google factory image, which will also flash the Google bootloader, this way all your updates come from Google vs VZW. But hurry this will be patched in November security patch which is nov 7th.
Click to expand...
Click to collapse
Apologizes, I'm new here. What is the benefit to flashing the factory image? Does the Google bootloader stay after going to the factory image or will you need to flash it again if i get an update from verizon?
DualSportDad said:
Has anyone actually been successful in flashing the factory image? I was reading the unlock thread earlier and people were saying the flash was failing
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Could you link to the unlock thread. Unable to find it.
treIII said:
Yes I flashed every image available. And the failures were due to having the wrong drivers. Including myself having the wrong drivers
Click to expand...
Click to collapse
What do you mean by drivers? Which drivers are required? I assume they're for the computer side and not on the phone?
Zeroflucks said:
Apologizes, I'm new here. What is the benefit to flashing the factory image? Does the Google bootloader stay after going to the factory image or will you need to flash it again if i get an update from verizon?
Could you link to the unlock thread. Unable to find it.
What do you mean by drivers? Which drivers are required? I assume they're for the computer side and not on the phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3484497
If you flash the factory image with the bootloader then you won't have the Verizon locked bootloader. You can lock and unlock.
Sent from my Pixel XL using Tapatalk
DualSportDad said:
http://forum.xda-developers.com/showthread.php?t=3484497
If you flash the factory image with the bootloader then you won't have the Verizon locked bootloader. You can lock and unlock.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Has anyone confirmed this to actually work?
kest874 said:
Has anyone confirmed this to actually work?
Click to expand...
Click to collapse
No it is not confirmed to be true and I'm pretty sure no one has stated that in that thread. There are other things in play here such as the Cid.
Does it matter which factory image i try to flash to? NDE63N is currently on my phone. The ones listed on the site are NDE63H, NDE63L, NDE63P.
Zeroflucks said:
Does it matter which factory image i try to flash to? NDE63N is currently on my phone. The ones listed on the site are NDE63H, NDE63L, NDE63P.
Click to expand...
Click to collapse
P is the latest.
Mike02z said:
P is the latest.
Click to expand...
Click to collapse
Thank you
How do you know that its running the google version instead of the verizon version?
Sent from my iPad using Tapatalk
polo2883 said:
How do you know that its running the google version instead of the verizon version?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I just got my phone today so I assume that N is the verizon version since thats what was on my phone. Im now on P from the factory image on the google website.
Zeroflucks said:
I just got my phone today so I assume that N is the verizon version since thats what was on my phone. Im now on P from the factory image on the google website.
Click to expand...
Click to collapse
That's what I am on too. But the OEM unlocking is still not toggle-able in the developer section.
Sent from my iPad using Tapatalk
polo2883 said:
That's what I am on too. But the OEM unlocking is still not toggle-able in the developer section.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Same here but it does say that bootloader is already unlocked below it for me
NDE63P is the latest firmware, regardless of where the phone came from. I'm not sure where people are getting this "Google Firmware" thing from that is everywhere. There isn't any special firmware for any carrier or model.
Sent from my Pixel XL
Okay, as the title says I would like to know if you can use depixel8 to unlock the verizon pixel xl then fastboot flash the google play store version factory images. Essentially turning the Verizon version into a non-verizon version. From having shamu, which had different carrier images, I would say it is more than likely possible. But surprisingly I cannot find any threads confirming this after an hour of searching.
I just ordered the Verizon pixel xl 128gb today, taking advantage of the steep discount they are offering. I am taking the risk knowingly that it may be patched, but am hopeful I will still be able to use depixel8 once it arrives. From what I am seeing, it has not been patched yet. And as long as I don't accept an OTA before unlocking I should be fine either way. Super excited for it to arrive!
hlxanthus said:
Okay, as the title says I would like to know if you can use depixel8 to unlock the verizon pixel xl then fastboot flash the google play store version factory images. Essentially turning the Verizon version into a non-verizon version. From having shamu, which had different carrier images, I would say it is more than likely possible. But surprisingly I cannot find any threads confirming this after an hour of searching.
I just ordered the Verizon pixel xl 128gb today, taking advantage of the steep discount they are offering. I am taking the risk knowingly that it may be patched, but am hopeful I will still be able to use depixel8 once it arrives. From what I am seeing, it has not been patched yet. And as long as I don't accept an OTA before unlocking I should be fine either way. Super excited for it to arrive!
Click to expand...
Click to collapse
Yes, you can use depixel8 to unlock the bootloader. Yes, you can flash V instead of X via fastboot. However no one has yet been able to figure out your last, and most important part: how to turn a VZW device into a GS device. Go here for more information > http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-toggling-oem-unlock-t3498287
cam30era said:
Yes, you can use depixel8 to unlock the bootloader. Yes, you can flash V instead of X via fastboot. However no one has yet been able to figure out your last, and most important part: how to turn a VZW device into a GS device. Go here for more information > http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-toggling-oem-unlock-t3498287
Click to expand...
Click to collapse
Asked in another thread, but I'm wondering is it possible for VZ to relock the BL from a firmware update, or once it's unlocked they can't touch it?
theycallmerayj said:
Asked in another thread, but I'm wondering is it possible for VZ to relock the BL from a firmware update, or once it's unlocked they can't touch it?
Click to expand...
Click to collapse
I'll give you the same answer you're seen elsewhere: No one's ever seen this done before. And Google would have to do it (at VZW's request) since they push the updates.
I highly doubt it, but anything's possible I suppose.
Thanks!
theycallmerayj said:
Asked in another thread, but I'm wondering is it possible for VZ to relock the BL from a firmware update, or once it's unlocked they can't touch it?
Click to expand...
Click to collapse
cam30era said:
I'll give you the same answer you're seen elsewhere: No one's ever seen this done before. And Google would have to do it (at VZW's request) since they push the updates.
I highly doubt it, but anything's possible I suppose.
Click to expand...
Click to collapse
While theoretically possible, it is absolutely unprecedented.
Sent from my Nexus 6 using Tapatalk
I believe when you lock and/or unlock the bootloader in Android it completely wipes your device including internal storage. So relocking bootloader by force without your consent I could see leading to major backlash if that's always the case
Sent from my Pixel XL using Tapatalk
cam30era said:
Yes, you can use depixel8 to unlock the bootloader. Yes, you can flash V instead of X via fastboot. However no one has yet been able to figure out your last, and most important part: how to turn a VZW device into a GS device. Go here for more information > http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-toggling-oem-unlock-t3498287
Click to expand...
Click to collapse
It cant be done. The google version has different world wide bands. However for all intent and purposes the devices are identical and other than the bands (which I bet someone could unlock)!
hlxanthus said:
While theoretically possible, it is absolutely unprecedented.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
sfetaz said:
I believe when you lock and/or unlock the bootloader in Android it completely wipes your device including internal storage. So relocking bootloader by force without your consent I could see leading to major backlash if that's always the case
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Click to expand...
Click to collapse
They would risk bricking devices if they ever tried that. I have a strong feeling you will never see it happen.
I know this thread is old but I am just curious about this. Has anyone or does anyone know if you can flash any of the factory images that say Verizon or Telekom on them onto a Pixel XL you purchased from Google? There was an article that was published stating that the Verizon version got some extra changes to help fix things with the device.
Jammol said:
I know this thread is old but I am just curious about this. Has anyone or does anyone know if you can flash any of the factory images that say Verizon or Telekom on them onto a Pixel XL you purchased from Google? There was an article that was published stating that the Verizon version got some extra changes to help fix things with the device.
Click to expand...
Click to collapse
Hello...
In the 7.1.2 beta thread I've seen people with Google version using Verizon firmware. :good:
Cheers...
5.1 said:
Hello...
In the 7.1.2 beta thread I've seen people with Google version using Verizon firmware. :good:
Cheers...
Click to expand...
Click to collapse
Im have a verizon pixel and flashed the Deutsche Ota on accident.
No issues.
JustusIV said:
Im have a verizon pixel and flashed the Deutsche Ota on accident.
No issues.
Click to expand...
Click to collapse
You should have quoted @Jammol
He is the one looking for this..!
Thank you though...
Jammol said:
I know this thread is old but I am just curious about this. Has anyone or does anyone know if you can flash any of the factory images that say Verizon or Telekom on them onto a Pixel XL you purchased from Google? There was an article that was published stating that the Verizon version got some extra changes to help fix things with the device.
Click to expand...
Click to collapse
You can flash any version on any Pixel XL as long as it is unlocked. If version is specific for the Verizon version it will still work it just a few things specific to fixes for the Verizon network.
5.1 said:
You should have quoted @Jammol
He is the one looking for this..!
Thank you though...
Click to expand...
Click to collapse
Im new here
I kid i kid..
yep missed opportunity hehe
nrage23 said:
You can flash any version on any Pixel XL as long as it is unlocked. If version is specific for the Verizon version it will still work it just a few things specific to fixes for the Verizon network.
Click to expand...
Click to collapse
Exactly, i have an unlocked pixel i clean flashed to 7.1.2 and i got a server unreachable error more than once then the verizon update came out so i flashed they new radio to fix that and i got better reception as well because its optimized for their Network
I was on NOF27B (7.1.1) rooted with a full install of TWRP. I signed up for beta testing 7.1.2 and started to install NPG47I thinking that it wouldn't due to being rooted. Nope! Phone restarted into 7.1.2 and now my google store pixel is unrooted with the stock recovery. Is it safe to root again or am I stuck for a bit?
Not sure anyone knows as of yet, guess you just have to try and see if it works or not. Likely worst case is a reflash of 7.1.1 to regain root and TWRP.
Sent from my Pixel XL using Tapatalk
you should be able to root
chevelle970 said:
I was on NOF27B (7.1.1) rooted with a full install of TWRP. I signed up for beta testing 7.1.2 and started to install NPG47I thinking that it wouldn't due to being rooted. Nope! Phone restarted into 7.1.2 and now my google store pixel is unrooted with the stock recovery. Is it safe to root again or am I stuck for a bit?
Click to expand...
Click to collapse
Your​ bootloader is unlocked you will be able to root the same as before. Boot into TWRP using fastboot and flash SU
Any idea as to why it even let me download and install the OTA while I was rooted? I didn't think that would be possible.
I just used a guy named Jovan Brown for rooting services.
I don't know if he has a website.. did a great job of rooting and unlocking my pixel xl, remotely.
It took him quite a while.. totally worth paying him.
He had rooted my note 4 in the past.. very nice guy.
If any of you are interested in using him for rooting, message me and I will give you his email.
If this post is not allowed by xda policy, please let me know and I will delete it.
chevelle970 said:
I was on NOF27B (7.1.1) rooted with a full install of TWRP. I signed up for beta testing 7.1.2 and started to install NPG47I thinking that it wouldn't due to being rooted. Nope! Phone restarted into 7.1.2 and now my google store pixel is unrooted with the stock recovery. Is it safe to root again or am I stuck for a bit?
Click to expand...
Click to collapse
Every time you update stock you will have to reroot. I was also able to update with the ota while rooted but was unable when the second beta dropped. I manually installed and am still rooted with twrp same as 7.1.1. Android O however is a totally different can of worms which you will not be able to root...yet
kka111 said:
I just used a guy named Jovan Brown for rooting services.
I don't know if he has a website.. did a great job of rooting and unlocking my pixel xl, remotely.
It took him quite a while.. totally worth paying him.
He had rooted my note 4 in the past.. very nice guy.
If any of you are interested in using him for rooting, message me and I will give you his email.
If this post is not allowed by xda policy, please let me know and I will delete it.
Click to expand...
Click to collapse
lol wut
people pay for rooting services?
flex360 said:
lol wut
people pay for rooting services?
Click to expand...
Click to collapse
**** I'll help someone for money haha. Crazy how trusting people are..
c7j8d9 said:
Every time you update stock you will have to reroot. I was also able to update with the ota while rooted but was unable when the second beta dropped. I manually installed and am still rooted with twrp same as 7.1.1. Android O however is a totally different can of worms which you will not be able to root...yet
Click to expand...
Click to collapse
Rooted 7.1.2 just fine with TWRP.
never lost root or twrp with my upgrade
kka111 said:
I just used a guy named Jovan Brown for rooting services.
I don't know if he has a website.. did a great job of rooting and unlocking my pixel xl, remotely.
It took him quite a while.. totally worth paying him.
He had rooted my note 4 in the past.. very nice guy.
If any of you are interested in using him for rooting, message me and I will give you his email.
If this post is not allowed by xda policy, please let me know and I will delete it.
Click to expand...
Click to collapse
You got ripped off.
kka111 said:
I just used a guy named Jovan Brown for rooting services.
I don't know if he has a website.. did a great job of rooting and unlocking my pixel xl, remotely.
It took him quite a while.. totally worth paying him.
He had rooted my note 4 in the past.. very nice guy.
If any of you are interested in using him for rooting, message me and I will give you his email.
If this post is not allowed by xda policy, please let me know and I will delete it.
Click to expand...
Click to collapse
Why would you pay somebody to remotely access your phone first off right there shows you're not the brightest bulb in the pack is going to let somebody remotely access your **** and second it took him a while to do it why when all you have to do is plug into your computer and literally two minutes later you're unlocked I guess to each their own and if you want to be that naive please by all means let me help you out I'll be more than glad to remotely connect to your ****
Does it matter what version of TWRP or SuperSU I use to root 7.1.2?
Because it did not work when I did the following:
fastboot booted twrp-3.0.2-0-RC1-fastboot-marlin.img
then installed twrp-pixel-installer-marlin-3.1.0-0RC2.zip
then installed SuperSU 2.79.zip
What am I doing wrong?
EDIT: apparently nothing... it worked the second time around
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
ClassickWORLD said:
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
Click to expand...
Click to collapse
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Badger50 said:
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Click to expand...
Click to collapse
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
While I haven't done it personally, I've seen several people do just that from stock recovery. At worst, the install will fail and nothing will be changed. Unlocking the bootloader is mainly for flashing factory images and rooting, not OTA's. Just follow the instructions from Google and see what happens. In your current situation, you really have nothing to lose.
https://developers.google.com/android/ota
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??????
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
You do want the February one. It's for all phones including Verizon.
Badger50 said:
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
Click to expand...
Click to collapse
So I can flash that with no radio issues? I thought OPM1 is google, OPM2 is Telus only, and OPD3 is Verizon only? I have a Verizon P2XL
Edit: I think I've found my issue. The person who had the device before me must have sideloaded 8.1.0 (OPM1.171019.018, Feb 2018)" to this device and that may be the reason for the error. I am thinking because that's not the Verizon P2XL firmware but the Google P2XL device firmware.
michaelbsheldon said:
You do want the February one. It's for all phones including Verizon.
Click to expand...
Click to collapse
Ok gotcha. Downloading now as we speak.
Badger50 said:
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??
Click to expand...
Click to collapse
Lol I still have my trusty ol' Nexus 6P as my secondary device.
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
ClassickWORLD said:
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
Click to expand...
Click to collapse
Fixed and you're a happy camper, right?
P.S. try a factory reset to complete this
You guys are great. The sideload fixed the problem! I truly appreciate you guys. Thanks a lot.
ClassickWORLD said:
Lol I still have my trusty ol' Nexus 6P as my secondary device.
Click to expand...
Click to collapse
Ok bruh, your forgiven :laugh: Did you get your problem fixed?
Oooops....never mind. I see that you did :good:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
tradermatt said:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
Click to expand...
Click to collapse
There is no method to unlock the Verizon P2XL!!
Is there a root, ideally a one-click type, for the Pixel 2 XL running Android 10? I'm on Verizon if that matters. Not looking to ROM, just want root for access to certain apps.
Sent from my Pixel 2 XL using Tapatalk
Big Ry said:
Is there a root, ideally a one-click type, for the Pixel 2 XL running Android 10? I'm on Verizon if that matters. Not looking to ROM, just want root for access to certain apps.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Magisk
https://github.com/topjohnwu/Magisk/releases
Read the info under Useful Links before proceeding... https://github.com/topjohnwu/Magisk
For the Pixel 2 XL you can flash it in TWRP
Lughnasadh said:
Magisk
https://github.com/topjohnwu/Magisk/releases
Read the info under Useful Links before proceeding... https://github.com/topjohnwu/Magisk
For the Pixel 2 XL you can flash it in TWRP
Click to expand...
Click to collapse
The readme stops at Android 9.0 for listed supported versions...
Sent from my Pixel 2 XL using Tapatalk
Big Ry said:
The readme stops at Android 9.0 for listed supported versions...
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
The latest stable version, 20.4, works fine on Android 10
Lughnasadh said:
The latest stable version, 20.4, works fine on Android 10
Click to expand...
Click to collapse
But is it intended for Android 10? I really don't want to risk bricking my device.
Sent from my Pixel 2 XL using Tapatalk
Big Ry said:
But is it intended for Android 10? I really don't want to risk bricking my device.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yes
https://github.com/topjohnwu/magisk_files/blob/2d7ddefbe4946806de1875a18247b724f5e7d4a0/notes.md
Lughnasadh said:
Yes
https://github.com/topjohnwu/magisk_files/blob/2d7ddefbe4946806de1875a18247b724f5e7d4a0/notes.md
Click to expand...
Click to collapse
Ah so i guess they just forgot to update the readme.
Man this has gotten so much more complicated since the last time i rooted a device (probably my Galaxy Nexus). I'm very much a novice, so a lot of this terminology is like a foreign language. I've flashed TWRP a long long time ago, so i recognize the name but that's about it lol
Do you know if the Pixel 2 XL has A-only system as root? Is there a list of devices somewhere?
Sent from my Pixel 2 XL using Tapatalk
Big Ry said:
Ah so i guess they just forgot to update the readme.
Man this has gotten so much more complicated since the last time i rooted a device (probably my Galaxy Nexus). I'm very much a novice, so a lot of this terminology is like a foreign language. I've flashed TWRP a long long time ago, so i recognize the name but that's about it lol
Do you know if the Pixel 2 XL has A-only system as root? Is there a list of devices somewhere?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's A/B. I would suggest you read these guides and maybe go through some threads to familiarize yourself with this device.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://forum.xda-developers.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330
Lughnasadh said:
It's A/B. I would suggest you read these guides and maybe go through some threads to familiarize yourself with this device.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://forum.xda-developers.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330
Click to expand...
Click to collapse
I don't like the sound of that. Is this going to be a real pita?
Sent from my Pixel 2 XL using Tapatalk
Big Ry said:
I don't like the sound of that. Is this going to be a real pita?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
No, it's easy. Just fastboot the TWRP image and flash the TWRP installer zip in TWRP (optional) and then flash the Magisk zip in TWRP. There are other ways but that's the easiest, imo.
Lughnasadh said:
No, it's easy. Just fastboot the TWRP image and flash the TWRP installer zip in TWRP (optional) and then flash the Magisk zip in TWRP. There are other ways but that's the easiest, imo.
Click to expand...
Click to collapse
I assume this still wipes data? Does it affect Google's incremental updates?
Sent from my Pixel 2 XL using Tapatalk
Big Ry said:
I assume this still wipes data? Does it affect Google's incremental updates?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
No, rooting does not wipe data. You can still take OTA updates but there are varying methods to do it with Magisk and TWRP installed. I suggest you read through the threads of the links I gave you so you can learn more about this phone and how to do things.
Also read through this... https://github.com/topjohnwu/Magisk
And this... https://forum.xda-developers.com/showpost.php?p=79456255&postcount=3100
Lughnasadh said:
No, rooting does not wipe data. You can still take OTA updates but there are varying methods to do it with Magisk and TWRP installed. I suggest you read through the threads of the links I gave you so you can learn more about this phone and how to do things.
Also read through this... https://github.com/topjohnwu/Magisk
And this... https://forum.xda-developers.com/showpost.php?p=79456255&postcount=3100
Click to expand...
Click to collapse
Yeah that's gonna take me a bit to get my head around. Kinda surprised you don't need to wipe to root. That always used to be the case. It annoyed the **** outta me actually. Honestly, i probably should wipe anyway. I've never factory restored this phone since the day i bought it on November 1st, 2017 lol. Kinda hard to believe it still runs so well. Blows any other phone I've ever owned out of the water.
Sent from my Pixel 2 XL using Tapatalk
I finally looked into doing this again, and I determined its not possible. I was following the official XDA tutorial on rooting the Pixel 2 XL using fastboot, but "OEM Unlocking" cannot be toggled on Verizon phones. This makes it impossible to root them apparently. **** Verizon, seriously.
yes, seriously. well, i hope someone grabs this and tells us it CAN be done . . .
kdavidb said:
yes, seriously. well, i hope someone grabs this and tells us it CAN be done . . .
Click to expand...
Click to collapse
We need to get some insiders to leak the necessary code for unlocking these things
Sent from my Pixel 2 XL using Tapatalk
OP said Verizon version! No root....never...period.
If you want to root a pixel 2xl you HAVE TO HAVE THE GOOGLE STORE PHONE.
If the phone was sold thru Verizon or another retailer root is probably never going to happen. The phone is getting old and less likely to see much more development (especially a Verizon pixel).
Quit wasting time and buy the right pixel so you can have root.
bigmatt503 said:
If you want to root a pixel 2xl you HAVE TO HAVE THE GOOGLE STORE PHONE.
If the phone was sold thru Verizon or another retailer root is probably never going to happen. The phone is getting old and less likely to see much more development (especially a Verizon pixel).
Quit wasting time and buy the right pixel so you can have root.
Click to expand...
Click to collapse
I bought my phone directly from Google and it's still locked down
Sent from my Pixel 2 XL using Tapatalk
Big Ry said:
I bought my phone directly from Google and it's still locked down
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
If you bought it from Google you should be able to unlock the bootloader. Is the OEM unlocking toggle grayed out and disabled in Developer Options?