Database Users

[SOLVED] Unable to get Magisk Manager to work - Request help

So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
UPDATE:
Got it to work. You need to have the app installed on internal storage. Mine was installed on sdcard. doh!

buggerman said:
So the problem that I am facing is that Magisk Manager stops working after I do a patched boot from fastboot. I also tried flashing the patched image to boot partition an rebooting but that didn't help either. Magisk Manager works fine as long as I'm on stock boot, so I was able to patch a boot.img myself as well.
I've already done the following (after unlocking the bootloader with fastboot oem unlock):
1. Startup using fastboot boot patched_boot.img (using the posted image and a freshly made image from Magisk Manager)
2. Startup after flashing the patched_boot.img with fastboot flash boot patched_boot.img
3. After both the steps 1 & 2 as a starting point, uninstalled and reinstalled Magisk Manager.
4. After both the steps 1 & 2 as a starting point, cleared the cache for Magisk Manager without clearing the data.
5. After both the steps 1& 2 as a starting point, cleared the data for Magisk Manager.
6. When I startup using fastboot boot twrp.img (v3.2.1.0 for tissot), it fails and boots system instead.
My logcat is located here
Can anyone help? Has anyone else faced this? I have tried this all using Magisk Manager 5.5.5. My Mi A1 is on the January Oreo build.
Thanks!
-buggerman
Click to expand...
Click to collapse
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I

Haizum74 said:
Are you using the correct patched boot img file with regards to your security update (Dec or Jan). Have a watch of this and try it that way https://www.youtube.com/watch?v=2wanENWhE9I
Click to expand...
Click to collapse
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.

buggerman said:
I patched the boot.img myself using Magisk Manager (on unpatched booting) as well.
Click to expand...
Click to collapse
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?

Haizum74 said:
Yes but did you use the correct one for your specific security update date? Also, why uninstall Magisk?
Click to expand...
Click to collapse
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled Magisk Manager because some people said uninstall and reinstall and try again.
I haven't installed/ uninstalled Magisk yet. Only the manager.

buggerman said:
Yes, I used the January 2018 image. I have January 2018 patch installed on my device as well. Uninstalled it because some people said uninstall and reinstall and try again.
Click to expand...
Click to collapse
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?

Haizum74 said:
Ok, well it seems from what you have said its working fine until you use the patch boot image. So, watch that video and try that and see if it works. They don't uninstall magisk (unless an update is required).
Are you trying to get root?
EDIT - Also, have you enabled OEM unlock in the developer menu?
Click to expand...
Click to collapse
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.

buggerman said:
I have enabled OEM unlock in Dev menu. I haven't yet installed Magisk to uninstall it yet. Unable to watch the video at the moment (at work). Will do it and report.
Click to expand...
Click to collapse
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.

Haizum74 said:
Sorry when I mean magisk, I mean magisk manager app. I was lazy typing. OK, let me know if that sorts it.
Click to expand...
Click to collapse
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk

Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs

Ahh I thought so, well that yt video is ideal then.

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
buggerman said:
Also to answer your question, I'm trying to root without messing with OTA updates.
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
As above

Haizum74 said:
If you install TWRP you will lose OTA so ignore that part unless you are installing a custom ROM.
As above
Click to expand...
Click to collapse
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs

buggerman said:
I'm also unable to boot TWRP. It just reboots into system.
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Sent from my tissot_sprout using XDA Labs
Click to expand...
Click to collapse
No, not if you still want to keep OTA updates without having to download them manually. From what I am aware, unlocking the bootloader and rooting as per the videos instructions is the only way to keep auto OTA.

buggerman said:
Is there a specific version of TWRP you recommend to try booting with (without install)?
Click to expand...
Click to collapse
TWRP by mohancm

TWRP not booting for me.

UPDATE:
Got it to work. Moved the app to internal storage. My device installed it on sdcard by default. That was causing the freeze.

Magisk on Oreo

I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.

I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...

GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?

+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)

+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?

kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!

+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?

GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.

kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)

I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.

kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?

GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:

Device boots only into fastboot after Magisk 22.0 update

I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?

Nikos2k said:
I had Magisk 21.4 and tried to update to Magisk 22.0, but after a restart the phone rebooted to fastboot and does not boot to system
I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)
But it still will not boot to system, it bootlops
Any ideas?
Click to expand...
Click to collapse
Try to re flash 21.4

