Develop Bugs

How to Enable OEM Unlock without enabling USB debugging/OEM status

didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.

You can't enable OEM unlock by fastboot/recovery.
But there's another way to rescue your phone.
So
Can you boot into recovery? (Bootloader mode switch to recovery mode using volume keys and press power to choose it)
If it started and you would see an Android with an red triangle press power and hit volume+ to turn on menu. If it works you are safe.
Then download OTA image from Android developers page (OTA, not factory), launch command line (I don't know how it works on Windows, I've never flashed anything on Windows )
And you will need to flash this OTA image by executing adb sideload nameofpackage.zip
Remember to choose adb sideload in recovery first and then executing a command. It should flash and your phone should work.
Good luck!
Wysłane z mojego Nexus 5X przy użyciu Tapatalka

I cant boot in recovery mode... When I tried to boot in recovery stuck in google logo then power off...

Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka

No not in warranty....
I contact in LG service center they said chage the motherboard and cost around 170$
That amount so big??

Is there any method to unlock in this case from fastboot?
I need to unlock for custom kernel to flash.
Im on bootloop and oem locked in the system (befor got bootloop)
Help

Domin_PL said:
Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone

There where some hidden fastboot commands on XDA. Maybe you can try some of them to see if they can go around this limitation.
Sent from my Nexus 5X using Tapatalk

akins0405 said:
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone
Click to expand...
Click to collapse
I have the same issue mentioned above. Downloaded Nexus Root Toolkit and i have tried unlock through Nexus Root Toolkit. It seems failure. Because, After detecting my device it reboots and my phone reboots and shows the google logo and reboot again and again... My phone will not boot into recovery mode. While we click on it, it shows google logo and reboots again and again... Is there any solution for this?

OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this

Seems options are very limited now
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..

I got the same issue.
Nexus 5X has no activated "Allow OEM Unlock".
I tried with the Nexus Root Toolkit.
When I try to unlock Bootloader or the option "Fix Bootloop" he wants me to put the phone into Fastboot.
When I put phone into Fastboot he recognizes it and then restarts the phone. From now on nothing more happens, because noe the bootloop is "active" again.
Recovery Mode is not working, too.
Before I can access it, bootloop starts.
Sound as the same issue as @tomsonmathewv has.
Can someone help me?
EDIT:
While I tried some other solutions my Nexus 5X booted and booted.
And suddenly it booted one time to the Pattern screen. I entered the pattern and waited again for the bootloop after google animation.
But then the google animation finished and a short black screen with s small blue line in the middle of the display appeared. Looked like a "graphics error". But then immediately the normal phone idle screen appeared. The phone started!
I immediately went to the DEV-Options and Allowed OEM-unlock. And I took screenshots of the current configuration.
The current Android is 8.1
Is it recommended to flash an older version of Android to prevent a new Bootloop?

I had the same issue after the latest Android update on my Nexus 5X.
Have you left the device in charge before it manage to start?
Thanks
EDIT: Solved leaving it unplugged.

Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.

aadeekhan79 said:
Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.
Click to expand...
Click to collapse
NRT isn't going to work unless you previously allowed for oem unlock in developer options. If you haven't done that and you can't boot into recovery or the system you're kind of sol.
Sent from my [device_name] using XDA-Developers Legacy app

Shuhan44 said:
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..
Click to expand...
Click to collapse
does that software (dc unlocker) actualy works? i've got the same issue with honor 8 pro, which opt. you have selected.

In my case before my N5X started bootlooping I allowed OEM unlock but didn't enabled USB Debugging Mode in Developer options. Is there a way to unlock bootloader with USB Debugging Mode disabled? I want to try the UNBLOD tool, but unlocked bootloader is a requirement.

xrehpicx said:
OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this
Click to expand...
Click to collapse
Hi
I also need help of a slightly different nature. I'm somehow locked out of my Huawei P10 whereby my unlock pattern is no longer recognized. USB debugging is not enabled. What are my option as i really do not want to factory reset the phone, did not backup data. Coincidentally enough, this occurred after the latest software update. Please can someone help me.

Thanks
Thanks

Roshan0746 said:
didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.
Click to expand...
Click to collapse
Every phone have boot. Img system . I also have a same fault redmi k20 pro. But i succeed to give rebirth it. Try to using fastboot commands only and flash fastboot flash boot boot. Img it will work definitely

[GLOBAL] Unbrick fix

Following this new tutorial (ONLY for GLOBAL versions!) you can continue enjoying your Xiaomi Redmi Note 8 Pro, so...
Click to expand...
Click to collapse
LET'S GO!
You'll need:
1. Download the file to your PC "MiFlashPro" (v4.3.1106.23)
2. Download firmware stock "begonia_global_images_V10.4.2.0.PGGMIXM"
3. An authorized Xiaomi Mi Service account.
Download and decompress the stock firmware on your desktop "begonia_global_images_V10.4.2.0.PGGMIXM" and follow this steps:
1.1- Instal and run MiFlashPro.
1.2- Go to the installation path in: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\mi), execute as administrator the file "account_auth.exe" and log into an authorized Xiaomi service account.
1.3- Go to the installation path in: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool), execute"flash_tool.exe".
(The program will open and you will have to select three files)
2.1- Download-Agent: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool/MTK_AllInOne_DA_mt6765_mt6785.bin)
2.2- Scatter-loading File: On your desktop, inside the folder "begonia_global_images_V10.4.2.0.PGGMIXM.... images", is called MT6785_Android_scatter.txt
3.3- Authentication File: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool/auth_sv5.auth)
1.4- Click on the "Download" button
1.5- With the phone turned off... connect the USB cable to the PC (ONLY TO THE PC, the other end you still don't connect).
1.6- Press the VOL + button on your phone and now connect the cable to your phone meanwhile you press the VOL + button
1.7- The firmware flashing process will start, wait a bit.
Now you can enjoy again your Xiaomi Redmi Note 8 Pro

klurosu said:
LET'S GO!
You'll need:
1. Download the file to your PC "MiFlashPro" (v4.3.1106.23)
2. Download firmware stock "begonia_global_images_V10.4.2.0.PGGMIXM"
3. An authorized Xiaomi Mi Service account.
Download and decompress the stock firmware on your desktop "begonia_global_images_V10.4.2.0.PGGMIXM" and follow this steps:
1.1- Instal and run MiFlashPro.
1.2- Go to the installation path in: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool\mi), execute as administrator the file "account_auth.exe" and log into an authorized Xiaomi service account.
1.3- Go to the installation path in: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool), execute"flash_tool.exe".
(The program will open and you will have to select three files)
2.1- Download-Agent: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool/MTK_AllInOne_DA_mt6765_mt6785.bin)
2.2- Scatter-loading File: On your desktop, inside the folder "begonia_global_images_V10.4.2.0.PGGMIXM.... images", is called MT6785_Android_scatter.txt
3.3- Authentication File: (C:\Program Files (x86)\MiFlashPro\SP_Flash_Tool/auth_sv5.auth)
1.4- Click on the "Download" button
1.5- With the phone turned off... connect the USB cable to the PC (ONLY TO THE PC, the other end you still don't connect).
1.6- Press the VOL + button on your phone and now connect the cable to your phone meanwhile you press the VOL + button
1.7- The firmware flashing process will start, wait a bit.
Now you can enjoy again your Xiaomi Redmi Note 8 Pro
Click to expand...
Click to collapse
Where can we get authorised account for free

girishjangir7 said:
Where can we get authorised account for free
Click to expand...
Click to collapse
sadly there is NOT auth accounts for free

I think that there already was a guide describing this process. But thanks anyway.

polfrank said:
I think that there already was a guide describing this process. But thanks anyway.
Click to expand...
Click to collapse
There is NO guide for that.
Or you have a partner's Xiaomi business or you must to spend 200 bucks (more or less).
One of this persons will CREATE an service authorized account for you.
That's it
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
There is NO guide for that.
Or you have a partner's Xiaomi business or you must to spend 200 bucks (more or less).
One of this persons will CREATE an service authorized account for you.
That's it
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
I meant this thread in XDA:
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
which explains basically the same thing.

klurosu said:
There is NO guide for that.
Or you have a partner's Xiaomi business or you must to spend 200 bucks (more or less).
One of this persons will CREATE an service authorized account for you.
That's it
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
Huh, it's not just binding your PRIVATE pc with your Mi account. Auth_whatever.exe allow me to login without any errors, ready to flash message not red unauthorised account warning.
I think my account authorized because either I plead to them for giving me authority to FLASH when on RN3PRO BIG MESS CASE, I must apply form in CHINESE (there was tutorial because I dunno any Chinese). I need one because very hardbrick after flashing alpha rom, yes one dead phone with no fastboot / recovery revived :silly:
Either that or because my account bonded and already unlock dozens different models devices (I am reseller, some people especially old ppl and technology illiterate ones let me managed their phones account).
Binded account unfortunately won't be able to be used on other pc. I got a notice that I will only got limited access for a week or so if I change the pc I Binded, so sharing is impossible.
If you ever ask authority to flash in Chinese and got accepted (I need to wait 5 days after submitting request) chance you got one authorized account

Hello,
I tried to use my standard mi account, just in case (spoiler, didn't work) and the download process is stuck at the state it is just before pluging the phone. I mean, pluging the phone does not start anything, but still my computer sees the phone. The flash tool does not display any error about authorization.
Does anyone know if it's a normal behaviour ? It sounds a bit strange not to display any error.

ScarletVeil said:
Huh, it's not just binding your PRIVATE pc with your Mi account. Auth_whatever.exe allow me to login without any errors, ready to flash message not red unauthorised account warning.
I think my account authorized because either I plead to them for giving me authority to FLASH when on RN3PRO BIG MESS CASE, I must apply form in CHINESE (there was tutorial because I dunno any Chinese). I need one because very hardbrick after flashing alpha rom, yes one dead phone with no fastboot / recovery revived :silly:
Either that or because my account bonded and already unlock dozens different models devices (I am reseller, some people especially old ppl and technology illiterate ones let me managed their phones account).
Binded account unfortunately won't be able to be used on other pc. I got a notice that I will only got limited access for a week or so if I change the pc I Binded, so sharing is impossible.
If you ever ask authority to flash in Chinese and got accepted (I need to wait 5 days after submitting request) chance you got one authorized account
Click to expand...
Click to collapse
Could you pm me from where you got the Chinese application form and tutorial? (any website address?) I need it badly, my RN8PRO bricked

Auth Account
klurosu said:
sadly there is NOT auth accounts for free
Click to expand...
Click to collapse
Where can we buy an authorized mi account officially

Thread cleaned
Please do not recommend/discuss/advertise paid remote unlock services on XDA as we do not support such business.
Please read the FORUM RULES especially those:
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links, all forms of crypto-mining and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
Thank you for your understanding.
strongst
Forum Moderator

Hi, my r8 pro has bricked recently, i'm really scared, can you help me? i already tried these options:
°boot > recovery = black screen
°boot > fastboot = black screen
°boot = black screen
°i disassembly my cellphone and disconected and re conected the battery but nothing
°i'm trying to drain battery power to 0% because it was charged to 80% and now i'm connecting some things to negative and positive parts of the cable of the battery to consume energy and drain the battery
°i tried "test point" but it is the same has enter to the recovery (vol+ pwr) because it boot to the recovery, and it ask me for MI account authorized when i try to flash stock rom in sp download tool
my redmi note 8 pro only led blinks when i connect the usb to my pc or when i charge it.
Can you help me? please. my discord
zumboy#2354

Haven't they changed the need for an authorized account? I bricked my RN8P and tried this.. the first time I used my mi account I got an error upon login, but the second time I tried it a bit later, it worked.. Does this mean I have an authorized account now? The unbrick process worked like a charm btw. I however, had the preloader files installed as stated somewhere else on this forum (preloader_begonia and lk).

Krakiathan said:
Haven't they changed the need for an authorized account? I bricked my RN8P and tried this.. the first time I used my mi account I got an error upon login, but the second time I tried it a bit later, it worked.. Does this mean I have an authorized account now? The unbrick process worked like a charm btw. I however, had the preloader files installed as stated somewhere else on this forum (preloader_begonia and lk).
Click to expand...
Click to collapse
when you tried that? i have a bricked r8 pro without authorized account.

error:status brom cmd fail(0xc0060005)请问这个怎么解决？

ScarletVeil said:
I think my account authorized because either I plead to them for giving me authority to FLASH when on RN3PRO BIG MESS CASE, I must apply form in CHINESE (there was tutorial because I dunno any Chinese). I need one because very hardbrick after flashing alpha rom, yes one dead phone with no fastboot / recovery revived :silly:
If you ever ask authority to flash in Chinese and got accepted (I need to wait 5 days after submitting request) chance you got one authorized account
Click to expand...
Click to collapse
Is that the same case as The Great Anti Rollback Pandemic? I've messed up my Note 5 Pro and missed the chance to apply for special permission, so got that bad boy resurrected with a bypassed xiaomi flash.

kekesed97 said:
Is that the same case as The Great Anti Rollback Pandemic? I've messed up my Note 5 Pro and missed the chance to apply for special permission, so got that bad boy resurrected with a bypassed xiaomi flash.
Click to expand...
Click to collapse
That is all thats needed for RN8 Pro as well.

Stuck in recovery
Hi guys
i'm stuck with my RN8P CN, I've made mistakes while thinking I have a global version but instead I have CN version. So now my phone is stuck with no rom and I have thestock recovery, the bootloader is locked, fastbook is ok.
But when i want to use mi unlock to install TWRP and the stock rom it failed saying "please add your account in MIUI settings".
How can i do that without a rom ? Or so, do you have a guide for getting back a stock phone with stock recovery/rom ?
Thanks in advance guys
Gary

GaryBogard said:
Hi guys
i'm stuck with my RN8P CN, I've made mistakes while thinking I have a global version but instead I have CN version. So now my phone is stuck with no rom and I have thestock recovery, the bootloader is locked, fastbook is ok.
But when i want to use mi unlock to install TWRP and the stock rom it failed saying "please add your account in MIUI settings".
How can i do that without a rom ? Or so, do you have a guide for getting back a stock phone with stock recovery/rom ?
Thanks in advance guys
Gary
Click to expand...
Click to collapse
Unfortunately, there is no helping as per today for your condition. Your only choises is:
Go to Xiaomi Service Center nearby,
Buy a Third Party smart box based flash solution (it cost fortune, but worth for investment if you see your smartphone as "toys").
Buy a Third Party account to authenticate flash with third party flash solution (No smartbox needed, and cost a fraction of fortune).
Go to a nearest phone repair shop (They usually have one of two flash solution above, cost around $20-$30, depends on your region)
Use a Remote-based flash solution (You connect your phone to your computer, repairman will ask you to install necessary tools, and control your PC via remote desktop)
Buy a new phone (totally cost an arm and leg)
As none of solution above is supported by this community, you will have to go on your own.
Cheers.

Struggling to unlock booloader: getting weird barcodes

I am following the instructions from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I've downloaded Motorola drivers for Mac, as well as platform-tools. I am booting the phone to booloader but then a weird barcode shows up: imgur.com/a/8sT2lds
Any idea how to make progress from there? By the way my phone model is XT2029-2

Nycticorax said:
I am following the instructions from motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I've downloaded Motorola drivers for Mac, as well as platform-tools. I am booting the phone to booloader but then a weird barcode shows up: imgur.com/a/8sT2lds
Any idea how to make progress from there? By the way my phone model is XT2029-2
Click to expand...
Click to collapse
Would like to know it too. Passed some days searching the web for a answer, and got none. The only thing I get when scanning the barcode is a number that AFAIK doesn't match any serial nor anything at all in the phone; just a number from what I can tell. Using fastboot oem get_unlock_data doens't work at all too, I just get a "command unknown" error returned from fastboot. Tried different drivers, none seemed to work, and the only ones that did, gave me the barcode and the fastboot error when trying to unlock. A very weird error, this one; fastboot devices work just fine, fastboot getvar all too, so it really doesn't seem like a fastboot or driver issue. My last try was this article (https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/) to see if I could get a list of the phones OEM commands and figure out how to unlock it. Tried to extract the bootloader from the firmware I downloaded online, using a tool I found on the forum, but no success until now. Will try to root the phone and extract it as it is shown in the tutorial to see if I can get more lucky. I saw somewhere that there's an app called sunshine that was used to unlock some older models, maybe you wanna try that too. I won't, because it's paid and I don't have the money to pay for it . Anyway, I'll try the bootloader extracting and see how that works, and depending on the output, maybe I'll post a tutorial here.

Def4lt_ said:
Would like to know it too. Passed some days searching the web for a answer, and got none. The only thing I get when scanning the barcode is a number that AFAIK doesn't match any serial nor anything at all in the phone; just a number from what I can tell. Using fastboot oem get_unlock_data doens't work at all too, I just get a "command unknown" error returned from fastboot. Tried different drivers, none seemed to work, and the only ones that did, gave me the barcode and the fastboot error when trying to unlock. A very weird error, this one; fastboot devices work just fine, fastboot getvar all too, so it really doesn't seem like a fastboot or driver issue. My last try was this article (https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/) to see if I could get a list of the phones OEM commands and figure out how to unlock it. Tried to extract the bootloader from the firmware I downloaded online, using a tool I found on the forum, but no success until now. Will try to root the phone and extract it as it is shown in the tutorial to see if I can get more lucky. I saw somewhere that there's an app called sunshine that was used to unlock some older models, maybe you wanna try that too. I won't, because it's paid and I don't have the money to pay for it . Anyway, I'll try the bootloader extracting and see how that works, and depending on the output, maybe I'll post a tutorial here.
Click to expand...
Click to collapse
Ok so after analysis the barcode just the IMEI associated with my SIM card's slot. (This phone has two SIM card slots.) Nothing interesting about it, I think.
Also it seems that Motorola does not support unlocking this bootloader as it does for other phones; in fact "motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a" is just a hub for any phone listed at "support.motorola.com/us/en/solution/MS87215", and this one is not on the list. I am not aware of any way to unlock the bootloader in these circumstances.
Please let me / us know if you are more successful than me. For now I will consider this phone not rootable via this method.
PS: The furthest I've been: `fastboot oem get_unlock_data` returns a blank line as if the mobile was working. No error message or anything.
PPS: What do you mean by "extracting the bootloader"? What rooting method is extracting the bootloader part of?

The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs

Nycticorax said:
Ok so after analysis the barcode just the IMEI associated with my SIM card's slot. (This phone has two SIM card slots.) Nothing interesting about it, I think.
Also it seems that Motorola does not support unlocking this bootloader as it does for other phones; in fact "motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a" is just a hub for any phone listed at "support.motorola.com/us/en/solution/MS87215", and this one is not on the list. I am not aware of any way to unlock the bootloader in these circumstances.
Please let me / us know if you are more successful than me. For now I will consider this phone not rootable via this method.
PS: The furthest I've been: `fastboot oem get_unlock_data` returns a blank line as if the mobile was working. No error message or anything.
PPS: What do you mean by "extracting the bootloader"? What rooting method is extracting the bootloader part of?
Click to expand...
Click to collapse
That's weird. My barcode number doesn't seem to match any numbers at all, serial, IMEI, nothing. I'll double check it to see if I have missed something. Never got this blank line, would be happy if you shared how you achieved it, maybe there could be some insight I can get from the process. Answering the question about the bootloader, the extraction isn't a part of a rooting method, it's only something I'm trying in order to get the list of oem fastboot commands of the phone. Those are manufacturer-specific, aren't listed anywhere, and differ from model to model. The method I'm using is the one from the article I pointed in my previous answer. Anyway, if it takes me anywhere, I'll bring an update about it with details.
---------- Post added at 23:36 ---------- Previous post was at 23:04 ----------
sd_shadow said:
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
The barcode is from entering the bootloader. Any method that gets you there shows it. At first I thought it was a driver-related bug, but after some experimentation it seems like whenever the device is recognized by fastboot, it shows this barcode; So it appears to be a bootloader-related thing (I never saw nothing like it, so just guessing for now). Also tried the method from the Motorola website, and I really wish it had worked as expected, but what it seems to me is that MediaTek devices are a pain in the ass in general for this kind of thing. The device doesn't recognizes the oem commands sent through fastboot as valid (And yes, OEM Unlocking is properly enabled under Developer Settings). Here's a screenshot from a powershell session showing the results of trying the commands. Notice how the device is correctly recognized by both adb and fastboot, only the unlocking commands doesn't work: https://pasteboard.co/JnW4cvK.png

sd_shadow said:
The official list of devices that can be unlocked has never been complete.
Usually all moto models can be unlocked, except Carrier branded devices or those on Amazon software channel.
Those getting the barcode screen, is that from
Pressing the volume down button and power on, or
adb reboot bootloader
?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
In my case the barcode shows up whenever I reach fastboot, whether via booting with [vol up + power] and then selecting fastboot, or via adb reboot bootloader. I've tried several barcode recognition apps and 2 out of 3 confirm it's my IMEI.

Nycticorax said:
In my case the barcode shows up whenever I reach fastboot, whether via booting with [vol up + power] and then selecting fastboot, or via adb reboot bootloader. I've tried several barcode recognition apps and 2 out of 3 confirm it's my IMEI.
Click to expand...
Click to collapse
Did you try
Code:
fastboot flashing unlock_critical
according to this thread... it is for e6 plus. May be it works with e6 play.
https://old.reddit.com/r/androidroot/comments/f6c5k5/unlock_bootloader_moto_e6_plus/fupyalw/

No,
Code:
fastboot flashing unlock critical
does not work. And no, we shouldn't assume that a method meant for the e6 plus works for the e6 play.

Phone in red state not able to change settings
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/

glensbo said:
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
Click to expand...
Click to collapse
It is not clear to me what you did exactly. The step where we -- the others participants to this post and I -- are stuck is [2] here below:
boot to fastboot by running `adb reboot bootloader` from a command line on a connected and turned on device
get the OEM unlock code by doing `fastboot oem get_unlock_data` from a connected device under the fastboot interface
exchange the unlock code on the motorola support site and input that code to confirm bootloader unlock

glensbo said:
I have struggled with the same problems as above. I am not able to get into the developer mode as I only have access to the recovery screen. Anybody who knows how to do that from the recovery screen - perhaps using terminal?
I have been able to enter into the phone by adb sideload filename.zip and the phone acknowledged connection, but the upload failed, probably due to I am not able to unlock the phone from the red state/Android Recovery. It is running bali-reteu/bali9/POAS29.550-81-1/
Click to expand...
Click to collapse
Got a little further as the code:
#fastboot flash unlock_critical Filename.zip#
the phone replied - Transferring and Transmission OK .... time etc
But I got an error sadly to say:
Failed (remote: not allowed in locked state) so I'm back to basics as I cannot open the state from the recovery mode (as of yet)

glensbo said:
Got a little further as the code:
#fastboot flash unlock_critical Filename.zip#
the phone replied - Transferring and Transmission OK .... time etc
But I got an error sadly to say:
Failed (remote: not allowed in locked state) so I'm back to basics as I cannot open the state from the recovery mode (as of yet)
Click to expand...
Click to collapse
Okay, I would like to be positive and call that a progress but the whole point of steps (2-3) is to have it unlocked so that you can proceed to root to flashing it the way you're trying to.
So I am pretty pessimistic on that one. To me it looks like a case of a cheap phone a company has no real urge to make easy to unlock.

Nycticorax said:
It is not clear to me what you did exactly. The step where we -- the others participants to this post and I -- are stuck is [2] here below:
boot to fastboot by running `adb reboot bootloader` from a command line on a connected and turned on device
get the OEM unlock code by doing `fastboot oem get_unlock_data` from a connected device under the fastboot interface
exchange the unlock code on the motorola support site and input that code to confirm bootloader unlock
Click to expand...
Click to collapse
Sorry got carried away finding a group dealing with the same problem as I have. And not skimming but reading the text I can confirm that I am stuck at the same place. Sorry for the interruption. I will revert if/when I have something new.

glensbo said:
Sorry got carried away finding a group dealing with the same problem as I have. And not skimming but reading the text I can confirm that I am stuck at the same place. Sorry for the interruption. I will revert if/when I have something new.
Click to expand...
Click to collapse
It's okay. I hope one of us can find something useful. Let Root, the God of Hacks, send His best love waves to you guys

wow No Help

Biniesuschristos said:
wow No Help
Click to expand...
Click to collapse
Just curious do you know what software Channel your phone is on?
The software Channel might be listed in
Settings/ about phone.
Or try
Code:
fastboot getvar all
While in fastboot mode
ro.carrier = Software Channel
Sent from my ocean using XDA Labs

You didn't ask me but perhaps it might help you help us:
Code:
reteu
for me.

I'm don't actually know anything regarding rooting mobile devices but i'm going to post some of my experience thinking it might help someone who actually knows what to do.
I've been having the same issue while trying to unlock the bootloader.
As it seems all of the fastboot commands are working fine except the OEM ones which is strange considering that i'm sure i toggled the OEM Unlock on the dev. options, just like some members commented already.
Regarding the barcode it shows as soon as i connect the device via USB in Fastboot mode, and it shows up when i use "adb reboot bootloader" too, but it wasn't showing before i updated the USB Drives so i could find the device via "fasboot devices" (the phone wasn't showing before i did it).

pontiacus said:
I'm don't actually know anything regarding rooting mobile devices but i'm going to post some of my experience thinking it might help someone who actually knows what to do.
I've been having the same issue while trying to unlock the bootloader.
As it seems all of the fastboot commands are working fine except the OEM ones which is strange considering that i'm sure i toggled the OEM Unlock on the dev. options, just like some members commented already.
Regarding the barcode it shows as soon as i connect the device via USB in Fastboot mode, and it shows up when i use "adb reboot bootloader" too, but it wasn't showing before i updated the USB Drives so i could find the device via "fasboot devices" (the phone wasn't showing before i did it).
Click to expand...
Click to collapse
Windows 10?
Sent from my ocean using XDA Labs

