Database Users

Magisk with android 9

I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?

xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Not the way you are doing it. I boot to TWRP, without installing it and have TWRP install the full zip.

Hm I'll try this. Used to the boot patching.

xringo said:
Hm I'll try this. Used to the boot patching.
Click to expand...
Click to collapse
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.

lorax70 said:
Just dirty flashed 9 over dp5, booted to twrp and flashed magisk. Rooted, and all appears well.
Click to expand...
Click to collapse
You can give link file magisk for use on android 9.

newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Fwiw. I've been using this magisk version for dp3-5, but there are newer versions, but 16.4 works for me...
https://thedroidarena.com/download-magisk-16-4-beta/
I may try a newer version at some point, but I'm in no rush.

newyesor said:
You can give link file magisk for use on android 9.
Click to expand...
Click to collapse
Got this from the Flash kernel thread. It works fine on Pie :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk

xringo said:
I did a clean reset and installed a fresh android 9. So no root, nothing.
Anyways I install magisk 5.8.3 and then tried to patch the boot.img from the android 9 factory image.
But every time I select the boot.img and try to patch it, it says "Failed! ! Installion failed!".
How has everyone else tried to install magisk on android 9?
Click to expand...
Click to collapse
Make sure your using 16.7 you have to change in setting to beta. Same thing happened to me trying to use 16.0

I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674

After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?

I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Airpil said:
I have the same issue TWRP also can't decript the phone. I am going to wipe everything, and fastboot erase userdata.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Don't wipe your phone! Just flash the new boot.img from the image file (not OTA file) and you will be able to go back to your Android system and disable the pin. After disable the pin, boot into TWRP and flash the Magisk from here https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Hope this helps!

madmuthertrucker said:
I get updater error :2 failed to install every freaking time. No matter what zip i use. 1600 1671 1674
Click to expand...
Click to collapse
Use magisk uninstall first and this should solve the issue.

lssong99 said:
After dirty flash (remove -w) Android 9 PPR1 then install Magisk 16.7, it seems I am not able to set PIN or any security... Anyone has the same issue?
Click to expand...
Click to collapse
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP

Brakiss said:
I have flashed ota from dp5 and fresh install of 9 and I cannot use security with 3.2.1_2 or 3.2.2 TWRP
Click to expand...
Click to collapse
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.

Badger50 said:
There's a 3.2.3-0 out as well. It's reportedly able to decrypt using alphanumeric codes. However a straight 4 number pin still isn't working for me.
Click to expand...
Click to collapse
Where did you see this? I have pattern and would like to keep it.

Brakiss said:
Where did you see this? I have pattern and would like to keep it.
Click to expand...
Click to collapse
One of the other threads. Here's the twrp version though. https://dl.twrp.me/taimen/

Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?

pr1vate piles said:
Been having issues myself since updating to Pie yesterday. TWRP installed working fine. Installed magisk manager, set to beta channel. Rebooted into TWRP and flashed magisk 16.7, phone hanging at the lovely google logo page. I then have to run the uninstaller back in TWRP or i cant get the phone to boot. Anyone had this?
Click to expand...
Click to collapse
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk

Badger50 said:
Yeah, rooting on P is a little tricky it seems. You'll likely have to run the uninstaller, then boot up. Then go back to twrp and flash this version of magisk. It's the 16.7(4) version found in the Flash kernel thread :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Your not wrong there. Tried it as you suggested, same thing, hanging at the G logo page with the bar animation under it. Had to run the uninstaller to get back into my phone. Very odd

How to update to the latest version?

Ok so i'm running now OOS Stable 10.0 with TWRP running, and Magisk ofc.
Now, i used this guide -
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-twrp-data-decryption-t3995861
To update from 9.0.17 to 10.0
But never tried to update from 10.0.
Can i update like the usual process ?
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Or i need to do it differently .
Edit : I want to update from 10.0 to OB3.

yot2703 said:
Ok so i'm running now OOS Stable 10.0 with TWRP running, and Magisk ofc.
Now, i used this guide -
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-twrp-data-decryption-t3995861
To update from 9.0.17 to 10.0
But never tried to update from 10.0.
Can i update like the usual process ?
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Or i need to do it differently .
Edit : I want to update from 10.0 to OB3.
Click to expand...
Click to collapse
Why would it be different?
It seems complicated enough for people to catch up with only one logical method, I dare not imagine what it would be if there were different procedures....

