Database Users

Fastboot oem unlock/ fastboot oem lock please read!

I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
1. Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
2. Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.
All this info is all ready on the forums in various threads already but I wanted to put in one place since I noticed quite a few users botch up the devices trying to update to 3.1 The last thing we need are a bunch of people bricking the devices and sending them in moto. I suspect if enough people do it they will end up changing their minds on the entire encrypted bootloader situation.

I know you have to unlock to flash "non-stock" images, but do you have to unlock if you are only going to flash the "stock" motodev images?

If I am currently just unlocked, not rooted do I need to lock in order to get the 3.1 update?

ccogan said:
If I am currently just unlocked, not rooted do I need to lock in order to get the 3.1 update?
Click to expand...
Click to collapse
NO. the update only checks for stock files, not lock or unlock.
Blaisun said:
I know you have to unlock to flash "non-stock" images, but do you have to unlock if you are only going to flash the "stock" motodev images?
Click to expand...
Click to collapse
before you can flash anything you will need to unlock the bootloader.

how to lock the bootloader????

albundy2010 said:
I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
1. Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
2. Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.
All this info is all ready on the forums in various threads already but I wanted to put in one place since I noticed quite a few users botch up the devices trying to update to 3.1 The last thing we need are a bunch of people bricking the devices and sending them in moto. I suspect if enough people do it they will end up changing their minds on the entire encrypted bootloader situation.
Click to expand...
Click to collapse
Question for you, how do I go about entering this command? My knowledge is basic. I have unrooted, restocked a Nexus 7. Trying to do oem lock without being able to use the screen. Cannot enable USB debugging because the screen is nonoperational. Any advice?

Root N4. (Little Scared)

Alright guys. I have been doing a lot of reading as of late about rooting my wonderful N4. Its prob the best phone I have ever had.
Reason I am scared is I am a little confused on the whole unlock bootloader and what not.
I had a S2 which was easy to root plug in Odin and away we went. I was hoping this would be much the same. I read the guide you have up and its very helpful. My problem is I am new to it really.
The reason I want to root is I want to try the custom ROM PIE as it looks sexy. So any good tips on the rooting process. How safe is rooting.
Sent From The Future.

Download the toolkit for the mako aka nexus 4.
http://forum.xda-developers.com/showthread.php?t=1995688
Watch the video first, install the drivers, and then follow the instructions in the video/thread. It can't get as easy as the dev who created the toolkit.
Don't a pansy about rooting, be confident; You're not going to break it. Soft-Brick maybe, but one can easily fix that.

ismethajametovic said:
Download the toolkit for the mako aka nexus 4.
http://forum.xda-developers.com/showthread.php?t=1995688
Watch the video first, install the drivers, and then follow the instructions in the video/thread. It can't get as easy as the dev who created the toolkit.
Don't a pansy about rooting, be confident; You're not going to break it. Soft-Brick maybe, but one can easily fix that.
Click to expand...
Click to collapse
Thank you dude. I'll look into it. I shall man up. Have you used pie custom ROM.
Sent From The Future.

Do. Not. Use. Toolkits.
Go through http://forum.xda-developers.com/showthread.php?t=2010312. All of it. Learn something that you can always use.
(click on the thanks button instead of saying thanks. People luv that in here. You will too, eventually. )

What the difference between what you posted and tool kits.
Sent From The Future.