@sd_shadow: Do you think it looks like a bootloader you could unlock?

UNBRICK Redmi Note 8 Pro (Begonia) No Recovery, No fastboot just LED.

Earlier this year i bricked a RN8P brought in by a customer to convert to global rom. After applying and waiting to unlock bootloader for 168 hours, it was successful then installing the global rom the device disconnected went into a total black screen no recovery, no fastboot just a white led when connected. after so many researches this forum and google there was nothing to write home about. i was frustrated and sad the only solution was to get someone with and authorization account which was $30 and couldn't afford. Customer was on my neck and was already talking of paying for the device then lo and behold today i was reading through some post on unbrick and i bumped into a solution i thought wasnt worth it as i have tried it buh never paid attention too. its a post by @white_3n on https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unbrick-stuck-da-mode-authorised-t4000433/page5. here is it in details:
1- open phone (this aint necessary)
2- disconnect the battery (this aint necessary)
3- wait 10 seconds (this aint necessary)
4- connect the battery (this aint necessary)
5- Press and hold power and volume-
6- Plug to PC
7- Wait for the second vibration (longer).
8- Download MiFlash2018-5-28-0 https://mva2.androidfilehost.com/dl/l-WKOxk-I6mBdYiEVPDMUQ/1598950844/8889791610682902064/MiFlash20181115.zip?
9- Download https://mifirm.net/download/3520
10- Extracted the firmware as it comes in a .TGZ format
11- then open MiFlash2018-5-28-0
12- Click on refresh to be sure its on fastboot mode
13- then select and locate file you have extracted in 10
14- then select clean at the bottom right side of the MiFlash2018-5-28-0
15- Flash
Viola RN8P is back to life

