Database Info

Magisk for dummies

Hi all,
I tried to find basic informations about Magisk without success.
Is anyone here could explain what is Magisk, as if I was 5 years old ?
Thanks in advance for your replies.

dont know if you saw this , but here is the thread for magisk. maybe will help. :what:
http://forum.xda-developers.com/showthread.php?t=3473445

mrrocketdog said:
dont know if you saw this , but here is the thread for magisk. maybe will help. :what:
http://forum.xda-developers.com/showthread.php?t=3473445
Click to expand...
Click to collapse
Thanks for your reply.
The thread for Magisk is too technical for me. In a first approach, I want only to understand with simple words, what Magisk can do.

root your device.

iwanttoknow said:
Thanks for your reply.
The thread for Magisk is too technical for me. In a first approach, I want only to understand with simple words, what Magisk can do.
Click to expand...
Click to collapse
I'm with you - that main thread completely lost me - I installed the manager and it errored from twrp and I guess it leads on to something about finding a boot.img to patch - but i'm lost

Lothaen said:
I'm with you - that main thread completely lost me - I installed the manager and it errored from twrp and I guess it leads on to something about finding a boot.img to patch - but i'm lost
Click to expand...
Click to collapse
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/

IronRoo said:
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/
Click to expand...
Click to collapse
yeah - i've been through both of those, but mine error during the flash with issue with the boot image, so then I get stuck and have no idea how to fix it or where to go - I tried asking on the Magisk thread but its so chatty I think it got lost very quickly.

IronRoo said:
@iwanttoknow
have you seen this one
https://www.xda-developers.com/what-is-magisk/
&
https://www.xda-developers.com/magisk-hub-2/
Click to expand...
Click to collapse
Thanks a lot IronRoo for your reply !
After reading I have understood that Magisk implies to install a recovery tool like TRWP.
So I have only to unlock the device's bootloader to install a recovery tool and after Magisk. Magisk doesn’t modify system files.
Ok but I don't understand how it's possible the device obtains root access. It's certainly magical

Most of the time I don't look for the sort of 'tell me like I'm a 5 y/o' info - but Magisk IS an exception for that, for me.
There is very little that I can find which is written in plain, simple words such that I can even figure out -IF- it is usable as I'd like it to be.
My example:
I have an unlocked Moto E6 - can I even get TWRP installed & working in that phone ??
No clue.
Prior to Android V5.x gaining root access was loads easier to accomplish & I've happily done so for my several older LG devices & our previously daily use Kyocera phones.
BUT:
For my couple of devices with versions of Android newer than V5 - I am only able to de-bloat those somewhat via ADB shell - but they are locked to AT&T which would mean I'd have to fulfill their unlocking requirements to get 'em unlocked - or am I mistaken about that ??
The closest I've found to a VERY simplified guide to using Magisk is here:
Root Android Phone with ADB Command, Magisk & TWRP
Here are 2 different methods to root your Android phone or tablet using ADB and Fastboot commands, Magisk and install TWRP Recovery.
technastic.com
But method 1 is not possible for my devices AFAIK & method 2 requires me to have a stock firmware IMG to patch...but I've zero idea where I might get those for a Moto or a 'modern' LG phone - is there any particularly good way to accomplish that ??
So - as the OP said - please tell me like I'm a 5 year old ?!?
Thanks.

[Q] Best safety-net fix to re-lock bootloader if stock?

So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!

cmivxx said:
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
Click to expand...
Click to collapse
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe

mac796 said:
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
Click to expand...
Click to collapse
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.

cmivxx said:
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
Click to expand...
Click to collapse
I usually just use the kernel that comes with the rom im on. And I use magisk. I have used ex kernel. I really like the ex manager app. And I do believe it still passes safety net with just unlocked bootloader. At least it used to. Google updated safety net this month so I don't know if that changes things.

Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!

cmivxx said:
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
Click to expand...
Click to collapse
You will probably be able to take the OTA with just a unlocked Bootloader, you will just have to boot TWRP and Flash that kernel every month. There also is a stock kernel someone builds for what you're trying to do

You can flash google's factory-image.
Then you can re-lock your bootloader and you can unlock it too.

Fire HD 10 and Magisk?

Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!

