Bootloader unlock - Xiaomi Mi A3 Questions & Answers

I know that the bootloader of most, if not all, Xiaomi smartphones can be unlocked. However, in most cases, this means opening a Xiaomi account and waiting a few weeks to receive a bootloader unlock code, which can only be used by a special Windows app. I prefer to do it in Ubuntu Linux, using the default Google Android way, via a simple ADB unlock, which is possible for my current Xiaomi Android One phone, the Mi A1.
Even if there's currently no custom ROM available, I can tweak the phone by installing some custom configuration files, which is only possible if I can gain root access (not necessarily to "root" the phone for online Android apps).
I am willing to overlook the one major defect of the phone if the phone can be unlocked purely by ADB. So has anybody successfully unlocked the bootloader of the phone? Is the unlock process the same as for the Mi A1, something like "adb unlock bootloader" (not sure about the exact commands as I don't have ADB currently installed)?

This is Xiaomi Android One phone, it doesn't required an Xiaomi account or requesting unlock code...just enable Developer Option, enable OEM unlock and you can unlock the bootloader via adb...

iPusak Gaoq™ said:
This is Xiaomi Android One phone, it doesn't required an Xiaomi account or requesting unlock code...just enable Developer Option, enable OEM unlock and you can unlock the bootloader via adb...
Click to expand...
Click to collapse
Thanks. I suspect that is the case. I just want to be sure Xiaomi policy hasn't changed, because I read the bootloader of most Nokia Android One phones cannot be unlocked.

Just execute this command to unlock bootloader "fastboot flashing unlock"

XaviBest said:
Just execute this command to unlock bootloader "fastboot flashing unlock"
Click to expand...
Click to collapse
And second command "fastboot flashing unlock_critical" for full unlock. I used both commands for unlock my Mi A3 bootloader

Will unlocking bootloader block future OTA?
Thanks!

Goldenmeadow said:
Will unlocking bootloader block future OTA?
Thanks!
Click to expand...
Click to collapse
No, OTA update engine doesn't check bootloader status . But it will break Safetynet - you'll need to use Magisk or custom kernel to pass the Safetynet.

Related

Can't get Bootloader Unlock permission!!!

Hello everyone,
I applied for permission to unlock my RN3(kenzo) bootloader around 3 weeks back, and still haven't got any message from Xiaomi. I tried going on without it, but the MiFlash unlock tool can't verify my device (after 50% progress it displays this message). Now I can't even seem to apply again for this permission. This is what happens :
I click the 'Unlock Now' button on this page:
http://en.miui.com/unlock/
And instead of applying for unlock permission page it takes me to this page :
http://en.miui.com/unlock/download_en.html
Where I can only download the MiFlash tool.
I have been trying this for days now but it can't seem to work.
Utterly frustrated, I have came to seek help on this forum. Hope you guys can help me get over this hurdle.
Regards.
[Attached are the screen shots of both pages]
hamzaalijoiyah said:
Hello everyone,
I applied for permission to unlock my RN3(kenzo) bootloader around 3 weeks back, and still haven't got any message from Xiaomi. I tried going on without it, but the MiFlash unlock tool can't verify my device (after 50% progress it displays this message). Now I can't even seem to apply again for this permission. This is what happens :
I click the 'Unlock Now' button on this page:
http://en.miui.com/unlock/
And instead of applying for unlock permission page it takes me to this page :
http://en.miui.com/unlock/download_en.html
Where I can only download the MiFlash tool.
I have been trying this for days now but it can't seem to work.
Utterly frustrated, I have came to seek help on this forum. Hope you guys can help me get over this hurdle.
Regards.
[Attached are the screen shots of both pages]
Click to expand...
Click to collapse
SSame thing happening to me. I didn't even applied once for unlocking. Still I can't request for unlock permission. Always directs me to download page Miunlock tool.
Had to unlock unofficially
You could try another account.
Dr. Joy Das said:
SSame thing happening to me. I didn't even applied once for unlocking. Still I can't request for unlock permission. Always directs me to download page Miunlock tool.
Had to unlock unofficially
Click to expand...
Click to collapse
And how did you do that?
Maybe you could point out respective thread!!!
hamzaalijoiyah said:
And how did you do that?
Maybe you could point out respective thread!!!
Click to expand...
Click to collapse
Here you go: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
theoneofgod said:
Here you go: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
Click to expand...
Click to collapse
Thanks a lot.
theoneofgod said:
You could try another account.
Click to expand...
Click to collapse
You mean another I should sign up for another MI account and again apply for unlocking permission??
hamzaalijoiyah said:
You mean another I should sign up for another MI account and again apply for unlocking permission??
Click to expand...
Click to collapse
Yes, that's an option. Seems this unlocking the bootloader thing is a pain for a lot of people.
theoneofgod said:
Yes, that's an option. Seems this unlocking the bootloader thing is a pain for a lot of people.
Click to expand...
Click to collapse
Yeah it is. I previously used a MOTO X 2014 (MOTO G 2013 before that) and unlocking bootloader was a breeze there. Took a maximum of 5 mins, and I thought it'd be same for this device. But, oh boy!!! Xiaomi really test your patience.
Anyways thanks a lot for this. Will give it a go too.
hamzaalijoiyah said:
And how did you do that?
Maybe you could point out respective thread!!!
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/how-to/method-miui-8-unlock-bootloader-twrp-t3529458
easiest, fastest and safest method (works for kenzo/kate):
prerequisite:
MIUI 8 Global Developer ROM 6.9.29
ZCX TWRP
Mi Flash 6.8.30
1) Download 6.9.29 fastboot MIUI ROM
2) Extract and replace recovery.img (in images folder) with ZCX TWRP.
3) Flash using Mi Flash (in EDL mode)
4) After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP
5) Backup, reboot to system and accept that TWRP disable/overwrite standard recovery
6) Boot to MIUI. (important step)
7) Finished!!
Now you have access to TWRP and can flash custom roms and kernels with locked bootloader.
No need to unlock bootloader anymore!
original thread: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
khajiit said:
easiest, fastest and safest method (works for kenzo/kate):
prerequisite:
MIUI 8 Global Developer ROM 6.9.29
ZCX TWRP
Mi Flash 6.8.30
1) Download 6.9.29 fastboot MIUI ROM
2) Extract and replace recovery.img (in images folder) with ZCX TWRP.
3) Flash using Mi Flash (in EDL mode)
4) After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP
5) Backup, reboot to system and accept that TWRP disable/overwrite standard recovery
6) Boot to MIUI. (important step)
7) Finished!!
Now you have access to TWRP and can flash custom roms and kernels with locked bootloader.
No need to unlock bootloader anymore!
original thread: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
Click to expand...
Click to collapse
Thanks a lot for your reply.
Although I succeeded in unlocking it the official way, but your answer will be able to help a lot of other folks experiencing the same problem.
i want to know how to Unlock Bootloader on redmi note 3 on marshmallow.
in Lollipop version i need to just replace emmc appsboot file in fastboot rom extracted folder then i can easily unlock its bootloader and installed twrp
but in marshmallow when i replaced same file which i used to unlock in lollipop fastboot rom it always shows unlock failed error
please anybody tell the solution for this
also i tried to unlock Officially. i got confirmation message on my both mi account to unlock permission but it always gives error current account is different from device account information
please help me to unlock bootloader officially/Unofficially on Marshmallow only
sumitkhkh said:
i want to know how to Unlock Bootloader on redmi note 3 on marshmallow.
in Lollipop version i need to just replace emmc appsboot file in fastboot rom extracted folder then i can easily unlock its bootloader and installed twrp
but in marshmallow when i replaced same file which i used to unlock in lollipop fastboot rom it always shows unlock failed error
please anybody tell the solution for this
also i tried to unlock Officially. i got confirmation message on my both mi account to unlock permission but it always gives error current account is different from device account information
please help me to unlock bootloader officially/Unofficially on Marshmallow only
Click to expand...
Click to collapse
use this method: https://forum.xda-developers.com/re...permission-t3541866/post70693744#post70693744
noob friendly and working 100%
sumitkhkh said:
i want to know how to Unlock Bootloader on redmi note 3 on marshmallow.
iqn Lollipop version i need to just replace emmc appsboot file in fastboot rom extracted folder then i can easily unlock its bootloader and installed twrp
but in marshmallow when i replaced same file which i used to unlock in lollipop fastboot rom it always shows unlock failed error
please anybody tell the solution for this
also i tried to unlock Officially. i got confirmation message on my both mi account to unlock permission but it always gives error current account is different from device account information
please help me to unlock bootloader officially/Unofficially on Marshmallow only
Click to expand...
Click to collapse
Maybe this will help you. I was having a lot of trouble too unlocking the bootloader as mi flas tool would never go past 50%. What I did was :
1) Apllied for unlock permission (that you've already done).
2) Downloaded mi flash tool and tried unlocking with it(that failed obviously)
3) Logged into Mi Cloud at i.mi.com
4) Checked connected devices, there were two there. You gotta Delete the one that's not Redmi Note 3, and make sure redmi note 3 is online.
5) Now you go to Settings>Additional Settings >Developer Options >Mi unlock status, and bind the account there for unlocking.
6) Goto i.mi.com and click on someting like 'Find my phone'. It'll be there.
7) Now if it can find your phone and tell its location, then you're good to go. (This step is important I guess)
8) Go ahead and try unlocking your phone with Mi flashtool.
I hope this works for you(worked for me though).
If you can't unlock via this method there are a few unofficial unlocking methods or you could contact Xiaomi and they will correct your data on their server side and you should be good to go.
sumitkhkh said:
i want to know how to Unlock Bootloader on redmi note 3 on marshmallow.
in Lollipop version i need to just replace emmc appsboot file in fastboot rom extracted folder then i can easily unlock its bootloader and installed twrp
but in marshmallow when i replaced same file which i used to unlock in lollipop fastboot rom it always shows unlock failed error
please anybody tell the solution for this
also i tried to unlock Officially. i got confirmation message on my both mi account to unlock permission but it always gives error current account is different from device account information
please help me to unlock bootloader officially/Unofficially on Marshmallow only
Click to expand...
Click to collapse
Here you go
http://en.miui.com/thread-345728-1-1.html
I did this for MM roms
hamzaalijoiyah said:
Maybe this will help you. I was having a lot of trouble too unlocking the bootloader as mi flas tool would never go past 50%. What I did was :
5) Now you go to Settings>Additional Settings >Developer Options >Mi unlock status, and bind the account there for unlocking.
Click to expand...
Click to collapse
For me (and a lot of others) it was impossible to bind it, server always returned an error and asked to try again later...I unlocked unofficially and I'm a happy user of RR 5.7.4
mooms said:
For me (and a lot of others) it was impossible to bind it, server always returned an error and asked to try again later...I unlocked unofficially and I'm a happy user of RR 5.7.4
Click to expand...
Click to collapse
Well you're right doing it. All this bootloader unlock charade is getting ridiculous now. I mean Xiaomi should learn from Motorola, their phones too come with locked bootloaders and unlocking them is a breeze(unless you use a carrier branded one).
Maybe it was just a good day for me that my BL got unlocked
Same here unlock always redirect to download page mi unlock tools or what ever ****!? Cant apply permission... Try another account, not help.
..