The phone must have the bootloader unlocked?

Goatzilla47 said:
The phone must have the bootloader unlocked?
Click to expand...
Click to collapse
yes bootloader already unlocked before brick

Hello Mdutsu,
Are you saying that removing the battery and putting it back gave you access back to fastboot (power + volume-) ?
I'm in your situation, without access to fastboot and only EDL falshing seems to be an option, but I have to pay someone with an authorized account...
I'd like to confirm that as you void warranty by removing the back cover.

hi this just happen to me i try you're method but screen stay black and when i connect to computer i just hear the connect/disconnect sound and mi tools don't find the phone what can i do ?

I had the same exact issue a few days ago. follow the instructions on this video and it should get you back up and running. Worked like a charm for me. ask me if have any questions.
There is a youtube video that will show you how to fix it but i cant paste the URL because it adds the entire video. search this in youtube
How To Unbrick Redmi Note 8 Pro || Flash Stock Rom using SP Flash Tool 100% Working without Mi Auth​

MidNight0780 said:
I had the same exact issue a few days ago. follow the instructions on this video and it should get you back up and running. Worked like a charm for me. ask me if have any questions.
There is a youtube video that will show you how to fix it but i cant paste the URL because it adds the entire video. search this in youtube
How To Unbrick Redmi Note 8 Pro || Flash Stock Rom using SP Flash Tool 100% Working without Mi Auth​
Click to expand...
Click to collapse
This video saved me too!

