Root not working after flashing Magisk patched boot.img on Samsung GT-I9300 - Magisk

It's a bit of an older phone but I cannot get root properly working on my Samsung GT-I9300 using Magisk. I need Magisk to hopefully get some banking apps working again on my LineageOS 17.1 custom ROM. I downloaded Magisk v25.2 (Latest) from github, patched the boot.img from the installed ROM: lineage-17.1-20200717-UNOFFICIAL-i9300.zip, all with no errors.
Instead of using fastboot I renamed the patched magisk_patched-25200_eb1Em.img to boot.img and created a tar file from it so I can flash it with Odin3 v3.14.1.exe (AP checkbox) as I did for the twrp recovery image. After this some signs of root access are visible. Root Checker Pro even shows my device as rooted. Still it says that the su binaries are missing and Magisk keeps showing as not installed. I even tried CF-Auto-Root-m0-m0xx-gti9300.tar through odin and/or flash UPDATE-SuperSU-v2.46.zip through the installed twrp recovery but the results stay the same.
Wat can I do more to get it working?

Related

Installed Magisk 19.3 using TWRP, seems not installed in Magisk Manager.

Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.
NeroDePero said:
Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.
Click to expand...
Click to collapse
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk
zencooler said:
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.
NeroDePero said:
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.
Click to expand...
Click to collapse
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk
zencooler said:
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
I am using a Samsung Galaxy Tab S3 (T825). I used a stock firmware from SamMobile (which exists of 5 times an .tar.md5 file) and flashed it on my device using Odin.
[EDIT] So here is what I did. Made a back-up using TWRP, and used that boot.img to patch in Magisk Manager.
Now I have a patched IMG file. But when I want to install it using TWRP I have to pick a partition and I am not sure which one to pick.
[EDIT] I tried installing it, and it was successful, yet shows the Magisk manager app that there is no ROOT available.
I guess I just need to start from the very beginning over again. Can you help me with that?
I have stock firmware .zip for my T825 from SamMobile which I can install using Odin.
I also have a working TWRP .zip file that works fine with that firmware on my device.
Other than that I'll need guidance because I keep screwing up :')
Your help is much appreciated
I did a factory reset, flashed TWRP, and installed Magisk using TWRP. After rebooting there was no Magisk Manager app (but it did install a TWRP app).
I installed the Manager app with a downloaded .apk (latest version) and it shows that Magisk is not installed.
So, I want to try patching my .img file using the manager app. The only problem is that I do not have an .img file, as I used . md5 files.
Can I make a back-up with TWRP and use the .img file from there?

installing magisk

hi i installed magisk with different ways but they didn't work firstly i wanted to install magisk without twrp recovery or any custom recovery
so i tried the first method
getting boot.img from my firmware and coping it into the device
then patching it with magisk
after that flashing it with adb
but adb doesn't detect my phone in fastboot mode and i tried installing drivers and every thing so i flashed it using odin
and after that i see that magisk is not installed
my phone is saumsung a505f bootloader unlocked
so i tried patching AP file from the firmware and that is the last method i had tried
coping the AP file to the device
patching it with magisk
getting device into download mode
and install the whole firmware using the patched AP
after that wiping the phone data
then after the normal installation i see that magisk is not installed
what did i miss and is there anyother way to install it

SafetyNet Problem after Magisk Installation

Hello.
I'm a beginner at thing like this. Please your understanding.
I choose Magisk because the SafetyNet bypass it offered.
My device is SM-G532G with Android 6.0
How I installed Magisk:
1. I patched the boot.img and flashed it using Odin. Not with ADB because I can't boot into fastboot mode. I don't know why.
2. Magisk succesfully installed and it work properly with root apps.
The only problem is that my device can't pass the SafetyNet. It also told me that my device is not official when i booted to Download Mode.
Then I tried installing Magisk with the zip file after I clean flash my device with the official firmware. I didn't solve the problem.
I have some guess about the problem.
1. I should flashed the boot.img with ADB.
2. Since I can't boot into fastboot mode, I'm not sure whether the bootloader was unlocked or not. I got the error "Can't mount /data" message. The problem might have something to do with that.
What I want to ask:
1. Does installing Magisk using the patched boot.img and the zip file brings different outcome?
2. Is it possible to fastboot my device?
Regards.

Magisk patch on SM-A520F (Galaxy A5 2017) FAILED

Hello,
I've been using magisk for some time now and no problem until now. I recently updated my firmware to the last version and intended to update it and keeping magisk, but it didn't worked.
Every time I would flash magisk to the boot image by any mean, the system would boot and tell me "system was modified : press the nuke button to restore it (you will lose all your data lol)" or womething like that.
I was able to flash the stock update and get my phone working with the last firmware but magisk is not installed. I also installed TWRP without problems (helped me a lot to flash the stock boot.img and restore the phone).
I tried to install magisk using :
- Odin : Modified boot.img using magisk app and repacked as boot.img.lz4 in the AP file (with correct lz4 parameters)
- TWRP : Flashed modified boot.img from earlier
- TWRP : Flashed magisk ZIP directly
- Odin : Flash full AP modified by Magisk app
Every time, I have that black screen that tells me my system will be wiped if I continue. Magisk, Odin or TWRP do not return any error
Feel free to ask for any file or further info and thank you for your help !
Firwmare version is A520FXXUGCTKA_CL19831441_QB36271825_REV00
Magisk app returns :
- Ramdisk YES
- A/B NO
- SAR NO
Did you try after you install the new rom through Odin, then instal Twrp and then in Twrp you Format data(not wipe) then immediately install magisk. If dosen't work try with another firmware.
I never update firmwares if there isn any visible difference. Mostly is always some security fixes which i dont care about.
hey, Im having a different issue where after installing lineage 18.1 on my a5 i flashed the latest magisk but once i got in the phone it cycled into a bootloop and now it's eternally turned off cant even turn it into twrp. any suggestion?

Magisk lost root after upgrade

I updated my magisk manager to the latest version 22000 and i lost root after I did direct install, I tried flashing the patched boot image with fastboot and I also did a clean flash of my phone and replaced my stock image with the patched boot image but magisk manager is still asking me to install magisk, I also tried with the latest canary build but same thing, I'm frustrated already.
My phone is Itel A11 running Android 6.0

Categories

Resources