Database Info

Root EMUI 9.0

Thx to topjohnwu you can use magisk on EMUI9. https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
What you need:
1. Unlocked Bootloader
2. be able to use twrp 3.2.3-1 (important! 3.2.3-1). In this case, im using latest offical twrp for the Huawei P20 Pro (charlotte). Only use ADB function, other features (backup/restore) are untested by me, it can harm your device eventually if you use other functions then ADB.
3. adb installed on PC
4. all-full-release.apk from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
5. magisk-release.zip from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
OK, so how we root the Honor 10 with EMUI9.0?
1. Download offical twrp from here: https://dl.twrp.me/charlotte/twrp-3.2.3-1-charlotte.img.html.
Be careful, this release was made for another device, but i had no issue with it on my Honor 10.
2. Download Magisk Manager (all-full-release.apk) from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds and install it.
3. Download magisk root (magisk-release.zip)
4. Enable OEM Unlock (so you can flash recovery in fastboot) , Power Off the device, push and hold VOL DOWN and plug in the usb cable. The device will start into fastboot.
5. Flash Twrp withon the PC: fastboot flash recovery_ramdisk twrp-3.2.3-1-charlotte.img
6. This one is a bit tricky! Type fastboot reboot, push and hold VOL UP and after sending fastboot reboot immediately remove cable and wait for twrp to boot. If you not remove the cable you will end up in eRecovery and have to redo the steps above.
7. In twrp, go to advanced and start ADB. Than plug in the USB cable.
8. PC: flash magisk-release.zip with: adb sideload magisk-release.zip
9. IMPORTANT: Remove cable, select reboot, but keep VOL UP pressed during reboot, otherwise you are not able to use magisk. You have to press VOL UP everytime you reboot the device otherwise you have to do Step 5-9 again.
10. Done, your device is rooted.
UPDATE to .162:
To Update succsessfully to .162 you have to do the following things:
1. flash emui stock recovery_ramdisk.img in fastboot (extract it from update.app using Huawei Update Extractor) use "fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG" You dont have to use recovery_ramdisk.img from .162. Just use the latest update.app to extract the recovery_ramdisk.img you can find in Firmware Finder.
2. Disable OEM Unlock and reboot the device
3. Go to Settings\System\Software Updates and Hit the 3 Dots on the top right. Select the Full Package Download.
4. Wait until download is complete and hit update. Now the device will boot into EMUI recovery and install the update the phone.
5. The device is now rootless, if you want root again, follow the instructions above.
Caution: Just in case: After the update and installation of magisk, adaway becomes unstable on my phone. It seems the "allow root" popup dont show up after adaway started. I have fixed this by autoallow root in magisk, start adaway, enable adblocking and set magisk to "ask permissions" again. After this, the popup shows correctly again. For now i have no clue why this was happen, another Honor 10 dont have this issue at all.
albysprx said:
Just disable battery optimization for magisk manager and the "allow root" popup will appear
Click to expand...
Click to collapse
Notice for UPDATE .179:
You can use the guide above but you have to update (Systemupdate) twice, since the update comes with 2 separate packages. After the first run, emui recovery shows "update failed". Just reboot to system, go to settings, and start the updateprocess again. The second package is about ~220MB in size. After this follow the guide above to get magisk running again.
Notice for UPDATE .203:
Just do the usual way. Flash STOCK recovery_ramdis.img with fastboot, reboot the phone, do the update. After this flash twrp in fastboot again and adb sideload magisk-release.zip.
Notice for UPDATE .207:
Works! Flash STOCK recovery_ramdis.img with fastboot, reboot the phone, do the update. After this flash twrp in fastboot again and adb sideload magisk-release.zip.
Notice for UPDATE .216:
Works!
Notice for UPDATE .223:
Works, but you have to use latest Magisk release (19.3) from topjohnwu: https://github.com/topjohnwu/Magisk/releases
At step 8. PC: flash magisk-v19.3.zip with: adb sideload Magisk-v19.3.zip
Notice for UPDATE EMUI 9.1:
9.1 Change a lot, you will have the latest stock RECOVERY_RAMDISK.IMG patched via Magiskmanager and install that with fastboot. After this, reboot and PRess VOL+. You will end up in eRecovery, hit Wipe/Factory Reset(Make BACKUP!) and reboot. This install magisk permanently. For Adaway: You need Systemless Mode activated in Magisk and Adaway.
Maybe i will write another Guide for 9.1, but for now im testing stability.