Bro I created a new account here just to thank you, my RN8PRO gave up and you saved me. THANK YOU SO MUCH
Mdutsu said:
Earlier this year i bricked a RN8P brought in by a customer to convert to global rom. After applying and waiting to unlock bootloader for 168 hours, it was successful then installing the global rom the device disconnected went into a total black screen no recovery, no fastboot just a white led when connected. after so many researches this forum and google there was nothing to write home about. i was frustrated and sad the only solution was to get someone with and authorization account which was $30 and couldn't afford. Customer was on my neck and was already talking of paying for the device then lo and behold today i was reading through some post on unbrick and i bumped into a solution i thought wasnt worth it as i have tried it buh never paid attention too. its a post by @white_3n on https://forum.xda-developers.com/re...brick-stuck-da-mode-authorised-t4000433/page5. here is it in details:
1- open phone (this aint necessary)
2- disconnect the battery (this aint necessary)
3- wait 10 seconds (this aint necessary)
4- connect the battery (this aint necessary)
5- Press and hold power and volume-
6- Plug to PC
7- Wait for the second vibration (longer).
8- Download MiFlash2018-5-28-0 https://mva2.androidfilehost.com/dl...0844/8889791610682902064/MiFlash20181115.zip?
9- Download https://mifirm.net/download/3520
10- Extracted the firmware as it comes in a .TGZ format
11- then open MiFlash2018-5-28-0
12- Click on refresh to be sure its on fastboot mode
13- then select and locate file you have extracted in 10
14- then select clean at the bottom right side of the MiFlash2018-5-28-0
15- Flash
Viola RN8P is back to life
Click to expand...
Click to collapse

