Related
Hi guys. I want to remove this warning message when i boot up my phone. Can anyone help me? Thanks!
being able to do this would be great! I tried all the fastboot commands that work on different devices to re-lock the bootloader, flashed the bootloaders again...downgrade to Android 5, uncheck enable EOM unlock in the developer options..tried fastboot commands.. all was in vain...
Any other ideas?
rigocalin said:
being able to do this would be great! I tried all the fastboot commands that work on different devices to re-lock the bootloader, flashed the bootloaders again...downgrade to Android 5, uncheck enable EOM unlock in the developer options..tried fastboot commands.. all was in vain...
Any other ideas?
Click to expand...
Click to collapse
I don't want to relock my bootloader. My goal is just removing this message. Because if the bootloop issue happen to me, sellers will not know that i've unlocked my bootloader. So they will repair my phone for free.
please can any mod close this? Has already been asked and answered. it's not possible! Do a damn search before!
there is not mention of this as far as I sow it anyways...
If you have it then post the link here so we can see it also .
PS: under the same logic we would not try to find a root or bootloader unlock and talk about it because its not currently possible.
5nickers said:
please can any mod close this? Has already been asked and answered. it's not possible! Do a damn search before!
Click to expand...
Click to collapse
If your in the EU and phone is still under warranty, LG will repair defected devices regardless if BL is unlocked as its a known defect. Read this thread.
http://forum.xda-developers.com/g4/help/g4-bootloop-lg-officially-admits-t3301629
awes0me1 said:
If your in the EU and phone is still under warranty, LG will repair defected devices regardless if BL is unlocked as its a known defect. Read this thread.
http://forum.xda-developers.com/g4/help/g4-bootloop-lg-officially-admits-t3301629
Click to expand...
Click to collapse
I live in asia region. I talked with the seller where that i bought (third party shop) and they said that unlocking BL void warranty. That is why i want to hide this message
Then it's a no...you cannot remove message when booting.
awes0me1 said:
Then it's a no...you cannot remove message when booting.
Click to expand...
Click to collapse
There are marshmallow boot animation in forums for g4. But i am not sure if it can hide this message or not.
xdaorxan said:
There are marshmallow boot animation in forums for g4. But i am not sure if it can hide this message or not.
Click to expand...
Click to collapse
No, as the message appears before the bootanimation.
davebugyi said:
No, as the message appears before the bootanimation.
Click to expand...
Click to collapse
That's awful
I read about a guy saying something like changing the I-M-E-I (dont want to get banned or something) to something else, reboot and then restore it, you should have a relocked bootloader..
it sounds a bit shady but maybe this can actually work...depending on how this unlock is done.
https://www.youtube.com/watch?v=DZBFc2Da83E
This guy actually relocked the bootloader nice
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Edit:
Tried multiple unlock keys from HTC
Tried factory reset
Booting into recovery phone image comes up with red warning icon in it and nothing happens. Need to power down and restart. Seems the recovery partition is possibly hosed.
Dissectional said:
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Click to expand...
Click to collapse
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
SacredDeviL666 said:
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
Click to expand...
Click to collapse
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Dissectional said:
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Click to expand...
Click to collapse
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
afuller42 said:
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
Click to expand...
Click to collapse
You may be right about the fingerprint scanner. I will look into that when I get it unlocked. That is the main goal right now.
If you are s-OFF the phone will show as "s-off, locked" but still, in fact, be unlocked.
the command to lock and unlock will not work.
I was confused to but when i checked the s-off thread i saw that it will ask if it should be "s-off unlocked or "s-off locked" and recomended Locked, but had no difference other then visual.
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
And btw, lock status should not affect the fingerprint scanner.
Confirmed it doesn't I am s-0ff and unlocked, twrp and custom rom. Fingerprint working 100%
the exclamation on booting to recovery just indicates that you are on stock recovery...
try the steps here for recovery flashing... and unlocking again... if it might help... http://forum.xda-developers.com/showpost.php?p=66713447&postcount=1
You could try contacting Scotty, might have a way like on previous devices to lock/unlock your bootloader without htcdev.com once S-OFF (DO NOT use the codes for M7 M8 or M9)
http://forum.xda-developers.com/showthread.php?t=2470340
Shouldn't this work?
fastboot oem unlock
Are your developer options enabled right now. And did you check the box to allow bootloader unlock again?
Sent from my HTC 10 using XDA Labs
Some luck
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
glad its sorted for you and back to flashaholic mode
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
Sounds like your Environmental PATH is set to just that one folder.
Windows?
There's some good threads here on XDA,
http://forum.xda-developers.com/showthread.php?t=1161776
Glad you got it working though!
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
gercdgcat said:
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
Click to expand...
Click to collapse
Thanks for replying - could you perhaps write a guide as to exactly how you unlock your bl after using fastboot lock?
I have seen a few folks who appear stuck at that point and I and they would be happy campers if they could get around that!!!
Thanks!
EDIT: I added a comment about "correct stock" to the first post... This may be key to the folks that are having trouble...
You might look at thread
https://forum.xda-developers.com/moto-z-play/help/please-help-urgently-t3814260
But I guess I would have to call anyone who successfully locks and unlocks again their bootloader as darn lucky. Some, (many?) can't.
In the end I still have to ask "why the heck are you locking your phone" - what could you possibly gain? It's totally unnecessary. it can be a very expensive little line of code.
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
pkadavid said:
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
Click to expand...
Click to collapse
LOL - right! Thanks!!!
bump
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
IncendiaryPyro said:
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
Click to expand...
Click to collapse
How's the 2xl?
hithere
KrisM22 said:
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Click to expand...
Click to collapse
I prefer stock without modifications but sometimes when i have time to try news modifications or roms i used to unlocked the phone and after this relock again, the process that i use is very simple, i just unlock with the same code that Motorola gaves to unlock bootloader, i don't have sure but if you request unlock codes to many times can be a problem but i use the same code and works good.
Basically: relock as are specifcified in another topic in this device forum( using the last stock version that you used)
And after this unlock with code again
Obs.: Is not recommended to unlock/relock to many times.
Obs2.: I only did this three times and i don't know if has a limit
bumpsi
It is my opinion also that relocking is a bad idea. But if someone likes to do it, eg to get Google Pay working without Magisk, why do you want to warn him?
Relock only is possible in combination with flashing a complete correctly firmware. If something is wrong with the firmware you flash, relocking won't succeed. Your device won't be locked if it does not fully succeed or the firmware is not correctly signed. The unlock code is supposed to stay valid, you should be able to unlock your device as many times as you want using the same code.
a) is fine, but does not consider Android SafetyNet
b) is just wrong, and this already was written in a comment.
Please do not bump wrong warnings.
i am trying to lock the bootloader again with my unlock code and it keeps saying the code is wrong, and it worked fine for unlocking.
my question is does the code change after a reset? i completely reset the phone to stock with stock loader,ercovery/recovery just cant seen to be able to relock the device.
darkmage1991 said:
i am trying to lock the bootloader again with my unlock code and it keeps saying the code is wrong, and it worked fine for unlocking.
my question is does the code change after a reset? i completely reset the phone to stock with stock loader,ercovery/recovery just cant seen to be able to relock the device.
Click to expand...
Click to collapse
I don't think it is supposed to have changed. At least it hasn't before.
fastboot oem relock *code_here*
what do you mean "stock loader"?
but if code is not working , it seems safe to say if you do lock it, and it will not work to unlock again......, if needed.
EDIT: god im stupid... this was the code they sent me: https://i.imgur.com/Zz2VgQz.png
so i was putting in 64ZR9670112GJ3F8 the code is supposed to be 64ZR96701I2GJ3F8
so lesson learned. make sure you really look at the code one's can look like i's in a pic.
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.