I tried flashing Magisk 16.0 with 15.3 installer today and got stuck in bootloop. It flashed but would just boot to amazon logo over and over. Have a Ti Backup but it sucks. I'm sure there's a way through adb. I'm still learning. I wanna know the best way to flash any zip in general cause without FF TWRP or some other custom recovery im lost. I'm assuming you'd have to uninstall SuperSu anyhow. My 2 cents. Rebuilding new ROM now, I love spending hours doing the same thing ?. In hindsight I get better each time and find new hacks tricks etc.

You might be able to use tasker with a variation of the code in this thread https://forum.xda-developers.com/apps/magisk/microsoft-intune-company-portal-t3611588/page12

btonetbone said:
Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!
Click to expand...
Click to collapse
Hide Rooting V1.7 is working for me. I rooted yesterday then realized Dtv now stopped working and had to scramble to fix it. So far that's the answer.

chris_dubs said:
I tried flashing Magisk 16.0 with 15.3 installer today and got stuck in bootloop. It flashed but would just boot to amazon logo over and over. Have a Ti Backup but it sucks. I'm sure there's a way through adb. I'm still learning. I wanna know the best way to flash any zip in general cause without FF TWRP or some other custom recovery im lost. I'm assuming you'd have to uninstall SuperSu anyhow. My 2 cents. Rebuilding new ROM now, I love spending hours doing the same thing . In hindsight I get better each time and find new hacks tricks etc.
Click to expand...
Click to collapse
Sorry for any revival, but is that really possible? I don't really think so, because Magisk, is by definition Systemless, meaning that it doesn't affect the system in any way, but modifies the boot.img. And modifying the boot.img even a tiny bit results in a bootloop, because it fails signature verification. I would be glad to hear any ideas because when we manage to get our Amazon tablet rooted, I would prefer Magisk over anything as I always did, because it is open source and systemless.

Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?

lifegap said:
Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?
Click to expand...
Click to collapse
This is an unrelated question.