yot2703 said:
Enter Recovery > Flash ROM > Flash TWRP > Flash Magisk ?
Click to expand...
Click to collapse
If you do it this way make sure you update to the latest version of TWRP that was released today (3.3.1-30) before upgrading the ROM.

Open magisk manager and restore boot.img.
Update locally in system settings.
Dont reboot.
Install magisk to inactive slot in magisk manager.
Reboot and provit.
No need for twrp.

Striatum_bdr said:
Why would it be different?
It seems complicated enough for people to catch up with only one logical method, I dare not imagine what it would be if there were different procedures....
Click to expand...
Click to collapse
There are people updating with local update.
alryder said:
If you do it this way make sure you update to the latest version of TWRP that was released today (3.3.1-30) before upgrading the ROM.
Click to expand...
Click to collapse
Update it via Magisk?
bokkoman said:
Open magisk manager and restore boot.img.
Update locally in system settings.
Dont reboot.
Install magisk to inactive slot in magisk manager.
Reboot and provit.
No need for twrp.
Click to expand...
Click to collapse
I still want TWRP , Flash it over Magisk?
And can you provide me the boot.img? 10.0

yot2703 said:
There are people updating with local update.
Update it via Magisk?
I still want TWRP , Flash it over Magisk?
And can you provide me the boot.img? 10.0
Click to expand...
Click to collapse
And why would you need TWRP?
You don't need boot.img. Magisk automatically backups the original boot.img and patches it. That way you can restore it thru magisk manager. And patch the new boot.img (install to in-active slot) after local upgrade.

bokkoman said:
And why would you need TWRP?
You don't need boot.img. Magisk automatically backups the original boot.img and patches it. That way you can restore it thru magisk manager. And patch the new boot.img (install to in-active slot) after local upgrade.
Click to expand...
Click to collapse
I'm trying this guide
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-update-to-op6t-ob3-q-t4021299

yot2703 said:
I'm trying this guide
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-update-to-op6t-ob3-q-t4021299
Click to expand...
Click to collapse
Well, that doesn't answer the question: why do you need TWRP?

The problem is that you ask for a recipe, without knowing clearly what you're doing when applying the recipe.
Yes you can update with local update while keeping Magisk and twrp. See first posts of OOS 10.0.1 thread in Guide section.
Yes you can update from within twrp, the way ROMs are fleshed since nearly a decade
Yes you can flash twrp with Magisk manager, since months it's a basic knowledge.
No you don't need stock boot.img
Don't follow the guide you quote WHICH WAS WRITTEN WHEN NO WORKING TWRP was available for A10. It's outdated now. Use regular and classical procedures

bokkoman said:
Well, that doesn't answer the question: why do you need TWRP?
Click to expand...
Click to collapse
Flash other zips and kernels?

yot2703 said:
Flash other zips and kernels?
Click to expand...
Click to collapse
Alright, well then it is useful.
IMHO, i recommend using stock OOS and root only. Because it already is a great rom. You can flash certain extras with magisk manager anyway.
But whatever rows your boat

Striatum_bdr said:
The problem is that you ask for a recipe, without knowing clearly what you're doing when applying the recipe.
Yes you can update with local update while keeping Magisk and twrp. See first posts of OOS 10.0.1 thread in Guide section.
Yes you can update from within twrp, the way ROMs are fleshed since nearly a decade
Yes you can flash twrp with Magisk manager, since months it's a basic knowledge.
No you don't need stock boot.img
Don't follow the guide you quote WHICH WAS WRITTEN WHEN NO WORKING TWRP was available for A10. It's outdated now. Use regular and classical procedures
Click to expand...
Click to collapse
Well now i'm stuck with no twrp. how to flash it ?

yot2703 said:
Well now i'm stuck with no twrp. how to flash it ?
Click to expand...
Click to collapse
The answer is in the post you quoted:
'Yes you can flash twrp with Magisk manager, since months it's a basic knowledge"
What I did was open Magisk Manager - go to Modules - click Add (+) - select the TWRP installer (zip) - exit Magisk Manager - reboot to TWRP - reinstall Magisk.
There might be a way to reinstall Magisk from Magisk Manager to the active slot but I'm not sure so I did it through TWRP.

Magisk and TWRP together in recovery? I am missing some knowledge ...