JknRich said:
What the difference between what you posted and tool kits.
Sent From The Future.
Click to expand...
Click to collapse
Learn how to use fastboot. Learn how to practically "hack" your phone so you can go back and correct things when they go wrong.
Toolkits are fine until you get stuck. But then you have no clue why & more importantly how to fix it.
Trust me, follow efrant's guide. :thumbup:
(you have to experience the joy of "fastboot oem unlock". That's why you got a nexus device mate!! )

Vangelis13 said:
Learn how to use fastboot. Learn how to practically "hack" your phone so you can go back and correct things when they go wrong.
Toolkits are fine until you get stuck. But then you have no clue why & more importantly how to fix it.
Trust me, follow efrant's guide. :thumbup:
(you have to experience the joy of "fastboot oem unlock". That's why you got a nexus device mate!! )
Click to expand...
Click to collapse
What is fastboot OEM unlock. Sounds like a STD Lol. I have to admit its the best android phone I have had.
So rooting is my next step. Feel like its a massive jump.
Sent From The Future.

JknRich said:
What the difference between what you posted and tool kits.
Sent From The Future.
Click to expand...
Click to collapse
difference is that you you dont learn anything from using a toolkit. so when it comes down to an easy fix for something, or some easy maintenance, you wont soft brick your device and wont start one of the "i bricked my device" threads. plus root toolkits can come with their own issues. it comes down to root toolkits are fine, if you already know what you are doing. but for someone new they should never be recommended. learning fastboot is easy, itll just take a little extra reading. in reality, using fastboot is faster then a root toolkit too, once you learn. this is all thats needed to do to unlock/root via fastboot.. type fastboot oem unlock, fastboot flash a custom recovery, flash either the su binaries or a custom rom in your new recovery, then reboot and profit.

lol I used toolkit and had no probs.
At least till I tried to reset it but then I learnt how to fastboot. So I'd recommend that you set up toolkit and fastboot. You might use the toolkit, but if you "break" something you can easily fix it with fastboot.
Sent from my Nexus 4 using xda app-developers app

simms22 said:
difference is that you you dont learn anything from using a toolkit. so when it comes down to an easy fix for something, or some easy maintenance, you wont soft brick your device and wont start one of the "i bricked my device" threads. plus root toolkits can come with their own issues. it comes down to root toolkits are fine, if you already know what you are doing. but for someone new they should never be recommended. learning fastboot is easy, itll just take a little extra reading. in reality, using fastboot is faster then a root toolkit too, once you learn. this is all thats needed to do to unlock/root via fastboot.. type fastboot oem unlock, fastboot flash a custom recovery, flash either the su binaries or a custom rom in your new recovery, then reboot and profit.
Click to expand...
Click to collapse
Ok I best get reading.
I have always loved playing about with my phone so a bit more reading won't hurt.
Has rooting your device benefited you.
Sent From The Future.

JknRich said:
Ok I best get reading.
I have always loved playing about with my phone so a bit more reading won't hurt.
Has rooting your device benefited you.
Sent From The Future.
Click to expand...
Click to collapse
it absolutely has, i have full control of my device.
the scariest things about rooting/modifying words used, the terminology. once you pass that stage, everything gets much easier.

I tried the fast boot way but could never get cmd to function. So I gave up because I couldn't find a solution anywhere. You guys just inspired me to try again. Gonna return my phone to stock and start over. Thank you.
Sent from my Nexus 4 using xda app-developers app

simms22 said:
difference is that you you dont learn anything from using a toolkit. so when it comes down to an easy fix for something, or some easy maintenance, you wont soft brick your device and wont start one of the "i bricked my device" threads. plus root toolkits can come with their own issues. it comes down to root toolkits are fine, if you already know what you are doing. but for someone new they should never be recommended. learning fastboot is easy, itll just take a little extra reading. in reality, using fastboot is faster then a root toolkit too, once you learn. this is all thats needed to do to unlock/root via fastboot.. type fastboot oem unlock, fastboot flash a custom recovery, flash either the su binaries or a custom rom in your new recovery, then reboot and profit.
Click to expand...
Click to collapse
Explained by a Meister.
---------- Post added at 12:59 AM ---------- Previous post was at 12:57 AM ----------
Jammol said:
I tried the fast boot way but could never get cmd to function. So I gave up because I couldn't find a solution anywhere. You guys just inspired me to try again. Gonna return my phone to stock and start over. Thank you.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Make sure you start in the same folder as your fastboot files. :thumbup:
Follow efrant's guide, it's gold.

i would avoid toolkits as you dont know what commands are being sent to your phone, im not saying they are not safe but you want to know what you are doing.i got stuck at selecting device version and build (step 1 lol) fast boot is easier.
i followed this link
http://forum.xda-developers.com/showthread.php?t=1993331
just learn about fast boot and cmd commands if you need to.
you gotta root at xda, underclocking and changing the dpi to make full use of the resolution, battery life increased having it maxed at a lower clock, i wouldn't of brought the nexus to stay on stock
i cant wait to travel next month with my phone, i remember my S2 could only last 1 day but this nexus is 3 times more efficient

ismethajametovic said:
Download the toolkit for the mako aka nexus 4.
http://forum.xda-developers.com/showthread.php?t=1995688
Watch the video first, install the drivers, and then follow the instructions in the video/thread. It can't get as easy as the dev who created the toolkit.
Don't a pansy about rooting, be confident; You're not going to break it. Soft-Brick maybe, but one can easily fix that.
Click to expand...
Click to collapse
This is such bad advice. How should he expect to be confident when he doesn't know what the toolkit is even doing?
Read up on how to use fastboot and ADB and do it manually, because if you just use the toolkit and something happens, how do you expect to fix it?

JknRich said:
What is fastboot OEM unlock. Sounds like a STD Lol. I have to admit its the best android phone I have had.
So rooting is my next step. Feel like its a massive jump.
Sent From The Future.
Click to expand...
Click to collapse
You see!? You have a Nexus, marvel of technology, and you don't know the mother of all fastboot commands..!!
I hope you are reading that guide I linked you up with already..

joshnichols189 said:
This is such bad advice. How should he expect to be confident when he doesn't know what the toolkit is even doing?
Read up on how to use fastboot and ADB and do it manually, because if you just use the toolkit and something happens, how do you expect to fix it?
Click to expand...
Click to collapse
QFT

estallings15 said:
QFT
Click to expand...
Click to collapse
Quite Fckng True..?

"fastboot oem unlock" was a gift from google to the moding community. it gave us the choice of unlocking our bootloaders without any potentially dangerous hacking. its a simple three word line that you type into the command window(fastboot) which then prompts us on the device with a simple yes/no question.. do you want to unlock tge bootloader. it started on the nexus one and continues with every nexus that followed. this separates nexus devices from all others.

simms22 said:
"fastboot oem unlock" was a gift from google to the moding community. it gave us the choice of unlocking our bootloaders without any potentially dangerous hacking. its a simple three word line that you type into the command window(fastboot) which then prompts us on the device with a simple yes/no question.. do you want to unlock tge bootloader. it started on the nexus one and continues with every nexus that followed. this separates nexus devices from all others.
Click to expand...
Click to collapse
You're taking away the magic. He was meant to be awed when he came to that point in efrant's guide. Ts ts, Dr Dr.. :banghead:

Does unlocked BL automatically mean root is possible.

I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?

Bubba Fett said:
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Click to expand...
Click to collapse
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.

lightninbug said:
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
Click to expand...
Click to collapse
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.

Bubba Fett said:
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Click to expand...
Click to collapse
No.. thought I was getting it today via UPS... Guess I was tracking the wrong package lmao (stoner moment)... The G pad X came today instead... Lammmmme!!!

LG blocked fastboot commands since MM so the standard would usually be Unlock BL, flash recovery then flash SU.
But its not the case anymore.
Now its Unlock BL wait till an official.tot or .kdz to be released or leaked from LG, then repack it with root or a recovery and flash via LGUP or LG Tool.

just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.

Z51 said:
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Click to expand...
Click to collapse
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.

lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.

douger1957 said:
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
Click to expand...
Click to collapse
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!

Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
Amen to that lol! Do you know how long does it take to restore every single app when you dont have titanium backup installed and your device rooted? (i have 113 user apps in my lg g3), you can easily take up to 2 hours installing and setting up. while when you have titanium, you can sit there and drink up your coconut juice while it does everything on its own and everything already set up, and it is pretty quick too. Also, i hate ads. unless the benefit me (that's how i found out about the LG V20 lol) Not to mention that many of the ads out there are either scam or viruses . Also, rooting is the way to really owning your device. a device is not yours until whatever thing you want to do can actually be achieved because you (the owner) wanted to and not because the company wanted to. :good:

I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.

Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
Lol you might as well return it now then. Beucase i doubt it will be done that quick. I mean, i bought this phone because of its great features. And even though i like to root, flash, and all that, well, i have set up my mind in a balanced mode and said "well, chances to get root are 50%, sure i like to root my phone but probably it wont be possible ". To be honest i usually wait about 3 month before buying a new released smartphone because by around that time, they usually have root and have gotten bugs already fixed. But i couldnt resist the offers on this one LOL. so, if it doesnt get root, i will stuck with it for a while anyway.

Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
I'm in the exact same boat as you. My V20 is sitting all pretty on my desk. T-14 days before I return it if no root. Been rocking the OnePlus 3 with an awesome ROM since the first Note 7 recall. Absolutely loving it. Got the V20 only because of the screen, camera, and supposedly better sound--all of which are probably marginal upgrades compared to OP3 especially considering it's well over twice the price.

V521 didn't have root until update was released. I grabbed and uploaded the ROM, and soon rooted .dz was there.

Confirmed: Similar to T-Mobile LG G5 there are not flash commands in fastboot to write a new recovery. Will need someone to create a TOT file to get us TWRP and root I think.

confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
c:\adb>fastboot boot v20.img
downloading 'boot.img'...
OKAY [ 0.700s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.721s
Click to expand...
Click to collapse

lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Don't get your panties in a bunch. It was a simple question. I come on here to make money. I fix phones for a living and I come here to fix what people attempting to root broke and brought to me to fix. If you don't want to root, you don't have to. If you do, then by all means root your phone. No need to be a **** about it.
Sent from my SM-G928V using Tapatalk

Amd4life said:
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
Click to expand...
Click to collapse
Apparently LG disables boot/flash. I'm going to try to get a tmobile TOT file tomorrow. I'm working on updating a TOT extractor tool right now to work it.

Can someone run this:
Code:
fastboot getvar all

Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
I will most likely root my phone when the time comes. I am not against rooting at all... I rooted all of my phones except the Note 7. What I'm saying is that root isn't for everyone, not everyone should root their phone even if they think it's the thing to do and that I think there's a place at XDA for people who don't want to learn ADB commands.

Buying a brick nexus 6p

I may be buying a nexus 6p for 70 bucks. The buyer said this
"powered off during a software update and it is in a "bricked" status. Screen turns on and you can access bootloader etc."
Is it fixable to get back to working condition? I wanna make for sure be for I buy it.

germanguy45 said:
I may be buying a nexus 6p for 70 bucks. The buyer said this
"powered off during a software update and it is in a "bricked" status. Screen turns on and you can access bootloader etc."
Is it fixable to get back to working condition? I wanna make for sure be for I buy it.
Click to expand...
Click to collapse
Doesn't sound bricked to me. I'd buy it for 70 and take your time figuring out how to get it working again.

tropical cactus said:
Doesn't sound bricked to me. I'd buy it for 70 and take your time figuring out how to get it working again.
Click to expand...
Click to collapse
Will do then was just curious 70 bucks isnt a bad deal at all.

germanguy45 said:
Will do then was just curious 70 bucks isnt a bad deal at all.
Click to expand...
Click to collapse
My opinion I would ask the owner if the bootloader is unlocked. If the owner is smart enough to know that the bootloader can be accessed then he or she can also tell you if it's unlocked and whether you will have the capability to flash anything to it or not. If the phone is in the boot loop of death you will at least need an unlocked bootloader to flash a fix.
Sent from my Nexus 6P using Tapatalk

funnel71 said:
My opinion I would ask the owner if the bootloader is unlocked. If the owner is smart enough to know that the bootloader can be accessed then he or she can also tell you if it's unlocked and whether you will have the capability to flash anything to it or not. If the phone is in the boot loop of death you will at least need an unlocked bootloader to flash a fix.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ok will do thank you for the good tip.

germanguy45 said:
Ok will do thank you for the good tip.
Click to expand...
Click to collapse
Also being able to access Recovery would be a good sign. If you you cannot access Recovery mode you cannot use ADB and is a tell tale sign of the BLOD.

The phone doesn't sound bricked. Even if the bootloader is locked as long as you can access it you should be able to sideload an OTA update which might get the phone working again. I think if your adb and fastboot binaries are up to date you can even sideload the entire factory image instead of just an OTA.

Someone with an unlocked Google Store variant

Please dd and pm me your frp, ftm, and if you are willing to, factory reset and then enable oem unlock, and send your userdata partition, all with the oem unlock allowed.
Thanks!

bump?

What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.

wgrant said:
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
Click to expand...
Click to collapse
The request is probably for this thread. People are trying to use the recently rediscovered exploit to finally be able to bootloader unlock Verizon Pixel 2 XL phones.

wgrant said:
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
Click to expand...
Click to collapse
On the LG V40 if the frp partition from a phone with the OEM lock flag triggered is dd'd to another device, the bootloader will allow unlocking, additionally, the ftm partition on the v40 seems to carry the imei so I assume the same is true for the Pixel, I'd understand if you didnt want to share that partition but I think if the phones imei registers as a Google store one, that could help trick it into working.

Is there any way an exchange can be done here for the Verizon software that enables WiFi calling, volte, voicemail, and video calling? Is that Verizon software out there somewhere? If you guys are trying to root and unlock vzw phones you'll be wiping and starting with a fresh phone anyway. Is that a good time to extract these files and provide them?

I have a Verizon Pixel 2 XL on Android 9 [last security patch]. Bootloader unlocked :good:

IcyAgitator said:
I have a Verizon Pixel 2 XL on Android 9 [last security patch]. Bootloader unlocked :good:
Click to expand...
Click to collapse
Could you follow this guide: https://forum.xda-developers.com/showthread.php?t=2450045 to get frp and ftm partitions? Then PM them to @Whoareyou
Thanks again!

Unfortunately I already was able to get these from someone with a Google Store unlocked one, the dd'd partitions didnt stick through a reboot, and it wasnt able to oem unlock, ive been messing with the oemlock-bridge-client, so far chaning the device_lock status from 1 to 0 does nothing :/

shwise said:
Could you follow this guide: https://forum.xda-developers.com/showthread.php?t=2450045 to get frp and ftm partitions? Then PM them to @Whoareyou
Thanks again!
Click to expand...
Click to collapse
I updated to Android 10 Security Patch October 6 2019. But I will do what I can.

Whoareyou said:
Unfortunately I already was able to get these from someone with a Google Store unlocked one, the dd'd partitions didnt stick through a reboot, and it wasnt able to oem unlock, ive been messing with the oemlock-bridge-client, so far chaning the device_lock status from 1 to 0 does nothing :/
Click to expand...
Click to collapse
Could you try flashing those from temp root, hard powering off (holding button) and then booting to BL?

shwise said:
Could you try flashing those from temp root, hard powering off (holding button) and then booting to BL?
Click to expand...
Click to collapse
I'll try when I get home, but I don't know if it'll be any different than using the "reboot bootloader" command.

No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.

krolla03 said:
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
Click to expand...
Click to collapse
I expect to get two more years out of this phone.... It'd be nice to have root options.

krolla03 said:
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
Click to expand...
Click to collapse
It's 2 years old