Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Catter38 said:
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Click to expand...
Click to collapse
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Unfortunately, I forgot to uninstall the modules.
I tried the adb command and the device reboots, but it's still in the same bootloop.
I also tried to uninstall the modules with TWRP, but since there isn't a fully working version for the OP7T Pro, this also didn't work.
What's weird is, that the magisk patched version of the boot.img always results in a way smaller file than the original.
The original file is ~100mb, while the patched version is ~40mb.
I don't know if this is normal, but it seems odd.
I also tried it with the canary version of magisk, which results in the same small boot.img.
Looks like I have to stay unrooted until this is fixed.
Ok, finally I got it to work.
Since my girlfriend also has a OP7T Pro and still is on 10.0.8 with root, I simply took her boot image and booted it with fastboot. This also resulted in the same bootloop, but now the adb command worked and I was able to boot a rooted 10.0.8 boot.img. Now I was able to use the direct install of magisk and patched the 10.0.9 installation with it.
I think my problem was, that I did't remove the modules in the first place, which screwed up the whole update.
I still can't explain why I wasn't able to patch the boot.img with magisk. It didn't work on my phone with the canary build of magisk, neither did it work on the phone of my girlfriend with magisk 20.4.
Anyway. Now I have a working 10.0.9 boot.img and can safely upgrade my girlfriends phone too.
Thanks for the help!
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img..... ?
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... Last build... Patched and the original img..... ?
Click to expand...
Click to collapse
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
https://app.box.com/s/at1mhbvpkspg4wfzp16cqppgdvvidese
I'm using it now.... Without problem
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
It seems to be normal. I'm not sure why but it might be due to compression. Anyway, glad you figured it out.
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img.....
Click to expand...
Click to collapse
Would you mind uploading the files again if you can? I'm struggling with my device being in bootloop and I can't remove the module causing it bc I can't access adb with the bootloop. With the stock boot img I'm hoping to boot the device again and remove the bad module via adb
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Im im a similar situation now, is there a way before removing the modules all i can backup them or atleast access a file or something with the modules names ?
kovacsabesz: can you please reupload the file? Thanks
Related
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
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
5 ) Enable adb debugging on your Pixel 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
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
so i tried to install viper4android and the driver made my phone be stuck at boot, ( i got it to boot by using the unpached boot image, but now i lost my root functionality)
so what i need is a modded recovery that supports adb
i found a tutorial in the oneplus forums to modify the recovery and give it adb shell posibilities, but thusfar i am unsuccessfull in modding the recovery
the original post describiong how to mod the recovery is located here
my post asking for help is here
the reason i post this topic is for references mainly,
if there is a solution i will link it here as well, so if anyone else runs into it, the solution can be found easily
Viper4android does not work on Android 10
subhnish said:
Viper4android does not work on Android 10
Click to expand...
Click to collapse
sadly i figured that out the hard way
because of the installation of the magisk module, if i use the patched bootloader i keep being stuck in loop.
So if you have any idea how to fix that, that would be nice .
so far the only way i found how to fix this is patching the recovery mode so i could adb from there, but sadly my attempts are unsuccessful
i posted a way to uninstall magisk modules with out a custom recovery on the oneplus one forum, there is a working viper4android for Q that works just fine with out any hassle of getting bootloop which is in the app section on xda viper4android fx 2.7 stable version 2.7.1.6 from march 17 2020, i have installed this version on my phone oneplus7t open beta 2 android 10 and it works just fine. try this out to see if it works i had some issues with a magisjk module and my device was stuck on a bootloop and this got me out of it, the only way i was being able to get in was like you said instlaling the stock boot img with out root, once i installed the boot img with root i would get the bootloop again so i found this method online and it saved my ass with out the need to install any extra stuff worked perfect clearing all the magisk modules from my phone with out losing root.
The way i remove my modules without installing any custom recovery is just by turning off the phone, connect to pc, go to command prompt, type the path of the folder where fastboot and adb is, type the following command: adb wait-for-device shell magisk --remove-modules,(while phone is off) turn phone on wait for it to get to the boot screen it will reboot, once it reboots modules will be uninstalled.
lil_kujo said:
type the following command: adb wait-for-device shell magisk --remove-modules,(while phone is off) turn phone on wait for it to get to the boot screen it will reboot, once it reboots modules will be uninstalled.
Click to expand...
Click to collapse
i've been looking in the pixel forums, and i think i also came a cross a post in the oneplus forums, but the command doesn't seem to work. but i guess that's due to not being able to use adb commands
my first idea was to get a recovery that supports adb, but i was unsuccessfull in modifying the recovery.
the same thing seems to happen with th alternative options i found:
what I tried first:
1
I tried to make an updated init file for the boot image that boots magisk in core-only mode. Modules should be disabled in that one.
I compiled magisk, and got the core-only init file, and replaced in the patched boot.img ( instructions I followed are Post #3 on this thread: https://forum.xda-developers.com/pixel-3a-xl/how-to/magisk-modules-disabler-booting-magisk-t3976625
Sadly, this made it still boot loop.
2 I added overlay.dcoreonly1.zip from this thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sadly, this also makes it boot loop.
for a second there I thought extracting and repackaging was the issue, but tried that as well with the non-patched boot version, and no problems there.
I cannot seem to figure out why this doesn’t work.
any suggestions are very welcome.
Now back on non-rooted version.
after resetting / factory whiping from the recovery , i repatched everything and am back on root again, so for now the issue is gone, but still it would be nice to have some backup if this goes wrong again, so if anyone has an answer to the above, that would still be nice.
on one of the oneplus forums i found this promesing news:
https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24
so i guess with a new magisk version and booting into safe mode it should be possible to recover.
i've been trying to figure out how to get into safemode, but so far i have no clue.
a google search did not really reveal hw to do that.
Did anyone here find out how to boot into safe mode?
https://support.motorola.com/us/en/Solution/MS148713 - When the phone is working.
From the off phone - hold while starting VOL-
subhnish said:
Viper4android does not work on Android 10
Click to expand...
Click to collapse
it works on my 10
3dekstron said:
https://support.motorola.com/us/en/Solution/MS148713 - When the phone is working.
Click to expand...
Click to collapse
i guess when in bootloop this is a bit useless, but still good to know
senz90 said:
From the off phone - hold while starting VOL-
Click to expand...
Click to collapse
This was indeed the info i was looking for. Thnx for that , ... didn't know it was so simple
i tried it a couple of times, and apparently you need to start pressing volume down when you see the first moto logo
if you hold it down right from the start it won't boot into safe mode
anyway,
This would mean with the new magisk ( when it becomes available ) we would have an easy recovery from a faulty module.
as soon as i find out the how and when, I'll post it here with some instructions
senz90 said:
it works on my 10
Click to expand...
Click to collapse
so did you install any other modules for that / do you have a guide for how you got it to work?
Safe mode - nothing will give at the moment, the modules continue to work.
I found this description:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#
See:
Disabling/uninstalling modules manually
No custom recovery.
3dekstron said:
Safe mode - nothing will give at the moment, the modules continue to work.
I found this description:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#
See:
Disabling/uninstalling modules manually
No custom recovery.
Click to expand...
Click to collapse
yeah but i think we have to wait on the next magisk version ( that wil be updated soon). that one will respond to auto-disabling modules when booting into safe mode
senz90 said:
it works on my 10
Click to expand...
Click to collapse
How did you get it to work? I can't get the driver to install properly.
So I accidentally installed the OTA, so now I'm at 10.0.10. I had Magisk installed at the time, no modules I just used it for root.
Phone still boots fine but I can't seem to get it reinstalled.
I tried searching around the forums but I was unable to find anything with this specific situation.
What could I do to fix his?
spifkie said:
So I accidentally installed the OTA, so now I'm at 10.0.10. I had Magisk installed at the time, no modules I just used it for root.
Phone still boots fine but I can't seem to get it reinstalled.
I tried searching around the forums but I was unable to find anything with this specific situation.
What could I do to fix his?
Click to expand...
Click to collapse
You have to repeat the initial steps you used to root since you have now a non patched kernel img!
FSadino said:
You have to repeat the initial steps you used to root since you have now a non patched kernel img!
Click to expand...
Click to collapse
I did try that, without succes.
It seems that there's still pieces of Magisk left from before I updated, which prevents it from installing properly now.
At the time I first rooted I used the tool found here: https://forum.xda-developers.com/7t-pro/how-to/magisk-auto-install-tool-magisk-t4001471
Simply running that again has not worked. Magisk manager will only say "Magisk is not installed"
spifkie said:
I did try that, without succes.
It seems that there's still pieces of Magisk left from before I updated, which prevents it from installing properly now.
At the time I first rooted I used the tool found here: https://forum.xda-developers.com/7t-pro/how-to/magisk-auto-install-tool-magisk-t4001471
Simply running that again has not worked. Magisk manager will only say "Magisk is not installed"
Click to expand...
Click to collapse
Download official ROM.zip and "Payload Dumper"
"Unzip" Payload.bin from official ROM.zip using "Payload Dumper"
Patch stock boot.img using magisk manager (already installed)
Flash new "Patched_boot.img using adb/fastboot
Commands:
Fastboot devices
Fastboot reboot fastboot
Fastboot flash boot "Patched_boot.img"
Fastboot reboot
FSadino said:
Download official ROM.zip and "Payload Dumper"
"Unzip" Payload.bin from official ROM.zip using "Payload Dumper"
Patch stock boot.img using magisk manager (already installed)
Flash new "Patched_boot.img using adb/fastboot
Commands:
Fastboot devices
Fastboot reboot fastboot
Fastboot flash boot "Patched_boot.img"
Fastboot reboot
Click to expand...
Click to collapse
You're a lifesaver! that fixed it!
Thank you very much!
spifkie said:
You're a lifesaver! that fixed it!
Thank you very much!
Click to expand...
Click to collapse
Next time don't reboot device after OTA installation finished, just open Magisk Manager and install root to inactive slot (4th option)
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)