[SOLVED] Locked down bootloader? - Google Pixel 2 XL Questions & Answers

EDIT: Solution: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?

frap129 said:
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
Click to expand...
Click to collapse
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Sent from my MHA-L29 using Tapatalk

danon.brown said:
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Click to expand...
Click to collapse
I already tried that command as I said in my post (unless there's one other than "fastboot flashing unlock" that I'm not seeing in the essential forum)

Can you see your phone with fastboot devices?
Sent from my MHA-L29 using Tapatalk

A few others with the phone have reported the same issue in the "rooting" thread...not sure what's going on!

I had the essential phone and had to get a more current Version of adb.
Sent from my MHA-L29 using Tapatalk

did you enable developer settings and see if there is a setting to allow OEM unlock?

Code:
fastboot flashing unlock
will unlock it

When I first booted the phone and enabled USB debugging, the OEM Unlock was greyed out. I had to put my sim card in for it to allow me to enable it. Then using the fastboot flashing unlock worked from bootloader.

fastboot flashing unlock worked for me.

Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over

@frap129 hope you get it sorted. Glad to see you got a 2 XL as well! Would love to eventually see Carbon and Electron on the 2 XL. Have been missing them since I RMA'd my 6P for an XL. :good:

What is the point if the stock android phone has locked bootloader!
I miss NEXUS phones

This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..

Thanks for all the responses, I guess it's just my fastboot version. I have the latest that's on the aur, but I'll try manually downloading from Google's site.

I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.

cryppie said:
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Click to expand...
Click to collapse
Disagreed. This was not necessary with the OG Pixel.
Further, I think most people here know that the chances of unlocking a Verizon bought Pixel are slim to none.

dirtyfingers said:
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
Click to expand...
Click to collapse
Ive been using adb reboot the whole time and can't get it to work, thanks for the heads up!

UPDATE: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Sorry for the double post, I just wanted to make sure anyone following this with the same issue gets the solution.

cwalker0906 said:
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
Click to expand...
Click to collapse
You could have also used the sdk manager to update the platform-tools.

Related

Pixel XL Locked

My non-Verizon Pixel XL is stuck with a locked bootloader, OEM Unlocking Disabled, and is unable to boot to recovery, or the system (thus I cannot enable OEM unlocking). When I try to boot, it has the red message stating that my device is corrupt, then it turns off and does not boot.
How can I fix this?
I has AOSPA installed before this all went down, but I agree I made some dumb moves, and I am hoping someone here can help me out of this hole.
How did you lock your bootloader with AOSPA still installed? You always go back to stock before re-locking your bootloader. That was a pretty big mistake, and I'm not so sure there is a way around this.
If it's a Google Pixel XL, then try booting into fastboot (hold Power+Volume Down), run the "fastboot oem unlock" command, without quotes to unlock the bootloader, and flash a stock image.
Hope it works.
-Maverick- said:
How did you lock your bootloader with AOSPA still installed? You always go back to stock before re-locking your bootloader. That was a pretty big mistake, and I'm not so sure there is a way around this.
If it's a Google Pixel XL, then try booting into fastboot (hold Power+Volume Down), run the "fastboot oem unlock" command, without quotes to unlock the bootloader, and flash a stock image.
Hope it works.
Click to expand...
Click to collapse
Can you unlock the bootloader from the bootloader screen with ADB command like you said when "allow OEM unlocking" in developer options has not been enabled? I'm sure that I could do that when I had the Nexus 6 but haven't tried it with my Pixel XL.
I think the command now is: fastboot flashing unlock
3aucla1r3 said:
Can you unlock the bootloader from the bootloader screen with ADB command like you said when "allow OEM unlocking" in developer options has not been enabled? I'm sure that I could do that when I had the Nexus 6 but haven't tried it with my Pixel XL.
I think the command now is: fastboot flashing unlock
Click to expand...
Click to collapse
I don't think you can, it's why I wasn't sure it would work, but still worth an attempt. I used fastboot oem unlock when I unlocked my bootloader, so I guess the old command still works, but yeah, fastboot flashing unlock is the new way of doing it. :good:
-Maverick- said:
I don't think you can, it's why I wasn't sure it would work, but still worth an attempt. I used fastboot oem unlock when I unlocked my bootloader, so I guess the old command still works, but yeah, fastboot flashing unlock is the new way of doing it. :good:
Click to expand...
Click to collapse
I've tried it and none of that works. The device is on its way back to Google since I just got a Google coverage plan replacement. Hopefully, they won't pitch a fit that it's locked up the way it is.
gettingerr said:
I've tried it and none of that works. The device is on its way back to Google since I just got a Google coverage plan replacement. Hopefully, they won't pitch a fit that it's locked up the way it is.
Click to expand...
Click to collapse
Unlikely. Are they going to attempt a repair, or just outright replace the phone?
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
jhs39 said:
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
Click to expand...
Click to collapse
You have to have to unlock your bootloader to install any custom rom on the pixel.
Hey did you ever solve this? im in a similar prediciment. My phone keeps bootlopping, trying to flash an older ROM but bootloader is locked and none of the fastboot oem unlock commands work.
jhs39 said:
I'm not yet adept on the ins and outs of flashing stuff on this phone. Is it actually possible to flash a custom Rom on the Pixel XL while the bootloader is locked? I know it's not something anyone who values their phone would even attempt but with most phones you could never do it anyway. I understand there is a temporary TWRP that you can boot into without actually installing the custom recovery on your phone. Does this make it possible to do what happened with this user?
Click to expand...
Click to collapse
Do it now!
@t4nks120
The bootloader unlock for the Verizon Pixel/Pixel XL is working. Go here to unlock it.