btonetbone said:
Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!
Click to expand...
Click to collapse
So far no. But don't worry. The HD 10 can be unlocked, it's just a matter of its done. Unfortunately, we don't have it easy. The HD 10 is built sorta convoluted. It's 64 but in some cases, 32 in the rest. Something's can't pick up on it. I have a thing or two I am working on. Unfortunately I am dead in the water PC wise until after 10 am. I need a new mouse. And I don't have a spare.
If anyone wants to help... mediatek uses their own fastboot executable, mtboot.exe. I still need to gather all the files to build it and or the binary (they aren't in the right places at all). But it would be nice if the mtboot.exe could be located somewhere on the web.
Also in the Amazon source code for the kernel, they left a potential honey pot. Datool, also known as fbtool. They left the module in their source, and I can't figure out why. In the source it lists some usb props, vendor and product IDs and lists three boot modes: unknown, brom, and preloader. It's also tied into sp flash tool somehow. When you compile the datool at the mediatek source, it will put the tablet into preloader mode. So prehaps it can also put it in brom. But if we can get datool to do a proper dump, we might be able to get SP flash tool working.
That's been my findings the past few days.
Now when I get a mouse, hopefully I will have the first test rom built today.

lifegap said:
Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?
Click to expand...
Click to collapse
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?

Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
The only thing we have available at the moment for flashing is flash fire, on the HD 10. I have magisk on a few devices. It's pretty cool once you get the hang of it. It's different and took me a while to get to the point of liking it. I think it will be amazing on the HD 10 because the hardware is great. I haven't tried it on my fire 7 yet. I don't have a rooted HD 8.
Sent from my MotoG3 using XDA Labs

DragonFire1024 said:
... The HD 10 is built sorta convoluted. It's 64 but in some cases, 32 in the rest. Something's can't pick up on it.
Click to expand...
Click to collapse
No, it's not. Same way many (arguably most) 64-bit devices behave in a 32/64 hybrid world. Someday 'everything' Android will be 64-bit or greater with 32-bit being religated to history - much 8/16-bit is today. Not there yet, especially on economy devices using older hardware. Amazon is not doing anything weird.

Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
Only SuperSu manage the root access. Magisk manager without Magisk installed is only an app.

Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
The SuperSu do the root management. Magisk manager is great on my phone, but it creates disaster on my HD 8 when testing the Magisk installing from the Manager. It made my HD8 boot loop at Amazon logo, no way to boot. I have to sideload the stock ROM then rooting again.

DragonFire1024 said:
If anyone wants to help... mediatek uses their own fastboot executable, mtboot.exe. I still need to gather all the files to build it and or the binary (they aren't in the right places at all). But it would be nice if the mtboot.exe could be located somewhere on the web.
Also in the Amazon source code for the kernel, they left a potential honey pot. Datool, also known as fbtool. They left the module in their source, and I can't figure out why. In the source it lists some usb props, vendor and product IDs and lists three boot modes: unknown, brom, and preloader. It's also tied into sp flash tool somehow.
Click to expand...
Click to collapse
Wondering if your still looking into fbtool - I think your right about its potential in fixing bricks/installing roms. Got a link to the mtboot source still?
Brainstorming how to unbrick patched Fire 7's here:
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
Make sure to read this guide completely before starting. You will lose all data on the tablet, make a backup of important data before you start. What you need: - a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux...
forum.xda-developers.com
Currently thinking about fbtool and a custom lineage compile, with hacked secureboot, fastboot enabled lk.bin and a preloader which skips rpmb. Further info on mtk's fastboot implementation would be useful.

[REQUEST] AOSP ROM for J327U?

Just wondering if anyone is working on/willing to start working on an AOSP Nougat or Oreo ROM for this device? I would go for it myself, however, my internet won't even let me sync repo. Thanks in advance for any responses
Toby.
Device: J327U
Recovery: TWRP 3.1.1-1 Ashyx
Root: Yes, SuperSU

waiting bro....:good:

At this point, we know the bootloader is unlocked. We have been able to successfully root it. Is it just that the market share is so low that no one is developing for this device yet?

TMet said:
At this point, we know the bootloader is unlocked. We have been able to successfully root it. Is it just that the market share is so low that no one is developing for this device yet?
Click to expand...
Click to collapse
I do believe that is the case (not worth a custom ROM). Have the phone myself, it's a solid, cheap, fast unit. More reliable that Moto's, etc., but not worthy of a custom ROM, sadly.

Question ROM in op 9 tmobile version

Hello everyone! I just bought an Amazon renewed Op 9, and I wanted to ask How to install Evolution X or Lineage OS, since maybe the instructions are different from the global Version and T Mobile version Add more step to installation or simply can not be achieved

Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Start here. Since I have a locked SIM, I used the MSM conversion package linked in the OP (https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501).
This will get you to the stock global ROM. After, you will need to update to the most recent OOS 11 ROM: https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
From here, you have a few options depending on whether or not you want to go Android 11 or 12 (since both Evolution X and Lineage OS are offered on both). Android 11 is pretty straightforward. Follow the directions in the thread to upgrade. For 12, you should be able to do the same. HOWEVER, if you become stuck with two SIM cards, neither of which show a SIM installed, you will need 1) an unlock.bin from OnePlus for your device, 2) to root your device using Magisk, 3) to apply the Magisk module found here: https://forum.xda-developers.com/t/tmo-oos-cos-data-fix.4392895/
I'm running a debloated OOS 12 and had to root and apply the fix. Custom/Lineage ROMs may not have this issue, but it's something to be prepared for if you don't want to waste as much time as I did reflashing everything. Please note that this is a very simple step by step tutorial. READ READ READ to ensure you don't brick your device. Most bricks can be recovered with the MSM fortunately.'
Please let me know if you have any questions, and I will try my best to answer. I am by no means an expert, but I feel comfortable messing around with my phone now, enough that I don't have to consult the forums for every little thing.
Good luck, and most of all, have fun!

