[Emui 10] Bootloader unlock not possible - Huawei Mate 20 Pro Questions & Answers

[Emui 10] Bootloader unlock not possible - Huawei Mate 20 Pro Questions & Answers

Hello everyone!
I spent the last few days trying to flash a stock emui 9 or 9.1 version to my Mate20Pro (C432) because my carrier notified me, that the emui 10 update is officially available.
I was finally able to go to version . 347 by following this guide: click
A few hours later I was offered the emui 10 update and it installed well.
The exact build nr is now: 10.0.0.154(C432E7R1P5patch01)
Only thing left: Root access.
And here's where the problems start:
The Bootloader was relocked somewhere down the road (the update to .347 probably). Now, I've had this issue before, jumping back and forth between ROMs, but was always able to re-unlock my bootloader with my code I got from funkyhuawei (back in the days).
Now when I try to unlock it now, following this procedure:
- turn usb debugging on
- confirm to always trust my computer
- open console - adb devices: I see my device.
- adb reboot bootloader: reboots the phone gracefully
- reached fastboot mode - bootloader lock confirmed. frp locked: no
- in terminal: fastboot devices: check
- fastboot oem unlock xxxxx
--> here i get following output:
Failed. Invalid command.
Has anyone also had this issue? is this some kind of security mechanism (did they change the unlock code?) Or did they chamge the fastboot command set?
What I've checked so far:
- usb drivers are installed (reinstalled them even)
- hisuite is installed (also tried it with uninstalling first)
- terminal is running as admin
- tried different usb cables
- googling
I would really appreciate all thoughts, ideas or experiences with this issue.
Thanks in advance!

On EMUI10 (at least early builds), it's normal behavior.
It's seem that oem unlock's fastboot command was made invalid or was modified...
It's told rolling back to emui9 B346 or B347 will open bootloader back or at least will enable back fastboot and old oem unlock commands.
Does magisk creator @topjohnwu achieved something related to emui10 ?

c4ph4lor said:
Hello everyone!
I spent the last few days trying to flash a stock emui 9 or 9.1 version to my Mate20Pro (C432) because my carrier notified me, that the emui 10 update is officially available.
I was finally able to go to version . 347 by following this guide: click
A few hours later I was offered the emui 10 update and it installed well.
The exact build nr is now: 10.0.0.154(C432E7R1P5patch01)
Only thing left: Root access.
And here's where the problems start:
The Bootloader was relocked somewhere down the road (the update to .347 probably). Now, I've had this issue before, jumping back and forth between ROMs, but was always able to re-unlock my bootloader with my code I got from funkyhuawei (back in the days).
Now when I try to unlock it now, following this procedure:
- turn usb debugging on
- confirm to always trust my computer
- open console - adb devices: I see my device.
- adb reboot bootloader: reboots the phone gracefully
- reached fastboot mode - bootloader lock confirmed. frp locked: no
- in terminal: fastboot devices: check
- fastboot oem unlock xxxxx
--> here i get following output:
Failed. Invalid command.
Has anyone also had this issue? is this some kind of security mechanism (did they change the unlock code?) Or did they chamge the fastboot command set?
What I've checked so far:
- usb drivers are installed (reinstalled them even)
- hisuite is installed (also tried it with uninstalling first)
- terminal is running as admin
- tried different usb cables
- googling
I would really appreciate all thoughts, ideas or experiences with this issue.
Thanks in advance!
Click to expand...
Click to collapse
Were you able to unlock bootloader or downgrade to 9.1 with locked bootloader or fix this issue by any means?

You can rollback to 9.1 using stock hisuite.
If rollback prompt is not shown, you can trigger it with 'Hisuite launcher' from Magnot.

oslo83 said:
You can rollback to 9.1 using stock hisuite.
If rollback prompt is not shown, you can trigger it with 'Hisuite launcher' from Magnot.
Click to expand...
Click to collapse
I tired stock hisuite, but it says does not support.

sharath91221 said:
I tired stock hisuite, but it says does not support.
Click to expand...
Click to collapse
Rollback link is shown from Hisuite 's update option, not from Hisuite' s recovery option.

