Related
Hey All!
I finally got T-Mobile to do a full carrier unlock on my device. It is not paid off, it is just 2 days out of the box. There is a long story that goes with it, which I'd be happy to provide. I do want some help though before I go through it, if you would please assist.
Before they unlocked the device; I had installed TWRP, custom kernel, and AllianceROM. Fortunately, I backed up my original stock ROM with Ktoonz kernel before flashing Alliance. The T-Mobile Unlock app does not work on AllianceROM for probably obvious reasons. ANYWHO...I flashed back to my backup, ran the unlock with them over the phone and done.
Am I safe to flash back to AllianceROM backup I made? My understanding is once unlocked, forever unlocked. I would hate to flash into my previous backup to only lose my carrier perma unlock.
Thanks for the help!!!!
Once its unlocked, it's unlocked. It makes no difference what Rom you install afterwards.
tehpud said:
Hey All!
I finally got T-Mobile to do a full carrier unlock on my device. It is not paid off, it is just 2 days out of the box. There is a long story that goes with it, which I'd be happy to provide. I do want some help though before I go through it, if you would please assist.
Before they unlocked the device; I had installed TWRP, custom kernel, and AllianceROM. Fortunately, I backed up my original stock ROM with Ktoonz kernel before flashing Alliance. The T-Mobile Unlock app does not work on AllianceROM for probably obvious reasons. ANYWHO...I flashed back to my backup, ran the unlock with them over the phone and done.
Am I safe to flash back to AllianceROM backup I made? My understanding is once unlocked, forever unlocked. I would hate to flash into my previous backup to only lose my carrier perma unlock.
Thanks for the help!!!!
Click to expand...
Click to collapse
Pretty much the exact same thing with me 2 days out of the box and not paid off or even used on the network. I did wait to flash recovery and what not till it was unlocked once it is perm unlocked though you are good to go I have flashed numerous roms and flashed via odin, and even had to use smart switch recovery by serial and still unlocked.
NexVision said:
Pretty much the exact same thing with me 2 days out of the box and not paid off or even used on the network. I did wait to flash recovery and what not till it was unlocked once it is perm unlocked though you are good to go I have flashed numerous roms and flashed via odin, and even had to use smart switch recovery by serial and still unlocked.
Click to expand...
Click to collapse
Thanks!
I went ahead and did a full back up of my unlock. Went ahead and flashed the ROM fresh over, not the backup, and reflashed the kernel. Still unlocked and good to go. Did it all through TWRP and no problems. Glad it didn't remove the unlock because I can't imagine continuing the battle! At least it is working perfectly with AT&T and has a full carrier perma unlock, rootable and bootloader unlock
tehpud said:
Hey All!
I finally got T-Mobile to do a full carrier unlock on my device. It is not paid off, it is just 2 days out of the box. There is a long story that goes with it, which I'd be happy to provide. I do want some help though before I go through it, if you would please assist.
Before they unlocked the device; I had installed TWRP, custom kernel, and AllianceROM. Fortunately, I backed up my original stock ROM with Ktoonz kernel before flashing Alliance. The T-Mobile Unlock app does not work on AllianceROM for probably obvious reasons. ANYWHO...I flashed back to my backup, ran the unlock with them over the phone and done.
Am I safe to flash back to AllianceROM backup I made? My understanding is once unlocked, forever unlocked. I would hate to flash into my previous backup to only lose my carrier perma unlock.
Thanks for the help!!!!
Click to expand...
Click to collapse
please help!! i unlocked my phone permanently! however i reflash the software with smart switch and then the unlock app came back and then i tried to unlock it again it fails to unlock it!! please help!!
It makes no difference what Rom you install afterwards.
kdan8888 said:
please help!! i unlocked my phone permanently! however i reflash the software with smart switch and then the unlock app came back and then i tried to unlock it again it fails to unlock it!! please help!!
Click to expand...
Click to collapse
Then you were not fully unlocked. You need to flash back to stock and call T-Mobile. Unlock app does come back after restore but it does not relock the device. It may say failed if you try to use it again as it is no longer in there system but unlock will stay.
NexVision said:
Then you were not fully unlocked. You need to flash back to stock and call T-Mobile. Unlock app does come back after restore but it does not relock the device. It may say failed if you try to use it again as it is no longer in there system but unlock will stay.
Click to expand...
Click to collapse
you were right!! it said failed but it is still unlocked!!! thanks for reply!
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Fastboot flashing lock? Or oem lock?
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
Fastboot flashing lock? Or oem lock?
Click to expand...
Click to collapse
It's that simple? Just run the fast lock command?
shibbnasty said:
It's that simple? Just run the fast lock command?
Click to expand...
Click to collapse
I think lol it's been awhile since I locked a phone
Sent from my Pixel XL using Tapatalk
oneandroidnut said:
I think lol it's been awhile since I locked a phone
Click to expand...
Click to collapse
I guess I should have mentioned as well it's a Verizon pixel xl and I had to use depixel8 to unlock it
shibbnasty said:
OK so I am going to have to return my pixel xl for a factory refurbished due to hardware issues with the camera flash. How do I relock the bootloader before taking it back?
Click to expand...
Click to collapse
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
lyall29 said:
You better be absolutely sure that your device is completely stock before relocking the bootloader. Once you are sure, boot into the bootloader and type, fastboot OEM lock
Click to expand...
Click to collapse
All I have done is unlock it. I have not flashed any kernels or mods or anything.
shibbnasty said:
All I have done is unlock it. I have not flashed any kernels or mods or anything.
Click to expand...
Click to collapse
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
lyall29 said:
Ok then. You should be fine. fastboot OEM lock will lock your bootloader and wipe your data at the same time.
Click to expand...
Click to collapse
Thank you very much!
@shibbnasty. Actually, relocking the bootloader may not wipe data. I can't remember. Let me know if it does or not.
Yes it does.
Rank N00b here... just getting that out of the way.
Device: Verizon Pixel XL
Build: NDE63X
Bootloader: unlocked via dePixel8 (done after Nov update)
So the phone is stock and I'm not really keen on modding right now. I don't want to use a alpha build of TWRP and SuperSU seems to be in flux too. These aren't criticisms by the way; I realize this a very new handset and those kinds of tools take time to develop. Nothing happens overnight.
So, anyway, my phone is currently unlocked and I'm wondering if I'm not better off relocking it? As a stock unit, it should still get OTA's, right? Like I said, total n00b here...
@loaba,
There's absolutely no reason to relock your bootloader, unless you are annoyed by the Google bootloader unlock warning during boot, or if you are planning on returning it or selling it. Otherwise, leave it unlocked. Gives you much greater flexibility to recover if something goes wrong.
@cam30era,
Thanks for the reassurance.
loaba said:
@cam30era,
Thanks for the reassurance.
Click to expand...
Click to collapse
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
michaelbsheldon said:
Also, Verizon may remove unlock ability via dePixel8 in their December update.
If that happens, you might have to wait awhile to get Unlock on a VZN Pixel again.
Click to expand...
Click to collapse
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
loaba said:
So if I want to maintain an unlocked device I need to act now... Guess I'll see which comes first - the possibly debilitating Dec update or a stable TWRP build (and a correspondingly stable custom ROM).
Click to expand...
Click to collapse
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
michaelbsheldon said:
Yep, do nothing and stay unlocked. You will still receive VZN OTA's and stay up to date as long as you do not install a custom recovery or kernel.
AND since you've remained unlocked, when the time comes that you do want a custom kernel or recovery, you can get them.
If it gets messed up somehow, you can do a clean RUU install as if nothing happened. If it's locked, you can't do that as easily.
Click to expand...
Click to collapse
About the OTA's - that was my big concern for now. Cool.
OP - thread derailed... sorry, man.
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Khanusma said:
You cannot use Android pay on an unlocked phone. Unless there is a workaround.
Click to expand...
Click to collapse
Most of the custom kernels fix that. Root is the hard one to hide.
Just got my pixel xl today, unlocked immediately. Question is if i update the bootloader from the factory images, am i going to lose my unlock or will this stick until i manually lock it (which i won't )? Thanks!
It will stick, no problem. Update away.
So just to clairfy because i'm paranoid about these things, I can run the flash-all script for the Feb update and my bootloader will remain unlocked correct?
danielson2047 said:
So just to clairfy because i'm paranoid about these things, I can run the flash-all script for the Feb update and my bootloader will remain unlocked correct?
Click to expand...
Click to collapse
Correct. Your bootloader will remain unlocked, unless you execute the following command: fastboot oem lock
With the Verizon bootloader, I used Depixel8 how do I work with the boot slots? I have been modifying since the LG ally but the table has changed and I don't want to end with a brick. Could I flash the bootloader to two slots?
Safest thing to do is to dePixel8 right off the bat, and then take an OTA before you do anything else. The OTA installs on the other slot, guaranteeing that you have a bootloader on both slots before you start monkeying around.
JU57US said:
Safest thing to do is to dePixel8 right off the bat, and then take an OTA before you do anything else. The OTA installs on the other slot, guaranteeing that you have a bootloader on both slots before you start monkeying around.
Click to expand...
Click to collapse
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?
palvarez05 said:
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?
Click to expand...
Click to collapse
No, unfortunately not.
I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.
Falargi said:
I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.
Click to expand...
Click to collapse
No it wont relock at all. ONly way for it to relock is to run the command for lock through download mode.
Falargi said:
I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.
Click to expand...
Click to collapse
Follow this guide, it's in the guides section
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
The only way to relock your bootloader is if you type "fastboot flashing OEM lock" once you have unlocked it, never never never relock it (VZW models only) only lock it if you need to do a RMA. Once unlocked you can flash whatever factory image your heart desires.
palvarez05 said:
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?
Click to expand...
Click to collapse
Are you positive that it had had to build out of the box? Or did it simply get upgraded before you checked? Either way you cannot now unlock the bootloader, but it is worthwhile to note whether or not Verizon is updating the phones before boxing them and shipping them. Check the side of your box your phone came in, to see the original build number that the phone had on it when it was boxed up.
I have my Verizon pixel xl unlocked with the sunshine mod from when I first got it. Can I relock the bootloader without the oem unlock setting being greyed out so I can unlock it in the future?
According to jcase, no.
http://theroot.ninja/depixel8.html said:
DO NOT RELOCK YOUR BOOTLOADER, unless you have restored it back to 100% stock and are sure you won't want it unlocked again.
Click to expand...
Click to collapse
Why do you want to relock it anyways?
fiveighteen said:
According to jcase, no.
Why do you want to relock it anyways?
Click to expand...
Click to collapse
While jcase was against it, after I have done my research, I attempted relocking my Verizon bootloader so I could send it out for RMA. I did it after I flashed the original factory image and made sure everything is back to OEM. So, I can tell you that it is possible. However, PLEASE don't take my words for it. Do your research and be 110% sure before you proceed. My heart was pounding so hard when I was trying to relock it because of the uncertainty... Anyway, do it at your own risk, I am just sharing you my experience, but please don't blame me if things go south
andrep182 said:
While jcase was against it, after I have done my research, I attempted relocking my Verizon bootloader so I could send it out for RMA. I did it after I flashed the original factory image and made sure everything is back to OEM. So, I can tell you that it is possible. However, PLEASE don't take my words for it. Do your research and be 110% sure before you proceed. My heart was pounding so hard when I was trying to relock it because of the uncertainty... Anyway, do it at your own risk, I am just sharing you my experience, but please don't blame me if things go south
Click to expand...
Click to collapse
Did you hit the slider too?
Were you able to unlock it again...if you tried?
Just curious and gathering info.....
TonikJDK said:
Did you hit the slider too?
Were you able to unlock it again...if you tried?
Just curious and gathering info.....
Click to expand...
Click to collapse
If by slider, you meant to ask if I locked it again, yes I did. I believe I relock it through fastboot.
There was really no point for me to unlock it again because I needed to send it for RMA so I never tried.
TonikJDK said:
Did you hit the slider too?
Were you able to unlock it again...if you tried?
Just curious and gathering info.....
Click to expand...
Click to collapse
If you unlock it and your already updated you won't be able to unlock again.
Haven't personally tried but I would be willing to bet a large sum of money if you relock it you will not be able to unlock it again I wouldn't even take the risk.
znel52 said:
Haven't personally tried but I would be willing to bet a large sum of money if you relock it you will not be able to unlock it again I wouldn't even take the risk.
Click to expand...
Click to collapse
I made the mistake of relocking and taking new updates. For sure, the unlock option was removed:
in first step of unlocking phone, the slider in Dev Options was forever greyed out. And it did not understand
fastboot unlock commands again. I would not recommend relocking Pixels for any reason other than return for
warranty repair.
michaelbsheldon said:
I made the mistake of relocking and taking new updates. For sure, the unlock option was removed:
in first step of unlocking phone, the slider in Dev Options was forever greyed out. And it did not understand
fastboot unlock commands again. I would not recommend relocking Pixels for any reason other than return for
warranty repair.
Click to expand...
Click to collapse
Locking on anything stock past 7.1 without root, would prohibit you from unlocking. If locking your BL + and no root capability = NO ability to unlock BL Thus what we have have So far, no known exploits...at least by me.
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I do have a computer, a Windows 10 Pro
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
sliding_billy said:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
Click to expand...
Click to collapse
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
coolhandz said:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
Click to expand...
Click to collapse
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
sliding_billy said:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
Click to expand...
Click to collapse
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
sliding_billy said:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
Click to expand...
Click to collapse
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.
eec007 said:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Click to expand...
Click to collapse
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
bobby janow said:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
Click to expand...
Click to collapse
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
eec007 said:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
Click to expand...
Click to collapse
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.
eec007 said:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
Click to expand...
Click to collapse
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
eec007 said:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Click to expand...
Click to collapse
They're right to mention that relocking a modified device can result in a brick.
Your best bet is to go to https://developers.google.com/android/images#taimen
Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.
Would suggest to do this anyway, no matter future unlock status.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...
Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said.
turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.