Develop Bugs

[HOW-TO] HUAWEI NOVA-PLUS root with MAGISK

Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen

MAGISK modules are HERE
Magisk MANAGER is available on PLAYSTORE

BEFORE making a twrp backup... (after data format ect.)...
you may want to FIX the huawei theme manager not working problem for some of us... the FIX is HERE
Thanks to Henkate
Youll need a good file system manager...i'm using ROOT EXPLORER and theres that new FX file explorer

does it work with android 7?

tanlikar1 said:
does it work with android 7?
Click to expand...
Click to collapse
Yes. In fact, this was meant for Android 7, but it should work on Android 6 too.

Absolutely...Im on Nougat emui5

does anyone have stock rom for MLA-L12C636B340 ?

Do you mean original firmware ?
Maybe you can still get it via firmware finder...

virusdunil said:
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
Click to expand...
Click to collapse
ya

Working on Nova?
Does it work in the non plus Nova as well? Any experiences?

Worked on Can-L11. Tested. No need format data, in twrp tree, i add img, that work with encrypted data.

I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?

Cooks_08 said:
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Click to expand...
Click to collapse
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot

virusdunil said:
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
Click to expand...
Click to collapse
Got the flash working. Used Garak's Twrp and now i got. Thanks.

Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.

Mezo21 said:
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Click to expand...
Click to collapse
Hi there,
I have Nova 2s, carefully follow this thread's instructions, it will 100% works : https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280

Thanks for the guidance, Magisk is doing very well.
Only TWRP is missing, but later.
Huawei Nova
CAN-L01C432B382

Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip

meskafonas said:
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
Click to expand...
Click to collapse
did you format data as f2fs? If yes, magisk doesn't go well along with it. If no, then you would get better support at magisk thread

virusdunil said:
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
Click to expand...
Click to collapse
Do you have this problem with fingerprint? [emoji853] https://r.tapatalk.com/shareLink?ur...share_tid=3907398&share_fid=3793&share_type=t
Enviado desde mi HUAWEI CAN-L11 mediante Tapatalk

HwOTA7 and HwOTA8 for Huawei P10 Lite

HwOTA7 + HwOTA8 for Huawei P10 Lite​1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
and will be repack firmware (only HwOTA8)!!!
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA_WARSAW.zip
Short video tutorial for upgrade of any version authorized or unauthorized in phone P10 Lite Thanks @Alexxxx1
HwOTA8 method for rollback from EMUI 8 to Emui 5 - Huawei P10 lite Thanks @Alexxxx1
If you like my work, you can thank TeamMT PayPal
PPS: Sorry for my English!!!

used this to update my phone, to oreo... but no twrp works now, recovery fails to boot! so... no way to get root xD

Locked Bootloader
GizmoTheGreen said:
used this to update my phone, to oreo... but no twrp works now, recovery fails to boot! so... no way to get root xD
Click to expand...
Click to collapse
If you read the instructions, the bootloader will be locked after the process is completed, therefore, you're gonna have to unlock it and reflash the custom recovery that you had before
---------- Post added at 10:43 PM ---------- Previous post was at 10:11 PM ----------
vovan1982 said:
HwOTA for Huawei P10 Lite​1. On the phone, make a backup of all data (since during the upgrade all data will be erased). This is an obligatory condition.
2. Unlock your bootloader: (There´s no way around it (unfortnuately), but after the procedure your device will be locked again, so don´t worry!). The device will make a factory reset, so once again, BACKUP your files!!!!!!!!!!
3. Enable ‘USB debugging’ and ‘OEM Unlock’ option from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
4. You must download three zip-archives with a full "Full OTA" firmware on which you want to flash (If you look through in the FF (FirmwareFinder), you see there are 4 archives for China and 3 for other locations. You must to download for the version what model and location you will have after the firmware);
5. Add the downloaded files to the folder "HWOTA\Update" and run the .cmd file, it will rename them automatically according to the template:
- update_data_full_public.zip to update_data_public.zip
- update_full_....zip to update_all_hw.zip
- update.zip don't rename
6. After run the universal batch file update.bat in the "HWOTA" folder, which will provide an opportunity to choose the required work option (change firmware/rebranding (change location)). FOLLOWING INSTRUCTIONS ON THE SCREEN OF THE MONITOR - the entire process is accompanied by prompts.
At the end of the process, everything should work fine... Be prepared, the bootloader will be locked after changing the location or firmware as a FullOTA.
7. If suddenly it turned out "bootloop" - go into the stock Recovery and make wipe.
PS: To change the firmware using the SD card, you need to create a folder "HWOTA" on the SD card and copy three firmware archives with the changed names (see above). In the batch file select item 1 "SDCard HWOTA directory"
HwOTA.zip
PPS: Sorry for my English!!!
Click to expand...
Click to collapse
Hello!
I need your help with the update.bat file
When I try to execute the file, it just shows a cmd screen for a couple of seconds and nothing happens
what am I possibly doing wrong?
Plus, theres no instrutions for pluggin the phone into the PC, what I being doing its plug in it on bootloader mode
I hope you can understand me, english is not my mother language.
And thank you in advance
EDIT: Forget it man, I make it work, I just copied the HWOTA directory to C: and it works
So far i just used the update firmware option and everything is working

GizmoTheGreen said:
used this to update my phone, to oreo... but no twrp works now, recovery fails to boot! so... no way to get root xD
Click to expand...
Click to collapse
Hi, of couse, on Oreo not TWRP. TWRP from Nougat does not work.

kristoff_andxp said:
If you read the instructions, the bootloader will be locked after the process is completed, therefore, you're gonna have to unlock it and reflash the custom recovery that you had before
---------- Post added at 10:43 PM ---------- Previous post was at 10:11 PM ----------
Hello!
I need your help with the update.bat file
When I try to execute the file, it just shows a cmd screen for a couple of seconds and nothing happens
what am I possibly doing wrong?
Plus, theres no instrutions for pluggin the phone into the PC, what I being doing its plug in it on bootloader mode
I hope you can understand me, english is not my mother language.
And thank you in advance
EDIT: Forget it man, I make it work, I just copied the HWOTA directory to C: and it works
So far i just used the update firmware option and everything is working
Click to expand...
Click to collapse
Yes, I can understand you. You did the right thing, way to HwOTA as short as possible.

vovan1982 said:
Hi, of couse, on Oreo not TWRP. TWRP from Nougat does not work.
Click to expand...
Click to collapse
so need to wait for twrp port... ok ^^
kristoff_andxp said:
If you read the instructions, the bootloader will be locked after the process is completed, therefore, you're gonna have to unlock it and reflash the custom recovery that you had before
Click to expand...
Click to collapse
1. it was not locked. and even if it was I can easily unlock it.
2. I flashed the recovery succesfully, it just gives an error when trying to enter it
so, need new twrp for oreo...

GizmoTheGreen said:
so need to wait for twrp port... ok ^^
1. it was not locked. and even if it was I can easily unlock it.
2. I flashed the recovery succesfully, it just gives an error when trying to enter it
so, need new twrp for oreo...
Click to expand...
Click to collapse
The greater question is: can be the bootloader locked after Oreo update ?

Eurofighter_ty said:
The greater question is: can be the bootloader locked after Oreo update ?
Click to expand...
Click to collapse
Don't know, I'm not going to try

My Bootloader is Unlocked after successful installation.
But why my PC says the prone is PRA-LX1 instead of WAS-LX1?

GizmoTheGreen said:
Don't know, I'm not going to try
Click to expand...
Click to collapse
Did u relocked bootloader?

Alexxxx1 said:
Did u relocked bootloader?
Click to expand...
Click to collapse
no. it did not relock bootloader automatically and I want it unlocked. also afraid of brick if I lock it with this rom.

GizmoTheGreen said:
no. it did not relock bootloader automatically and I want it unlocked. also afraid of brick if I lock it with this rom.
Click to expand...
Click to collapse
Yes, with this method bootloader stay unlock same as on p10 plus, but if you can enter in stock recovery no afraid of any brick if you relock bootloader.
Poslato sa VKY-L29 uz pomoć Tapatoka

for anyone wondering, I solved Magisk installation on oreo!
use .app extractor to get the RAMDISK image, patch it with magisk app on the phone. then use fastboot to install to ramdisk partition, like so
Code:
fastboot flash ramdisk patched_image.img
hope this helps

GizmoTheGreen said:
for anyone wondering, I solved Magisk installation on oreo!
use .app extractor to get the RAMDISK image, patch it with magisk app on the phone. then use fastboot to install to ramdisk partition, like so
Code:
fastboot flash ramdisk patched_image.img
hope this helps
Click to expand...
Click to collapse
Did you try it? Someone said he wasn't able to do it.

Jaizu said:
Did you try it? Someone said he wasn't able to do it.
Click to expand...
Click to collapse
yes I have magisk working
now that I think about it I tried earlier with the kernel image as well, there is no "boot" image.
maybe you need to do both kernel and ramdisk images seperately
either way, magisk working here, I already replaced the emojis

GizmoTheGreen said:
yes I have magisk working
now that I think about it I tried earlier with the kernel image as well, there is no "boot" image.
maybe you need to do both kernel and ramdisk images seperately
either way, magisk working here, I already replaced the emojis
Click to expand...
Click to collapse
So, what's the first impressions of Emui 8?
Sent from my WAS-LX1 using Tapatalk

GizmoTheGreen said:
yes I have magisk working
now that I think about it I tried earlier with the kernel image as well, there is no "boot" image.
maybe you need to do both kernel and ramdisk images seperately
either way, magisk working here, I already replaced the emojis
Click to expand...
Click to collapse
Mind sharing patched .img files? What device model are you using?

GizmoTheGreen said:
so need to wait for twrp port... ok ^^
1. it was not locked. and even if it was I can easily unlock it.
2. I flashed the recovery succesfully, it just gives an error when trying to enter it
so, need new twrp for oreo...
Click to expand...
Click to collapse
On P10 Lite with Oreo worked TWRP with P Smart Oreo.

vovan1982 said:
On P10 Lite with Oreo worked TWRP with P Smart Oreo.
Click to expand...
Click to collapse
Got a link?

vovan1982 said:
On P10 Lite with Oreo worked TWRP with P Smart Oreo.
Click to expand...
Click to collapse
If you mean that: http://www.mediafire.com/file/icpfjhw9eysjlao/FIGO321.img (TWRP-3.2.1-0 for Huawei P Smart)
I've not test yet if it's fully comatible, but you can enter into TWRP and seems to works.
Reboot into fastboot and enter the command:
fastboot flash recovery_ramdisk FIGO321.img
recovery_ramdisk partition in Android 8 is the Recovery

TWRP 3.3.1 & Root for Moto 1 Vision

