Develop Bugs

Helium: Unlock BL & install TWRP & ROOT Friendly Guide

* i tested thist on my Mi Max Helium 64gb 3g Global Rom Locked Bootloder and Latest Miui 8.2.3 installed phone. Works fine
* This guide includes unlocking bootloader and installing recovery & superuser without formating data or factory reset. You also did not need flash developer rom.
* Unlocking bootloder may voids your warranty it depends on your reseller or repair service provider. Before use this guide please double check that. (i called my reseller and got confirmation not to void my warranty. Doing this advised)
* Continue At your own risk.
:silly:
1. install drivers here. if promted select install for unsigned drivers.
2. install ad and fastboot here
3. Update the system V8.2.3.0.MBDMIDL with ota or other methods from here
4. Create Mi Account and login with it on your phone
5. Go to: System Settings > About Phone and tap "Miui Version" 4-5 times to enable developer settings
6.Go to: Settings > Additional Settings > Developer Options:
Select OEM Unlock and then click Mi Unlock and And Add device (this will add your device to your account) also select USB Debugging on
7. Go to the web site on your computer http://en.miui.com/unlock/ then login with your mi account, click unlock and fill the form your name, area code, phone number, your unlocking reason
8.Do not close the web page and wait for the phone number confirmation SMS
Then enter the code. Now wait for unlock confirmation SMS. it says 10 day but confirmation SMS sent to me with in 15 minutes.
9. Do not download the new unlock tool. it is not allowed you before 70 hours to unlock your phone instead of download old version here
10. Power of your phone and press volume down + power or open an command prompt and enter
Code:
adb reboot bootloader
then Fastboot screen apper connect your phone then confirm to unlock wait for %100 then reboot phone
Now unlocking done. if you want check it from developer options when phone booted.
11. Download latest twrp img from here (i used helium version twrp-3.1.1-0-helium.img)
12. Download latest supersu zip here. i used version 2.82 recovery flashable z.p) copy zip file to your sd card or internaş storage
14. go to the twrp img folder then shift + right mouse button --> open cmd here
then enter the following:
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.1.1-0-helium.img
Keep the volume up button pressed enter the following
Code:
fastboot reboot
After a while TWRP recovery booted.
15 (optional) before installing superuser make a backup of your non touching system select backup and select all images data system cache.... and make a system backup.
16. Select install and slect superuser .zip file from internal or external storage where you copied it. Then flash superuser.zip
* note that super user zip also patching the boot image T& kernel to disable encryption and dm-verity. so there is no need to wipe data or factory reset.
16. when finished select reboot and reboot your system. when booted check for suoersu installed.
Enjoy.

Thanks for the guide.
Please note:
matrixrio said:
12. Download latest supersu zip here. i used version 2.82 recovery flashable z.p) copy zip file to your sd card or internaş storage
Click to expand...
Click to collapse
link provided here is for twrp (same as step 11), not for supersu!
thanks

BenG7 said:
Thanks for the guide.
Please note:
link provided here is for twrp (same as step 11), not for supersu!
thanks
Click to expand...
Click to collapse
Link revised Thanks

matrixrio said:
Keep the volume up button pressed enter the following
Code:
fastboot reboot
Click to expand...
Click to collapse
Could you please confirm if it should be fastboot reboot recovery?
Bcoz last time i tried to reboot to system after allowing swipe modifications i got bootloop..
So after entering recovery should i swipe to allow system modifications or keep read only? Please help....

[guide] Update Nougat and Oreo Flashing Method P10 Lite