thank you for the heads up about rooting and emui 10, i have been tempted to try it for myself but had to much to do at home and at work, but i will wait a bit more.
also: dload version will always lock the bootloader

I was able to install CUST and PRELOAD for lya-l09 emui 10 using dload method and it fixed the issue. Thank you.

Check oem option in developer settings.It must be enabled

farizazizov said:
Check oem option in developer settings.It must be enabled
Click to expand...
Click to collapse
thanks yes the obvious-not the issue though (same issue on mate 20 x evr-l29) cannot unlock bootloader (same failed command issue) after emui 10 upgrade (went through an update as well)
---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------
sharath91221 said:
I was able to install CUST and PRELOAD for lya-l09 emui 10 using dload method and it fixed the issue. Thank you.
Click to expand...
Click to collapse
could you elaborate please? (explain in detail) thanks

mac231us said:
thanks yes the obvious-not the issue though (same issue on mate 20 x evr-l29) cannot unlock bootloader (same failed command issue) after emui 10 upgrade (went through an update as well)
---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------
could you elaborate please? (explain in detail) thanks
Click to expand...
Click to collapse
I have funkyhuawei account but still that was unable fix the issue. So what i did was:
I choose 365 ver in funkyhuawei website and tried flashing it using modded hisuite. When it downloaded the firmware i replaced the 365 firmware files like CUST AND PRELOAD with EMUI 10 version, it failed at the beginning. I keep on retrying multiple times and final it flashed CUST and PRELOAD and my system booted with EMUI 10 .

sharath91221 said:
I have funkyhuawei account but still that was unable fix the issue. So what i did was:
I choose 365 ver in funkyhuawei website and tried flashing it using modded hisuite. When it downloaded the firmware i replaced the 365 firmware files like CUST AND PRELOAD with EMUI 10 version, it failed at the beginning. I keep on retrying multiple times and final it flashed CUST and PRELOAD and my system booted with EMUI 10 .
Click to expand...
Click to collapse
Do you have the link or if you could upload please the modded hisuite? Appreciate it.
EDIT
So in the dload folder, you used the main update zip from the 9.1 (365) and the custom and preload zips from emui 10? Thanks. (asking also since you say you booted in emui 10 even though from what you have described you seem to have had the main update zip in 9.1...or was it the other way around?)
(I tried-though on mate 20x and the software installation failed-restart-so is that what you tried many times? (in the erecovery update through card/otg option?)
Highly appreciate your clarification here (might just help me get out of this emui10 mess)

mac231us said:
Do you have the link or if you could upload please the modded hisuite? Appreciate it.
EDIT
So in the dload folder, you used the main update zip from the 9.1 (365) and the custom and preload zips from emui 10? Thanks. (asking also since you say you booted in emui 10 even though from what you have described you seem to have had the main update zip in 9.1...or was it the other way around?)
(I tried-though on mate 20x and the software installation failed-restart-so is that what you tried many times? (in the erecovery update through card/otg option?)
Highly appreciate your clarification here (might just help me get out of this emui10 mess)
Click to expand...
Click to collapse
Modded hisuite only work, if you have funkyhuawei account and required credits for that account.
Yes, thats correct i used main update.zip is from 9.1 and custom and preload are from emui 10.
Currently your mobile already have emui 10(update.zip). But when mobile boots it goes through custom and preload and then it loads Operating System(emui 10).
In order to fix it . You need to load custom and preload for supporting emui 10.
If you have a regular hisuite, try erecovery mode.
Hisuite will download a package(update.zip, custom.zip and preload.zip) in documents folders if you are using Windows system. Once it downloads them, it will unzip those files and then it starts flashing customs, preload and then update(in this order). You need to figure out a way, to replace custom and preload folder with emui 10 files before Hisuite start flashing them.

so, since bootloader unlock is not longer possible with emui 10 i will give the phone to one of my kids so it will be a youtube interface, myself ordered a s20+ and hopefully samsung will treat me right.

Related

How to use recovery features & firmware (eRecovery/dload/HWOTA/recovery)

I can turn this into a guide if we get the right info.
I have used DC-Unlocker to unlock bootloader and FRP.
I installed v20 Phh Generic System Image via fastboot flash system.
my FRP is locked now and bootloader unlocked, and oem unlock greyed out.
i am investigating a solution and maybe it can help others.
Recovery:
can flash updates if bootloader and frp is unlocked
eRecovery:
i can connect to wifi, but no firmware is found
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
HWOTA:
seems to be a method used on older devices - not sure if it will work to flash this device.
the sh. script seems fairly straightforward so maybe it can be modded to work with this device
Device: SHT-W09 M5 8.4 (eu)
Build Number: 8.0.0.151 (C432)
OS: Stock 151 with Phh GSI applied
ive never had a device this difficult to recover. samsung had odin to flash firmware, nexus 5/7/9 always had a way out - when i was building roms for moto xoom it wasnt this difficult.

Good luck man, it seems like when this thing bootloops, it activates some sort of defense mechanism that makes recovery particularly challenging.
I bootlooped after editing my vendor/build.prop file. DLoad method failed. Flashing partitions via fastboot failed. Stock recovery failed. TWRP became available, and I got it working...but no partitions would mount r/w. I paid to use Funky Huawei's unbrick tool, and it failed.
Funky Huawei's eRecovery method is basically all that worked for me. But I paid to use it (I still have a few weeks remaining on a pass).
These instructions, which don't involve payment to Funky Huawei, might or might not work:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165

Thanks for the alternative method.
I tried with hisuite using firmware finder, it uses the same funky DNS server. When I start the process the download works fine then on hisuite it says installing, does nothing then fails. After I reboot (usb in pc, all 3 buttons) it shows a usb symbol - installing but hangs at 5% for ages.
I tried with a portable router with ERecovery and it did not work unfortunately still failed to get info

I had to result to funkyhuawei who have now added SHT-W09C432 to their system.
In the 30 days I have this I'm tdetermined to find alternative solutions to fix this issue like all other devices tend to have.
I battled it out with Huawei support and there's no chance of an frp key - at least first 3 attempts. Also tried to get them tonexplqin ERecovery but said it's for insiders only just for service repairs. They have no regard for helping developers.
I was trying to figure out where the file get stored on ERecovery so if we could adb push to it and hold vol down + up + power to recover the device. I found i could pull from /dload (not internal/externalsd) which contained firmware_update_dload.zip but when uncompressed e enwbti be referenced to Qualcomm chips.
Any ideas on patching the recovery or boot image to prevent frp lock?
I also tried to see if there is a way from adb (while OS is running) to flip the OEM unlock back to on but there's nothing in system/global/settings that represents that.
It's strange because frp should not lock if you log back into the same account.

LOGMD said:
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
.
Click to expand...
Click to collapse
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?

omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279

OK, thanks for this info, of course I thought that this device would be as easy to utdate then my much older M2-801L via dload which worked every time. And thanks for the tool tip, I'm looking into that thread as well :good:

Butch1326 said:
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank You for the info.
Used it to update my CMR-AL19 and worked like a charme

omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
Sorry for the late reply had some busy months!
So from what I remember it's because the UPDATE.APP was too big. I tried recreating the update.app without the non-essentials but I couldn't get it working.
Huawei support when I asked about how to update via recovery just kept saying it's only for technicians at Huawei so they won't help me in any way!

[GUIDE] Bricked K20 Pro after flashing (raphaelin) 10.3.3

Hello Xda and K20 Pro-ians.
Just wanted to share with you what I did after accidentally selected “ clean all and lock” options during the process of putting in K20 Pro India ROM (raphaelin) 10.3.3 into my K20 Pro which was running on China (raphael) 10.3.14.
Started reading the forum and somehow TEST POINT Reset was my last option as I can’t boot into the ROM and was at the Recovery screen, Tried EDL as well still no go
I read through some post, and one of the members mentioned about using an older version of Unlocking application. Immediately, I tried all possible version that I could find and so far version “miflash_unlock-en-2.2.406.5” did the unlocking and straight went into the newly installed India ROM(raphaelin).
FYI. the latest version of MiUNlock doesn’t permit you to unlock bootloader process for another 30days (Mi Policies)
Steps Taken
1. Got my New Phone ( China Rom ) updated to version 10.3.14
2. Read through the post in XDA and begin ripping off my warranty -> Downloaded India Rom 10.3.3
3. Unlock Bootloader (waited for three days) -> starts flashing -> With Clean all and Lock option being checked! - FML!
4. Tried to unlock again with Miflash version 3~ no go
5. Install MiFlash unlock 2.2.4
6. Booth into Fastboot. Run the app and waited for 6 to 8 minute for the unlocking process.
7. Phone restarted
8. Happy days!
If the post help, just buy me a beer
bitcoin = 38s3pyXL4yS47JNZRxRYiRZkGypUwrjusz
Ether = 0xB2e0f140b8d1704Db8BEdaB2D812D07bC33Bf5c5
to download MiFlash Unlock version 2.2.4 simply google it

Thank you, I am sure this will help many people.
Here is the download link for miflash 2.2.406.5: https://androidfilehost.com/?fid=889764386195901972

Thanks !
Legend! I tried putting the link in however due to the infancy of my user account, I am not allowed to do so
thank you again!

After installing 10.3.3 indian rom to your chinese K20 pro, does it automatically change to L1 security policy and your able to watch netflix in HDR?

Jumundz said:
Hello Xda and K20 Pro-ians.
Just wanted to share with you what I did after accidentally selected “ clean all and lock” options during the process of putting in K20 Pro India ROM (raphaelin) 10.3.3 into my K20 Pro which was running on China (raphael) 10.3.14.
Started reading the forum and somehow TEST POINT Reset was my last option as I can’t boot into the ROM and was at the Recovery screen, Tried EDL as well still no go
I read through some post, and one of the members mentioned about using an older version of Unlocking application. Immediately, I tried all possible version that I could find and so far version “miflash_unlock-en-2.2.406.5” did the unlocking and straight went into the newly installed India ROM(raphaelin).
FYI. the latest version of MiUNlock doesn’t permit you to unlock bootloader process for another 30days (Mi Policies)
Steps Taken
1. Got my New Phone ( China Rom ) updated to version 10.3.14
2. Read through the post in XDA and begin ripping off my warranty -> Downloaded India Rom 10.3.3
3. Unlock Bootloader (waited for three days) -> starts flashing -> With Clean all and Lock option being checked! - FML!
4. Tried to unlock again with Miflash version 3~ no go
5. Install MiFlash unlock 2.2.4
6. Booth into Fastboot. Run the app and waited for 6 to 8 minute for the unlocking process.
7. Phone restarted
8. Happy days!
If the post help, just buy me a beer
bitcoin = 38s3pyXL4yS47JNZRxRYiRZkGypUwrjusz
Ether = 0xB2e0f140b8d1704Db8BEdaB2D812D07bC33Bf5c5
to download MiFlash Unlock version 2.2.4 simply google it
Click to expand...
Click to collapse
So with this version no need to use test point?

overcustom said:
So with this version no need to use test point?
Click to expand...
Click to collapse
Apparently that's the claim. I don't imagine there's going to be many volunteers to deliberately brick their phone just to try this out.
We'll have to wait for the next person whose too impatient to fully read the guides and accidentally bricks the phone, before we can get any validation.

Robbo.5000 said:
Apparently that's the claim. I don't imagine there's going to be many volunteers to deliberately brick their phone just to try this out.
We'll have to wait for the next person whose too impatient to fully read the guides and accidentally bricks the phone, before we can get any validation.
Click to expand...
Click to collapse
Hi Zadjalixx, unfortunately, is still L3, xiao mi need to up their game for this ~ I didn't root or load any custom recovery like TWARP into this phone YET. My initial Idea is the review the phone so I can use it for my daily drive. Also I can't see Netflix in PLaystore, ( so is a bummer for sure ). you have any alternative that could suggest? thanks mate.
overcustom said:
So with this version no need to use test point?
Click to expand...
Click to collapse
Yeah , so far that works for me , I have given up at 1st and ready to make use of the hairdryer to remove the back cover to perform the test point reset.
I read through some treads which I am having issues to trace back, by using an older version of miflash unlock we can unlock the phone without the wait for another 30days.
Like Robo says we need to wait for the next victim to do so ~ I should have recorded a video during that process. Cheers ~

About Netflix, you can download the APK on apkmirror: https://www.apkmirror.com/apk/netfl...oid-tv-6-2-5-build-2789-android-apk-download/

DontDamnMe said:
About Netflix, you can download the APK on apkmirror: https://www.apkmirror.com/apk/netfl...oid-tv-6-2-5-build-2789-android-apk-download/
Click to expand...
Click to collapse
I don't think this will work . due to teh security level , It needs to have L1 rather then L3 to use Netflix service.

I also made the same mistake. I tried to unlock with newest and older unlock tool, but it failed. It is showing to go and check unlock status from the developer option. My device can't boot then how can to developer option?? Please suggest me what should I do. Thanks in advance

Nachiketa.jstu said:
I also made the same mistake. I tried to unlock with newest and older unlock tool, but it failed. It is showing to go and check unlock status from the developer option. My device can't boot then how can to developer option?? Please suggest me what should I do. Thanks in advance
Click to expand...
Click to collapse
you need to download the chinese or indian fastboot rom and install it trough mi flash tool, then once the rom is installed again, you can go into the menu to enable bootloader unlock. Then you probably have to wait a week until you can unlock it using the xiaomi unlock tool.
---------- Post added at 02:23 PM ---------- Previous post was at 01:44 PM ----------
Everytime I use the latest unlocker tool my phone won't boot to OS anymore and the stock recovery boots up. I have to do a factory reset and then i have to apply for the bootloader to unlock again.
Is there an option to see the unlock time without needing to reset the phone?

dev-DaT said:
you need to download the chinese or indian fastboot rom and install it trough mi flash tool, then once the rom is installed again, you can go into the menu to enable bootloader unlock. Then you probably have to wait a week until you can unlock it using the xiaomi unlock tool.
---------- Post added at 02:23 PM ---------- Previous post was at 01:44 PM ----------
Everytime I use the latest unlocker tool my phone won't boot to OS anymore and the stock recovery boots up. I have to do a factory reset and then i have to apply for the bootloader to unlock again.
Is there an option to see the unlock time without needing to reset the phone?
Click to expand...
Click to collapse
Yeap I MR Dev-T is right did the same ~ it should get your phone runnign in no time. Good luck

Jumundz said:
Yeap I MR Dev-T is right did the same ~ it should get your phone runnign in no time. Good luck
Click to expand...
Click to collapse
How is this correct? While Installing India rom, the bootoader got locked and you’re stuck at the Recovery menu. How Can you Enable Developer Options to bind the ID again when the device doesn’t boot?
Are you saying post the lockout, you booted immediately into fastboot and used the Mi Unlock?

dev-DaT said:
you need to download the chinese or indian fastboot rom and install it trough mi flash tool, then once the rom is installed again, you can go into the menu to enable bootloader unlock. Then you probably have to wait a week until you can unlock it using the xiaomi unlock tool.
---------- Post added at 02:23 PM ---------- Previous post was at 01:44 PM ----------
Everytime I use the latest unlocker tool my phone won't boot to OS anymore and the stock recovery boots up. I have to do a factory reset and then i have to apply for the bootloader to unlock again.
Is there an option to see the unlock time without needing to reset the phone?
Click to expand...
Click to collapse
Nachiketa.jstu said:
I also made the same mistake. I tried to unlock with newest and older unlock tool, but it failed. It is showing to go and check unlock status from the developer option. My device can't boot then how can to developer option?? Please suggest me what should I do. Thanks in advance
Click to expand...
Click to collapse
Hi Mate, you tired using MiFlash unlock 2.2.4 as well ? Does it work. Basically once i Login to using my MI account and I leave the application run for few minutes and then I am able unlock the bootloader.
Most important step is that you need to put your phone to fastboot then unlock using older version -> then you should be able to boot into your ROM then from there you can enter the developer mode. But initially you should have your phone unlock(boot loader 1st right)
hope it works.

You need to boot your phone into fastboot. in order for the application to work.
Recovery menu ( Original Recovery from Mi / I have yet to load custom recovery like TWRP )
you could restart the phone and boot into fastboot even you are in the original recovery menu. Not sure if that makes sense.
thanks

My problem
Jumundz said:
You need to boot your phone into fastboot. in order for the application to work.
Recovery menu ( Original Recovery from Mi / I have yet to load custom recovery like TWRP )
you could restart the phone and boot into fastboot even you are in the original recovery menu. Not sure if that makes sense.
thanks
Click to expand...
Click to collapse
This is a problem, when trying to pass the Chinese rom with the bootloader unlocked, the phone neither turns on nor fastboot mode and is only recognized via edl, have any idea what I can do?

I can't post external link. If you search on YouTube K20Pro EDL recovery you will get the video , that that is what you looking for.
The application only works if you are in fastboot mode. Thx and good luck
Sent from my Redmi K20 Pro using Tapatalk

kinraraland said:
I can't post external link. If you search on YouTube K20Pro EDL recovery you will get the video , that that is what you looking for.
The application only works if you are in fastboot mode. Thx and good luck
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
thank you very much, do you know which channel talks about this?

How to unlock your bootloader (Chinese ROM)

Credit to @user_ScoTTT
1. First of all, you need to sign up and login on the official website of Oppo in China. (Use Google Translate if you need to)
https://bbs.coloros.net/graphic?id=1498611
2. Follow the links and download the unlock program of Oppo Find x2 /x2 pro
3. Install the apk on your phone
4. Ensure your device has the latest version of your ROM installed.
5. Click "Start Applying" on the Unlock App. You will need to wait about a month. After a month, open the application, and if "Approved" is displayed, please go to the next step.
If not, Force Close the Application several times over and over, and maybe it will display "Approved".（Some Chinese citizens reported a similar situation.）If you still can't, please contact oppo online customer service, they can solve this problem for you.
6. Next, please back up your data.
7. After receiving the 'Approval' in the app.
Go to Settings - about mobile phone - version information - version number Click here five times.
Go to settings - other settings - Developer options then Check OEM unlock.
8. Once again, open the Deep Test application and click "Start the Depth Test". The phone will automatically restart and enter Bootloader mode.
9. Connect your phone to the computer.
10. Open the command prompt browse to your adb/fastboot location and enter
"fastboot flashing unlock"
then confirm. At this time, the mobile phone will give some warning information. Please read it carefully before making a decision.
If you decide, choose "unlock the bootloader" and press the power key to restart. It is worth noting that the phone will be formatted here. If you have opened "find my phone" before, you need to enter your oppo account password to start your phone.
11. You now setup your phone as normal though with an unlocked bootloader.
12. If you wish to Root then please see this guide: https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327

can i flash global rom after unlocked bootloader ?

i was wondering the same thing. i dont see why not. give it a shot and let us know. you have nothing to lose it will simply not let you flash if it doesnt work and your existing ROM/Phone will be unaffected.

Ok, so I've unlocked my Chinese Find X2 Pro using the official method, which is by using the depth testing app and waiting for approval, then unlocking via Fastboot.
But I still can't flash the global ROM using the stock ColorOS recovery. I've tried various versions, just either get the 'Installation failed' or 'The installed version is lower than current' error.
Do I need to wait until TWRP is available for the X2 Pro or is there another way? I don't want to root, just install the stock ROM from another region. Will Magisk allow me to do this?
Was really hoping unlocking the bootloader would do it, guess it's a good start

bugger.. it would appear that the ColorOS Recovery is preventing the install. So yes you would need TWRP or someone to hack the ColorOS recovery to flash without the check.
though with an unlocked bootloader you can flash TWRP as soon as it's been developed by someone.. or risk flashing a twrp from a similiar phone?

Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
And FYI, I've been using a python tool to decrypt the ozip files. Have looked in multiple ROMs, beta and standard, Chinese and global and even a few Realme ROMs.
I'm starting to hate Oppo, it's even more of a pain in the ass than Samsung! :silly:
I bought a Xiaomi Mi Mix 3 5G yesterday off eBay just to get me by for the time being, it was a carrier version and I managed to get the stock global ROM with MI12 on it in 30 minutes using fastboot and flashing all the images. Refreshingly easy

klanbo78 said:
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
What method were you using to flash mate?
I had a look at the extract of the Global ROM and can see a heap of img files.. though your right there is no obvious Recovery image file.
That is strange. As the device has a Recovery mode. It would be very strange to make it part of the Boot Image. Surely Oppo has a recover tool that just puts everything back to default?
Click to expand...
Click to collapse

Sage said:
What method were you using to flash mate?
Click to expand...
Click to collapse
Just using the adb toools via command prompt on my PC and phone on fastboot mode.
I.e. fastboot flash boot boot.img
There's no system image either, only vbmeta_system.img which I don't think it's the same thing. Watching YouTube videos and searching the internet now to try and figure out

Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again

klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?

Sage said:
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Click to expand...
Click to collapse
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc

Sage said:
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Click to expand...
Click to collapse
Thanks for your support
I'll upload the recovery images for the global and Chinese variants once I'm back on my desktop later.
So the issue I'm facing now is it this phone doesn't have a system, vendor or product partition. My assumption is that I need to flash the global system image, as that's the one that basically contains the OS.
I think that these images are contained within the "super" partition which appears to be a dynamically resizable partition. I have no idea how to flash to these!
I'm trying to make sense of it all but fastbootd has come up a few times, which apparently is needed to flash to userspace which is where this super partition resides.
I can see in the ROM there is an updater script file that refers to these images, create groups in the super partition and resizes them as necessary. It seems to use the vb_meta_system image in some way. I have no idea how to replicate this script in fastboot though or if it's even possible?
Can anyone help?
---------- Post added at 08:59 AM ---------- Previous post was at 08:46 AM ----------
A bit of info on dynamic partitions...
https://source.android.com/devices/tech/ota/dynamic_partitions/implement

vbmeta.img removes the boot verification so you definitely want to use that. see this thread for its use.
https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327

I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?

golemagg said:
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
Click to expand...
Click to collapse
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?

klanbo78 said:
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline or something like that - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
Click to expand...
Click to collapse
Understood. I'll keep monitoring it. Thanks a lot for the information.

klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Can you please upload the recovery.img for people to use?
any other progress to report?

Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Yeah, that would be really nice. I couldn't boot also in recovery after android 11 beta:silly:

Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Here's the link to the recovery (and boot) images, have zipped them as they're quite large. I've included both variants (so PDEM30 and CPH2025).
https://drive.google.com/drive/folders/1HkNeQSuzsPDdue4KqRbDWLah0YH-CSwb?usp=sharing
In terms of progress, there is none. I got a bit adventurous and decided to flash all of the partitons on my PDEM30 with the images from the CPH2025 (manaully as there is no "flash-all.bat" file in the OTA ROM). I think it would have worked as it has for phones I've flashed this way in the past, but as I now know phones that launced with Android 10 are quite different due to having a dynamic "super" partition. This super partition contains the system, product, vendor image, etc. It should not (can't be) be flashed from fastboot as it's held in the "user space" of the phone and fastboot doesn't know how to deal with these partition types.
Pixel devices have a program called fastbootd which I think can be used for this, but Oppo doesn't appear to have that mode. Basically the phone now won't boot to recovery at all, I can only get into fastboot mode.
Not even worth holding out for TWRP as as of right now, TWRP doesn't support these dynamic partions (so any phone launced with Android 10). I contacted Oppo UK support and they said I could send in for repair, but then got told by the company who would be doing the repair (SBE UK) that they only support UK and EU devices. So looks like it might be going back to China for a repair (just need to find a freind who speaks Chinese )
Before that though I'm going to see if I can edit the recovery.img in Android Kitchen, to see if I can find the bit that's responsible for it not booting into recovery mode. I think at this point I have nothing to lose!!

I can't download unlock program of Oppo Find x2 / x2 pro, can you help me download it, thanks

Installing a custom rom

Hello
First of all, i know its risky and i don't mind it, because the emui os is totally ****ty. So i was trying to install a custom rom, but i ended up in a big unknowness. Recently I installed a custom rom on a samsung device, but that doesnt compare. My version of the phone is ANE-LX1, having EMUI 9.1.0.392. From what i know i should get an unlock code from dc-unlocker (however i totally don't know how ) and then just type some commands and get to TWRP, but from what i read there are a lot of errors so if anyone is very kind and guides me i will be very happy.
Take care!

Dc-unlocker doesnt work on emui 9. You have to go back to emui 8 to use it. And if i recall corretly you can't use emui 8 dload packages while emui 9 is installed. You can however use hisuite to rollback to 8. Dc-unlocker doesn't work in the version hisuite puts you to. So you have to downgrade little more with dload packages. I unlocked mine in build .125 or something. Just follow any youtube video demonstrating dc-unlocker once you're back in one of the compatible versions. Dc-unlocker is not your only option btw. You can use a tool called potatonv to get your code. With dc-unlocker you mess with software but with potatonv you have to short some pins on your phones board. Software or hardware, choose your poison.

Ok i understand now. However it's not the unlock problem, but after the unlock i don't know how to flash to TWRP. Can you please tell me what to do?

And one more thing @Frax3r . I was planning to install Pixel Experience 11 plus from @-Alf- , and it requires emui 9. If i unlock the bootloader on emui 8 i can upgrade then to emui 9? Thank you

Crotaru said:
i can upgrade then to emui 9?
Click to expand...
Click to collapse
Yes,
- via System (OTA) update,
- via HiSuite & PC
- using dload method & Service ROM (aka full stock ROM).

Ok thank you very much. I'll keep you in touch if something happens.
Cheers

No problem

Can't enter fastboot mode

My Realme 6 is kept showing me:
The serial is not match
fastboot_unlock_verify fail
every time I tried to get into fastboot mode Using command adb reboot bootloader,
the bootloader is already unlocked, so I can't enter fastboot mode via the (In-depth Test) App.
It would be my pleasure if anyone got a fix for this problem,
regards

Do u have a solution for this? I was able to unlock but I want to relock and in I'm getting a similar window in fastboot, mine shows this :

@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 12, after accidentally updating from rooted android 11 to android 12 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 12.
Any ideas??

leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.

soler37 said:
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.
Click to expand...
Click to collapse
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!

leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?

Y-YoUsSef-F said:
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?
Click to expand...
Click to collapse
Yeah, android 11 and 12 not 10 and 11. I'll fix it.

leopseft said:
Yeah, android 11 and 12 not 10 and 11. I'll fix it.
Click to expand...
Click to collapse
Ok bro

leopseft said:
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!
Click to expand...
Click to collapse
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.

soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Hi, but bro I am in android 12 (F.07) with magisk Root and google wallet (NFC) works great, I think for now not sure if I gonna upgrade to F.09 and losing root access
As my friend @leopseft described our situation, can't enter fastboot mode

soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Actually you can pass the safetynet tests with Magisk modules and magisk hide. But this is another topic. I can help you if you decide to re unlock and root!!
But I have an idea which I wanna try first about the access to fastboot mode.
In the guide you posted there is a step in which you bypass mtk authentication.
(4. Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.))
Did you try to access into fastboot after this step or you continue to the flash process??

Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot

leopseft said:
Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot
Click to expand...
Click to collapse
Thank you bro for this solution and I'm so glad you replied to this thread,
but for me, I was able to get into fastboot without this problem after I installed A13 custom Rom (EvolutionX v7.2 UNOFFICIAL)
I used these commands:
adb devices
adb reboot bootloader
As a reminder, my problem was:
The serial is not match
fastboot_unlock_verify fail
Click to expand...
Click to collapse
Thanks again <3

Better Mobile App

welcome