Hello, I need help installing and configuring Magisk on my tablet. Here is why and what I'm trying to do:
On my Samsung SM-T350, I originally installed TWRP and then installed a custom ROM which has root access (as far as I know, stock recovery is no longer on device). I recently installed a particular app and it indicates the program will not run all of the features because it has detected 'root' access. The suggestion online to work around this problem has been to install Magisk.
From this, I first went to the Magisk Manager website and download the 5.4.3apk and installed it. Then when I open the Magisk Manager app, it asks me if I want to 'Install Magisk-v14.0.zip now'. If I click 'install', a list of choices pop up (Download Zip Only, Patch Boot Image File, Direct Install). Which should I choose? I don't remember which of these I tried, but I recall it didn't work or didn't do anything.
So in the mean time, I downloaded the Magisk-v14.0.zip file locally to my tablet (Downloads folder). I 'think' the proper way to install is to boot into TWRP, then select 'Install', then navigate to the Magisk-v14.0.zip and then install image? Is that correct, or will this attempt to install over my custom ROM? What is the proper way to finish the installation?
Thanks in advance!
Does anyone have any suggestions?? Thanks
First - the "Magisk Manager website" is not a place you want to visit. It is not an official source for anything Magisk and should not be trusted. Only download from xda or @topjohnwu's GitHub.
Second - if you're already rooted you need to first unroot. Read more on installing Magisk in the release thread and the Installation and troubleshooting thread. Most, if not all your queries should be answered there.
Related
I am looking for a ELI5 installation guide for Magisk. I have very little experience with rooting phones and the guides I have found confuse me. thank you in advanced for the help
Install TWRP.
Flash Magisk zip in TWRP.
Boot up your device.
Install Magisk Manager (for Magisk v12, from v13 it'll be installed automatically).
It's that easy. Of course, there might be compatibility issues, but let's assume there won't be for now and cross that bridge if we get to it.
Looking at the Unlock/Root/etc thread in the X Style forum, you almost had it with the TWRP install. You were doing the correct commands, but using the wrong file. You were trying to install an apk (an app), where you needed to us an image file (*.img). Go back to the thread and you'll see they gave you the link for the proper download.
Links for the Magisk zip and the Magisk Manager are in the release thread.
Also, here's a link to another thread started today on a similar subject. I put a bunch of links and tips in there that may also be useful for you.
Edit:
An important, basic tip when doing things to your device is to always have a backup of important files. Don't leave anything on there that you can't afford to lose.
I have a successfully installed magisk 14.0 from twrp still safety net was showing false so i tried to update through magisk manager but installation keeps on failing for magisk v14.2 now same error with 14.3 it says unable to unpack boot image, any help would be greatly appreciated
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
newuxtreme said:
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
Click to expand...
Click to collapse
I thought Dr. Ketan's N10 ROM was pre-rooted with either Magisk or SuperSU. Did you not have this option in the AROMA Installer? If not, here is some help..
I personally recommend Magisk for root. It's just as easy to use Magisk over SuperSU. Each root solution has its own dedicated app as well. To root with Magisk you will need the latest root zip which is V14.0 along with the latest Magisk Manager apk.
You can download the latest Magisk Manager apk and the latest Magisk V14.0 root zip from the link below...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Here you can read and learn all about Magisk too. Once you download both the root zip and the apk, transfer both to your internal storage.
Next, download the no_verity_opt_encrypt_5.1 zip from here...and transfer it to your internal storage.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
(Its the second link from the bottom in the list)
Easy steps to root your device with Magisk..
Boot to TWRP Recovery
Select Backup and put a check in each box. That way if anything goes wrong you can restore the backup and have a working device.
Next, select WIPE - Advanced WIPE - Check both caches
Swipe to wipe both caches
Next, select INSTALL
Navigate to where you saved the root zip and select the zip.
Swipe to flash the zip
Click on the box to wipe the caches
Now, just in case, flash the no_verity_opt_encrypt_5.1 zip that you downloaded earlier.
Reboot your device. Once booted up, install the Magisk Manager apk. It will install as a normal app. Make sure you have enabled "unknown sources" in Settings - Lock Screen and Security so you can install apps outside of the Play Store.
Open the Magisk Manager app and set it up to your preference. It's very easy to use.
If you run into any issues don't hesitate to ask questions.
Good luck and happy flashing!
Sent from my Samsung SM-G955U using XDA Labs
when I opened the magisk app I was prompted to install magisk then I clicked install but it didn't install I clicked install the downloadable zip
Do you mean to say you're not getting the "! Unable to unpack boot image" error anymore, that you reported about in the other thread you started?
Anyway... Whatever the case is, if you need help you have to be more detailed. Check this part of the Magisk guide for some info about that, and feel free to browse the rest as well for further tips.
Hello all,
Hope this isn't a needless duplicate, but I've done a fair amount of searching and I can't find that this question has been answered anywhere.
If I understand correctly, it should be possible to use a 100% stock phone to produce a patched boot.img which can then be flashed to that same phone? From the instructions in topjohnwu's main thread about Magisk, I'm lead to believe Magisk can "bootstrap" itself in this way:
1) Install Magisk Manager and copy a stock boot.img extracted from the OTA
2) Use the "Install" menu item to produce a patched_boot.img, which can then be lifted off the phone and used (with ODIN) to flash the phone.
I never get to item 2.
My MagiskManager says "Magisk is not installed" which is obviously true, however, the instructions seem to say one can proceed from there, and yet I can't see how. I've created an /sdcard/magisk folder and an /sdcard/MagiskManager folder and stuck a(n unpatched) boot.img file in either of them; as well, I've just stuck one in /sdcard/ for good measure (the "root" of user-accessible storage) And yet no go.
Am I misunderstanding something? Is the patching of the boot image supposed to be happening somewhere else than on the (stock) phone? Poking around, I see that topjohnwu's "Magisk" git tree includes something called "magiskboot", but that doesn't seem to be part of the Magisk Manager package.
TL;DR: From what topjohnwu writes, it's supposed to be possible to install Magisk WITHOUT having a custom recovery installed, but I cannot find a way to actually do it with the provided tools and instructions.
You need internet access to download the Magisk zip to patch the image. No internet - no install button...
Ouch. Thanks for the help, Didgeridoohan, that's the answer right there. I like to get my phones set up "just right", which includes getting root and then backup up and freezing various things (for example using Titanium Backup), before ever allowing the phone to go online for the first time and triggering connections and synchronisations and registrations of the tonnes and tonnes of shovelware crap that seems to come in with the tide on any modern smartphone these days.
Thanks for the explanation. I guess I can get it taken care of with SuperSU, freeze the things I don't like and then get my download happening in Magisk Manager. Then when I'm ready with my patched boot.img, I can re-flash the stock ROM.
Wouldn't be a terrible feature to be able to just set up the files MagiskManager expects to find so that this all could work in an offline configuration, though!
Tangib1e said:
Ouch. Thanks for the help, Didgeridoohan, that's the answer right there. I like to get my phones set up "just right", which includes getting root and then backup up and freezing various things (for example using Titanium Backup), before ever allowing the phone to go online for the first time and triggering connections and synchronisations and registrations of the tonnes and tonnes of shovelware crap that seems to come in with the tide on any modern smartphone these days.
Thanks for the explanation. I guess I can get it taken care of with SuperSU, freeze the things I don't like and then get my download happening in Magisk Manager. Then when I'm ready with my patched boot.img, I can re-flash the stock ROM.
Wouldn't be a terrible feature to be able to just set up the files MagiskManager expects to find so that this all could work in an offline configuration, though!
Click to expand...
Click to collapse
If you have another device, you can use that one to patch the boot.img. just put magisk manager and the stock boot.img on that one and patch it. Then move it to your PC for flashing in Odin. Make sure that, in the patched boot format settings in magisk manager, you select .tar for the format of the patched image.
Didgeridoohan said:
You need internet access to download the Magisk zip to patch the image. No internet - no install button...
Click to expand...
Click to collapse
The app should really display a message if the phone is offline
Good evening lads. I've been having problems installing Magisk.
I've successfully rooted my device (a Samsung J5 2016) and installed Magisk Manager. From there, I selected "Install" and after the confirmation that I want to install Magisk v20.4(204000) I choose "Direct Install" , which is also the recommended option but get an installation error.
Here's my log:
Code:
- Target image: /dev/block/mmcblk0p16
- Device platform: armeabi-v7a
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
- Repacking boot image
! Unable to repack boot image!
! Installation failed
I'm very noob at this and barely have any idea with what I'm doing, so I'm asking you, what can I do? I checked other threads but their logs was very different.
I've never had any other problem with other root apps (Lucky Patcher, Titanium Backup, Root checker etc.) and all I want to do is hide my root so I can use the Nintendo Switch app, lol.
Thanks in advance for your help.
The usual answer is, into Recovery and flash Magisk Uninstaller, then install the Magisk file in Recovery.
I can't give any guarantees, but that always used to be the way to go, if Magisk did not install with Direct Install option.
Like I say, no guarantees.
Should have said, make a Recovery Backup before attempting.
Second thoughts, another poster has just reported a problem installing 20.4 in TWRP, so maybe it's not such a good idea after all.
I don't advise.
Sorry for wrong advice.
Sent from my SM-G965F using Tapatalk
if anyone is having trouble while installing magisk I have come up with solutions.
if you have installed magisk but it never detects as it is installed the following would be solutions i have found for my self
install magisk that is older than the one you are going to install in recovery with sideload for eg. to install magisk 25.00 from the recovery you need to install magisk 24.1 apk before that without shutting down your phone.
the second step you need to do is you have to side-load the latest version after you have installed the older version from the recovery
that is it simple as it is