Thanks a lot man!

Well P20 hardware share similarity with honor 10. Twrp should work logically but you never know when you came up against something bad so I will for now hehe
Sent from my Honor 10 using XDA Labs

Will it work with mate 10 pro emui 9?

neo2k17 said:
Will it work with mate 10 pro emui 9?
Click to expand...
Click to collapse
I've tested and it works

Hi, either it's not working for me or i'm stuck somewhere.
Steps 1-5 are working.
Then it reboot the device with fastboot reboot and press&hold the vol up.
But my phone doesn't boot into twrp. All i get is erecovery.
When i turn the phone off, no usb cable plugged in and try to get into twrp by press&hold power + vol up i get:
error mode
attention!
please update system again
error!
func no: 11 (recovery image)
func no:2 (load failed!)
Click to expand...
Click to collapse
Normal boot still worked fine.
What am i doing wrong?
I just updated from 8.1 to 9 today fyi.
edit: after flashing my latest twrp image that worked i can access twrp recovery again.
but everything at /sdcard looks encrypted since all folders and files have crazy names like asdfASdfasdFGADSgm
I currently don't have any password etc. on my honor.

leAndroid91 said:
edit: after flashing my latest twrp image that worked i can access twrp recovery again.
but everything at /sdcard looks encrypted since all folders and files have crazy names like asdfASdfasdFGADSgm
I currently don't have any password etc. on my honor.
Click to expand...
Click to collapse
Android 9 comes with build in crypto, so its perfektly normal to see folders like "akgaufagkiugsduiphps". Thats the reason we have to use ADB with latest TWRP, only 3.2.3-1 has support for it. So i beleive, if you cant get 3.2.3-1 running, you cannot have magisk atm.

ThreeMMM said:
Thx to topjohnwu you can use magisk on EMUI9. https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
1. Download offical twrp from here: https://dl.twrp.me/charlotte/twrp-3.2.3-1-charlotte.img.html.
Be careful, this release was made for another device, but i had no issue with it on my Honor 10.
2. Download magisk (all-full-release.apk) from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds and install it. Its Magisk Manager.
3. Download magisk-release.zip
4. Disable OEM Unlock, Power Off device, push and hold VOL DOWN and plug is the usb cable. The device will start into fastboot.
5. Flash Twrp with: fastboot flash recovery_ramdisk twrp-3.2.3-1-charlotte.img
6. Type fastboot reboot, push and hold VOL UP until device boots into twrp.
7. In twrp start ADB
8. PC: flash magisk-release.zip with: adb sideload magisk-release.zip
9. IMPORTANT: Select Reboot but keep VOL UP pressed during reboot, otherwise you are not able to use magisk.
Click to expand...
Click to collapse
Thx a lot! Works fine
One question about 9. - I had to remove the cable first, otherwise by pushing VOL UP+reboot it goes directly to eRecovery-mode?!

Uhm ... just one question for my understanding.
How am i supposed to flash a new recovery in step 5 when i disable oem unlock in step 4?
As far as i know deactivating oem unlock prevents from flashing even if the bootloader is already unlocked.

leAndroid91 said:
Uhm ... just one question for my understanding.
How am i supposed to flash a new recovery in step 5 when i disable oem unlock in step 4?
As far as i know deactivating oem unlock prevents from flashing even if the bootloader is already unlocked.
Click to expand...
Click to collapse
You're right, i just went through without reading that point correctly. It's a little bit misleading