Nameless Foe said:
Try to re flash 21.4
Click to expand...
Click to collapse
yes, but how?

Nikos2k said:
yes, but how?
Click to expand...
Click to collapse
Are you able to boot into fastboot mode?

Nameless Foe said:
Are you able to boot into fastboot mode?
Click to expand...
Click to collapse
Yes

Nikos2k said:
Yes
Click to expand...
Click to collapse
Are you able to flash the older version magisk through fast boot?

Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
Don't know how
Magisk 21.4 is a .zip file: Magisk 21.4
Is it possible to flash it through fastboot ?

Nameless Foe said:
Are you able to flash the older version magisk through fast boot?
Click to expand...
Click to collapse
You might have to reset your phone via fastboot then flash the stock firmware

Nameless Foe said:
You might have to reset your phone via fastboot then flash the stock firmware
Click to expand...
Click to collapse
How can i reset it from fastboot?
And will I lose all my data?

Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.

Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.

Nikos2k said:
How can i reset it from fastboot?
And will I lose all my data?
Click to expand...
Click to collapse
Just use the MSM tool,, easier and risk free

wgs1028 said:
Did you have any luck restoring your OP8 pro? The same thing (updating from Magisk 21.4 to 22.0) soft-bricked my 8pro. I believe soft-brick is the correct term since it's in a bootloop at loading O.S.--I guess I'll try to figure out how to flash Magisk 21.4, but I've reset it through fastboot, and when I try to flash boot.img garnered through payload dumper, I keep getting messages that says I cannot flash to critical partitions. I've tried Mauronofio's all-in-one tool but keep getting flash-bat-all missing. Man I sure would appreciate any earnest suggestions. Thank you.
Click to expand...
Click to collapse
I didn't manage to restore it by just flashing boot.img
I then flashed all the image files from the output of payload dumper, but it didn't work either
Then wiped userdata (by using -w switch of fastboot), still no luck
Then changed active slot and flashed all the image files to that slot, and it booted successfully

dladz said:
Just boot the image you originally patched it with, that'll get it to boot
Then remove 22 and install 21.4
If that doesn't work then boot the stock boot image.
Magisk 22 beta causes a bootloop.
Click to expand...
Click to collapse
i didn't manage to successfully boot it with the stock boot.img ...

Nikos2k said:
i didn't manage to successfully boot it with the stock boot.img ...
Click to expand...
Click to collapse
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required

dladz said:
What did you end up doing? Strictly speaking the only thing that changes should be the app and the boot image.
So fixing them should be all that's required
Click to expand...
Click to collapse
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata

Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Then did you try safe mode

Add bookmark
#45
For the Oneplus 8 pro with 11.0.4.4.IN11AA I had to get a boot.img (for 11.0.4.4IN11AA) and flashed it with adb via fastboot (from PC), then my phone started up without root but still unlocked (and none of my data was lost). I reinstalled Magisk 22.0 (apk) and then put the boot.img on my sdcard and used Magisk to patch my boot.img and then i booted into fastboot and and flashed the patched boot.img via adb fastboot(from my PC). I never orginally had Magisk hidden so not sure why my phone lost root after the Magisk 22.0 update. Hopefully this helps someone onto the right path.

Nikos2k said:
flashed all the images extracted from the payload dumper, to both slots, including wiping the userdata
Click to expand...
Click to collapse
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK

dladz said:
Oh you installed all those images to the boot slots? Why? They need to be flashed to particular partitions AFAIK
Click to expand...
Click to collapse
No no, i installed them to their respective partitions
Like a total firmware reset

How to update to 11.0.8.8IN11AA on pre rooted device

Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.

paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.

MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?

Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.

MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.

paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.

Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.

Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...

datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?

Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches

What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.

It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.

Could someone post boot img I can't find this 11.8.8 to download.
Thanks.

Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.

If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.

h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541

OnePlus 8 [IN2015]-[A13-F15]-Stock Boot-Recovery & Patched Boot vs Modded Recovery with ADB Enabled

OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]

Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks

LinhBT said:
OnePlus 8 series has just got F15 Update with Dec Security Patch and few improvements. Since it's Incremental Update so it'll be little annoying to extract stock images from payload.bin. So attached to this post are :
+ Stock boot image of IN2105-F15
+ Magisk patched boot image of IN2105-F15
+ Stock recovery image of IN2105-F15 ( in case )
+ Modded recovery image of IN2105-F15 with ADB Enabled, Allow-mock-location and Debuggable are both enabled.
How :
Just simply flashing the images u want using fastboot command.
Cheers! [And Happy New Year Yall]
Click to expand...
Click to collapse
Thank you so much man! May I ask how do you extract boot.img from incremental updates?

karib97 said:
Hi, I just bought this phone with this F15 update. Should I root it and flash your version ? I'm looking to have the full cam back. thanks
Click to expand...
Click to collapse
Yes, if your bootloader is unlocked.

LinkinLover2013 said:
Thank you so much man! May I ask how do you extract boot.img from incremental updates?
Click to expand...
Click to collapse
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B

LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?

LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015

LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Click to expand...
Click to collapse
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!

LinhBT said:
You sure that ur device's IN2015? Cuz this happened means smt wrong with the kernel ( which inside boot.img and sometimes in dtbo.img too ). And I can only give out 1 guess that is ur device is not In2015
Click to expand...
Click to collapse
Ye I have IN2015.

LinhBT said:
About the OTA update without lossing root, just don't reboot when System update finished its job and ask to reboot. Instead, Open Magisk, disable all modules, then choose to install to Inactive Slot. After finish, reboot like normal and u'll still have root!
Click to expand...
Click to collapse
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.

LinkinLover2013 said:
Well the problem is that If I try to install update it won´t install when I´m rooted. Always saying error and only thing that helps is to flash stock boot.
Click to expand...
Click to collapse
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?

LinhBT said:
I used modified payload_dumper script bro. But in fact, if you're already rooted, you can do it easily since our device is A/B
Click to expand...
Click to collapse
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...

LinkinLover2013 said:
Yes but always when I update my phone I need to unroot and then I can't get boot.img of incremental. Btw I flashed F15 boot.img modified with magisk and now my wifi isn't working and is stuck on turning on. Strange. What to do Now?
Nah I tried flashing stock boot.img back from the files u provided but it didn't do anything. Guess I'll need to do fresh install od F13...
Click to expand...
Click to collapse
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?

LinhBT said:
Strange! How did u flash the magisk patched image? And did u do the disable verity with vbmeta?
Click to expand...
Click to collapse
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that? Also do you have an app that works for updating with oxygen updater pls? I downloaded a zip but can´t find an working updater app that install zips...

LinkinLover2013 said:
I got your stock boot.img; patched with magisk app; flashed through PC fastboot (fastboot flash boot boot.img) and that´s all. I wasn´t disabling any verity; what´s that?
Click to expand...
Click to collapse
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )

LinhBT said:
When flash non-stock images into stock firmware, we'll have to disable AVB ( Android verified boot ) by flashing vbmeta image ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img ) ( OOS13 on 1+ devices may need to flash vbmeta_system too )
Click to expand...
Click to collapse
Well. Where can I find Vbmeta.img for F15 pls?

LinkinLover2013 said:
Well. Where can I find Vbmeta.img for F15 pls?
Click to expand...
Click to collapse
I used these files!

LinhBT said:
Use Oxygen Updater to download the update build! Btw, did u fix the wifi?
Click to expand...
Click to collapse
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.

LinkinLover2013 said:
Well. I don't quite understand how to use oxygen updater to update since when I download incremental in oxygenupdater and try to install it through OPocalupdate it fails after like 20% installing same like if i try to install it through classic updater. In oxygenupdater it recommends to switch to full but when you switch to full it doesn't show incrementals, just big system updates like from OOS12.1 to OOS13.
Click to expand...
Click to collapse
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?

LinhBT said:
I always do the Magisk flash to Inactive slot and never failed. May be there's smt wrong from ur side?
Click to expand...
Click to collapse
So you do it in this order: Go to magisk and select flash to inactive slot -> do OTA update through OPlocalupdate app -> restart phone? Does it have any effect to select flashing magisk to inactive slot before I start OTA udpate? Because it seems like the incremental OTA udpates can install only on unrooted phone with Stock boot.img if I leave it rooted it always stops due to error.