Bootloader UNLOCKED - need ROM

Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.

RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com

RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Are you use EMUI 9.1 to unlock Bootloader ?

RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here is my p20 pro , can I unlock the Bootloader ?

ArthurTsai said:
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com
Click to expand...
Click to collapse
Awesome! Thanks a lot. I've found an UNOFFICIAL rom yesterday and flashed it, but looks like I'll be doing it all over again today with this one.

ArthurTsai said:
Are you use EMUI 9.1 to unlock Bootloader ?
Click to expand...
Click to collapse
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.

RafBB said:
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.
Click to expand...
Click to collapse
Things are not that simple. The HiSuite on Mac have been updated.
I can't find the button that can roll back or check for update after this.
Maybe I should try HiSuite on Windows.

I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?

ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
You *should be able to unlock it with EMUI 9. I rolled it back to 8, just to find out later on I need 9.0.0.159 anyway. So I used HiSuite to update it to 9 - but it wasn't the version I wanted and also doing this in HiSuite removed my bootloader code, so I ended up using HCU Client on EMUI 9 and it worked just fine. After that I used DC Phoenix to flash the 9.0.0.159 (bootloader stayed unlocked). It was a pain, but yeah you SHOULD be able to unlock it with EMUI9.

ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
Here's a log from unlocking 9.0.0.168...

Just to let you know that official ROM (lineage-16.0-20210211-nightly-charlotte-signed.zip) is not working on my P20 Pro. It crashes on the first boot. I'm back with (lineage-16.0-20190217_125340-UNOFFICIAL-charlotte.zip) I believe it was made made by LuK1337. Works great. I use it with open gapps pico version.

guys, this is p20 non-pro forum.
why are you discussing this here?