Yesterday I followed this instruction:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
and got my Tablet rooted by Magisk with stock ROM.
Next: I want LinageOs on this device, so I had to install TWRP. For TWRP I followed the links on top of the mentioned XDA-thread:
Go HERE if you are interested in custom recovery (e.g., TWRP).
Click to expand...
Click to collapse
which got me to this page:
https://twrp.me/samsung/samsunggalaxytabs5ewifi.html
There is this advice:
You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery.
Click to expand...
Click to collapse
I followed the link in this advice an read both 3 times, but I am not sure, what this means.
Next was wiki.lineageos-page for the TAB S5e:
https://wiki.lineageos.org/devices/gts4lvwifi/install
which I also read, but none the wiser. And for more confusing: in the suitable download-page is besides the linage-file a recovery-image, which is not mentioned anywhere. Or I am blind ...
What I at least did: installed TWRP with the TWRP-app and could boot into this custom recorery and installed LineageOS. The Tab S5 is running fine with LinaegeOS but without root ...
What must be done to root?
Spielmops

I flashed the default TWRP into recovery, installed LineageOS from TWRP, and then followed these instructions: https://forum.xda-developers.com/redmi-note-7/how-to/install-magisk-android-11-r-100-t4162761
I have working installation of TWRP and Magisk now.

If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. ... When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through Magisk Manager. The app will be aware of your device state and install to the correct partition and reboot into the correct mode.
Click to expand...
Click to collapse
The thread you mentioned, is the normal way which I know. This is a special device!
Spielmops