TWRP 3.3.1 & Root for Moto 1 Vision​Thanks to the efforts of yuri-2016 and and my humble contribution, the TWRP 3.3.1 was made from scratch and a new method of Root was tested.
Accept this gift from the bottom of your heart! :highfive:
Instructions
USB debugging must be enabled on the phone and the bootloader must be unlocked!
1. Download attached archive TWRP_Root_Motne_Vision.zip and extract files from it in the following order::
- .bat executive file and vbmeta.img to the folder with the firmware files;
- TWRP-3.3.1_Motorola_One_Vision.img to \adb\ folder.
- TWRP-3.3.1_Installer_Motorola_One_Vision.zip, Disable_Dm-Verity_ForceEncrypt.zip, Magisk Installer, MagiskManager copy to External SDcard in your phone.
2. Load phone in fastboot mode, then connect it to PC, then start an executive file .bat. At the end of flashing the phone will reboot into bootloader-mode and then TWRP again.
3. In the Recovery at the very beginning we put a checkmark in the checkbox to avoid this request in future, and give permission to modify the system for writing.
4. Go to the Wipe page and run the Format Data for decryption. Enter "yes" for the request. Exit to the Main Menu and reboot to Bootloader.
5. Attention! You mus BOOT into Recovery mode (DO NOT INSTALL it !), through the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
6. Flash an archive TWRP-3.3.1_Installer_Motorola_One_Vision.zip which will make TWRP permanent.
NOTE: If you want to keep the stock Recovery , do not install this archive, but in order to boot into TWRP you will need to run the command from Step 5 every time.
7. Configure TWRP via “Settings”-page (time, time zone, language, etc.) as you want.
8. Go to “Install” page and flash the Magisk Installer , and flash Disable_Dm-Verity_ForceEncrypt.zip
9. Reboot in System. Phone will reboot several times, don`t worry. Perform initial settings again.
10. Install MagiskManager.apk, because the application installed in the system generates an error and does not start.
Now your device has a custom recovery TWRP and Root rights! :good: :victory:
01/10/2019 New instruction have been made
30/09/2019 New build TWRP !!!
Fixed: Removed the "Enable MTP" button.
Note: Who will reinstall the new TWRP build over the old one, follow these steps:
1. Download new TWRP_Root_Motne_Vision.zip
2. Load into Recovery mode via the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
3. Install TWRP-3.3.1_Installer_Motorola_One_Vision.zip
4. Flash Magisk installer, Disable_Dm-Verity_ForceEncrypt.zip.
5. Reboot in the Recovery again.
6. Try to adjust the brightness, connect USB-OTG, check the absence of the "Enable MTP" button.
Old instructions
Friends! I got the Root for this device.
I'm not saying it's the only way to get a Root. I suggest something I used on my own device.
You are responsible for everything you do with your device!
Getting Root was performed on firmware XT1970-3_KANE_RETEU_DS_9.0_PSA29.160-30
Attention! The process of receiving the Root will delete all your data from the device.
1. The bootloader must be unlocked on the device beforehand.
2. Extract files from the archive https://drive.google.com/open?id=1xgTVlIXOFWq59I1-D9bnRlj1heJycT_I :
- vbmeta.img, vbmeta_patch.img and boot_patch.img to the adb folder;
- MagiskManager-v7.3.4.apk to a convenient folder for you. It will then need to be copied either to the phone memory or to the SD Card.
3. Load the device into fastboot mode and connect it to your PC.
4. Flash vbmeta.img with the command:
Code:
fastboot flash vbmeta_a vbmeta.img
5. Flash boot_patch.img with the command:
Code:
fastboot flash boot_a boot_patch.img
6. Flash vbmeta_patch.img command:
Code:
fastboot flash vbmeta_a vbmeta_patch.img
7. Load the device into the system by pressing the Start button. Phone will reboot in Recovery where there will be a warning that it is necessary to execute Factory reset. It is necessary to give your consent.
The phone will reboot several times again, don't worry.
8. Perform the initial setup. Install MagiskManager-v7.3.4.apk.
9. Launch the MagiskManager application. He will offer to update the application, click the Yes button. The phone will reboot.
Your device now has Root permissions and access to the system!

ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
Thank you so much!
That's incredible. I hope it works on Moto One Action too.

ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
This is excellent news, thanks !

Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone

SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
Those step give you the validation img error

I'm continuing with my friend to create TWRP

SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
That's what a lot of people think. I thought so too.

Thank you so much for the guide... I'll try in the afternoon

@ilia3367
Hello
I have a One Action, could you help me to get root?
Do I need to patch all those images with Magisk?
Thanks in advanced.

sfoot13 said:
@ilia3367
Do I need to patch all those images with Magisk?
Click to expand...
Click to collapse
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.

ilia3367 said:
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
Click to expand...
Click to collapse
Thank you so much for your help and work!
I'll do that when I arrive at home

Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?

Tuandroidaldia said:
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Click to expand...
Click to collapse
Replied on the previous page.

ilia3367 said:
Replied on the previous page.
Click to expand...
Click to collapse
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.

@ilia3367 Finally Rooted. Thank you so much for your work. Very appreciate!

Tuandroidaldia said:
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
Click to expand...
Click to collapse
what about vbmeta? was possible to flash it?

@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?

AndresOrue said:
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
Click to expand...
Click to collapse
Magisk probably hides the bootloader status so that update check works, but it will most likely fail during install. At least that's how it works on moto one and moto one power.
On moto one I either reflash current build without wipe and then take ota and re-root after, or just flash the update if I get them early, and re-root-

AndresOrue said:
It means that I can update the firmware via ota?
Click to expand...
Click to collapse
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.

ilia3367 said:
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
Click to expand...
Click to collapse
Thanks a lot. I just unlocked my BL for the second time and this root method is working fine.
May I ask if you just used magisk manager to patch boot, cause when I do I get error on flash.
Code:
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (33792 KB) OKAY [ 1.172s]
Writing 'boot_a' FAILED (Status read failed (Too many links))
And how did you patch vbmeta?
I'm just curious since this patched boot isn't the latest and I wonder how to make this work with the latest boot.img from September patch update.

rooting ( after unlocking bootloader)

So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.

Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?

testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed

pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?

Sorry, no idea, i found the provided link via google,

testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/

zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?

No fastbootd?
One Hyper needs fastbootd in order to flash boot and root

mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.

pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery

mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?

https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know

pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.

Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.

CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super

Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.

Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.

hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.

hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.

[OP7T] Tool to root your device without patched boot.img

Hey guys, because there is unfortunately no fully working TWRP yet and lack of magisk patched boot.img for each rom, i decided to make a script to make things easier.
This script is based on the post https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100, which is based on thread [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
What does it do?
The script pull the boot image from your actual system and copy it to your PC.
Then you have to copy the boot image back to your device and patch it with Magisk Manager.
To prevent problems and bootloops the script will boot the patched image first, if anything went well the script will flash it subsequently.
Requirements:
unlocked bootloader
ADB/Fastboot installed
latest TWRP from here
Make sure the .bat and twrp image are in your adb/fastboot folder!!
How to use?
Download the .bat file, place it into your ADB/Fastboot directory and start it.
If windows shows a warning, then just click on "more informations" and then "run anyway".
If you trust me, dont trust the internet and check hash sum MD5 after downloading the file with:
Code:
CertUtil -hashfile <filename> MD5
MD5 checksum is: 303f338c32841ac752d24647ec6ede14
If you dont trust me there are several options:
Use the guide from https://forum.xda-developers.com/showpost.php?p=81277507&postcount=613 from @gpz1100 and do it yourself
or use any guide from [GUIDE] How to Root OnePlus 7T without TWRP by @mauronofrio
check the code on github here
If you run into problems/errors:
Be sure the .bat file is located where adb.exe and fastboot.exe is
If you need urgent root, than follow the guide mentioned above
Be patient, i try to fix the problem as soon as possible
Only tested on Oneplus 7T with OxygenOS
Download from: google drive or from github
Credits:
topjohnwu - for Magisk
mauronofrio - for TWRP
gpz1100 - for his guide

Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.

slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
no, but you can root again with the tool

slipnslider said:
Will I still be rooted if I take an OTA update?
Click to expand...
Click to collapse
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.

slipnslider said:
Will I still be rooted if I take an OTA update?
---------- Post added at 01:16 PM ---------- Previous post was at 12:57 PM ----------
Also at one point your after trying to pull the boot image from the phone the script says:
## checking for adb devices..
## device still not in custom recovery, retrying...
Yet the phone restarts. The script retries about 4 times then fails. I think at whatever set in the script before that occurs, it needs to fastboot into recovery rather than do a normal restart.
Click to expand...
Click to collapse
oh sorry i missed the second question,
the script should boot your phone into twrp recovery, where it get's adb access to pull the boot.img. Do you named the twrp img to TWRP.img?

Yeah it was named TWRP.img but I actually had another problem going on with my device that I believe was causing this. Got it all fixed using that back to root/unbrick Msm.exe tool that someone else posted

Worked flawlessly, got a little bit lost when the prompt about magisk came out then realised that I needed to copy files over, patch on the phone with the Magisk Manager app then copy files over again.
But once that's sorted, it worked with no issues

Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?

Radicalcokemonkey23 said:
Noob question but the flash of the modified boot.img would be a clean flash or a flash over the existing one,asking cause I haven't rooted a device and was wondering if this would erase all of my apps and existing settings?
Click to expand...
Click to collapse
Flashing boot.img won't wipe your data. But unlocking the bootloader will reset your phone.

Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
I didn't want to update because I would loose root but I'll give your advice a go.

At 71% it says something went wrong.

imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
i think ur phone disconnect during the process, maybe try another usb cable or usb port for the process

Kollachi said:
No. After ota you won't have root. But after installation of ota don't reboot and do this:
1. Open magisk manager
2. Install --> install after ota
3. Reboot.
Now you have updated system with root.
Click to expand...
Click to collapse
Yes, just make sure you install into INACTIVE slot after OTA, if you havent rebooted yet.

I believe one problem exists with twrp (possibly depending on the version) ... when the script tries to download the stock image, TWRP wants confirmation for write access. Unless I confirm that, the download doesn't succeed. Once confirmed, the same adb line in the script entered manually then works ...

I bought a phone advertised as factory unlocked. It has no carrier branding. It turns out to be a model HD1907, which in Wikipedia shows as T-Mobile.
I installed the OnePlus USB drivers from the phone.
I used the original cable.
In Developer Options I had set Advanced Reboot on and USB Debugging on. I tried OEM Unlocking on and off just to try.
I am getting a failure at the boot to TWRP step. The fastboot error, which I tried manually as well, is:
FAILED (remote: 'boot is not allowed in Lock State')
On the fastboot screen I do see the message:
DEVICE STATE - locked
Am I going to need to go through a bootloader unlocking process like this?
Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.*** A note for the Moderators: I am...
forum.xda-developers.com
It's a nicely done script, by the way.

I'm sorry but I'm really newbie, so please can you tell me how to activate adb access?

imakul8 said:
At 71% it says something went wrong.
Click to expand...
Click to collapse
I'm stuck in the same problem, I changed the slot but nothing changes...