Database Develop

[GUIDE]Unlocking Bootloader + Magisk Root for Huawei Mate 20 Pro

I read through quite a few post here to get everything sorted out and in order to save every one some time here is a summary of all the info I have gathered so far, and my way to thank the forum for offering me so many helpful tips. I'll try to keep this thread updated as information comes in.
All credit goes to their respective owners, I am only aggregating all the information here.
Current status on BL Unlock:
China version: OEM unlock not greyed out, direct BL unlock possible
EU/NA version (L09/L29/L0C): OEM unlock greyed out in developer options, BL unlock possible via FunkyHuawei method by upgrading to .170.
UPDATE 2019/01/02: Some users reported they have already received the .171 update from carrier (https://forum.xda-developers.com/showpost.php?p=78571337&postcount=6), if that is the case you can skip the FH Method part and go directly to unlock BL.
Note: Currently .170 is not GooglePay certified, so Google Pay won't work on this, if you must have Google pay please wait for your carrier to update to some version that support OEM unlock (tap build number 7x to get Developer Options in Settings -> System -> About Phone and then go to Settings -> System -> Developer Options and see if Enable OEM Unlock option is enabled).
Also current recovery install requires you to boot into recovery (Power and volume up with phone disconnected from USB) every single time if you want root, which is not perfect.
The only time you'd be required to wipe your phone is right after your BL is unlocked with fastboot OEM unlock, please make sure you have a backup before doing that step.
Where to get unlock code?
In order to get BL unlocked, you need both allow OEM unlock option NOT greyed out (i.e., you can enable it) AND a BL unlock code. BL unlock code can only be purchased either from FunkyHuawei (55 USD one time for BL unlock code only or if you buy an unlimited pass 132USD for unlimited flashing + BL unlock code (note that it is locked to your phone and can not be transferred)), or MinistryOfSolutions (30 Euro, https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares, BL unlock code only).
FunkyHuawei Method (for non-China version)
1. Create an account in https://funkyhuawei.club/membersarea, buy 1 credit (if you just want to download .170 firmware, each credit cost 18USD).
2. Go to Select Firmware tab, use LYA-Global if you don't see the exact model. Then select .171 version.
3. Follow instructions here: https://pastebin.com/raw/Db5ZSyqu, you must download the specific HiSuite version (9.0.2.301）and the specific installer executable. Run the executable FHHiSuiteInstaller.exe as administrator (right-click and choose Run As Administrator) <- must run as admin since it will need to modify your host file. Make sure the script runs without error.
3.1 (Additional step for L0C): Edit the c:\users\YOURHOMEFOLDER\appdata\local\hisuite\userdata\updatedogdev\hisuiteconfig.xml file and change LYA-L29 to LYA-L0C everywhere it occurs and save the file. (Thanks to FunkyHuawei Support for pointing this one out).
4. Put the phone into fastboot mode (adb reboot-bootloader or with the phone off connect the usb cable while holding volume down, or boot the phone holding volume down with USB cable connected to PC).
5. Go to HiSuite on your PC and click on System Recovery (furthest to the right towards the bottom of the main screen), and let it do the magic. You will see some cmd windows pop up however it should get to the download progress with a percentage pretty fast, if you don't see that pop up then please check to make sure you have at least one credit in the FH Select Firmware tab and you have installed the specific versions of HiSuite and ran the installer as admin in Step 3.
6. Once everything is completed please verify to see if your firmware version is .171.
Unlock Bootloader
Again, get the BL code and go to Settings -> System -> Developer Options and make sure Enable OEM Unlock option is enabled. Also check to make sure you have everything backed up. Also enable USB Debugging in the same screen as well.
Rest is pretty standard:
Code:
adb devices (will bring up the authorization window on your phone, click on Always Trust)
adb reboot-bootloader
fastboot devices (make sure the device is in fastboot mode)
fastboot oem unlock *UNLOCK CODE*
at this point there will be a format operation performed on the phone, if it didn't complete successfully don't worry, your phone is wiped. During the boot you should see a black window with yellow text of warnings to tell you your phone is unlocked and not secured.
Go through all the steps to initialize the phone, turn on Developer options again, and enable USB Debugging again.
Root
1. Download and install Magisk Manager from this XDA post: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Switch channel, go to Magisk Manager -> Settings -> Update Channel , set it to Custom, and the URL is https://bit.ly/2N8UVlq (at the moment, per https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337). Go back to main screen and down swipe to refresh, it should say Latest Version > v18.0.
3. You will need to find the stock RECOVERY_RAMDIS.img file, I used HW Firmware Finder (https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146) to help me with the task, however I couldn't find the L0C update file and ended up using L09 update file instead, which appear to work. I also couldn't find the update.zip for .171 so I ended up using the latest full update version that was available to me (http://update.hicloud.com:8180/TDS/...69/g1750/v181585/f1/full/update_full_base.zip).
4. Unzip the file, drag out UPDATE.APP file in the zip package, and opened it with Huawei Firmware Extractor (I used 0.9.9.5 in this thread: https://forum.xda-developers.com/showthread.php?t=2433454). Extract and open the UPDATE.APP in update file. If you get a checksum error make sure to uncheck both of the verify checksum in Settings -> Extract.
5. Now you should see a RECOVERY_RAMDIS.img file, right click and extract it.
6. Send the RECOVERY_RAMDIS.img file back to your phone (anywhere is fine), go back to Magisk Manager -> Install -> Patch boot, get the patched_boot.img file from the phone back to the PC.
UPDATE 2019/01/02: @pvillasuso was kind enough to post the ramdisk image (both original and Magisk modified) for Mate 20 Pro LYA-L09 (Firmware version .171):https://forum.xda-developers.com/showpost.php?p=78575496&postcount=13, obviously use it at your own risk.
7. Go to fastboot mode again:
Code:
adb devices
adb reboot-bootloader
fastboot devices
fastboot flash recovery_ramdisk "PATH_TO_patched_boot.img"
fastboot reboot
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Boot up and if you go to Magisk now you should be able to see Magisk installed with Installed Version same as Latest Version.
Congrats you are now rooted!
In future you will need to boot into recovery each time to maintain root (which requires you to turn phone off and power + vol up), if you prefer not to do so @ThatsJustLogic suggested you can use the app https://forum.xda-developers.com/showpost.php?p=78569733&postcount=2 to add a one-click reboot from your dropdown menu.
Credits:
@ThatsJustLogic - Figured out the installation steps to patch ramdisk: https://forum.xda-developers.com/showpost.php?p=78554707&postcount=125
@duraaraa - Guy behind FunkyHuawei for figuring out the .171 upgrade and make everything works smoothly https://forum.xda-developers.com/mate-20-pro/how-to/unlock-rebrand-unbrick-update-t3855065
@mutahharbashir - Guy behind MinistryOfSolutions for the unlock BL code.
And creators of Magisk, HWFirmwareFinder, HWUpdateExtractor.

zhuanyi said:
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Click to expand...
Click to collapse
To stop you needing to do this on every boot this app: https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials allows you to add a "Reboot Recovery" button to your notification tray so its just a one tap reboot instead of holding volume up when you want to reboot after applying a change or something its something small but it saves some hassle.

Awwsome, thank you so much. Now I can finally use Google pay on global firmware 9.0.0.171. It's working perfectly

This is amazing development

Hi, can someone post his oeminfo?

On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.

Thank you for the guide.
Can we re-brand from Chinese to international now?

thunderpossuem said:
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Click to expand...
Click to collapse
How come? Can you post a screenshot with developer options on yhe screen?? Oh, you have. Can this mean that we will be able to unlock bootloader for free when v168 update arrives to other countries??
Sent from my LYA-L29 using XDA Labs

The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks

deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
That's just what i thought
Sent from my LYA-L29 using XDA Labs

Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know

pvillasuso said:
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
Click to expand...
Click to collapse
The patched file will work for anyone who has the mate 20 pro and the same FW version as you. Theres no extra steps it just removes the finding the FW, extracting and patching the image yourself They will still need magisk and the canary channel.
If you are going to share I would specify Firmware version and attach a non patched one incase people have issues and want to revert.

My phone model : Mate 20 Pro LYA-L09 (Firmware version 9.0.0.211)
patched_boot.img > https://www.mediafire.com/file/fp3jk281d47bh6k/patched_boot.img/file
Apply on your own risk , worked for me !

Hi, glad to hear that even L0C model has to the chance to root. Just wondering after flash the global .171 version which should solve the OEM greyed-out problem, the next step is to purchase a BL unlock code? And is there a chance that after BL and FRP unlocked. My model (LYA-L0C) can be rebrand to another one?

deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
Indeed it is 18 USD saved, also hopefully it is more compatible with your phone.

Can you give an example of your path to "PATH_TO_patched_boot.img"
I must be getting syntax incorrect for the file in internal storage download folder, and I have tried everything with and without / leaving out folders.

is this ota proof?

Some rooting questions....
Hi.
I will try to be brief and on topic. Feel free to remove post if not according to Xda forum rules.
Long story short. I am an heavy iOS user from the apple jailbreak scene. I am no developer (only user) and now I have taken the big step from IOS to Android.
Huawei mate 20 pro broke my curiosity. I have always "jailbroken" my iPhone since 2007 and now I am considering root of my HM20PRO.
I have some questions before I try this and brick my phone.
I have Norwegian model, LYA-L29 with 9.0.0.153 (c432) software. (BL unlock greyed out here as well)
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
Hope that someone can take the time to help me with my questions.
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
sorry for the noob questions, but I am new with this so thanks...
Regards,
Kenneth - Trondheim, Norway
PS:I have to say the switch from iOS to android and Huawei mate 20 pro have been great so far (except new replacement phone on the first day with green screen on BOE screen.) Now all is good.
Main reasons to root android?
I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.

fromiOS2Android said:
Hi.
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
Main reasons to root android? I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
Click to expand...
Click to collapse
Hi, first of all, welcome to Android
My advice is to NOT root until you got an answer to all your questions
I'll let some pros answer the technical questions on the partitions) but here's what I can tell you:
- Main reason to root for me is adblockers and (not a must though) custom roms.
- There is a function within magisk to hide root from apps.
- On the fixes, yes, 171 is the one that allows root and that's also the latest one with all the fixes.
- Once you root you stay rooted, you don't have to repeat the whole process at every boot.
- From what I read in several threads, right now you can't revert to older firmwares. Also, the 171 seems to be market specific, what I will do is to wait until the update gets rolled out in my market by Huawei, I read that the unlock bootloader option is then available officially.
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)

charliebigpot said:
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
Click to expand...
Click to collapse
Using Magisk Hide on Google Pay will prevent it from detecting root, however if SafetyNet fails then it probably still won't work.
There are a few Magisk modules that can (apparently) force SafetyNet to pass, however I haven't ever used any of them.

Urgent help regarding downgrading from pie to oreo or nougat....

Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.

drvish said:
Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.
Click to expand...
Click to collapse
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.

Only if they are same bootloader
Sent from SM-N950U Still Rooted Note 8

stonedpsycho said:
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.
Click to expand...
Click to collapse
Oh.... i checked my bootloader version is 6. Is there any way to downgrade to version 5 ????

No, there is not, sorry

Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that

drvish said:
Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that
Click to expand...
Click to collapse
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/

stonedpsycho said:
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/
Click to expand...
Click to collapse
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app

drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
As far as I am aware it is not possible without root.

drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
Just use Magisk Hide to disguise, that you are using root

Reaper1337 said:
Just use Magisk Hide to disguise, that you are using root
Click to expand...
Click to collapse
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....

drvish said:
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....
Click to expand...
Click to collapse
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.

Xenos7 said:
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.
Click to expand...
Click to collapse
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.

I hope someone can provide me edited s health apk

drvish said:
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.
Click to expand...
Click to collapse
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8

Xenos7 said:
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8
Click to expand...
Click to collapse
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....

drvish said:
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....
Click to expand...
Click to collapse
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.

Xenos7 said:
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.
Click to expand...
Click to collapse
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily

drvish said:
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily
Click to expand...
Click to collapse
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.

Xenos7 said:
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.
Click to expand...
Click to collapse
Hmmm.... lets wait for some godman to do the favour..... i am from medical profession so dont know much abt this coding stuff. Otherwise i would have done that myself :laugh:

Bootloader lock or hide

Hi,
I hope somebody can give me a hint.
I just got a used p20 pro with open bootloader but stock rom.
Unfortunately the Google security check has some "problems" with this situation and doesn't allow me to use several apps like Netflix, Google pay, etc.
So I'm looking for a way to easily fix this problem, the phone will be used by my parents.
Either lock the bootloader or "hide" it probably.
But how - I don't have the bootloader code - and I'm not too much into android rooting...
Usefull hints are appreciated.
Merry xmas
Mounty

You're on thin ice my pedigree chum..
Avoid flashing anything that would allow a block of any kind which is an absolute reality.
Having used absolutely every ROM and OS from 8.1 to 10
My advice. Flash AOSIP and then ask in thread to get safety net working.
Literally nothing else it worth your time.
Unless you're strange and like EMUI.
In such case, stuck with stock.
Just be aware you're in a position that a lot of people would kill for.

Google have done some **** stuff to make people who have unlocked bootloader a nightmare. I don't think there is a way to hide it unless you use Magisk

mounty77 said:
the phone will be used by my parents.
Click to expand...
Click to collapse
If they are not some kind of advanced users, unlocked bootloader has exactly 0 added value for them. Search the forum for flushing methods, the ones that will warn you that this method re-locks the bootloader, flush the latest stock ROM for your region and live a happy and calm life.

As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.

Horayken said:
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Click to expand...
Click to collapse
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty

mounty77 said:
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
Click to expand...
Click to collapse
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).

abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
thx for your offer/advise. I’ll try this way - it sounds most promising to me.
Can I do this on the mobile only, or do I need a pc?
Where / How do I find the ramdisk recovery?

BL Lock
I can lock (yes, lock) your bootloader for free.
Contact me at Telegram (@AntiEngineer), you don't need to open up your device.

abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
unfortionatly I wasn´t sucessfull till now.
At https://openkirin.net/ is a very usefull description availaible but I´m still searching for the RAMDISK Extract. I found that database where you can donwload several versions, but mine wasn´t provided there
https://pro-teammt.ru/en/online-firmware-database/
My Version is:
CLT-L29
10.0.0.138 (C432E3R1P3log)
Anybody knows where I can download that`?
Best regards
mounty

@mounty77
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.

You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
Click to expand...
Click to collapse
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader

mounty77 said:
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
Click to expand...
Click to collapse
Installing a "RECOVERY_RAMDIS.img" patched with Magisk is rooting the phone.

I´m fine if i have to root it to hide the open bootloader

Question EU-version how many

Everybody trying to flash/boot and everthing that couild work.
But how many have get the eu-version or global?
Have it work for nobudy?
Or that is am that doesnt get what some happen.
Are that money some waiting på Andriod 13, it should couils change language to every app.
I waiting on that, i dont come longer then unlock boatlooder.
Or are that somebody that have any simple instructures ?

I only understand from your message, that you are asking if there is anyone who is using global/eu ROM, correct? So I do use it.

Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?

zelma83 said:
Yes, that was that i was asking,i have tried many different ways but i dont get it.
Did you fink it was easy?
Click to expand...
Click to collapse
I have OP10P which is global unlocked at all so I didn't need to switch from chinese coloros to global/europe OOS.

Ok, that was nice

I have eu op10pro unlocked and rooted.

I've got a guide on how to root, plus the stock and patched boot images, I'll release them on each new update.
All will be EU
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com

Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.

zelma83 said:
Great,
But im in mac.
I download the files but i dont know to open then on mac.
And my phone is NE2210_11_A.13. Couild it work with yours settings and files?
Which firmware are to mine?
Thanks that you wrote to me.
Click to expand...
Click to collapse
You'd need windows..
So if you're on a Mac like I am for work then you could use boot camp and have a dual boot or just get parallels, have an OS within an OS, it's £70 a year but it works extremely well..

mxmda said:
I have eu op10pro unlocked and rooted.
Click to expand...
Click to collapse
I've also

Me too

Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?

zelma83 said:
Ok how have you done, like his setttings?
It says that i have one update in oxygen updater, but then it go to recovery,wipe data, reboot. I have tried all.
But couild i use magisk boot file that is to NE2210_11_A.13. like my phone is?
Click to expand...
Click to collapse
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.

I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)

Ultimatum99 said:
I'm on NE2210_11_A.13 too, local install doesn't work (it doesn't recognize the Oyxgen ROM)
Click to expand...
Click to collapse
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.

dladz said:
Turn on airplane mode,turn off wifi, then reboot, does it show it then?
read this the other day, someone was able to get it to show by doing something like this.
Or could be a Magisk module causing it, if you disable them then reboot, that may make it work.
Click to expand...
Click to collapse
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.

Ultimatum99 said:
It doesn't show if there is an update pending to install. Solution is to reset the phone and not connect it to the internet or to delete the installation hidden files.
Unfortunately the problem is not finding the option, but that when you pick the .zip for Local Install it says it's invalid. I've downloaded the ROM .zip file directly from Oxygen Updater and from external links to no avail.
Click to expand...
Click to collapse
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?

dladz said:
Ahh I see so can I clarify, at the moment you're on the Chinese OOS?
And you're attempting to install another regions firmware?
Click to expand...
Click to collapse
Correct, NE2210_11_A.13 is the Chinese version. I'm attempting to simply install an OxygenOS official ROM but it's not allowing to. I have an OP8 Plus and it worked very easily, simply pick the original ROM, local upgrade (now the option is called "Local install" instead) and then clean cache and good to go. This is not working now for whatever reason. I tried both in A.12 CN to A.12 EU and A.13 CN to A.12 EU.

dladz said:
Your phones saying you have an update?
If you're rooted then you do not want to update the conventional way..
This is in my guide on rooting mate. Just follow it.
In short to update you do this.
1. Install oxygen updater
2. Change update method to full in the app.
3. If an update is available then download the whole thing, it'll be big.
4. Once downloaded, back out and navigate to the normal phones system update and click the 3 dots, then select local upgrade.
5. Take the update and let it install.
DO NOT REBOOT WHEN PROMPTED!!!
6. Back out and open Magisk.
7. Click the top install button and then install after OTA.
8. Reboot and you're updated and rooted.
Click to expand...
Click to collapse
It didnt work.
But look here you can se update is availble but not install.
It is in full mode.

I think that i most find something else.

Question MIUI Rollback 13.0.17.0.SKFEUXM to 13.0.16.0.SKFEUXM

Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.

awambawamb said:
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
Click to expand...
Click to collapse
Google fastboot flash with PC or recovery flash via custom Recovery.
For both the bootloader has to be unlocked. In my opinion there's no other way to rollback .

I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A

awambawamb said:
....
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide......
Click to expand...
Click to collapse
I advise to search for the right information on XDA and the downloads from Xiaomi servers.

awambawamb said:
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
Click to expand...
Click to collapse
Downgrading using the rename trick is not possible now due to OTA validation. But still, downgrading is still possible as long as the bootloader is unlocked (you can re-lock bootloader afterwards btw so no worry about banking apps).
Procedure might be something similar to this:
1. Unlock bootloader
2. Flash any latest OSS ROM (this is just to remove MIUI)
3. Use MiFlash and fastboot method to install old versions (re-lock if you want)
Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.
PS: Just to add, Anti-Rollback is not yet enabled for sweet so no worries with getting bricked while downgrading. Just be careful and flash appropriately.

Thanks for the kind reply, @BigChungus321 . Glad to hear that I can still unlock and lock the bootloader! at least for those 6 months of warranty.
Just one thing, in the step you suggested you said:
1. Unlock bootloader​2. Flash any latest OSS ROM (this is just to remove MIUI)​3. Use MiFlash and fastboot method to install old versions (re-lock if you want)​Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.​​Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?

wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?

awambawamb said:
Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
Click to expand...
Click to collapse
It is the same but I do encounter people who face anti-rollback error rejecting the downgrade if flashing from MIUI to MIUI. But going from OSS to MIUI, this arb check does not seem to occur.
awambawamb said:
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
Click to expand...
Click to collapse
No clue if that prevents the issue/bug you encounter. I usually just dirty flash the full rom update (not the incremental which is around ~200mb) in recovery and I don't seem to get issue this way, aside from recovery being replaced because dm-verity is getting activated again.
awambawamb said:
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
Click to expand...
Click to collapse
I've seen many people who have this issue too. Again, no clue how to fix this. Maybe reboot, and just enable mobile data. Try changing sim card or switching sim card slots. Use other Mi Account for unlocking. I did see discussions about how using the same sim card and same Mi account can on a different device can cause this. I still have no clue how to fix this though so sorry. Might be a good idea to use a fresh sim card and mi account if you still encounter it.