fastboot unlock vs fastboot unlock critical

When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Az Biker said:
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Click to expand...
Click to collapse
Only if you want to update the bootloader. That's the only thing I can see that critical does.
Sent from my Pixel 2 XL using Tapatalk
I believe unlock_critical is necessary if you want to be able to flash updates manually..
"For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock "
Above quote is from Google Factory Image page.
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Badger50 said:
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Click to expand...
Click to collapse
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Wickidmasshole said:
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Click to expand...
Click to collapse
This is why I asked the question. I wasn't sure if doing the basic unlock prior to the critical unlock would be an issue.
I'm running the critical unlock when I get home tonight (I want to be able to update the bootlader in the future), I'll let you know what I run into, if anything.
Az Biker said:
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Click to expand...
Click to collapse
Didn't use any toolkits, just these 2 guides....
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176 https://forum.xda-developers.com/pixel-2-xl/how-to/guide-magisk-root-snoke-kernel-t3701930
....and didn't run into any problems at all. My P2XL is just humming right along. The battery on this thing is phenomenal! Takes me a good 2 days to knock it down to 10% :good:
Now we just need some TWRP to get Beans up and running :good::good:
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
iamjimmy said:
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
Click to expand...
Click to collapse
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Badger50 said:
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Click to expand...
Click to collapse
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Click to expand...
Click to collapse
This one :good:
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
marbertshere said:
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
Click to expand...
Click to collapse
I've unlocked the ordinary bootloader first, then the bootloader_critical without any problems :good:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
jaybird779 said:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
Click to expand...
Click to collapse
The bootloader_critical unlock has to be performed only if you want to flash the bootloader (e.g. when you flash a factory image), but, if you want to perform all the other operations, such as rooting, kernel flashing, etc., you have to unlock the ordinary bootloader, too.
So, these are the two Fastboot commands:
fastboot flashing unlock_critical (for bootloader flashing, you've already performed this)
fastboot flashing unlock (for all the other operations)
The request which appears on your phone, when you enter these two commands, is the same, and you have to allow the bootloader unlock in both cases :good:

Fastboot refusing to take commands after oem unlock

I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
RenaldiDroidXDA said:
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
Click to expand...
Click to collapse
I think your problem is you used 'fastboot oem unlock' instead of 'fastboot flashing unlock.'
Well, now I see the problem.
Now I need to know how to fix it .-.
RenaldiDroidXDA said:
Well, now I see the problem.
Now I need to know how to fix it .-.
Click to expand...
Click to collapse
did you enable usb debugging in developer options?
lucky_strike33 said:
did you enable usb debugging in developer options?
Click to expand...
Click to collapse
Yes, I did. adb works quite well enough, but fastboot detects nothing.

Easier Way To OEM Unlock Via Fastboot?

This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!
Did this method work for your....
LysolPionex said:
This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!
Click to expand...
Click to collapse
which variant you use?
angel8502 said:
which variant you use?
Click to expand...
Click to collapse
SM-960F/DS.
But I just got the "Only Official released binaries are allowed to be flashed" message, so I might get to try this method again myself, lol.
How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten
beatbreakee said:
How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten
Click to expand...
Click to collapse
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?
LysolPionex said:
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?
Click to expand...
Click to collapse
take a pic n post it of download mode
elliwigy said:
take a pic n post it of download mode
Click to expand...
Click to collapse
Just a close up, nothing else relevant in the screen.
LysolPionex said:
Just a close up, nothing else relevant in the screen.
Click to expand...
Click to collapse
most likely is the rmm state
elliwigy said:
most likely is the rmm state
Click to expand...
Click to collapse
That makes sense with what I found last night in another thread. I think I used an old version of the rmm Mesa bypass too, so we'll see what happens. In another 5 days...
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
This is the first time I've seen a clear explanation off all of this. Thank you for that!
What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..
Regikitten said:
What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..
Click to expand...
Click to collapse
I'm not familiar with it, but I assume he's talking about this: https://forum.xda-developers.com/ga...ollection-combination-rom-samsung-s9-t3782737
There are a couple other threads about it in the S9 forum.
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?
LysolPionex said:
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?
Click to expand...
Click to collapse
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all
elliwigy said:
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all
Click to expand...
Click to collapse
Lol, so I'm at 182 hours uptime, but the OEM option isn't in dev options...do I risk going to download mode to see RMM status?
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance
Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
askader said:
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance
Click to expand...
Click to collapse
Will appear within 5-7 days since you flashed stock ROM.
ZoiraP said:
Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
Will appear within 5-7 days since you flashed stock ROM.
Click to expand...
Click to collapse
Did it solved after 7 days?

pixel 2 xl cant oem unlock bootloader

I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
fryedmonk911 said:
I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
Click to expand...
Click to collapse
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Badger50 said:
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Click to expand...
Click to collapse
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
crixley said:
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
Click to expand...
Click to collapse
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
sinkoo1979 said:
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
Click to expand...
Click to collapse
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Badger50 said:
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Click to expand...
Click to collapse
didn't check
yes
yes
yes
yes
sinkoo1979 said:
didn't check
yes
yes
yes
yes
Click to expand...
Click to collapse
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Badger50 said:
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Click to expand...
Click to collapse
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
sinkoo1979 said:
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
Click to expand...
Click to collapse
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
fryedmonk911 said:
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Click to expand...
Click to collapse
I'm guessing when Google told you that all phones coming from Google were fully unlocked they were talking about being carrier unlocked instead of having the capability of unlocking the bootloader.
When buying a LG phone (e.g. Pixel 2 XL) it's good to have the seller run an IMEI check and post the screenshot for you from this site... https://www.imeipro.info/check_lg.html
Under they buyer name you can tell if you are getting a Google or Verizon variant.
Badger50 said:
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
Click to expand...
Click to collapse
Since all Minimal ADB and Fastboot does is bundle up the platform tools and add a Windows executable stub to them, removing it isn't a bad idea. An alternative - that I took - would be to update the platform tools in the Minimal ADB folder with the latest from Google.

Categories

Resources