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?
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 installed DP2 and then re locked my phone. I installed from the factory image posted today.
Now when I open up Android pay and try to add a card it's saying that it can't be used on my device and my device might be rooted or unlocked.
It's not.
Is anyone else seeing this?
Sent from my Pixel 2 XL using Tapatalk
Give it a day or two, they have to approve the new image in the system. It happened with some other updates too.
Just a minor point about the subject: it should be "since installing DP2" or "after DP2".
When I saw your heading initially I was confused because DP2 has been out for seemingly less than a day. So I thought you meant "since DP1" or something else.
OK, end of the grammar patrol.
pilotgav said:
I installed DP2 and then re locked my phone. I installed from the factory image posted today.
Now when I open up Android pay and try to add a card it's saying that it can't be used on my device and my device might be rooted or unlocked.
It's not.
Is anyone else seeing this?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
does not work for me either.
uicnren said:
does not work for me either.
Click to expand...
Click to collapse
OTA or flashed image?
Sent from my Pixel 2 XL using Tapatalk
This is an issue for everyone regardless of whether the update was received via OTA or flashing the factory image. Like Twitch175 said, it'll just take a few days to approve the new image and all should be good.
Meanwhile, there is an official Google Plus community for the Android Beta Program where lots of users are already discussing this issue, along with others.
Android Beta Program
It is working for me now, google must have fixed it.
Working now.. wasn't originally recognizing DP2 though
S0UTHPAWK1LLA said:
Working now.. wasn't originally recognizing DP2 though
Click to expand...
Click to collapse
Yaaaaay ?
pilotgav said:
OTA or flashed image?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
dirty flashed factory image. it is working for me now. Play store still says device is uncertified however.
So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk
Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk
applezen said:
Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
IDK much about computers much but I learn quick and understand well what I did was set the power-tools as path I didn't do fastboot but fastboot is in the power-tools folder so is this correct?
Sent from my Pixel 2 XL using Tapatalk
Install latest SDK and start the CMD from there
Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.
Ace0spades808 said:
Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.
Click to expand...
Click to collapse
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Click to expand...
Click to collapse
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh ???
Sounds like the same issue as here: https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187/page6 - that's post number 51.
The user resolved it by updating ADB/Fastboot.
Badger50 said:
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh [emoji108][emoji106][emoji41]
Click to expand...
Click to collapse
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Click to expand...
Click to collapse
Hell yeah!!! ???
non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Didn't mean to offend you or anything. I just wanted you to be aware that the developer preview isn't meant to be flashed because it is the "latest and greatest". If you want to try it out go for it but you could end up causing yourself more headache than it's worth (you could brick it or render your phone inoperable for days) since you yourself said you aren't sure what you are doing.
non_smoker0922 said:
So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.
uicnren said:
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.
Click to expand...
Click to collapse
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.
uicnren said:
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.
Click to expand...
Click to collapse
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Sent from my Pixel 2 XL using Tapatalk
non_smoker0922 said:
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Click to expand...
Click to collapse
Did you run both bootloader unlocking commands?
Badger50 said:
Did you run both bootloader unlocking commands?
Click to expand...
Click to collapse
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk
So the issue is that you can't get the phone unlocked? Do you still have the option to enable ""OEM Unlocking" in Developer Settings? If it is greyed out, you'll have to reset the phone. First backup and then perform "erase all data(factory reset) and then skip through all of the setup on the phone. Once you are in the phone, gain developer settings, enable "OEM Unlocking" and USB Debugging. You should then be able to unlock via fastboot.
non_smoker0922 said:
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Best I can suggest for you now, is to see HERE.
You can ignore the stuff about C:/D: drives.
Twice now you have used the term unlock_critical. Did you actually type in "fastboot flashing unlock_critical"?
Can someone with a Non-VZW P3XL who has unlocked the BL share the boot.img and Bootloader.img from build PD1A.180720.031 (Sept build - BL b1c1-0.1-4948814)? Still tinkering and have a few other "experiments" to test out.....
Sent from my Pixel 3 XL using Tapatalk
Aren't they in the factory images? https://dl.google.com/dl/android/aosp/crosshatch-pd1a.180720.030-factory-38b1b90a.zip
Yes, they are, but in the locked state. I need one after it has been unlocked for an experiment for the Verizon P3XL. That's why I requested if someone with a non-vzw could share.
Sent from my Pixel 3 XL using Tapatalk
Sorry for the confusion. Out of curiosity, if the bootloader is unlocked in order to flash the image, and flashing those in the factory image doesn't relock, how are they locked?
Not trolling, I am curious. I haven't rooted or unlocked since my Pixel 1.
No problem, you're not trolling. What prevents the VZW P3's from being unlocked is just a theory. My current idea may not even bear results, but until I prove otherwise I just need to try it and see........
Sent from my Pixel 3 XL using Tapatalk
FernBch said:
Can someone with a Non-VZW P3XL who has unlocked the BL share the boot.img and Bootloader.img from build PD1A.180720.031 (Sept build - BL b1c1-0.1-4948814)? Still tinkering and have a few other "experiments" to test out.....
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yeah I'm pretty sure there's a how to root method where the guy has a boot.img prepatched with magisk pretty sure unlocking the bootloader was step one. He's got 3 different months of boot.img posted one of the first threads that pop up when I come to the Pixel 3 XL forum... https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712
billyt1 said:
Yeah I'm pretty sure there's a how to root method where the guy has a boot.img prepatched with magisk pretty sure unlocking the bootloader was step one. He's got 3 different months of boot.img posted one of the first threads that pop up when I come to the Pixel 3 XL forum... https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712
Click to expand...
Click to collapse
Can't flash a modded boot.img on a locked device.....
Sent from my Pixel 3 XL using Tapatalk
Cant a patched boot. Img be put into an ota zip and flashed with adb in stock recovery with locked device?
hilla_killa said:
Cant a patched boot. Img be put into an ota zip and flashed with adb in stock recovery with locked device?
Click to expand...
Click to collapse
No, signature check will fail. The image needs to be resigned with their key. It has to do with AVB (android verified boot). I have a couple ideas but it's a long shot. I noticed when flashing a factory image it doesn't flash boot.a, locked BL.
Sent from my Pixel 3 XL using Tapatalk
Still in search of a bootloader.img and boot.img for a Non-Verizon unlocked P3XL for the Sept build (031) if anyone wants to share. I haven't updated yet, don't want to make it harder than it is....
[emoji16]
Sent from my Pixel 3 XL using Tapatalk
If I was still on Sept I'd just pull it with DD, but I'm not. I might roll back later to grab it for you but no promises [emoji16]
Sent from my Pixel 3 XL using Tapatalk
Not sure if you can rollback. I've been reading up on AVB, Titan security, etc. Rollback is one of the things the new security may prevent.
Sent from my Pixel 3 XL using Tapatalk
You can with an unlocked bootloader, that I know for sure.
Reading more on your post I don't think the unlocked flag is stored in the bootloader. Why else would it retain the unlocked status upon flashing a newer version? I'm pretty sure it is like older HTC devices where the "secure flag" is another partition that just holds a simple value telling the unlocked status.
FernBch said:
Not sure if you can rollback. I've been reading up on AVB, Titan security, etc. Rollback is one of the things the new security may prevent.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
Not sure what I can/can't do once unlocked. Just looking for a way in to the VZW P3XL and trying all I can think of. Hoping to "stumble" across something is all. That's the reason I'm asking for what I am.
Sent from my Pixel 3 XL using Tapatalk
FernBch said:
Not sure what I can/can't do once unlocked. Just looking for a way in to the VZW P3XL and trying all I can think of. Hoping to "stumble" across something is all. That's the reason I'm asking for what I am.
Click to expand...
Click to collapse
Is there a way to sign the modified boot image so it thinks its official? If you have a stock boot to just merge both together then package that into an update.zip.
Unless you can fool AVB probably not. The zip would need to be signed with the proper key.
Sent from my Pixel 3 XL using Tapatalk
FernBch said:
Not sure what I can/can't do once unlocked. Just looking for a way in to the VZW P3XL and trying all I can think of. Hoping to "stumble" across something is all. That's the reason I'm asking for what I am.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
As I said the unlock flag is likely stored elsewhere. The boot and bootloader images I'd pull for you would essentially be the factory ones except they would end up being the size of the whole partition. So you could just grab the factory image and extract it yourself.
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
As I said the unlock flag is likely stored elsewhere. The boot and bootloader images I'd pull for you would essentially be the factory ones except they would end up being the size of the whole partition. So you could just grab the factory image and extract it yourself.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm thinking you're right. I've done some digging and tinkering and am noticing some clues. I have an idea, just not sure if it will either work or if not how bad I will crash the system....
Pixel 3 XL, I haven't crashed it. YET....