Develop Bugs

One M8 (Three UK) network unlocked - can't root?

I want to use the Root call blocker app which requires root access.
HTCdev instructions for root emphasise that 'OEM unlock' should be ticked in developer options before proceeding further. This option is not shown in my developer options screen & when I look at the bootloader screen the top item shows **LOCKED**
I guess this is why OEM unlock isn't shown.
I'm a complete novice & my only reason to root (so far....) is to use that particular call blocker. I have called HTC & they don't seem to know what i'm talking about...they think i'm asking how to get into developer options screen! Any help will be appreciated & explanations in simple terms also

Ah.. you don't reply in other thread but you open a new one.. and I asked moderator to move this to Q&A section.
Why don't you use any call blocker apps that don't require root access ? There are many of them on Play Store.
Anyway .. to root your M8, you need :
1. unlock the bootloader thru http://www.htcdev.com/
2. install TWRP recovery
3. install SuperSU.zip
There is no such thing "OEM unlock" on M8

Hi, Thanks for reply & sorry for posting in wrong section earlier.
The reason I want to use 'root call blocker' is because unlike other such apps it doesn't use the ring & hang up or divert to voicemail method. It kills the call completely & as such avoids the single ring scam which has just started to affect some phones here....mostly Vodaphone users. As yet no one is sure how the scam works but the victims are left with huge phone bills & have never called the number itemised on the bill. So......that's why I want to use that app.
Regarding Htcdev.....I have registered with them, having researched them as probably being the safest for someone with no experience & it is the reason for this post as I quote below step 2 of their instructions
''Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
NOTE: All new HTC devices shipped since One M9 support download mode instead of bootloader mode for this step. And for select HTC devices with Android Lollipop and all devices that receive Marshmallow, you will need to first manually enable OEM unlocking in Developer options in order to allow the bootloader to be unlocked and proceed with the next steps.''
The reason I can't proceed is because my device does not show the option for OEM unlocking....yes I do know how to get to developer options.
I have tried all the ''one click root'' methods & they haven't worked........so......any help?

There is no OEM UNLOCKING on HTC M8, only certain/newer devices have that.
In step 2, they explain how to get to fastboot screen. If your current screen show hboot (highlighted in blue) -- press power once to get to fastboot screen
As long as your screen now is showing fastboot usb (highlighted in red) when connected to PC .. you can proceed to step 5 to run command
fastboot oem get_identifier_token

setup loop with original OS

I got a used Wileyfox Swift which I did a factory reset on using Recovery. As far as I know it is the original OS.
My problem is that it loops over the Google login during setup. I.e. it asks me for login data which I enter. I then use Google Authenticator on another device for two factor authentication. After that it ask me for login data again, and so on.
I've tired to unlock the bootloader but get the following error:
Code:
$ ./fastboot oem unlock
FAILED (remote: oem unlock is not allowed)
I had enabled USB debugging, but did not enable OEM unlock in Developer option. That was before I had it factory reset. I'm not sure if those settings hold after the reset.
What can be done to get past the login loop, or skip it altogether?
Can the bootloader be unlocked at this point, and if so, how?

SM-N9750 bootloader unlock issue

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?

Unlock greyed oem option help

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

Question Bootloader Unlock... Trick?

I vaguely remember a speedbump when unlocking my G7P a couple years back, but cannot recall what it was.
Search gives me many, many, many results that omit anything but a happy ending, are dated platforms and have differing procedures/results.
Procedure I followed:
Fresh XT2025-1 fresh out of the box this morning.
Disabled Google Play Protect & enabled Developer Options + ADB Debugging.
Restarted into Bootloader.
I submitted my fastboot oem get_unlock_code results, clicked the blue button & confirmed scary warranty-now-void pop-up.
Received email from Moto w/ the code. Did it a 2nd time & received same code.
Ran fastboot oem unlock UNIQUE_KEY(w/ 20 digit key that motorola emailed me).
Result: WARNING: This command erases all user data. Please re-run this command to continue. Total time: 0.008s.
Ran fastboot oem unlock UNIQUE_KEY again.
Result: Check 'Allow OEM Unlock' in Android Settings > Developer Options. Total time: 0.007s.
Rebooted & OEM Unlock is still greyed out. Still says oem_locked on Bootloader screen. Boot logo is still generic Moto.
Phone has been on wifi for an hour or so, do not have a SIM @ this time. EDIT: Was on wifi for hours before, as well.
Anyone have any ideas?
PS: I paid full price @ BB w/ no subsidies, just so I can unlock now. Using latest ADB/platform-tools_r31.0.2.

After ~15 minutes & my multi-edits to my post, the unlock toggle became available. Was just impatient.
Mods, please delete post unless you think it may be useful for reference.

googleverifysux said:
After ~15 minutes & my multi-edits to my post, the unlock toggle became available. Was just impatient.
Mods, please delete post unless you think it may be useful for reference.
Click to expand...
Click to collapse
In my case, it became available soon after I connected to wifi.
I tried many things, but I couldn't get the option active without wifi connection.
I don't know if having SIM card influence this, because I tried everything without SIM, as well.
With moto e6, I had the option without wifi (and without SIM).