posar said:
Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Start here. Since I have a locked SIM, I used the MSM conversion package linked in the OP (https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501).
This will get you to the stock global ROM. After, you will need to update to the most recent OOS 11 ROM: https://android.googleapis.com/packages/ota-api/package/580d47a7dde5862a306c07ff939cc4fe1520860f.zip
From here, you have a few options depending on whether or not you want to go Android 11 or 12 (since both Evolution X and Lineage OS are offered on both). Android 11 is pretty straightforward. Follow the directions in the thread to upgrade. For 12, you should be able to do the same. HOWEVER, if you become stuck with two SIM cards, neither of which show a SIM installed, you will need 1) an unlock.bin from OnePlus for your device, 2) to root your device using Magisk, 3) to apply the Magisk module found here: https://forum.xda-developers.com/t/tmo-oos-cos-data-fix.4392895/
I'm running a debloated OOS 12 and had to root and apply the fix. Custom/Lineage ROMs may not have this issue, but it's something to be prepared for if you don't want to waste as much time as I did reflashing everything. Please note that this is a very simple step by step tutorial. READ READ READ to ensure you don't brick your device. Most bricks can be recovered with the MSM fortunately.'
Please let me know if you have any questions, and I will try my best to answer. I am by no means an expert, but I feel comfortable messing around with my phone now, enough that I don't have to consult the forums for every little thing.
Good luck, and most of all, have fun!
Click to expand...
Click to collapse
Its neccesary the root for the steps?

Yasser.d said:
Its neccesary the root for the steps?
Click to expand...
Click to collapse
It's necessary to root if you experience the dual SIM issue on a 12 ROM. Otherwise, you can run unrooted just fine.

posar said:
It's necessary to root if you experience the dual SIM issue on a 12 ROM. Otherwise, you can run unrooted just fine.
Click to expand...
Click to collapse
But for backup and stuff like that? the root its needed or not? where i find a tutorial for root for my t mobile version :ccc

Yasser.d said:
But for backup and stuff like that? the root its needed or not? where i find a tutorial for root for my t mobile version :ccc
Click to expand...
Click to collapse
Sorry for the delayed response; I wanted to find a guide that explained the process better than I could. Here are the steps to root:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
I was able to extract the boot.img using the win64 build of Payload Dumper. If I'm reading this article correctly, you shouldn't need to worry about patching vendor_boot.img or vbmeta.img unless you are rooting ColorOS (I didn't have to patch either when rooting OOS 12).

posar said:
Sorry for the delayed response; I wanted to find a guide that explained the process better than I could. Here are the steps to root:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
I was able to extract the boot.img using the win64 build of Payload Dumper. If I'm reading this article correctly, you shouldn't need to worry about patching vendor_boot.img or vbmeta.img unless you are rooting ColorOS (I didn't have to patch either when rooting OOS 12).
Click to expand...
Click to collapse
Oh thank you very much! I'm new to oneplus and I'm afraid of doing something wrong, in xiaomi's it was a little easier.
I'll try when I have the bootloader unlocked (I'm still waiting for the oneplus email for the unlock token) so I can root and have a backup with the app in the tutorial.
Later I will try to update to oxygenos 12 I think, I liked oxygen os11 and I don't know if it's worth the change to new roms

Yasser.d said:
Oh thank you very much! I'm new to oneplus and I'm afraid of doing something wrong, in xiaomi's it was a little easier.
I'll try when I have the bootloader unlocked (I'm still waiting for the oneplus email for the unlock token) so I can root and have a backup with the app in the tutorial.
Later I will try to update to oxygenos 12 I think, I liked oxygen os11 and I don't know if it's worth the change to new roms
Click to expand...
Click to collapse
I like OOS 12, but some people have had complaints. I haven't noticed any glaring bugs or anything crazy. Battery life has been great, no issues with bluetooth, no crashes or anything.
I'm personally keeping my eye on the Pixel Experience 12 ROM and will probably be flashing to that once the bugs are ironed out.

posar said:
I like OOS 12, but some people have had complaints. I haven't noticed any glaring bugs or anything crazy. Battery life has been great, no issues with bluetooth, no crashes or anything.
I'm personally keeping my eye on the Pixel Experience 12 ROM and will probably be flashing to that once the bugs are ironed out.
Click to expand...
Click to collapse
ohh I understand, but pixel experience 12 is the one that doesn't have security certificates from banks and stuff? I do not remember the app but it was the one that said that it passed the test or it did not pass

after that fix dual sim is working?

Yasser.d said:
ohh I understand, but pixel experience 12 is the one that doesn't have security certificates from banks and stuff? I do not remember the app but it was the one that said that it passed the test or it did not pass
Click to expand...
Click to collapse
I haven't heard this, but I haven't really been keeping track. I guess I'll find out.
gioodo said:
after that fix dual sim is working?
Click to expand...
Click to collapse
To my knowledge dual sim can't work on the T-Mobile OnePlus 9. It doesn't even have a dual sim tray.