Stock rooted PIE a month ago.
Looking through my command history, I see
Code:
$ fastboot flashing unlock
but I do not see the subsequent
Code:
$ fastboot flashing unlock_critical
I am 99% sure I did run this command also, but there's that 1%...
Is there anything I can check on the phone itself to confirm that indeed, I've unlocked critical as well?
When in fastboot mode, the phones' display shows SECURE BOOT - yes and DEVICE STATE - unlocked.
Also
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.001s
$
I wonder if there's a var for critical.. or how to get a list a vars..
IDK if there is, but I am interested in finding out if there's a variable to check, and more importantly if that command does anything of value. I've not unlocked "critical" (100% certain), but I couldn't see it having a real point.
To be clear, I've never had any issue in flashing or rooting the PH-1, or with many of the issues that others report.
Code:
fastboot oem device-info
ultrasuper said:
Stock rooted PIE a month ago.
Looking through my command history, I see
Code:
$ fastboot flashing unlock
but I do not see the subsequent
Code:
$ fastboot flashing unlock_critical
I am 99% sure I did run this command also, but there's that 1%...
Is there anything I can check on the phone itself to confirm that indeed, I've unlocked critical as well?
When in fastboot mode, the phones' display shows SECURE BOOT - yes and DEVICE STATE - unlocked.
Also
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.001s
$
I wonder if there's a var for critical.. or how to get a list a vars..
Click to expand...
Click to collapse
I also forgot and was unsure so I just ran the critical unlock again and got the message already unlocked
jionny said:
I also forgot and was unsure so I just ran the critical unlock again and got the message already unlocked
Click to expand...
Click to collapse
I am afraid to simply re-issue the cmd because *I think* it wipes the phone completely.
munchy_cool said:
Code:
fastboot oem device-info
Click to expand...
Click to collapse
Code:
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Device modem EFS unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
finished. total time: 0.001s
Thanks for the tip.
Any idea what the last two represent?
ultrasuper said:
Any idea what the last two represent?
Click to expand...
Click to collapse
nopes
ultrasuper said:
I am afraid to simply re-issue the cmd because *I think* it wipes the phone completely.
Click to expand...
Click to collapse
you should be prompted in the bootloader to confirm
ultrasuper said:
I am afraid to simply re-issue the cmd because *I think* it wipes the phone completely.
Click to expand...
Click to collapse
how can it rewipe the phone if its already unlocked? impossible besides the cmd shows you that its unlocked so you are good
jionny said:
how can it rewipe the phone if its already unlocked? impossible besides the cmd shows you that its unlocked so you are good
Click to expand...
Click to collapse
both unlock and unlock_critical initiate wipes
ziddey said:
both flashing unlock and flashing unlock_critical initiate a wipe
Click to expand...
Click to collapse
not if its already unlocked. I did so already and simply got back already unlocked
---------- Post added at 06:15 PM ---------- Previous post was at 06:05 PM ----------
ziddey said:
both unlock and unlock_critical initiate wipes
Click to expand...
Click to collapse
lmao ok you got it
jionny said:
not if its already unlocked. I did so already and simply got back already unlocked
---------- Post added at 06:15 PM ---------- Previous post was at 06:05 PM ----------
lmao ok you got it
Click to expand...
Click to collapse
both initiate wipes, and warn accordingly. but yes, if op is already unlocked, it won't do anything
ziddey said:
both initiate wipes, and warn accordingly. but yes, if op is already unlocked, it won't do anything
Click to expand...
Click to collapse
That has been my point all along if it is already unlocked it will do nothing but tell you its already unlocked. Thank you
kboya said:
IDK if there is, but I am interested in finding out if there's a variable to check, and more importantly if that command does anything of value. I've not unlocked "critical" (100% certain), but I couldn't see it having a real point.
To be clear, I've never had any issue in flashing or rooting the PH-1, or with many of the issues that others report.
Click to expand...
Click to collapse
Yes the command is of value, it's to Unlock Critical Partitions
https://mata.readthedocs.io/en/latest/
Thanks but that's not as self-evident as you seem to think. I've read that and much more besides about other devices. Yet I still don't see its value to me and my use case where I've never needed these critical partitions. The last Android partitioning I needed to do was on the Nexus one and HTC Desire to ensure that small ROMs had a suitably small system partition and thus more storage abatement for apps.
Also, without unlock_critical I've had no issues with flashing and rooting, unlike so many others that have unlocked it.
kboya said:
IDK if there is, but I am interested in finding out if there's a variable to check, and more importantly if that command does anything of value. I've not unlocked "critical" (100% certain), but I couldn't see it having a real point.
To be clear, I've never had any issue in flashing or rooting the PH-1, or with many of the issues that others report.
Click to expand...
Click to collapse
kboya said:
Thanks but that's not as self-evident as you seem to think. I've read that and much more besides about other devices. Yet I still don't see its value to me and my use case where I've never needed these critical partitions. The last Android partitioning I needed to do was on the Nexus one and HTC Desire to ensure that small ROMs had a suitably small system partition and thus more storage abatement for apps.
Also, without unlock_critical I've had no issues with flashing and rooting, unlike so many others that have unlocked it.
Click to expand...
Click to collapse
This is suppose to be the basic understanding, they/the partitions are Locked and in order to flash properly to them, we need to Unlock them...
I highly suggest until someone says otherwise to make sure you unlock them...
I understand the difference between locked and unlocked; you've missed the point entirely.
I'll leave it.
kboya said:
I understand the difference between locked and unlocked; you've missed the point entirely.
I'll leave it.
Click to expand...
Click to collapse
You asked before if there was any value and you didn't see the point.
So if it's locked, it can't be flashed to, so you don't see the value or point in that?
From reading around, there seems to be some people getting away with keeping them locked, and others having problems.
But the correct way for now is to unlock them to avoid any problems.
I thought that was clear.
Yeah, read around:
"For Pixel 2 XL only with loader version prior to TMZ20a: 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" (source: google factory images)
kboya said:
Yeah, read around:
"For Pixel 2 XL only with loader version prior to TMZ20a: 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" (source: google factory images)
Click to expand...
Click to collapse
I have already read around...
I unlock it because I am hacking on Stock.
Related
This process has been done with the HTC International version available in Australia.
Im sure everyone would appreciate follow up from others to confirm which versions of the phone this process works with.
The process below assumes a small amount of familiarity with HTC unlock process AND WILL WIPE THE DATA FROM YOUR PHONE!
The process is basically the same as ever with a few variations
Install adb
Go to http://www.htcdev.com/bootloader and sign up, click unlock bootloader
In the device selection drop-down select "any other supported device"
Boot into "Download Mode" - Which is the equivalent of fastboot. (shutdown your phone, hold power+volume down until you boot into this mode). This is the mode with the black background and red text
Connect phone to PC, and issue "fastboot oem get_identifier_token"
Copy the code into the returned by adb into space on HTCs website
Get the email, download the attachment and issue "fastboot flash unlocktoken Unlock_code.bin"
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Always good to know we can root the new flagship
Super-Veloce said:
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Click to expand...
Click to collapse
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Really?? Damn..
I keep getting:
Code:
C:\WINDOWS\system32>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Tried it on 2 different systems :S
What mode was your phone in? Were you in download mode? Or in the bootloader?
daveh86 said:
What mode was your phone in? Were you in download mode? Or in the bootloader?
Click to expand...
Click to collapse
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
EndoSurf said:
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
Click to expand...
Click to collapse
Thanks, I've added a note in my comment that mentions that download mode is the one with black background and red text.
And how i will make it S-Off?
Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
By being patient... the device is not even available in most regions yet, give developers a little time would you.
For Verizon test M9's, can't even pull identifier token. Fastboot command yields "FAILED (remote: unknown command)," which is interesting because I used fastboot to successfully flash TWRP then root.
jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Is there a way to s-off? Ive seen some have already done it, but how?
Test devices come S-OFF.
hgoldner said:
Test devices come S-OFF.
Click to expand...
Click to collapse
Or you can give the Phone to a shop / repair centre to s-off it
In Germany you can do it at:
http://www.gsm-europe.de/epages/635...3/Products/htc_soff/SubProducts/htc_soff-0001
Its a shop in Berlin they do s-off and supercid
And they can do it on the Onde M9
Only bad thing they cant Unlock bootloader it without HTC Dev.
So You get your phone back with S-Off and with Super Cid but Boodloader is Locked and you must Unlock it via HTC dev
because for Unlock via Fastboot you need root on Android 5
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Prasad said:
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Click to expand...
Click to collapse
Didn't notice any loss after unlocking M9 ..
jauhien said:
Didn't notice any loss after unlocking M9 ..
Click to expand...
Click to collapse
Thank you! Now I can confidently proceed when the device arrives in a couple hours.
Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
you're gonna have to wait a while for that
Been a long time since I unlocked a bootloader. But I don't lose any OTA functionality do I?
Sent from my HTC One M9 using XDA Free mobile app
I have a moto x pure pre release phone. It was a model that was issued before the initial release of moto x pure. I have tried to get the unlock code with no success. I get a failed error message. I have tried this on windows 10 and Linux. I can successfully recognize the device on fastboot and adb. However, no unlock code. I am now thinking somehow the phone is locked and unable to get this code. I'm thinking about selling this phone and getting a new one. I would like any feedback if you think I will have the same issue or if the pre release may be locked.
Sent from my Nexus 6 using XDA Free mobile app
I had no issue unlocking a phone bought directly from Motorola on November.
jcasares said:
I had no issue unlocking a phone bought directly from Motorola on November.
Click to expand...
Click to collapse
Was it a pre-release version? My guess is no.
Did you go into settings and flip the unlock switch? Hard to help when you don't list the steps you took to unlock.
lafester said:
Did you go into settings and flip the unlock switch? Hard to help when you don't list the steps you took to unlock.
Click to expand...
Click to collapse
I installed Android sdk and Motorola driver. Then enabled USB debugging and checked OEM unlock. Then booted into bootloader. Then typed fastboot OEM get_unlock_data. Then it fails to get information.
brholt6 said:
Was it a pre-release version? My guess is no.
Click to expand...
Click to collapse
It is special phone specifically designed to show off the phone before launch.
droc83 said:
I installed Android sdk and Motorola driver. Then enabled USB debugging and checked OEM unlock. Then booted into bootloader. Then typed fastboot OEM get_unlock_data. Then it fails to get information.
Click to expand...
Click to collapse
Eng boot loader by chance ? Did you try fast oem unlock?
Sent from my SM-T810 using Tapatalk
I was simply answering his doubt about purchasing a new one and facing the issue of unlocking the bootloader again.
He won't have this issue anymore with a unit purchased from Motorola.
dottat said:
Eng boot loader by chance ? Did you try fast oem unlock?
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
What does fast oem unlock do? Do you mean fastboot oem unlock? I didn't try either one.
droc83 said:
What does fast oem unlock do? Do you mean fastboot oem unlock? I didn't try either one.
Click to expand...
Click to collapse
Yes dang keyboard.
Sent from my XT1575 using Tapatalk
droc83 said:
It is special phone specifically designed to show off the phone before launch.
Click to expand...
Click to collapse
Ya, I wasn't asking what a pre-release version was. I think you misread.
dottat said:
Yes dang keyboard.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I tried fastboot oem unlock. It is asking for a code which I can't get.
Did you go to moto and request unlock?
The code you need you can get it on the Motorola support site (I believe this).
jcasares said:
The code you need you can get it on the Motorola support site (I believe this).
Click to expand...
Click to collapse
I need the code from my phone to do this. That is where my trouble is. Everytime I enter fastboot oem get_unlock_data it gives me this.
C:\SDK\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
lafester said:
Did you go to moto and request unlock?
Click to expand...
Click to collapse
They won't help with unlocking my bootloader. They just refer to a website on how to do it. I have told them I believe something is wrong with the phone but they don't want to help with this. I think I am going to just give up and sell the phone and cut my losses.
So why dont you actually follow the process for Bootloader unlock on Moto's Site?
droc83 said:
I need the code from my phone to do this. That is where my trouble is. Everytime I enter fastboot oem get_unlock_data it gives me this.
C:\SDK\platform-tools>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you try flashing the stock factory images in fastboot, then rebooting and trying the process once more? You could have an odd boot loader version or something.
Sent from my XT1575 using Tapatalk
dottat said:
Did you try flashing the stock factory images in fastboot, then rebooting and trying the process once more? You could have an odd boot loader version or something.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Do you have a link on how to do this?
fkofilee said:
So why dont you actually follow the process for Bootloader unlock on Moto's Site?
Click to expand...
Click to collapse
I did follow these steps. However, I have to send them a code from my phone which I cannot get.
Me and this guy was talking about unlocking the bootloader by modifiying the .bin in an ota file and to my surprise he apparently was able to unlock the Pixel 2. Maybe this will work for those in on a Verizon Pixel 1 so give this a shot!
From all I can tell your just unlocking the critical partition with the command "Fastboot flashing lock_critical" then it allows for you to unlock. Refer to this thread and good luck!
https://forum.xda-developers.com/pixel-2/help/maybe-stupid-question-verizon-pixel-2s-t3726294
Couldn't be this easy, so many devs have looked into this.
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Couldn't be this easy, so many devs have looked into this.
Click to expand...
Click to collapse
I too think this is too easy but if it works it works.
I don't see how you can modify an OTA and still pass the the cert signing check and update checker.
TonikJDK said:
I don't see how you can modify an OTA and still pass the the cert signing check and update checker.
Click to expand...
Click to collapse
That is what is interesting me but it seems another person has done the same and it worked.
I don't even have Verizon or the Verizon pixel, but I'm curious if this works too lmao.
Didn't for me on my pixel. Says cannot be unlocked
abranson said:
Didn't for me on my pixel. Says cannot be unlocked
Click to expand...
Click to collapse
I see is this on the Pixel XL or just the Pixel ?
5 inch. I wouldn't think it would matter
abranson said:
5 inch. I wouldn't think it would matter
Click to expand...
Click to collapse
It just seems that all the success stories of the Pixel 2 are of the smaller verison and not the Pixel 2 XL so I didn't know if one or the other would work better. Also what error did it give you?
Edit: the critical part is an XL command only so try
Fastboot lock
Or
Fastboot flashing lock
The flashing lock-critical said it wasnt a valid command, so tried the lock_critical. Already locked and did nothing else. Also if changed to unlock_critical, fails and says unlocking is not allowed ,
abranson said:
The flashing lock-critical said it wasnt a valid command, so tried the lock_critical. Already locked and did nothing else. Also if changed to unlock_critical, fails and says unlocking is not allowed ,
Click to expand...
Click to collapse
How about fastboot flashing lock or flashing unlock
Did those too. The oem unlocking not allowed came up. Can't toggle oem unlocking switch, so idk
abranson said:
Did those too. The oem unlocking not allowed came up. Can't toggle oem unlocking switch, so idk
Click to expand...
Click to collapse
I don't understand this comment maybe a typo?
Oem unlocking toggle under developer options is greyed out. When you input those commands, it says failed, and says unlocking is not allowed. I'm not at a PCat the moment, but I can do again tomorrow, and take a pic
---------- Post added at 02:22 AM ---------- Previous post was at 02:15 AM ----------
And I was under the impression the critical command was only for pixel 2 and 2xl, so Idk. I have latest adb and fastboot
abranson said:
Oem unlocking toggle under developer options is greyed out. When you input those commands, it says failed, and says unlocking is not allowed. I'm not at a PCat the moment, but I can do again tomorrow, and take a pic
---------- Post added at 02:22 AM ---------- Previous post was at 02:15 AM ----------
And I was under the impression the critical command was only for pixel 2 and 2xl, so Idk. I have latest adb and fastboot
Click to expand...
Click to collapse
I thought the critical command was just a Android Oreo thing not specific to the Pixel 2's
EstiR86 said:
I thought the critical command was just a Android Oreo thing not specific to the Pixel 2's
Click to expand...
Click to collapse
For Pixel 2: To flash the bootloader, Pixel 2's boot loader must be updated to at least Oreo MR1's version first. This may be done by applying an over-the-air (OTA) update, or sideloading a full OTA with the instructions on that page.
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
Looks like this exploit does not work for the original Pixel. Bummer waste or a thread, good luck to those still trying to unlock.
try this, take Sim out and scratch out gold plating square closest to cut in one corner. reinsert Sim, reboot phone and adb/fastboot first then try activate oem unlock.sean
petiolarissean said:
try this, take Sim out and scratch out gold plating square closest to cut in one corner. reinsert Sim, reboot phone and adb/fastboot first then try activate oem unlock.sean
Click to expand...
Click to collapse
I'm confused what this would do, would you like to elaborate more.
I need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
SD008 said:
I need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
Click to expand...
Click to collapse
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
acejavelin said:
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
Click to expand...
Click to collapse
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
sinchan_nohara said:
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
Click to expand...
Click to collapse
If you haven't changed anything in /system or /vendor and your device is stock unrooted there's no problem with OTA updates. If you flashed the stock logo.bin everything is ok even when it shows BL is unlocked.
Sent from my Moto G5 Plus using XDA Labs
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
I've been here a long time, didn't mean to offend... All I had to go by was your limited information of the first post, I assumed nothing that wasn't included in your post. You didn't state anything that you had tried, so of course I assumed you didn't look because you didn't state anything.
Sorry. I will just bow out and wish you luck.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
Click to expand...
Click to collapse
Man, I was having the same issue on my Moto G6 (Ali) and was like you, looking here and there with no solution, and your solution was the only one that worked!! Thank you so much!
Is anyone tried to unlock bootloader of there nothing phone 1
hasnainali2404 said:
Is anyone tried to unlock bootloader of there nothing phone 1
Click to expand...
Click to collapse
I can't wait to get my hands on the device.
Think you can unlock the bootloader with fastboot/adb (same as with Nexus/Pixel/Oneplus-devices) no?
Hey!
After enabling OEM Unlock in the developer options, the commands to unlock it are:
fastboot flashing unlock
fastboot flashing unlock_critical
Hope this helps.
What about relocking?
Krullendhaar said:
What about relocking?
Click to expand...
Click to collapse
same commands, just change "unlock" with "lock" ^^.
I like old OnePlus brand/Carl Pei for that, Root Friendly
No Knox, No 169 hours Waiting Period or Forbidden Unloack Bootloader.
It's premature to say whether this will be possible or not, as the Phone(1) was released only 5 days ago.
But knowing Carl, I think that everything will be allowed on this smartphone so that it can be used by many people.
It will be a while before we have a custom recovery and therefore can develop around the Phone(1).
But the kernel is already available for developers which is a good sign.
Post with link for Phone(1) Kernel
@gigantino said:
Hey!
After enabling OEM Unlock in the developer options, the commands to unlock it are:
fastboot flashing unlock
fastboot flashing unlock_critical
Hope this helps.
Click to expand...
Click to collapse
Thanks man, definitely helps
Sib64 said:
It's premature to say whether this will be possible or not, as the Phone(1) was released only 5 days ago.
But knowing Carl, I think that everything will be allowed on this smartphone so that it can be used by many people.
It will be a while before we have a custom recovery and therefore can develop around the Phone(1).
But the kernel is already available for developers which is a good sign.
Post with link for Phone(1) Kernel
Click to expand...
Click to collapse
if you're a developer ,know this, I love you guys for the stuff you domake us proud
Does unlocking bootloader wipe my data? If yes, is there a way to circumvent this?
abrattic said:
Does unlocking bootloader wipe my data? If yes, is there a way to circumvent this?
Click to expand...
Click to collapse
Yes!! No!!
abrattic said:
Does unlocking bootloader wipe my data? If yes, is there a way to circumvent this?
Click to expand...
Click to collapse
Yes! Unlocking your phone will always wipe your data!
And No! if you want to unlock your phone, there is no way around the data wipe at the moment
Is it able to retain L1 status after unlock?
After unlocking (without root, unmodified partitions):
I still have L1 wildvine ("DRM Info").
Safetynet CTS profile match fails.
I'm missing play protect certification.
I can still apply OTAs. (just did 1.1.0 -> 1.1.2)
dedors said:
After unlocking (without root, unmodified partitions):
I still have L1 wildvine ("DRM Info").
Safetynet CTS profile match fails.
I'm missing play protect certification.
I can still apply OTAs. (just did 1.1.0 -> 1.1.2)
Click to expand...
Click to collapse
You need to install Magisk (and also root your device) in order to install Universal safetynet fix module and ofc actually pass safetynet. Worked fine on my device.
I have unlocked many phones but never used this command "fastboot flashing unlock_critical"
Why do we have to use that command aswell?
bariz143 said:
I have unlocked many phones but never used this command "fastboot flashing unlock_critical"
Why do we have to use that command aswell?
Click to expand...
Click to collapse
You don't need to.
bariz143 said:
I have unlocked many phones but never used this command "fastboot flashing unlock_critical"
Why do we have to use that command aswell?
Click to expand...
Click to collapse
If you have read my tuto with all the process and explanations , you would have seen this point that concerns your question:
12-Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
Click to expand...
Click to collapse
Sib64 said:
If you have read my tuto with all the process and explanations , you would have seen this point that concerns your question:
Click to expand...
Click to collapse
So as long as I flash ROMS i don't have to use that command. Only for modem.and so on.
bariz143 said:
So as long as I flash ROMS i don't have to use that command. Only for modem.and so on.
Click to expand...
Click to collapse
Since my HTC Hero, it's the 1st time that I have inserted this command