Sorry guys, i have edit the Post so now its more clear what to do. Thanks for the hints, it a pleasure to contribute to such a nice community! Keep rockin!

Haj
point 2
Installation Magisk all-full-release.apk. The application is installed, additional files are downloaded, but end with the message "Magisk not installed". Is this how it should be?

By keeping oem unlocked i was able to flash twrp, too.
And i was able to boot into twrp.
But for /sdcard it kept showing me the encrypted files and folders
What's the reason behind:
9. IMPORTANT: Remove cable, select reboot, but keep VOL UP pressed during reboot, otherwise you are not able to use magisk. You have to use this everytime you reboot the device.
Click to expand...
Click to collapse
Is magisk checking if vol up is pressend and then activates, otherwise it stays inactive?
edit:
i was not able to boot like mentioned in step 9.
1st try: i got stuck at "your device is booting now..." (still pressing vol up).
Then released vol up and waited for another 3-4 minutes but nothing happend.
2nd try: When not pressing any button my phone booted as expected but without magisk.
3rd try: Then i shut it down again.
Turned it on, pressend and hold vol up but i just got into eRecovery.
Any ideas?

Does this method keep magisk permanently after the first boot or do I need to repeat the procedure every time if my bootloader is locked?

Coraz said:
Does this method keep magisk permanently after the first boot or do I need to repeat the procedure every time if my bootloader is locked?
Click to expand...
Click to collapse
You don't have to do the whole procedure except step 9, you have to push VOL UP during every reboot to keep magisk active.

p. 2
magisk (all-full-release.apk) install.
select method:
- Download zip only
- Patch boot image file (then click)???

kmarek11 said:
p. 2
magisk (all-full-release.apk) install.
select method:
- Download zip only
- Patch boot image file (then click)???
Click to expand...
Click to collapse
Just install the app and go on with step 3.

To install using a zip file?

kmarek11 said:
To install using a zip file?
Click to expand...
Click to collapse
Install the apk file, the zip file is for rooting your device via adb sideload.

I am installing magisk (all-full-release.apk) from the given link
the application appears on the phone
in the magisk application I click "installation" I get communication, do you want to install Magisk-v18.0 (18000) zip? and choice:
1 I do not thank you
2 changes
3 this installation I click and the "Choose method" message is displayed: and the option to choose
1 download only zip or
2 Patching the boot image file
Which one to choose to go to the next steps?

Just updated to the Q beta, I have a little problem, any suggestions?

Hi all,
I just updated to the latest beta with Android Q, everything is fine except one thing. I successfully re-enabled Magisk with a patched boot image, and all was fine.
However when I flashed a module (despite it saying it was compatible with Q), my phone desicided not to boot anymore.
If I fastboot flash the unpatched boot image, of course it works, but I don't have root access anymore.
If I re-flash the patched boot image, it stays stuck to the boot animation.
Since I'm on Q, I have no TWRP recovery, so impossible to flash the magisk uninstaller zip.
What could I try ?
My options are now either to erase data and start fresh, which is a lot of trouble for such a small problem, or to wait for a TWRP release.
Any other suggestion would be very welcome
Thanks!
Edit: Managed to solve it. Little how-to, in case someone else has the issue :
On the PC, relaunch your adb daemon in root mode by typing
Code:
adb kill-server
and then
Code:
adb root
Now reboot your phone into Fastboot and plug it in the PC
Flash the patched boot image by typing
Code:
fastboot flash boot oos_10_ob1_patched_boot.img
and start the phone
While it's attempting to boot (it is stuck on the animation because of the problematic module), type
Code:
adb shell
then in the shell, type
Code:
magisk --remove-modules
The phone should reboot, and complete this boot sequence normally. You can then go into Magisk Manager and reflash magisk (direct install) and start over

Thanks for this. Keeping this as reference. I believe this works only if you've enabled USB Debugging in your phone and granted it access to your PC, right?

[Help] Updating to Android 11 while preserving root

I have a Pixel 3a that had Magisk installed and it has been rooted for a while. I want to upgrade to Android 11 but in Magisk Canary there is no option to install Magisk into the inactive slot. Am I missing a button somewhere or what?

SirHappyCatIII said:
I have a Pixel 3a that had Magisk installed and it has been rooted for a while. I want to upgrade to Android 11 but in Magisk Canary there is no option to install Magisk into the inactive slot. Am I missing a button somewhere or what?
Click to expand...
Click to collapse
I'm assuming youre still on 10 right? Follow the steps on magisk's github

Roarmaster said:
I'm assuming youre still on 10 right? Follow the steps on magisk's github
Click to expand...
Click to collapse
The issue is that those steps are for the stable magisk build, but as far as I can tell only Magisk Canary supports android 11. The issue being that Magisk Canary doesn't seem to have a button to install magisk into the inactive slot after downloading the update.

SirHappyCatIII said:
The issue is that those steps are for the stable magisk build, but as far as I can tell only Magisk Canary supports android 11. The issue being that Magisk Canary doesn't seem to have a button to install magisk into the inactive slot after downloading the update.
Click to expand...
Click to collapse
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again

Roarmaster said:
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again
Click to expand...
Click to collapse
Alright, I was hoping to avoid the manual route, but I'll try it, thanks.

Roarmaster said:
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again
Click to expand...
Click to collapse
Well I've tried patching the boot image and flashing 3 times now to no avail. To be clear I updated to android 11, installed the latest canary magisk manager, downloaded stock images for pixel 3a, took the boot.img from the stock images, and patched it with magisk. Now when I try to flash the patched image I get infinite G logo.

SirHappyCatIII said:
Well I've tried patching the boot image and flashing 3 times now to no avail. To be clear I updated to android 11, installed the latest canary magisk manager, downloaded stock images for pixel 3a, took the boot.img from the stock images, and patched it with magisk. Now when I try to flash the patched image I get infinite G logo.
Click to expand...
Click to collapse
In magisk manager, set the update channel to Canary before you patch the boot.img file

captain sideways said:
In magisk manager, set the update channel to Canary before you patch the boot.img file
Click to expand...
Click to collapse
It is set to canary and I am on version d6dbab53. I'm going to downgrade to android 10 for now I suppose, I'm not sure what else I can do other than wait for stable magisk to support Android 11.
edit: seems like downgrading to android 10 required a device wipe. I might just need to live without root until I can get this to work.

SirHappyCatIII said:
It is set to canary and I am on version d6dbab53. I'm going to downgrade to android 10 for now I suppose, I'm not sure what else I can do other than wait for stable magisk to support Android 11.
edit: seems like downgrading to android 10 required a device wipe. I might just need to live without root until I can get this to work.
Click to expand...
Click to collapse
It deffo works - start with a clean slate and do it step by step - I do this all the time and it does work.
Right so:
Flash a clean boot.img from the stock firmware files so your phone will boot.
When it boots, uninstall magisk manager all together and reboot.
Install the Magisk Manager linked below (confirmed working)
Set the update channel to Canary and reboot just to be sure. Open manager and see there is an update available to manager so update it and reboot.
Now copy the clean boot.img to your phone's download folder.
In manager, install magisk by selecting and patching the boot.img
Copy the resulting magisk_patched.img to your computer's adb folder.
Open command prompt as administrator and navigate to your adb folder so your prompt should reads C:/adb
At the prompt, type:
adb reboot bootloader
With your phone now in bootloader at your prompt, type:
fastboot flash boot magisk_patched.img
When it completes, start your phone. This is how I do and I've done it loads of times and I boot first time.
I have a few extra reboots in there and you can do it with less, but it just keeps every thing clean and fresh and in place while you master the process ? let me know...
http://bit.ly/magiskcanarymanagerxda

captain sideways said:
It deffo works - start with a clean slate and do it step by step - I do this all the time and it does work.
Right so:
Flash a clean boot.img from the stock firmware files so your phone will boot.
When it boots, uninstall magisk manager all together and reboot.
Install the Magisk Manager linked below (confirmed working)
Set the update channel to Canary and reboot just to be sure. Open manager and see there is an update available to manager so update it and reboot.
Now copy the clean boot.img to your phone's download folder.
In manager, install magisk by selecting and patching the boot.img
Copy the resulting magisk_patched.img to your computer's adb folder.
Open command prompt as administrator and navigate to your adb folder so your prompt should reads C:/adb
At the prompt, type:
adb reboot bootloader
With your phone now in bootloader at your prompt, type:
fastboot flash boot magisk_patched.img
When it completes, start your phone. This is how I do and I've done it loads of times and I boot first time.
I have a few extra reboots in there and you can do it with less, but it just keeps every thing clean and fresh and in place while you master the process let me know...
http://bit.ly/magiskcanarymanagerxda
Click to expand...
Click to collapse
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.

SirHappyCatIII said:
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.
Click to expand...
Click to collapse
Ah OK, I'm sorry to hear that, I really am out of ideas now but hope you manage to get it sorted if you do, let me know cos I'll be wondering about it now trying to work it out ?
Did all of the steps work apart from your phone booting? Have a look at the file size of your magisk_patched.img in windows explorer, does it report as 0kb? That happened to me one time so I just did the whole process again and then it worked

Update: I wiped my entire phone, flashed stock images, and tried again. It worked first try. Maybe it had something to do with a module I had installed? No idea. Thanks for the help though everyone.
another update: seems like one of the modules i installed (probably riru edxposed?) stops the phone from booting. Time to wipe everything and try again yayyyy.

captain sideways said:
Ah OK, I'm sorry to hear that, I really am out of ideas now but hope you manage to get it sorted if you do, let me know cos I'll be wondering about it now trying to work it out ?
Did all of the steps work apart from your phone booting? Have a look at the file size of your magisk_patched.img in windows explorer, does it report as 0kb? That happened to me one time so I just did the whole process again and then it worked
Click to expand...
Click to collapse
I think the Rira - EdXPosed module in magisk is what was stopping it from booting. I wiped my phone and restarted everything and installing magisk worked first try. As soon as I installed EdXposed and rebooted I got infinite G logo.

SirHappyCatIII said:
I think the Rira - EdXPosed module in magisk is what was stopping it from booting. I wiped my phone and restarted everything and installing magisk worked first try. As soon as I installed EdXposed and rebooted I got infinite G logo.
Click to expand...
Click to collapse
Ah lush, right, OK that makes sense
I've not used exposed since I had the moto x play (years ago) so don't have that on my phone ? glad you worked it out, it's good knowledge to have for the future
For reference, you don't need to wipe your phone, just flash the stock boot img then you can go into magisk manager and remove the offending module ?

captain sideways said:
Ah lush, right, OK that makes sense
I've not used exposed since I had the moto x play (years ago) so don't have that on my phone glad you worked it out, it's good knowledge to have for the future
For reference, you don't need to wipe your phone, just flash the stock boot img then you can go into magisk manager and remove the offending module
Click to expand...
Click to collapse
Haha wish I knew that 3 hours ago. I don't know why I didn't think to just remove the module.

I know, it's a pain in the ass but you'll remember for the future?

SirHappyCatIII said:
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.
Click to expand...
Click to collapse
I had issues also, rename the magisk_patched.img to boot.img, after I did that it booted and was rooted

Just an FYI, you can now set the update channel to beta and get the version of Magisk that supports android 11.

[GUIDE] [TA-1032] How to unlock bootloader, install TWRP and Magisk

Code:
TRY THIS AT YOUR OWN RISK! This could brick your phone. It shouldn't but it can. If you brick your phone, or anything stops working on your phone, YOU are responsible.
Reboot combinations:
Fastboot: Shutdown and with USB cable hold power and volume down until it says FASTBOOT MODE at the bottom
Recovery: Shutdown and with USB cable hold power and volume down until the
Code:
Please release key to power off *
dissapears.
Unlocking Bootloader
Code:
Note: This will delete all user data! Backup all your data before doing this!
This part of the guide is part of the tutorial made by @Arin59 at https://forum.xda-developers.com/nokia-3/how-to/method-to-unlock-bootloader-nokia-3-pie-t4012285
First of all convert your serial number (should look like NE1*************) to MD5 Hash and enable OEM Unlock in developer options.
Then reboot to fastboot and type
Code:
fastboot oem key {HASH}
then type
Code:
fastboot flashing unlock
.
To reboot to Android, run fastboot reboot.
Installing TWRP
Code:
This will delete your user data, but it should be already deleted.
You can use any TWRP image made for this device but I had the most success with https://forum.xda-developers.com/nokia-3/development/twrp-teamwin-recovery-nokia-3-t3762512 .
Flash your TWRP Image chosen with
Code:
fastboot flash recovery your-recovery-image.img
and then reboot to recovery.
In TWRP go to Wipe and then Format Data and type yes.
Install Magisk
Install Magisk normally.

< waiting for device >
I put the phone in fastboot mode and ran fastboot with the oem key md5 hash command but it just said "< waiting for device >". I think it might be because I forgot to install the Nokia 3 USB drivers. I'm using a linux computer, do I need to find OS specific drivers?
edit: And now my phone is stuck in fastboot mode and for some reason will not shutdown no matter how long I hold down the power button for.

Totalitor said:
I put the phone in fastboot mode and ran fastboot with the oem key md5 hash command but it just said "< waiting for device >". I think it might be because I forgot to install the Nokia 3 USB drivers. I'm using a linux computer, do I need to find OS specific drivers?
edit: And now my phone is stuck in fastboot mode and for some reason will not shutdown no matter how long I hold down the power button for.
Click to expand...
Click to collapse
If you're using a linux computer, you should try running the command with sudo.
If it doesn't work, try with another cable (or computer if it doesn't work) and try again.

#AC said:
If you're using a linux computer, you should try running the command with sudo.
If it doesn't work, try with another cable (or computer if it doesn't work) and try again.
Click to expand...
Click to collapse
Thanks. I've since got it working. For some reason I had to use the -i argument (the interface argument) along with the code for the device (0x2e04) "fastboot -i 0x2e04 <command>".
However, I've recently bypassed the "NO COMMAND" screen and gained access to TWRP custom recovery but in trying to shut down the phone, it shuts down fine but only boots up in fastboot mode. Even using the fastboot reboot command from adb tools boots it up in fastboot mode. This is a problem as I need to boot it in its normal mode so I can download the magisk.zip file required for installing magisk but I seem to be unable to do so.

Totalitor said:
Thanks. I've since got it working. For some reason I had to use the -i argument (the interface argument) along with the code for the device (0x2e04) "fastboot -i 0x2e04 <command>".
However, I've recently bypassed the "NO COMMAND" screen and gained access to TWRP custom recovery but in trying to shut down the phone, it shuts down fine but only boots up in fastboot mode. Even using the fastboot reboot command from adb tools boots it up in fastboot mode. This is a problem as I need to boot it in its normal mode so I can download the magisk.zip file required for installing magisk but I seem to be unable to do so.
Click to expand...
Click to collapse
Try holding volume up and down at the same time while holding the power button.

#AC said:
Try holding volume up and down at the same time while holding the power button.
Click to expand...
Click to collapse
Thanks, it worked.
Though I tried wiping, but it didn't solve the booting issue. Unsure how to proceed at this point. I feel like I've tried everything. Actually, I just checked my /boot folder and it's empty...is that why it's always booting into fastboot?
I tried using adb to sideload the magisk.zip file but then the phone rebooted into stock recovery??
Any and all guides on this say to download the magisk.apk either into the SD card or internal storage, but I don't have a micro SD card and I can't access the normal mode of the phone to download anything.
What can I do?

I've flashed TWRP successfully but forgot to download the magisk.apk. Now whenever I boot up my phone, it boots into stock recovery mode automatically, even if I tell TWRP to reboot into system it reboots into Stock Android recovery. I can still access TWRP by holding down the up + power buttons on boot though, but I can't access the normal mode of the phone anymore.
I tried using TWRP's sideload feature with ADB tools to sideload Magisk.zip and it said it succeeded but in using TWRP's install feature to find the zip file, it wasn't in /sideload/ or /storage/ as both were empty.
How can I temporarily restore normal functionality so I can simply download the Magisk manager.apk?

Oneplus 7 Pro bootloop Magisk

Hello,
I'm having a problem with Onplus 7 Pro bootlooping. It wont go past the "The boot loader is unlocked and software integrity cannot be guaranteed." screen.
It stays in that screen for about couple of minutes and then boots itself into fastboot mode. Im guessing it has something to do with Magisk, because when i uninstall it from TWRP it boots just fine. The funny thing is that i've been using Magisk for ~2 years now with this phone and haven't had any issues until now. The bootloop started after i just normally restarted the phone. And im running android 10 on the phone.
It boot into recovery fine. Also it boots into TWRP from fastboot.
Help would be appreciated, because i really dont want to reset my phone.
I will provide logs etc. if needed (im kinda new so dont know what helps).
Thanks in advance!

Kloopset said:
Hello,
I'm having a problem with Onplus 7 Pro bootlooping. It wont go past the "The boot loader is unlocked and software integrity cannot be guaranteed." screen.
It stays in that screen for about couple of minutes and then boots itself into fastboot mode. Im guessing it has something to do with Magisk, because when i uninstall it from TWRP it boots just fine. The funny thing is that i've been using Magisk for ~2 years now with this phone and haven't had any issues until now. The bootloop started after i just normally restarted the phone. And im running android 10 on the phone.
It boot into recovery fine. Also it boots into TWRP from fastboot.
Help would be appreciated, because i really dont want to reset my phone.
I will provide logs etc. if needed (im kinda new so dont know what helps).
Thanks in advance!
Click to expand...
Click to collapse
Sounds like maybe a bad or corrupted magisk module. This is what I do to remove all modules due to bootloop:
You'll need your stock boot.img and a magisk_patched.img.
1. Boot into fastboot: "fastboot flash boot boot.img", reboot
2. Start process of entering safemode: on my phone you long press power button for power menu. Long press "power off" for safemode option. Once choosing safemode, boot back to fastboot before your phone boots all the way up.
3. In fastboot flash your magisk_patched.img "fastboot flash boot magisk_patched.img", reboot. You should now boot rooted and in safemode. In cmd window, run this script:
"adb wait-for-device shell magisk --remove-modules"
Your phone should reboot rooted with all modules removed.
I don't have your phone but this works for me on mine

Tulsadiver said:
Sounds like maybe a bad or corrupted magisk module. This is what I do to remove all modules due to bootloop:
You'll need your stock boot.img and a magisk_patched.img.
1. Boot into fastboot: "fastboot flash boot boot.img", reboot
2. Start process of entering safemode: on my phone you long press power button for power menu. Long press "power off" for safemode option. Once choosing safemode, boot back to fastboot before your phone boots all the way up.
3. In fastboot flash your magisk_patched.img "fastboot flash boot magisk_patched.img", reboot. You should now boot rooted and in safemode. In cmd window, run this script:
"adb wait-for-device shell magisk --remove-modules"
Your phone should reboot rooted with all modules removed.
I don't have your phone but this works for me on mine
Click to expand...
Click to collapse
Thanks for the help, but i tried that already, it didnt solve my problem. It seems i'm going to need to do a reset

What modules are you using?
Try using Magisk canary

Did your phone get a android 11 update? If u look in twrp file manager are the file encrypted,this is what happened when 11 updates. If it's not that, and u think it's a module u can also use twrp explore and remove them ,or the terminal.