UPDATE TO THE MOST RECENT VERSIONS NUGAT AND OREO
FLASHING METHOD​
Hello with all, I introduce myself I am catuv21 I enter this beautiful community and I have made roms for the huawei P9lite 2016, today I will leave these works for this great terminal Huawei P10lite thanks to a community of technicians that having seen my work for Pllite, they sent me a P10lite bluish, to which I am grateful and will be presenting works in this community, such as roms MidgarD (modified cover stock), MorfuZ (based on kangvip), and others.
HTML:
- An advert! The Flash phone can have bricks. I'm not responsible for that:p:p.
- If you are not sure, do not make any changes and you can leave this forum:confused::confused:.
- This method uses a modified stock recovery that does not verify the files.
- It serves to update firmware, as well as update to Oreo, but not to do Downgrade Nougat.
- also serves to perform rebrand changing cust.
- make copies of data and applications.
- I will not explain how to unlock the bootloader and install twrp, there are many tutorials.
- with this method the bootloader will be blocked again.
EXPERIENCE
- my compilation was WAS-LX3C605B172 and update to WAS-LX3C605B186 (demo video)
- being in WAS-LX3C605B186 I changed from cust REBRAND, to compilation WAS-LX1C432B208 (demo video)
- finally being in WAS-LX1C432B208 UPDATE FLASH WAS-LX1C432B321 (8.0.0.321) (demo video)
REQUIREMENTS:
- activate OEM unlocking from developer options.
- Unlock the bootloader.
- install recovery twrp P10 lite nougat
- download the firmware finder.exe to download the updates
- download the firmware of your compilation and / or rebrand compilation
- Download the HWOTA file and unzip.
- minimum battery of 50%
PROCESS.​
FLASH UPDATE
- unzip the file HWOTA.zip
- download the firmware of your compilation (settings / about the phone)
- the firmware is three files in the update.zip, update_data_full_public.zip and update_full_XX-LXX_hw_xx
- the latter "update_full_XX-LXX_hw_xx" there are usually several L21, L01, etc. just download one and it will depend on the cell model.
- If there are not three, it does not work.
- Rename the firmware as follows : update.zip, update_data_public.zip, update_all_hw.zip
- copy and paste the renamed files into the "HWOTA" directory.
- the HWOTA folder, copy and paste in the external memory.
- turn off the cell phone and boot in recovery twrp.
- change to external memory.
- find the HWOTA folder and flash the OTA_catuva21.zip file
- the cell phone will automatically restart
- and start updating let it finish
- if for some reason it remains on the black screen, or sticks to the huawei logo
- perform hard reset (press the volume more and power, and perform both wipes)
- CONGRATULATIONS UPDATE YOUR ANDROID.
REBRAND
- unzip the file HWOTA.zip
- download the "WAS-L ... C ... oeminfo.zip" (it's a flasheable file)
- download the firmware, this depends on the brand you want to change "WAS-L ... C ... oeminfo.zip"
- rename updates: follow steps 3 to 8 of FLASH UPDATE
- Create a folder in the external memory and paste the "WAS-L ... C ... oeminfo.zip" of your selection.
- turn off the cell phone and boot in recovery twrp.
- change to external memory.
- search the folder oeminfo and flash "WAS-L ... C ... oeminfo.zip"
- DANGER DANGER:crying::crying:
- when finished flashing DO NOT REALIZE REBOOT SYSTEM
- return to the main screen.
- select reebot.
- select bootloader and automatically restart in fastboot mode.
- and as you will see the bootloader is blocked.
- unlock the bootloader with your code (if it is in red, just unlock)
- once unlocked it will boot in recovery twrp.
- search the HWOTA folder
- find the HWOTA folder and flash the OTA_catuva21.zip file
- the cell phone will automatically restart
- and start updating let it finish
- if for some reason it remains on the black screen, or sticks to the huawei logo
- perform a hard reset (press the volume more and power until the wipes menu appears)
- CONGRATULATIONS UPDATE YOUR ANDROID .
CREDITS
CATUVA21 (to be adapted for this terminal)
Idrees Patel (take your night recovery, and adapt)
mankindtw (use your flash method that I publish for high ranges)
FirmwareFinder (for publishing the updates)

GOOD LINK OF THE BASE OF THIS WORK
[Guide] Mate 9 Flash Oreo Update Package and Downgrade Nougat
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
Huawei P8 Lite 2017 / Honor 8 Lite Android Oreo update brings Project Treble support
https://www.xda-developers.com/huaw...e-android-oreo-update-project-treble-support/

Removed
at the moment there are only two oeminfo flas
WAS-LX1C432 dual sim
WAS-LX3C605 dual sim
You can share your message to make it flashable.
Removed

CATUVA21 said:
UPDATE TO THE MOST RECENT VERSIONS NUGAT AND OREO
FLASHING METHOD​
Hello with all, I introduce myself I am catuv21 I enter this beautiful community and I have made roms for the huawei P9lite 2016, today I will leave these works for this great terminal Huawei P10lite thanks to a community of technicians that having seen my work for Pllite, they sent me a P10lite bluish, to which I am grateful and will be presenting works in this community, such as roms MidgarD (modified cover stock), MorfuZ (based on kangvip), and others.
HTML:
- An advert! The Flash phone can have bricks. I'm not responsible for that:p:p.
- If you are not sure, do not make any changes and you can leave this forum:confused::confused:.
- This method uses a modified stock recovery that does not verify the files.
- It serves to update firmware, as well as update to Oreo, but not to do Downgrade Nougat.
- also serves to perform rebrand changing cust.
- make copies of data and applications.
- I will not explain how to unlock the bootloader and install twrp, there are many tutorials.
- with this method the bootloader will be blocked again.
EXPERIENCE
- my compilation was WAS-LX3C605B172 and update to WAS-LX3C605B186 (demo video)
- being in WAS-LX3C605B186 I changed from cust REBRAND, to compilation WAS-LX1C432B208 (demo video)
- finally being in WAS-LX1C432B208 UPDATE FLASH WAS-LX1C432B321 (8.0.0.321) (demo video)
REQUIREMENTS:
- activate OEM unlocking from developer options.
- Unlock the bootloader.
- install recovery twrp P10 lite nougat
- download the firmware finder.exe to download the updates
- download the firmware of your compilation and / or rebrand compilation
- Download the HWOTA file and unzip.
- minimum battery of 50%
PROCESS.​
FLASH UPDATE
- unzip the file HWOTA.zip
- download the firmware of your compilation (settings / about the phone)
- the firmware is three files in the update.zip, update_data_full_public.zip and update_full_XX-LXX_hw_xx
- the latter "update_full_XX-LXX_hw_xx" there are usually several L21, L01, etc. just download one and it will depend on the cell model.
- If there are not three, it does not work.
- Rename the firmware as follows : update.zip, update_data_public.zip, update_all_hw.zip
- copy and paste the renamed files into the "HWOTA" directory.
- the HWOTA folder, copy and paste in the external memory.
- turn off the cell phone and boot in recovery twrp.
- change to external memory.
- find the HWOTA folder and flash the OTA_catuva21.zip file
- the cell phone will automatically restart
- and start updating let it finish
- if for some reason it remains on the black screen, or sticks to the huawei logo
- perform hard reset (press the volume more and power, and perform both wipes)
- CONGRATULATIONS UPDATE YOUR ANDROID.
REBRAND
- unzip the file HWOTA.zip
- download the "WAS-L ... C ... oeminfo.zip" (it's a flasheable file)
- download the firmware, this depends on the brand you want to change "WAS-L ... C ... oeminfo.zip"
- rename updates: follow steps 3 to 8 of FLASH UPDATE
- Create a folder in the external memory and paste the "WAS-L ... C ... oeminfo.zip" of your selection.
- turn off the cell phone and boot in recovery twrp.
- change to external memory.
- search the folder oeminfo and flash "WAS-L ... C ... oeminfo.zip"
- DANGER DANGER:crying::crying:
- when finished flashing DO NOT REALIZE REBOOT SYSTEM
- return to the main screen.
- select reebot.
- select bootloader and automatically restart in fastboot mode.
- and as you will see the bootloader is blocked.
- unlock the bootloader with your code (if it is in red, just unlock)
- once unlocked it will boot in recovery twrp.
- search the HWOTA folder
- find the HWOTA folder and flash the OTA_catuva21.zip file
- the cell phone will automatically restart
- and start updating let it finish
- if for some reason it remains on the black screen, or sticks to the huawei logo
- perform a hard reset (press the volume more and power until the wipes menu appears)
- CONGRATULATIONS UPDATE YOUR ANDROID .
CREDITS
CATUVA21 (to be adapted for this terminal)
Idrees Patel (take your night recovery, and adapt)
mankindtw (use your flash method that I publish for high ranges)
FirmwareFinder (for publishing the updates)
Click to expand...
Click to collapse
This is bad instruction. My HwOTA will rename the files of firmware automatically. Rebrend works in hwota, no need to flash "WAS-L ... C ... oeminfo.zip"

Can i use it to change from an android 7 custom rom to the official android 7 emui?

Mapl3x said:
Can i use it to change from an android 7 custom rom to the official android 7 emui?
Click to expand...
Click to collapse
yes you can, but my test was from a modified emui rom, but not from aosp

it worked
CATUVA21 said:
yes you can, but my test was from a modified emui rom, but not from aosp
Click to expand...
Click to collapse
it worked, now you have an official test who proves it works, thanks a lot

Mapl3x said:
it worked, now you have an official test who proves it works, thanks a lot
Click to expand...
Click to collapse
thanks to you for doing it, now you can return to emui.

After i go from cm to official emui 5.1, i forced the update to 8.0.0 using hwota,but my phone serial is still the emui 5.1 serial, what i need to do? Can i change it manually? (I have root)
(During the update it was an error but after the reboot and the low factory reset it work)

Worked!
OMG. It worked on WAS-LX21C432 EMUI 5.1.1!!! Thank you very much. Also I have a question. Can I make "how to install" video? Thank you

Can i flash oreo update from c432b198 build

Thread closed until download links are available that are not pay per click.
Edit: Thread reopened.

[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)

How to Flash TWRP & Root Samsung Galaxy A10 series (Unlocked Exynos Only, A10s (A107F/M) not supported)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!).
How to get OEM Unlock option back?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.2. setup the phone by skipping the wizard.
B. Disabling Android Verified Boot
1. Reboot to DOWNLOAD mode.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
C. Flashing TWRP/Magisk
link
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Thanks and credit
For more details read Installation guide by @topjohnwu from Here.
All credit and thanks go to @topjohnwu for magisk & guide.
@dr.ketan for this guide from Here
@jesec for rooting guide Here
@ianmacd for multidisabler from here
Me

reserved.

Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?

dani3ltony said:
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
Click to expand...
Click to collapse
Unplug USB and replug it then make sure the size of tar file almost the same as origin.

for step 6, can we transfer the file via SD card?

afaneh92 said:
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
Click to expand...
Click to collapse
Hi
I triple did it, but no luck

s_ryan said:
for step 6, can we transfer the file via SD card?
Click to expand...
Click to collapse
Sure.
dani3ltony said:
Hi
I triple did it, but no luck
Click to expand...
Click to collapse
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.

I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
afaneh92 said:
Sure.
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
Click to expand...
Click to collapse

s_ryan said:
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
Click to expand...
Click to collapse
yes
will try to make patched tar for all bootloaders when I got some free time.

Guide updated with more details

Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
afaneh92 said:
Guide updated with more details
Click to expand...
Click to collapse

s_ryan said:
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
Click to expand...
Click to collapse
My bad I didnt test this, the BL file contain vbmeta.img and need to be patched. Will try to find better solution.
You can flash stock BL file only then reboot again to bootloader and flash the rest files.

I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!

s_ryan said:
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
Click to expand...
Click to collapse
Can you replace vbmeta.img from patched AP with BL using 7zip.
remove md5 extension from BL file.

Guide updated and added flash TWRP instructions

afaneh92 said:
2.Download A10_multidisabler-*-1.41.zip from here and copy to Ext Storage (Because once you flash TWRP, Int storage will not be readable)
Click to expand...
Click to collapse
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.

ianmacd said:
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
Click to expand...
Click to collapse
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.

afaneh92 said:
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
Click to expand...
Click to collapse
Thanks. In your case, it's easier now if you just verify that the script I attached is working, since I've already integrated the changes you made in your clone.
Anyone who wants multidisabler support for a new device, however, can either send me a pull request against the latest code, or run the following script on a live, rooted device:
Code:
#!/bin/sh
getprop ro.boot.bootloader
echo --
ls -l /vendor/etc/init/pa_daemon*.rc /vendor/etc/fstab.exynos*
echo --
cat /vendor/etc/fstab.exynos*
echo --
su -c cat /init.rc

Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.

s_ryan said:
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
Click to expand...
Click to collapse
Try using this vbmeta.img (inside the tar file). It worked for me on the A20 with similar error. This file normally seems to be a checksum checker and if it doesn't match what the phone wants to see it gives you that error. But this file was modified to essentially be blank so there is nothing to give the phone an error.

Convert Docomo dtab d-02h into Global version 802L

I do not own any of the original work. I just tried it, it worked and Reposted in XDA as there was no such guide here. I know it is an old device but there are still some legends and those people can take advantage of this guide.
It only takes time to do it properly, so you can download necessary files and so on.
Start TWRP
Connect to PC by USB debugging and execute adb reboot recovery command, or press and hold the volume button and power button at the same time (about 8 seconds) from the power off state to start.
Select Wipe ⇒ Format Data from the menu and select yes. . .
* If you do not delete the data once, the upgrade package distributed for Mediapad M2 to be introduced may cause an installation error.
File download
The DL and folder name of the required files are " M2 ". (Zip and harden)
Decompress after DL and move the files inside to "platform-tools".
BOOT.img
CUST.img
SYSTEM.img
RECOVERY.img
There are four files mentioned above.
Install M2-android5.1.X. . .
* If you do not do this, you will not be able to upgrade to a later version.
* Please keep your PC and tablet ADB after this.
adb devices
fastboot flash boot BOOT.img
fastboot flash cust CUST.img
fastboot flash system SYSTEM.img
Finally, make the recovery the original M2 one
fastboot flash recovery RECOVERY.img
fastboot reboot
After reboot, it will be changed to Huawei M2-android5.1.X including recovery.
Download "M2-802LC229B207CUSTC229D006" from " [ROM] [STOCK] [Android 6.0] [M2-802L] B207-Android 6.0 Marshmallow with EMUI 4.0 " of Android 6.0 Marshmallow with EMUI 4.0
XDA . Move the downloaded file to the platform-tools folder without decompressing it and execute the following command. * Please create a "dload" folder in the tablet in advance, otherwise an installation error will occur when the command is executed.
adb push update.zip /sdcard/dload
After transfer, open Settings ⇒ System Update and select “Update Locally” from the menu. After selecting update.zip, tap Install to start the update.
With the above, it is changed to Huawei M2-android6.0.X / EMUI 4.0.X. . . Remember to reboot after installation! ! !
Credits: https://www.yukari.ne.jp/shtml/?p=14588
https://utekno.com/konversi-huawei-dtab-d02h-ke-mediapad-m2-14905

hi,. i just want to clarify, i have this dtab d-02h docomo lock and i cant use it with my simcard.. will this tutorial work? after this i will be able to use diffrent simcard?

hi good day, my tablet sim network lock,. can i still proceed with this? do i need to unlock my bootloader first?? thank you!

hello, i have this dtab d02h, network locked from docomo japan.. current os is 5.1.1, can i skip the 1st step "flash via fastboot" and directly flash the update.zip using dload method.. local update through secret code using calculator... because there is no local update in settings..

How To Guide [CLOSED] [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13-A.10

This tutorial will :​
Provide you with all the steps to unlock your Oneplus 11 bootloader
Provide you with all the steps to root your Oneplus 11 (with your bootloader already unlocked)
Provide you with all the steps to keep root during/after an OTA (system update)
Provide you with some Interesting Magisk Modules
Provide you with a lot tricks if you have troubleshooting questions
Provide you with a lot of solutions of you have softbricked your Oneplus 11
Provide you with all the ways if you want to bring back your Oneplus 11 to unroot & lock back the bootloader
PHB110 - China : ColorOS
CPH2447 - India : DA
CPH2449 - EU : BA
CPH2449 - GLO: International
CPH2451 - NA/Global : AA / North America
Original_Init_boot images : Extracting Payload.bin
use payload dumper go from https://github.com/ssut/payload-dumper-go
Guide: how to extract payload from the OTA Package and get the init_boot.img ?
And share the Original_init_boot.img with us by posting them in this thread.
All init_boot.img are Orginals (not patched with Magisk, that will be your job to patch them following the guide below!)
OxygenOS 13.1.0.501_init_boot :
CPH2451 Init_Boot (AA) / Not yet available
CPH2449 Init_Boot (BA/GLO) / Not yet available
CPH2447 Init_Boot (DA)
Full OTA packages / Not yet available
OxygenOS 13 A.10_init_boot :
CPH2451 Init_Boot (AA)
CPH2449 Init_Boot (BA/GLO)
CPH2447 Init_Boot (DA)
Full OTA Packages / Full OTA EU A10 / Full OTA DA/India A10
OxygenOS 13 A.09_init_boot :
CPH2451 Init_Boot (AA)
CPH2449 Init_Boot (BA/GLO)
CPH2447 Init_Boot (DA)
Full OTA packages
OxygenOS 13 A.08_init_boot :
Init_Boot (AA)
Init_Boot (BA) / Not yet available
Init_Boot (DA)
OxygenOS 13 A.07_init_boot :
Init_Boot (AA)
Init_Boot (BA)
Init_Boot (DA)/ Not yet available
OxygenOS 13 A.06_init_boot :
Init_Boot (AA)
Init_Boot (BA) / Not yet available
Init_Boot (DA) / Not yet available
PHB110 - China : ColorOS
CPH2447 - India : DA
CPH2449 - EU : BA
CPH2449 - GLO: International
CPH2451 - NA/Global : AA / North America
STEPS to root your device:
I recommand to update first your device with all OTA available using Settings/updates before unlocking & rooting it. It is also recomended not to set any lockscreen password before unlocking the bootloader/rooting. So if you have a lockscreen password / fingerprint just remove it, root your device and set it up after rooting your device.​Unlock the Bootloader and Root the OnePlus 11​Step 1 – Enable OEM unlocking​You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings > About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2 – Unlock your bootloader​Set up adb, reboot into your bootloader, and run the following command. Yes, it’s really that simple!
"fastboot flashing unlock"
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Unlocking the bootloader wipes your device :
Root your Oneplus 11 (with Bootloader already unlocked)​
Patch OnePlus 11 Init_Boot.img via Magisk​
Download and install the lastest Stable Magisk App starting from v26.1 works fine.
Then launch it and tap on the Install button next to Magisk.
After that, choose ‘Select and Patch a File’, and navigate to the stock init_boot.img file, and select it.
Then tap on the Let’s Go button situated at the top right.
The init_boot.img file will now be patched and placed under the Downloads folder on your device. You should transfer this file to the platform-tools folder on your PC and rename it to magisk_patched_boot.img.
Boot OnePlus 11 to Fastboot Mode​
Now connect your device to the PC via a USB cable. Make sure USB Debugging is enabled.
Then head over to the platform-tools folder, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the following command in the CMD window to boot your device to Fastboot Mode "adb reboot bootloader"
To verify the Fastboot connection, type in the below command and you should get back the device ID.fastboot devices
Flashing the magisk_init_boot​1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. First, enter the following command in the PowerShell/Terminal window to ensure that your PC can communicate with the phone over the fastboot interface.
"fastboot devices"
The command should return your phone’s unique ID. In case it doesn’t, then make sure that you have the required USB drivers installed and restart your PC. You can also use TOOL ALL IN ONE, not officially updated to Oneplus 9 Pro but once install go to Others options and go to Install drivers.
3. Code once in fastboot mode:
"fastboot flash init_boot magisk_init_boot.img"
Change to the exact name "magisk_init_boot.img" of the init_boot that has been patched
"fastboot reboot"
Step 2 - Reboot and your device is now rooted !​
Keep Root after OTA Updates​
How to update OTA and KEEP ROOT
It is advised to disable or even uninstall all magisk modules to be safe!
How: go to Magisk application/modules/disable &/or uninstall
Option 1: With full OTA Access (BA/DA) :
Step 1 - Get & install the full OTA zip file​1. Go to System-Update or update get the OTA using Oxygen Updater
2. Tap OK when the message that you are rooted appears
3. Tap "Download and install" or local update if OTA from Oxygen Updater
For Android 13, install this APK "OPLocalUpdate_For_Android13.apk"
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW! Use the above application to make sure your device will not reboot
5. Open Magisk Application
a. Select the Install option.
b. Use Install to inactive slot
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​​Option 2: with incremental OTA Access (AA) :​
Option 2A : Get back your original init_boot image using Magisk Manager
1. open the Magisk Manager application, select “Uninstall”, and choose the “Restore Images” option. Magisk will restore your phone’s stock init_boot image that was backed up during the rooting process.
2. Now go to “Settings” → “System” → “System updates” and select “Download and Install Now” to install the OxygenOS OTA update on your rooted OnePlus 11
3. Open Magisk Manager
a. Select the Install option.
b. Use Install to inactive slot
Reboot and enjoy​
Option 2B : Get back your original init_boot image
You can find your originel init_boot.img in our thread from your current OTA.
Go to fastboot.
Code once in fastboot mode:
"fastboot flash init_boot original_init_boot.img"
You will obviously loose Root access once you have flash the originel_init_boot.
Then just flash the incremental OTA using your system OTA or Oxygen Updater.
To get root again just read the above guide :
Patch OnePlus 11 Init_Boot.img via Magisk​
Troubleshooting questions :​
Before reporting any trouble, follow the steps below in order to have GooglePlay certified, keep L1 Widevine & pass CTS :
Step 1 - Magisk Settings​1. Once rooted, in Magisk setting, select MagiskHide and Systemless host
2. In MagiskHide select GMS, Netflix, Google Store & any application you may find sensitive to Magisk detection
For Netflix, go to Settings, Appplications & select Netflix:
a-force stop the app
b-clear cache and storage
c-hide the App in magisk
d-restart phone to recovery and clear cache
Hide everything under Google play services and store.:
3. Reboot
Step 2 - Clear caches​Clear caches of Google Play Service & Play Store
Go to Settings, Applications & select Google Play Service, delete data
Go to Settings, Appplications & select Play Store, delete data
Step 3 - Safetynet Fix​Install Safetynet Fix Magisk Module
Step 4 Optional - Shamiko Module​Install Shamiko Module​How to use it : guide
How to fix Netflix ? :​​If you can't install/update Netflix thru Google Play install the latest Netflix from apkmirror manually (like any other apk file)
Option 1 - Follow this guide​
Option 2 - Flash the DRM module attached
Option 3 - Flash another DRM module attached
Usefull Magisk Modules For Oneplus 11:​Google materials:
Enable Call Recording with native
Enable unlimited storage Google photos
Music & Video materials:
Viper 4 Android
Revanced Manager to get Revanced Youtube & others Revanced applications
Theming materials:
- Substratum lite : Liv Dark theme & OOS Outher theme
- Cyberpunk Bootanimation
- OOS Status bar magisk module (see attached)
- Repainter application
- Seeker application
- LWP+ application
- OOS themer by Oneplus
Tools materials:
Enable Volte
Enable Engineering unlock
Enable IPV6
Disable Flag secure
Magisk Bootloop Protect
Modules Management materials:
Fox Module Manager
Phone Bricked ? :​
Five options (ranked from the easiest to tougher method):
Option 1 - Reboot to Safe mode & remove Magisk modules​
Option A : Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Option B : thru adb command
1. Code with phone connected with USB debugging on (from developpers options):
"adb wait-for-device shell magisk --remove-modules"
2. reboot
Option 2 - Get back the original init_boot.img​If your device can go to fastboot mode:
Flash back the original init_boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash init_boot.img" (use the "Original_init_boot.img" from the above zip file)
Change to the exact name "Original_init_boot.img" of the boot that has been posted in the above zip file
"fastboot reboot"
Option 3 - Flash the rollback full OTA file (will wipe data)​
OnePlus 11 / Rollback packages :
OnePlus 11 NA Version (A.09)
OnePlus 11 IN Version (A.09)
OnePlus 11 EU Version (A.09)
OnePlus 11 GLO Version (A.09)
Flash it using local update or thru the application OPLocalUpdate_For_Android13.apk
You can also flash it by extracting and flashing the partitions using fastboot and fastbootd manually.
You may also use Fastboot Enhance.
​Option 4 - Flash back full OTA file​If you can still go to Settings:
Flash back the OTA RUU full package and reboot
Option 5 - Change the active slot​If your device can go to fastboot mode:
"fastboot getvar current-slot"
This will tell you what (corrupted) slot you are currently booting from (either a or b).
Then just change to the other slot with the following command:
"fastboot --set-active=a"
or
"fastboot --set-active=b"
Then reboot with the command:
"fastboot reboot"
Option 6 - Wipe data with fastboot command​
Code once in fastboot mode:
"fastboot- w"
Option 6 - OFD/EDL​
Option 1, 2 & 4 would normally not alter your personal data, applications and own set-up​Option 3 and 6 will wipe your personal data and applications
Return your phone to unlock and unroot? :​Option 1 : Original init_boot & relock with fastboot command​Step 1 - Restore orignal init_boot.img​Option A : Thru Magisk App
Open Magisk App on your phone. You will see the Uninstall button in the app. Just click on Uninstall button.
Then you need to click on Complete Uninstall. Your phone will be rebooted automatically.
Option B : Thru fastboot mode
Flash back the original init_boot.img (w/o magisk) and reboot
Code once in fastboot mode:
"fastboot flash init_boot.img" (use the "Original_lnit_boot.img" from the above zip file)
Change to the exact name "Original_init_boot.img" of the init_boot that has been posted in the above zip file
"fastboot reboot"
Once booted, remove Magisk application
Option C : after removing Magisk app entirely Flash the current or latest full OTA zip twice. Why twice, to ensure both slot have the latest update flashed with original init_boot.
Step 2 - Relock the bootloader​1. Execute the following command to proceed for bootloader unlocking: ""fastboot flashing unlock""
2. A verification window will appear on your mobile device asking to confirm the action. Just highlight “Relock Bootloader”using volume buttons and hit the power button to confirm.
3. The phone will initialize to relock the bootloader. It will take some time to reboot after resetting the whole phone into a locked stage.
4. Your device is now locked again !
Do any process described at your own risk. None Xda none the author are responsible for your own choice to unlock & root your Device.

Great job, @Steve0007! That looks like an incredibly helpful and well-written tutorial. You've done an excellent job breaking down a complex process into easy-to-follow steps, making it accessible for users of all levels. Your attention to detail and clear explanations make it a valuable resource for anyone looking to learn and improve their skills. Keep up the great work!

Sorry for the pollution, but : just WOW. Thank you for your valued time and gathering all this here.
> I didnt know you can skip uninstalling magisk if you do a full OTA update, nice.
> You actually cannot clear cache from the recovery on this phone (with included recovery that is)
> Despite following the instructions thoroughly (except the full wiping cache), i still cannot use Netflix. Might be really device related though since i never had issues will my previous devices

Thank
_Johnito_ said:
Sorry for the pollution, but : just WOW. Thank you for your valued time and gathering all this here.
> I didnt know you can skip uninstalling magisk if you do a full OTA update, nice.
> You actually cannot clear cache from the recovery on this phone (with included recovery that is)
> Despite following the instructions thoroughly (except the full wiping cache), i still cannot use Netflix. Might be really device related though since i never had issues will my previous devices
Click to expand...
Click to collapse
Thank you for your comments.
Just updated the guide included 2 options to get Netflix working while rooted !

Thank you and @qriozum , i have netflix working following this steps. Didnt even need to hide it in magisk.

Can I extract the stock init_boot after unlocking bootloader cause I didn't do that before unlocking bootloader. Plus, can anyone teach me on how to extract the stock init_boot. I'm using OxygenOS 13 A.08 CPH2449- EU : BA.

kairukaizer99 said:
Can I extract the stock init_boot after unlocking bootloader cause I didn't do that before unlocking bootloader. Plus, can anyone teach me on how to extract the stock init_boot. I'm using OxygenOS 13 A.08 CPH2449- EU : BA.
Click to expand...
Click to collapse

Thanks. Rooted successfully. Btw how to get root with locked bootloader? Cause I want to get L1 for netflix. I could get root with locked bootloader on my rog 6.

kairukaizer99 said:
Thanks. Rooted successfully. Btw how to get root with locked bootloader? Cause I want to get L1 for netflix. I could get root with locked bootloader on my rog 6.
Click to expand...
Click to collapse
You can't get root with locked bootloader on this (and most) phones.
Anyway, root doesn't necessarily mean that you won't get L1. On my rooted OnePlus 8T I still have L1.

i am on cph2451_11_A09...patching above a06 initA06 and flashing on this build works or not?

N
vnod said:
i am on cph2451_11_A09...patching above a06 initA06 and flashing on this build works or not?
Click to expand...
Click to collapse
No, you should better use your current init_boot.img to patch it. Now we can use the latest v26.0 Magisk app

Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !

zeldomar said:
Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !
View attachment 5881975
Click to expand...
Click to collapse
I tried the second:
And since my OnePlus 11 is in bootloop (the animated OnePlus logo never appears).
Can you help me, please?
Thanks a lot

zeldomar said:
Hello @Steve0007 ,
What is the correct command to enter please, the first or the second?
Thanks !
View attachment 5881975
Click to expand...
Click to collapse
"Fastboot flash init_boot NAME_OF_YOUR_Magisk_init_boot.img"

zeldomar said:
I tried the second:
View attachment 5881985
And since my OnePlus 11 is in bootloop (the animated OnePlus logo never appears).
Can you help me, please?
Thanks a lot
Click to expand...
Click to collapse
My OP 11 works again thanks to this tutorial : https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/

Hi ,can someone please post boot.img for CPH2449 (EU) A.09? I accidentally flashed init_boot over boot... what a silly move.
Alternatively, the link to the A.09 OTA, I can extract it myself, I tried looking for it but for now nobody posted it.

@geomass this is untouched boot.img for CPH2449 (EU) A.09
But FWI you could just retrieve it yourself easily with lets say Fastboot Enhance and the firmware itself of course.

Thank you so much @_Johnito_ . The timing of your response is insane
I don't use windows so can't run fastboot enhance. How can it be done with fastboot?

You are welcome. I am not the most informed guy here by far but my guess is that if you borked boot.img on your phone, it is probably better to recover it from the vanilla firmware more than from the phone (with fastboot commands). I hope i get your question right though.
For general cases, instructions on "how to backup persist.img" on this great tutorial can be applied for any android partition / any desktop OS with a command line software.

I tried booting into that image you provided, and while it correctly sends it to the device and reboots the device, it goes into fastboot every time.
Flashing it fails every time, like so:
fastboot flash boot boot_CPH2449_11_A.09.img
Sending 'boot' (196608 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed