Related
I don't think I have one of the models that has locked bootloader. But I have problems with fastboot, and everything sort of rely on it. Doing a 'fastboot devices' does not get a return value feedback of any kind or error neither.
Is this just matter of setting up ADB , fastboot, drivers? I hope so. I'm beginnig to run in circles though.
model R800A world gsm. In the keypad service info, network value 0, Root: Boot Loader unlock allowed: YES
I've had an unlocked Snapdragon Note 10+ sitting around for quite a while doing nothing (it was powered on much of the time) and finally decided it was time to give it the gift of TWRP and Magisk. After enabling developer mode, the OEM unlock toggle was present, and seemeingly was reflected on the download screen:
Code:
OEM LOCK : OFF (L)
The bootloader welcome screen was shown in Asian characters, so I initially didn't realize what was going on, but in each case, my attempts to flash TWRP failed with the booatloader indicating it was blocked by the OEM lock. I ultimately did a few factory resets to see if they would have any effect. In some cases after factory reset, the OEM Unlock setting in developer options was present and in other cases it was not. However, in each case where it was missing, I was ultimately able to get it to appear by manipulating a combination of date/time and software update settings as described in numerous posts and articles.
What I didn't realize was that the Asian language welcome screen was simply asking me to press volume up to enable custom image flashing. After realizing this, my impression here is that the OFF/ON refers to the bootloader's interpretation of the OEM Unlock status, and the (L/U) refers to whether the user pressed volume up at the welcome screen (unlock to enable flashing custom images) or something else (leaving the bootloader locked).
However, now regardless of the OEM Unlock setting, I always see the following on the download screen, depending on whether I press volume down on the welcome screen:
Code:
OEM LOCK : ON (L)
or volume up:
Code:
OEM LOCK : ON (U)
I also see:
Code:
RMM STATUS : CHECKING
So, what's going on here? Did I just earn myself a 7-day RMM lockout, or is something else going on? I thought that 7-day lockouts were indicated by an RMM status of "PRENORMAL". How can I can get the bootloader to unlock properly?
The software build currently on the device is N9750ZSS2ASKB.
Thanks.
sjevtic said:
I've had an unlocked Snapdragon Note 10+ sitting around for quite a while doing nothing (it was powered on much of the time) and finally decided it was time to give it the gift of TWRP and Magisk. After enabling developer mode, the OEM unlock toggle was present, and seemeingly was reflected on the download screen:
Code:
OEM LOCK : OFF (L)
The bootloader welcome screen was shown in Asian characters, so I initially didn't realize what was going on, but in each case, my attempts to flash TWRP failed with the booatloader indicating it was blocked by the OEM lock. I ultimately did a few factory resets to see if they would have any effect. In some cases after factory reset, the OEM Unlock setting in developer options was present and in other cases it was not. However, in each case where it was missing, I was ultimately able to get it to appear by manipulating a combination of date/time and software update settings as described in numerous posts and articles.
What I didn't realize was that the Asian language welcome screen was simply asking me to press volume up to enable custom image flashing. After realizing this, my impression here is that the OFF/ON refers to the bootloader's interpretation of the OEM Unlock status, and the (L/U) refers to whether the user pressed volume up at the welcome screen (unlock to enable flashing custom images) or something else (leaving the bootloader locked).
However, now regardless of the OEM Unlock setting, I always see the following on the download screen, depending on whether I press volume down on the welcome screen:
Code:
OEM LOCK : ON (L)
or volume up:
Code:
OEM LOCK : ON (U)
I also see:
Code:
RMM STATUS : CHECKING
So, what's going on here? Did I just earn myself a 7-day RMM lockout, or is something else going on? I thought that 7-day lockouts were indicated by an RMM status of "PRENORMAL". How can I can get the bootloader to unlock properly?
The software build currently on the device is N9750ZSS2ASKB.
Thanks.
Click to expand...
Click to collapse
RMM status of "PRENORMAL". you cann't flash TWRP
kin201303 said:
RMM status of "PRENORMAL". you cann't flash TWRP
Click to expand...
Click to collapse
It's not though. It's on "CHECKING". What's blocking my installation of TWRP?
sjevtic said:
It's not though. It's on "CHECKING". What's blocking my installation of TWRP?
Click to expand...
Click to collapse
see the Image
kin201303 said:
see the Image
Click to expand...
Click to collapse
And more specifically, why isn't the bootloader OEM lock status message following the OEM unlock toggle setting in developer options?
sjevtic said:
And more specifically, why isn't the bootloader OEM lock status message following the OEM unlock toggle setting in developer options?
Click to expand...
Click to collapse
I don't know
I have
After a week (168 hours) of uptime, booting into download mode no longer results in an RMM status message. Although the OEM Unlock toggle in developer options is set to ON, the bootloader still does not reflect this, instead still indicating that the OEM lock is activated. How can I resolve this?
Thanks.
For all that wondered what was going on: the problem here was the lack of a long press of the volume up button on the bootloader unlock confirmation screen to complete the second stage of bootloader unlocking. Though this is clearly explained on the screen, this particular device features bootloader screens in Asian language characters which I sadly didn't understand.
sjevtic said:
For all that wondered what was going on: the problem here was the lack of a long press of the volume up button on the bootloader unlock confirmation screen to complete the second stage of bootloader unlocking. Though this is clearly explained on the screen, this particular device features bootloader screens in Asian language characters which I sadly didn't understand.
Click to expand...
Click to collapse
korean or What?
I have a metropcs Oneplus nord n100 I'm trying to access the the bootloader but oem option in developer mode is greyed out. Also i don't own a pc is there any way i can unlock.bootloader without a pc?
There are a few devices on which the bootloader can be unlocked without the need of a PC and fastboot command sets. For example, many Samsung devices can be bootloader unlocked by going to device Settings>About Phone and tapping Build Number 7 times until Developer Options is enabled. In Developer Options, enabling the OEM Unlock option will unlock the bootloader, thus disabling the layer of protection which restricts flashing of certain device partitions. Other than Samsung, there are some device OEMs and models which also allow bootloader unlocking in this manner. However, on most devices, in addition to enabling OEM Unlock, fastboot mode must be initiated, device and PC synced with a cable, and a command line or command set must be executed.
If your device oem unlock is greyed out, you can try unlocking it using fastboot and recovery mode with the help of a pc.
LegendSayantan said:
There are a few devices on which the bootloader can be unlocked without the need of a PC and fastboot command sets. For example, many Samsung devices can be bootloader unlocked by going to device Settings>About Phone and tapping Build Number 7 times until Developer Options is enabled. In Developer Options, enabling the OEM Unlock option will unlock the bootloader, thus disabling the layer of protection which restricts flashing of certain device partitions. Other than Samsung, there are some device OEMs and models which also allow bootloader unlocking in this manner. However, on most devices, in addition to enabling OEM Unlock, fastboot mode must be initiated, device and PC synced with a cable, and a command line or command set must be executed.
If your device oem unlock is greyed out, you can try unlocking it using fastboot and recovery mode with the help of a pc.
Click to expand...
Click to collapse
Thanks i will do further research and once again thank you for taking the time to reply
Carrier-locked devices generally do not have unlockable bootloaders, or at the very least until 6 months has passed for a SIM unlock in the case with Metro going by how T-Mobile handled bootloader unlocking with the OnePlus 6T. However, that's unconfirmed and I could not find any information on either carrier-locked models for the N100 regarding this matter. So for now, it's a dead end.
yes I'm having the same issue here with the be2015 metropcs variant. They're saying 180 days (6months) till able to unlock this phone. I've been searching for some sort of way around it but no lock as of yet. Please everyone keep us all updated just in case.
when i do
Code:
fastboot oem unlock
I get FAILED (remote: 'Flashing Unlock is not allowed.
I've been trying to follow this guide here with Shizuku but I'm also running into issues. any help here please? Thanks yall
Yeah, that tuturial in the other post that the mod locked, he also deleted the commands. I'm guessing there's an issue that xda doesn't want to be involved in, kinda like writing new imei's. So I guess we're kinda screwed.
I bought this phone cheap, €117 at a discount. And Its EU version, where I can unlock the oem bootloader on this phone.
You can enable OEM unlock in Debug menu with debloat until from girhub, but you cannot unlock bootloader in metro phones.
Even if you have got unlock token, OnePlus says that's imei failed.
So is there any way to unlock this phone from carrier?
meowmee said:
So is there any way to unlock this phone from carrier?
Click to expand...
Click to collapse
if it's metro, it has the unlock app on it; still have to be paid up and 180 days in on your account, though
CandymanCA said:
I have a metropcs Oneplus nord n100 I'm trying to access the the bootloader but oem option in developer mode is greyed out. Also i don't own a pc is there any way i can unlock.bootloader without a pc?
Click to expand...
Click to collapse
Just for the record everyone:
Bugjaeger Premium - Apps on Google Play
Debugging and maintenance tool for Android devices
play.google.com
Bugjaeger Premium actually allows you to use an OTG Connection, (Android-->Android), that enables A Real connection via ADB/Fastboot.
So for all those that have no PC, but have two devices, it is possible to use one to run the ADB or Fastboot consoles and run authentic commands. I use it all the time since a desktop isn't so portable.
It takes a little thinking when it comes to the directories used, but I've easily ran Fastboot oem unlock and flashing commands before on the go
ways2 said:
yes I'm having the same issue here with the be2015 metropcs variant. They're saying 180 days (6months) till able to unlock this phone. I've been searching for some sort of way around it but no lock as of yet. Please everyone keep us all updated just in case.
when i do
Code:
fastboot oem unlock
I get FAILED (remote: 'Flashing Unlock is not allowed.
I've been trying to follow this guide here with Shizuku but I'm also running into issues. any help here please? Thanks yall
Click to expand...
Click to collapse
Tell you the truth, I was in the process of switching out SD Cards in the BE2015 and while I had the SIM/Tray out I saw that the developer options allowed the OEM Unlock toggle to be switched....
The option greyed itself back out once the sim was reinserted, but, I was able to toggle the switch ON before it did all that.
And even greyed out the option remains switched ON now.
For the record.
here your solution
One+_TooL with Grayed out Oem_Unlock (Bootloader Unlock)enabler & Engineer Decrypt
Here is my latest version of My Oneplus Tool . This tool can do almost everything for you. I have added a method to switch the Oem_Unlock switch on Sim locked devices. It will ungray the switch so you can flip it and bootloader unlock. It still...
forum.xda-developers.com
I bought a used unlockable (or it was advertised as such) Motorola Moto G7 Play from Amazon in the hopes of unlocking the bootloader and installing something like LineageOS on it. The model is XT1952-4 and the cid is 0x0000, which is supposed to be unlockable according to their website. In the developer options, Android debugging and OEM unlock are ticked on.
I enter the bootloader (via adb reboot-bootloader in a terminal [Im on FreeBSD] or turning off the phone and holding down the lower volume and power button) and then run fastboot oem get_unlock_data in order to get a string for the unlock code on their website. However, this is where I get stumped:
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.011s]
^ is the result. I have contacted both their forum and via phone and on the phone their higher up told me that the Moto G7 Play cannot be unlocked.. Yeah. So now I'm left with no clue as to what to do, which is why I'm here to ask does anyone have a solution to this? This "unlock data unavailable" error is seldom mentioned and there's no clear answer. Could someone please provide some clarity and/or a solution to this issue? I would preferably not want to have to return this phone and find another after waiting so long for it.
so i was able to, after reading here that a12 allows OEM unlock to not be greyed out anymore, google the OEM unlock and then run the fastboot OEM get_unlock_code and able to get the code. however after entering the imei, code, email and serial number on the unlock token website, it continues to tell me that code or serial number is invalid. however it isn't. everything is correct. anyone have a fix for this?
JohnFawkes said:
so i was able to, after reading here that a12 allows OEM unlock to not be greyed out anymore, google the OEM unlock and then run the fastboot OEM get_unlock_code and able to get the code. however after entering the imei, code, email and serial number on the unlock token website, it continues to tell me that code or serial number is invalid. however it isn't. everything is correct. anyone have a fix for this?
Click to expand...
Click to collapse
Are you on T-Mo or another ROM.
T-Mo requires a token to be emailed to you from OP. The others do not and can be unlocked from fastboot.
Well yea I know. What I'm saying is that on a12 stock tmo the oem unlock toggle is no longer greyed out. Sim locked. I was able to get the fastboot get_unlock_code and use that for the code on the website. When I enter in the unlock code, the serial number, email address and imei, the website complains the unlock code or serial number is invalid even though they aren't. This is the step to get the unlock code email from OP after 1 week.
Superguy said:
Are you on T-Mo or another ROM.
T-Mo requires a token to be emailed to you from OP. The others do not and can be unlocked from fastboot.
Click to expand...
Click to collapse
JohnFawkes said:
Well yea I know. What I'm saying is that on a12 stock tmo the oem unlock toggle is no longer greyed out. Sim locked. I was able to get the fastboot get_unlock_code and use that for the code on the website. When I enter in the unlock code, the serial number, email address and imei, the website complains the unlock code or serial number is invalid even though they aren't. This is the step to get the unlock code email from OP after 1 week.
Click to expand...
Click to collapse
Regardless I was able to do the conversion to EU and unlock that way without needing to sim unlock first since a12 has oem unlock available without sim unlock