Spielmops said:
The thread you mentioned, is the normal way which I know. This is a special device!
Click to expand...
Click to collapse
All I can tell you is that I didn't preroot anything. (My device is the LTE variant, but I think it doesn't matter other than needing the correct TWRP and Lineage image).
I started with a stock ROM and locked bootloader.
Unlocked the bootloader and installed the current TWRP image via ODIN (In my case, this one: https://dl.twrp.me/gts4lv/, you will want this: https://dl.twrp.me/gts4lvwifi/).
Installed LineageOS 18.0 and GApps through TWRP sideload.
Booted and set up Lineage.
Downloaded the three files from the thread I linked. Installed them and rebooted in the order given.
Finally, updated Magisk Manager and Magisk to the Beta-Channel (21.1) through Magisk Manager.
Done. I have root.

Finally, updated Magisk Manager and Magisk to the Beta-Channel (21.1) through Magisk Manager.
Click to expand...
Click to collapse
Updated Magisk? I think, there was no Magisk in your device?

Spielmops said:
Updated Magisk? I think, there was no Magisk in your device?
Click to expand...
Click to collapse
aserraric said:
Downloaded the three files from the thread I linked. Installed them and rebooted in the order given.
Click to expand...
Click to collapse
I installed both Magisk Manager and Magisk from the files in the other thread. That is a custom version, which I updated to Beta after installing.

I don't find LOS 18, please give me a hint ...

Spielmops said:
I don't find LOS 18, please give me a hint ...
Click to expand...
Click to collapse
Right here in the ROMs section.
Obligatory disclaimer: LOS 18 is still a preview and more likely to have bugs than 17.1, but I'm more than happy with it so far.

@topjohnwu
Can you tell anything to this problem? I've read this:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Spielmops

I've installed Lineage a few times now on this devices, and I always use the developers instructions here. Then I flash Magisk from TWRP. If you are using LOS 17.1, I just flash it in TWRP. Modules and such can NOT be flashed in TWRP your tablet will not BOOT.
The only version of Magisk that I've found that works in LOS 18 / Android 11 is 297. Links in this post.

Install Magisk 22 on Xiaomi Redmi Note 7 Global

Hi,
I was trying to install the new version of Magisk 22, by patching my recovery image since Ramdisk is indicated as No in Magisk, but I can't figure out which recovery.img I should be using. I have OrangeFox 11 recovery installed, but I tried with its .img and it didn't work. My phone got encrypted, and I had to format my data thus reseting my phone in order for it to boot.
I also tried to flash the Magisk.apk file renamed as .zip but same issue, password at reboot which made me format my data partition again.
It's bugging me and I don't know what to do.
If someone can help me I would be very thankful!

U need only a recovery, flash the apk as zip. That's working

I already tried flashing the apk, it only ended with the same issue at boot, asking a password I didn't have

Ti64CLi++ said:
I already tried flashing the apk, it only ended with the same issue at boot, asking a password I didn't have
Click to expand...
Click to collapse
Then use magisk from orangefox. It's 21.4 I think

Thanks I will.
But it's still bizarre that Magisk 22.0 doesn't work on my phone

I just tried and once again it didn't work. I had to format data partition once again, and restore a previous backup, which by the way, didn't fully work.
I'm starting to think that I won't be able to install Magisk on my phone anymore

Ti64CLi++ said:
I just tried and once again it didn't work. I had to format data partition once again, and restore a previous backup, which by the way, didn't fully work.
I'm starting to think that I won't be able to install Magisk on my phone anymore
Click to expand...
Click to collapse
It worked fine for me. Maybe try and ask you problem in the general Magisk support thread? https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2264#post-84825737

svendsvin said:
It worked fine for me. Maybe try and ask you problem in the general Magisk support thread? https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2264#post-84825737
Click to expand...
Click to collapse
You too have a Redmi Note 7?
Did you manage to install Magisk 22.0 or an older version?
Thanks I will ask on the general Magisk support thread

Yes I have. I used Magisk from Orangefox first time and since updated to Magisk 22.1.

I whould suggest flashing Magisk v20.4 zip for Redmi Note 7 using OrangeFox recovery, cause this worked for me, then using the Magisk app, update it to 22.1 using the app itself, its quick and painless and also can remove force encryption. I hope it could work for you.
The required files for root are in this link (i used the same files) https://drive.google.com/drive/folders/1bpvlCnRFNQS8hIrYY5ePWS6WXfeSyt9x?usp=sharing
P.S. dont unzip anything cuz the zip file has to be flashed all together

update : the apk is deleted cuz the zip already installs it

oneplus 6t stuck when i try to flash twrp after msm

so, i had my op 6t bricked and in a bootloop to fastboot
i managed to recover my data through twrp, but couldnt get lineage to run again, so i used the msm tool to downgrade to android 9 oos
now when i try to install a custom recovery i the phone freezes in this "the bootloader is unlocked warning"-screen
no idea why i cant boot into a custom recovery, with a unlocked oem
my plan is to get it back to run lineage os with twrp recovery
can u maybe help me?

I wasn't able to boot into twrp since a11. Had to install from magisk in booted oos using twrp installer. Not sure why it wouldn't work if you downgraded but maybe not using the correct twrp? Sounds like things are messed up. I would start from scratch and get a clean oos on both slots. If you can't boot into twrp then root with magisk and install directly from magisk manager with the installer.

So I am on 11.1.2.2, how do I get twrp installed on this. I cannot get twrp to boot past the logo. I have been trying to Flash HAVOC but have been stuck

Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.

Brettroth said:
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Click to expand...
Click to collapse
Which magisk? latest or canary

Gytole said:
Which magisk? latest or canary
Click to expand...
Click to collapse
I use the latest

and are we talking 3.6.0_9? orr...

Gytole said:
and are we talking 3.6.0_9? orr...
Click to expand...
Click to collapse
Yeah that's the newest. Older ones work but that one has a lot of good changes

Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.

Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
You need to flash a magisk modded boot in fastboot from your oos. Someone has a post somewhere in here hosting them I'll try to get a link for you.

so fastboot flash boot_a and b like usual for the patched boot image and then once in android just open magisk, then install the latest twrp from there? I think that's what put me in crash dump mode before

Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
Are you on 11.2.1.1?

Brettroth said:
Are you on 11.2.1.1?
Click to expand...
Click to collapse
11.1.2.2 I believe?

Gytole said:
11.1.2.2 I believe?
Click to expand...
Click to collapse
Sorry that's what I meant. Here is modded boot. Flash in fastboot.

Brettroth said:
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Click to expand...
Click to collapse
Done. Now I boot into android, open magisk, and install the recovery?

Gytole said:
Done. Now I boot into android, open magisk, and install the recovery?
Click to expand...
Click to collapse
Yessir

Brettroth said:
Yessir
Click to expand...
Click to collapse
Work out for ya?

Wow. Alright. You all need to remember this. Msm only flashes to slot a. NOT slot b. So, if you were previously in A10 or A11 and flash msm OOS 9, there will be issues unless you local update the same android version to slot b. You can't have 2 different android version on your slots unless you're using dualboot mod. Like on 8 pro, crashdump happens when twrp is installed if both slots aren't using the same android version