no OEM unlock?

On the latest t mobile software, dev mode enabled, but I dont see "OEM UNLOCK" anywhere...does anyone have that option on their note 8?
thanks
wase4711 said:
On the latest t mobile software, dev mode enabled, but I dont see "OEM UNLOCK" anywhere...does anyone have that option on their note 8?
thanks
Click to expand...
Click to collapse
I think you use that TMO device unlock app.
I thought that was just for carrier unlock, NOT OEM unlock...have you used that app?
thanks
wase4711 said:
I thought that was just for carrier unlock, NOT OEM unlock...have you used that app?
thanks
Click to expand...
Click to collapse
No, I disabled it. Been with TMO too long, I'm not going anywhere and neither are they. Thanks for teaching me the difference, lol! This bootloader is locked.
there are a few different "locks" to deal with on this phone; the bootloader, which is currently locked, carrier lock, meaning you are locked to tmobile, and the OEM unlock, which allows you to flash roms, both stock and custom, assuming you have an unlocked boot-loader
On most other phones, in the developer options, there is a OEM Unlock entry you activate if you plan on flashing anything...
wase4711 said:
there are a few different "locks" to deal with on this phone; the bootloader, which is currently locked, carrier lock, meaning you are locked to tmobile, and the OEM unlock, which allows you to flash roms, both stock and custom, assuming you have an unlocked boot-loader
On most other phones, in the developer options, there is a OEM Unlock entry you activate if you plan on flashing anything...
Click to expand...
Click to collapse
The OEM Unlock option doesn't appear until 7 days after the device was first booted on the Exynos version. That might not be the case with your version because the bootloader is locked so the OEM Unlock toggle is redundant.
Have a read through this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
I've had many phones with locked bootloaders in the past where the OEM unlock appeared in the dev options, so unless this is something new with the note 8. im not sure why its not there..
wase4711 said:
I've had many phones with locked bootloaders in the past where the OEM unlock appeared in the dev options, so unless this is something new with the note 8. im not sure why its not there..
Click to expand...
Click to collapse
All the OEM unlock toggle does is allow you to flash a custom recovery so you can then flash custom ROMs only if the the bootloader is unlocked. If the bootloader is locked like on US snapdragon N8s having the toggle is pointless.
If you check out the thread linked above you'll see that a bunch of people with exynos versions that do have unlocked boot loaders are missing the toggle which later appears & disappears. No one knows why yet, all just speculation.
The N8 is the first to have this happen. What a big headache. Hopefully they figure it out. I'm one of the lucky with an exynos N8 without that issue.
yeah, its not a big deal, especially since there is no way to unlock this bootloader at this point anyways...weird that it comes on and off on the Exynos though..
Torquemada288 said:
The OEM Unlock option doesn't appear until 7 days after the device was first booted on the Exynos version. That might not be the case with your version because the bootloader is locked so the OEM Unlock toggle is redundant.
Have a read through this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
Click to expand...
Click to collapse
Correct, for our t mobile USA ones, we will never get that OEM Unlock option in any amount of days.
Well if we can. Get root we can oem toggle
smiley45 said:
Well if we can. Get root we can oem toggle
Click to expand...
Click to collapse
We already have a root, it just wasn't released yet and it seems to be the same as S8, so with similar disadvantages. Expect to be out any day now.
smiley45 said:
Well if we can. Get root we can oem toggle
Click to expand...
Click to collapse
Even if you get the OEM unlock toggle to appear it doesn't mean anything. If you have a locked bootloader the OEM unlock won't unlock it. OEM unlock is just a safety switch.
shouren04 said:
Even if you get the OEM unlock toggle to appear it doesn't mean anything. If you have a locked bootloader the OEM unlock won't unlock it. OEM unlock is just a safety switch.
Click to expand...
Click to collapse
Yes that maybe so.. but I will feel better when I add that option to my note 8... I'm just waiting on root and it on form there
Sent from my SM-N950U1 using Tapatalk
Oem needs to be unlocked before u can us cf autoroot or any other means of root I have j7 metro no oem unlock option tried to use Odin and cf auto root it failed because the bootloader is locked and can't be unlocked. I know this is for the n8 but I seem to be suffering from the same problem.
Lost without root
XxdeadhatexX said:
Oem needs to be unlocked before u can us cf autoroot or any other means of root I have j7 metro no oem unlock option tried to use Odin and cf auto root it failed because the bootloader is locked and can't be unlocked. I know this is for the n8 but I seem to be suffering from the same problem.
Lost without root
Click to expand...
Click to collapse
Does having an engineering bootloader help?
How do I test if the bootloader is unlocked?
Sent from my SM-G892U using Tapatalk
reukiodo said:
Does having an engineering bootloader help?
How do I test if the bootloader is unlocked?
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
Its not plain and simple.
sent from my Pixel 2 XL or Note FE
so i cant root or put twrp on my j727U ? SEEN PEOPLE DO IT WITH J727p so why not the U ? no oem toggle on a galaxy how is this, should all come together and never buy phones from a company that goes against what customers want.
so i cant root or put twrp recovery on my galaxy j727U ? ? how has a phone tech not beat this by now even without oem toggle , it should still be beat by now.. this is why i liked htc cause they unlock bootloader for you and allow it on there own page, anyone wanna trade a htc for a new galaxy j7 ?
lol i think this thread needs to be closed
Yes there is an OEM unlock option. I know because I discovered It! Simply flash the K2 combination file, when factory binary loads go into the left hand screen, with apps. Click on the settings icon, then enable dev options the usual way. OEM unlock should be there. You may need to toggle it off and on a few times before you get the popup security message.
It makes a change in the system as it should. If you do a factory reset, then reload the factory binary, you'll see that Dev Options are already enabled (saved from last time you unlocked) AND OEM will already be toggled. This means that the unlock sticks!
So there you go. It even changes the OEM line in the .prop.... that being said...
DO NOT TRY TO FLASH TWRP AFTER DOING THIS!!!
(I already tried, the secure boot still is in effect, and you'll have a softbrick until you can re Odin your recovery. )
The OEM unlock may be one part of this, but there's more. Hopefully we are making progress toward the goal of a bootloader unlock!

Help! mate 10 pro relocking bootloader

hi,i have a mate 10 pro with stock android 8, unlocked bootloader by flashing unlock key via fastboot. frp unlocked.
stock recovery. not rooted.
bla-l29 c432 131
when i start my mate 10 it says "device cannot be trusted".. before it boots as normal.
Can i lock\relock bootloader and make it go away??
tried:
fastboot oem relock "unlock code"
fastboot oem lock "unlock code"
and it came password failed :\
usb debugging: on
oem unlock: on
flash oem info of sorts?
try: fastboot reboot oem relock?
if i switch oem unlock to off again in developers option and then use commands??
Thanks for help!
FiXed, used adb interface drivers, i tried several until i found 1 that worked
Hi, with mate 8 and mate 9 when you flash officiel firmware he relock bootloader, try this or you can buy credit (4) for relock with DC unlocker.
So... tell me please why you unlock your bootloader if you don't flash twrp or root ??
Dont buy any credit. I Will provide you The solution today.
---------- Post added at 05:49 AM ---------- Previous post was at 05:03 AM ----------
614Emil said:
hi,i have a mate 10 pro with stock android 8, unlocked bootloader by flashing unlock key via fastboot. frp unlocked.
stock recovery. not rooted.
bla-l29 c432 131
Click to expand...
Click to collapse
Use this tutorial (flash update)
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
In short:
- download your full firmware (3 files)
- in repack part chose to lock bootloader
- ota part
End of story.
badmania98 said:
Dont buy any credit. I Will provide you The solution today.
---------- Post added at 05:49 AM ---------- Previous post was at 05:03 AM ----------
Use this tutorial (flash update)
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
In short:
- download your full firmware (3 files)
- in repack part chose to lock bootloader
- ota part
End of story.
Click to expand...
Click to collapse
Thanks, I will try this later and let you know how it goes!
If you only want to relocked your bootloader just use the HWOTA8_Mate 10 tool from the link bellow.
download the tool > go to lock directory > use relock.bat
you'll need to provide your bootloader unlock code to re-locked it.
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Lykeul said:
Hi, with mate 8 and mate 9 when you flash officiel firmware he relock bootloader, try this or you can buy credit (4) for relock with DC unlocker.
So... tell me please why you unlock your bootloader if you don't flash twrp or root ??
Click to expand...
Click to collapse
hi aok ill look into that plan was getting viper or some good sound mod, but it seems its not finished developed for Oreo 8.0
Buran79 said:
If you only want to relocked your bootloader just use the HWOTA8_Mate 10 tool from the link bellow.
download the tool > go to lock directory > use relock.bat
you'll need to provide your bootloader unlock code to re-locked it.
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
it did not work :\
614Emil said:
it did not work :\
Click to expand...
Click to collapse
did you try info.bat? does it restart to fastboot mode so you can see the bootloader status?
what method or tool did you use to unlock de bootloader?
Buran79 said:
did you try info.bat? does it restart to fastboot mode so you can see the bootloader status?
what method or tool did you use to unlock de bootloader?
Click to expand...
Click to collapse
i have to set it in fastboot manually then it shows:
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Current build number:
BLA-L29 8.0.0.131(C432)
Product model:
BLA-L29
to unlock i used cmd and -fastboot oem unlock "code"-
Buran79 said:
If you only want to relocked your bootloader just use the HWOTA8_Mate 10 tool from the link bellow.
download the tool > go to lock directory > use relock.bat
you'll need to provide your bootloader unlock code to re-locked it.
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
hi^^ did not work either, after i put in the "code" in the cmd window,i can see Failed before the cmd window quickly dissapears
614Emil said:
hi^^ did not work either, after i put in the "code" in the cmd window,i can see Failed before the cmd window quickly dissapears
Click to expand...
Click to collapse
I think you are not having proper mate 10 pro windows drivers. Try following the HWOTA_mate10 guide about preparation, there is a registry fix and you should uninstall HiCare for proper device recognition
Buran79 said:
I think you are not having proper mate 10 pro windows drivers. Try following the HWOTA_mate10 guide about preparation, there is a registry fix and you should uninstall HiCare for proper device recognition
Click to expand...
Click to collapse
Hi, i just started thinking about that, just to be sure since i did not get mtp folder in my computer anymore(win 10)
i switched to my laptop win 8.1,
installed the adb driver manually as adb composite interface in normal mtp\debug phone on.
in fastboot the driver said adb sooner single interface
and then when i am supposed to switch inn to the stock recovery modded with adb support,
i get 3 devies with yellow ! in device manager:
1. huawei- device properties and details then choose bus reported device description: huawei
2. unknown device: - device properties and details then choose bus reported device description: adb interface
3. unknown device: - device properties and details then choose bus reported device description: hdb interface
what should i set these to manually?
i am trying to use "flash update" in HWOTA_mate10 guide and i am on step D run ota.
supposed to switch from fastboot to recovery then the script waits for adb connection
Did you disable oem unlocking in developer options?
EngrVan said:
Did you disable oem unlocking in developer options?
Click to expand...
Click to collapse
no, but i just fixed it!
it showed adb interface, i tried different android drivers\adb drivers, found the right combo inn the end
Bootloader Unlock not possible - but eRecovery working
@ante0
I have Mate 10 BLA-L09c432 and installed latest Firmware 8.0.0.157 since two days. I updated with official OTA.
Before I had 8.0.0.137 → on that Firmware I read the Bootloader Unlock Code with DC Unlocker → and I got a new Unlock Code.
The originial Unlock Code did not work anymore (Phone was from a friend of mine and bricked and I restored it by FunkyHuawei - and bought it).
I unlocked the Bootloader with the new Code (read by DC) and it worked.
Two days ago I decided to update with OTA. I reflashed the original recovery_ramdisk and ramdisk.img. Update was succesful.
→ I tried to relock the Bootloader (because I am thinking about to sell the phone) → and it does not work! Not with the originial Code, not with the new Code (read on b137)
I did nothing wrong, because this year I unlocked about 40 devices (because I am helping to repair bricked phones from Users of Android Hilfe de) and I know very well how to do. (OEM Unlock enabled, ADB Debugging and USB Debugging enabled, HiSuite HDB disabled, HiSuite on PC closed, ADB and Fastboot working....)
Code:
fastboot oem relock UNLOCKCODE
does not work
But I have no idea yet how to relock the Loader I will try once more - but perhaps you or someone has an idea?
So perhaps I should just be happy to have a unlocked Phone and keep it instead of selling it....
Everything else is working.
And I found out some interesting point → seems Huawei started to bring the Feature of eRecovery even to European Versions of his Phones (from a certain firmware version)
I booted to Huawei eRecovery and "Download latest version and Recovery" is running without FunkyHuawei
Tecalote said:
@ante0
I have Mate 10 BLA-L09c432 and installed latest Firmware 8.0.0.157 since two days. I updated with official OTA.
Before I had 8.0.0.137 → on that Firmware I read the Bootloader Unlock Code with DC Unlocker → and I got a new Unlock Code.
The originial Unlock Code did not work anymore (Phone was from a friend of mine and bricked and I restored it by FunkyHuawei - and bought it).
I unlocked the Bootloader with the new Code (read by DC) and it worked.
Two days ago I decided to update with OTA. I reflashed the original recovery_ramdisk and ramdisk.img. Update was succesful.
→ I tried to relock the Bootloader (because I am thinking about to sell the phone) → and it does not work! Not with the originial Code, not with the new Code (read on b137)
I did nothing wrong, because this year I unlocked about 40 devices (because I am helping to repair bricked phones from Users of Android Hilfe de) and I know very well how to do. (OEM Unlock enabled, ADB Debugging and USB Debugging enabled, HiSuite HDB disabled, HiSuite on PC closed, ADB and Fastboot working....)
does not work
But I have no idea yet how to relock the Loader I will try once more - but perhaps you or someone has an idea?
So perhaps I should just be happy to have a unlocked Phone and keep it instead of selling it....
Everything else is working.
And I found out some interesting point → seems Huawei started to bring the Feature of eRecovery even to European Versions of his Phones (from a certain firmware version)
I booted to Huawei eRecovery and "Download latest version and Recovery" is running without FunkyHuawei
Click to expand...
Click to collapse
Use the DLOAD method with the B150 firmware from androidhost.ru, that should lock (not relock) it.
Pretoriano80 said:
Use the DLOAD method with the B150 firmware from androidhost.ru, that should lock (not relock) it.
Click to expand...
Click to collapse
Thanks Mate :good:
So I have just to check the Xloader thing before
Tecalote said:
Thanks Mate :good:
So I have just to check the Xloader thing before
Click to expand...
Click to collapse
B150 from androidhost.ru is xloader 2, which build do you have now?
Pretoriano80 said:
B150 from androidhost.ru is xloader 2, which build do you have now?
Click to expand...
Click to collapse
I have b157 (latest Firmware for c432, installed with official OTA (Full) from b137 to b157)
Tecalote said:
I have b157 (latest Firmware for c432, installed with official OTA (Full) from b137 to b157)
Click to expand...
Click to collapse
Then you can use B150 to downgrade with DLOAD method. That should reset the phone and lock the bootloader, to fabric condition.

How to Unlock FRP?

I dont have OEM options in dev menu, already rooted device and bootloader unlocked, I even installed TWRP and LineageOS - now i wanna update device but cant update TWRP because FRP is unlocked
Well, you need the OEM unlock option in the first place to lock the FRP.
As of how to do it?! I'll look in the forums and see if I come by anything

How To Guide The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)

OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile network; and a Windows PC, where a PC is used (though I imagine the Mac/Linux commands are quite similar). This is more to gather the info in one place than to provide step-by-step instructions.
SIM/NETWORK UNLOCK
Before you can unlock the bootloader, the N200 needs to be SIM unlocked. The option to Enable OEM Unlock won't even show up in the developers options until then. A temporary SIM unlock won't work, it needs to be a permanent SIM unlock.
If your N200 is the T-Mobile variant, you can get it SIM unlocked free here (be sure to read the first post thoroughly to be sure you qualify):
[CLOSED][T-Mobile USA] Free SIM Unlocking Service - [OnePlus/Samsung/Google/LG/Moto]
Hello XDA, I am back at it again with the free T-Mobile network unlocks. Yep, you heard that right... 100% FREE. This service will allow you to go into your Settings and perform a network unlock. I've been doing this for over 3 years now with...
forum.xda-developers.com
@mobbdeep had my SIM unlocked within 24 hours of sending him the required info.
You MUST have an active T-Mobile network (not Sprint or Metro) SIM card in the N200 for at least 3 full days before sending your SIM Unlock request in.
---
*edit-
An alternate is to use this debloat script:
Found a chink in the armor... Just enabled OEM unlocking after 11 update...
I haven't got a lot of time to get this out before heading out on a job, so here's the nitty gritty. A few days ago I flashed over "OnePlus_Nord_N10_5G_Metro_by_T-Mobile_OxygenOS_10.5.8" to get a clean start. I then allowed 10.5.14 to install...
forum.xda-developers.com
Which should unlock the OEM Unlock option in the developer options.
This should work with non-T-Mobile variants of the N200 as well.
Thanks to @PopCaps1996 for pointing this option out.
---
*edit2-
Thanks to user @DeadDjembe we now know the specific command from the debloat script which enables OEM Unlocking.
Code:
adb shell pm uninstall --user 0 com.qualcomm.qti.uim
Running this ADB command on a stock T-Mobile variant N200 should enable the greyed-out Allow OEM Unlock option in the developers settings, without needing to run the full debloat script.
---
Once your N200 is SIM Unlocked, the Enable OEM Unlock option will show up in the developers options.
USB DRIVERS
You may need to use the Google USB Driver from Android Studio to allow your PC to recognize your phone when it's in fastboot mode.
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
Android Studio won't install the USB Drivers by default, you'll need to install them through the SDK Manager (Android Studio -> Projects -> More Actions -> SDK Manager -> SDK Tools -> Google USB Driver checkbox -> Apply)
You'll need to manually install the drivers through the device manager while the phone is in fastboot mode and connected to the PC (right-click -> Update Drivers -> Browse Computer -> Let Me Pick -> Have Disk).
The drivers should be located at:
C:\Users\[username]\AppData\Local\Android\Sdk\extras\google\usb_driver\android_winusb.inf
You'll want the 'Android Bootloader Interface' driver.
UNLOCK CODE/TOKEN
Once you can access your phone in fastboot mode, you can try:
'fastboot oem unlock'
But, you'll just get a message asking for an unlock token. Doesn't hurt to try, just in case, though.
What you need to do now, is type:
'fastboot oem get_unlock_code'
This will display both the phone's serial number, plus a 64 digit unlock code. (you might not be able to select the code to copy it, but a ctrl-a / ctrl-c should work, then just paste it in notepad)
Now, on your phone (still in fastboot mode) hit up/down on the volume buttons, until you see "Show Barcode", then tap the power button to select it.
This will bring up a barcode, as well as listing you devices IMEI number. (there are other ways to get the IMEI, but this is quick, and you're already right there)
Copy the IMEI down.
Now go to:
https://www.oneplus.com/unlock_token
You'll need to create an account.
In that form, you'll need to select the phone's model, and then enter the serial number, 64 digit unlock code (no spaces), the IMEI, and your email, as well as checking a box that you acknowledge that you void the warranty by bootloader unlocking the phone.
If all goes well, It should take about a week from submission for them to send you the unlock token.
------
I've just sent in my info an hour or two ago, and am now waiting for my unlock token.
I'll update this with what you need to do with the token once I've gotten mine and figure it out myself, lol.
------
Exactly 7 days (nearly to the minute) after sending the request in, I received the unlock code. So here's the update:
APPLYING THE UNLOCK CODE
You can use this URL to check the status of your Unlock Coed request:
unlock token - OnePlus (United States)
www.oneplus.com
Once your Status is listed as "Finished", there will be a download button at the lower right corner.
Download the "unlock_code.bin" file to your PC.
Place 'unlock_code.bin' in:
C:\Users\[user name]\AppData\Local\Android\Sdk\platform-tools\
Or where ever you have your fastboot.exe file.
If you don't know where it is, the command:
Code:
fastboot --version
will give your it's location.
Now in command line, navigate to the folder "fastboot.exe" and "unlock_code.bin" are located in. Get your phone connected via USB, and in fastboot mode, and use the following command:
Code:
fastboot flash cust-unlock unlock_code.bin
(Thanks to @lentm for posting this command)
After checking the output, to be sure it worked, use this command:
Code:
fastboot oem unlock
Follow the on-screen instructions on your phone to finish the bootloader unlock.
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
PopCaps1996 said:
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
Click to expand...
Click to collapse
OK, that's neat.
I can't personally test it, as I'm already SIM unlocked; but all comments in the thread seem to indicate it working.
It'd be quite interesting if someone could narrow down exactly which of the removed apps enables the OEM Unlock option (as an uninformed guess: adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth).
I'd need to research what all those different apps do, but at a glance I see at least 2 or 3 on that list I'd want to keep. At any rate, I'd rather wait until after I get TWRP Recovery on my phone (once we get a release for the N200) before debloating it, just to be safe. I'm far more knowledgeable about computers than phones, which gives me just enough knowledge to seriously screw up my phone by doing the wrong thing, lol.
edale1 said:
OK, that's neat.
I can't personally test it, as I already have that unlocked; but all comments in the thread seem to indicate it working.
It'd be quite interesting if someone could narrow down exactly which of the removed apps enables the OEM Unlock option (as an uninformed guess: adb shell pm uninstall --user 0 com.qualcomm.qti.remoteSimlockAuth).
I'd need to research what all those different apps do, but at a glance I see at least 2 or 3 on that list I'd want to keep. At any rate, I'd rather wait until after I get TWRP Recovery on my phone (once we get a release for the N200) before debloating it, just to be safe.
Click to expand...
Click to collapse
i can confirm it works that's the method i used to unlock my bootloader for my n200
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
PhoenixPath said:
Using the debloater worked beautifully to get ability to enable OEM Unlocking. Now it's just the week wait to get the code.
Really wish they'd speed that up; I've had to do this for four devices through them. Major benefit to buying direct from OnePlus, IMO. The last one I did was unlocked moments after getting home...(and is now running crDroid which I really hope comes to the N200)
Click to expand...
Click to collapse
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Yes, but to my knowledge unlocking the bootloader is the only part of the entire process of installing a custom recovery and rooting that wipes the device. So it's best to get that out of the way ASAP, before the phone's loaded with stuff you don't want to lose.
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
can you send me the extracted payload.bin pm me please
PopCaps1996 said:
can you send me the extracted payload.bin pm me please
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
lentm said:
https://android.googleapis.com/packages/ota-api/package/2c0d5671fc9a0f7829ab54b08139378afc295f46.zip
Click to expand...
Click to collapse
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
lentm said:
View attachment 5377289
I got the unlock bin file from OnePlus a couple of days ago, and just finished unlocking my N200 from T-Mobile with the code below:
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
Edit:
I was able to download the latest ota (July) zip, extract the boot.img out of payload.bin using payload dumper on python; however, even the latest Magisk Canary version couldn't patch the img, says unknown image format.
Click to expand...
Click to collapse
Maybe it's because the ota is just an update, not a full zip?
PopCaps1996 said:
the payload bin that you extracted? can you zip up the extractred imgs from payload . bin. an send them to me?
Click to expand...
Click to collapse
I can get you the boot.img, not every img files. Check the attached.
lentm said:
I can get you the boot.img, not every img files. Check the attached.
Click to expand...
Click to collapse
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
dragonnightx said:
When trying to patch the boot.img file with Magisk Stable version 23.0 (23000) (21) and Canary version f822ca5b (23001) (21), I get "Unsupported/Unknown image format. Installation failed".
Click to expand...
Click to collapse
Yea, that's what I get too.
How long does OnePlus usually take in processing the bootloader unlock request?
TheLoonyRebel said:
How long does OnePlus usually take in processing the bootloader unlock request?
Click to expand...
Click to collapse
7 days
PopCaps1996 said:
you will not be able to modify anything anyways once you get the bootloader unlocked because oneplus has not released stock rom for the N200 on their website yet. so there for we do not have stock boot.img to be able to patch an root but i heard they will be uploading the rom soon. unless we can figure out how to back up boot img through fastboot but don't think that's possible
Click to expand...
Click to collapse
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
jilebi said:
Have you tried downloading full ROM of OxygenOS11 using the Oxygen Updater app?
Click to expand...
Click to collapse
I tried it and even I set it manually to N200, but no full ROM available
PopCaps1996 said:
you do NOT need to carrier unlocked for bootloader unlock use this...... debloat script oneplus through ADB an once finished OEM UNLOCK will be ungrayed. then you can request a unlock token from oneplus then wait 7 days then flash an unlock bootloader.
im still carrier locked
Click to expand...
Click to collapse
Do you know which specific app to uninstall removes the OEM unlock restriction? I want to unlock the bootloader, but would rather keep the other preinstalled software.

Categories

Resources