After flashing stock rom it seems that root is gone and phone passes safety net. However after managing to flash Magisk, Magisk is not installed in the manager and the safety net fails. It seems that Samsung devices struggle with Magisk.
Phone is Galaxy Note 3 SM-N900
Samsung devices are... Samsung.
A recovery log from the installation might show something.
I'd like to dig up this old topic again, as I'm facing the same issue.
Up until shortly I was using LineageOS 16 on my Galaxy S4 (GT-I9505, jfltexxx), but after replacing the broken OLED screen against an LCD one LOS wouldn't boot anymore and I had to go back to Samsung Stock Lollipop (5.0.1) to be able to continue using the phone (I am poor and can't afford to buy a current model phone, at the moment).
So I tried to root my S4 with Magisk 18.1 (had been running perfectly on LOS), then 19.0, and finally 17.2. The flashing completes successfully, but when I restart the phone and open Magisk Manager it says Magisk is not installed.
Is there a version limit up to which Magisk version is running on Lollipop? Or is Knox the problem here?
Currently, it's rooted with SuperSU, but I urgently need the hide feature to use my banking app.
Can anybody help me please?
Cheers,
Sascha
I have the same problem with S5 klte LOS 16 and TWRP 3.2.3-0 MagiskManager 7.1.1 Magisk 18.1.
The same device type, is running with this setup.
I have tested with other version, but the same problem.
But of all my KLTE devices cannot install Magisk 19 -> boot to download mode (I have not yet had time to look for the mistake)
Related
I have 2 Note 5 T-Mobile SM-N920T my first one i had version 14.0 after i did update to version 15.0 it got stuck on T-Mobile Logo and i had to restore it after that i tried to install twrp 3.2.0 was bootlooping samsung logo , i tried 3.1 and 3.0 was giving same issues on the phone that i had to restore. I used CF-Auto Root and TWRP worked fine with CF-Auto Root then i uninstalled CF-Auto Root and Installed Magisk version 14.0 no issues but once i updated it to version 15.0 same thing so with this phone is only working on version 14.0, now what is confusing me is that my other phone has version 15.0 everything most recent updates with TWRP but no issues on that one so i really do not know and understand why it works on that one but it does not work on this one if they are both same models same phones, can someone explain thank you.
Grab a logcat when the device is bootlooping and then upload that together with the Magisk debug log (you can pull it from /data/adb/).
I just downloaded catlog? how to get the log after it booploops or before? and upload the files here?
Didgeridoohan said:
Grab a logcat when the device is bootlooping and then upload that together with the Magisk debug log (you can pull it from /data/adb/).
Click to expand...
Click to collapse
After I installed Magisk v15 I saved the log with catlog
what's confusing is keeps failing to install smali module as well, I have done it right same steps as my other note 5 something is blocking this, now maybe I need a clean stock the one I have it does the job but I noticed OEM is enabled after developer option is enabled that usually stays disabled after stock firmware is installed, I am just so mad why it's doing this it used to work before now is giving hard time with the same phone.
Catlog File after I installed Magisk 15
https://drive.google.com/file/d/1faS5d6V6DfpGd-afa_3M0-n9zfqYYoSw/view?usp=drivesdk
finally got it to work now. Clean stock firware then i did update to 7.0 naugat, now for my phone SM-N920T the only way i can root with magisk is this way i add TWRP first through Odin once install is done i go to TWRP recovery then i load 2 files Magisk 15 plus antiroot removal tool 4.1 most recent for some reason its working perfect with these steps if antiroot is not in it gets stuck.
Good day guys.
Everytime I flash Magisk 16.0, I get an error (Insufficient boot partition size detected) making the installation incomplete. Any way to fix it? Just new to whole idea.
Just a background. The unit is samsung tab s sm-t805. It was rooted from superSU and want to move to magisk. I tried to unroot SuperSU but end up removing the whole OS of the tablet but found a new 1 and used ODIN to install it. Installed twrp so that I can flash the new magisk. But had the error. Rebooted the system and tried root checker. The app just loads for a long time. The magisk manager just hangs after opening. Thanks for the help.
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Organics said:
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
Please help me to root Moto X4, bootloader unlocked
hrushikesh.inc said:
Please help me to root Moto X4, bootloader unlocked
Click to expand...
Click to collapse
Wrong thread.
https://forum.xda-developers.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
I haven't need to use edxposed as I was refusing to upgrade from my old oneplus 3, so I'm a complete noob here at this point,
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Thanks!
everlasting207 said:
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Click to expand...
Click to collapse
Morning
I have just purchased the same phone, but I didn't get as far as you, so in the hope we can help each other here is a summary of what I did and how far I got -
I upgraded stock ROM all the way upto Android 11
Then enabled dev. options, and clicked on OEM unlock and then rebooted following the new unlock bootloader option on the download screen.
Then rebooted into download mode and flashed vbmeta_disabled.tar via ODIN (this then factor reset the phone).
Then had to re-flash stock android (via ODIN), as OEM unlock disappeared from dev. options.
Then back into download model to flash twrp 3.5.1 via ODIN.
Then after to trial and error and help from @afaneh92 I figured how to get into twrp recovery (and how to stop the phone from restoring stock recovery).
I then extracted & patched boot.img in Magisk (see instructions)
Then I booted back into download mode and 'tried to flash to new magisk patched boot.img via ODIN, but it failed with Can't open the specified file (line: 2006)
I then installed magisk manager 8.05, then tried flashing Magisk 21.2 via twrp and it failed with (Android Rescue party trigger).
So I then re-flashed multi-disabler.zip via TWRP and without rebooting formated data, then power off and boot back into recovery. I then flashed magisk 21.2 no problem.
Back into Android I loaded up magisk to confirm I was rooted and to get Riru & EdXxposed installed.
I installed EdXposed manager via its APK.
I then went back into Magisk manager and found and installed Riru 23.3 (this as i understand it replaced Riru - core).
I then found the latest stable version of EdXposed YAHFA 0.4.6.4 (4563) and this refused to install via magisk manager, with error ( ' Riru - core ' is not installed, Unsupported v22+ is installed, user 21.3 instead ) . So Clearly the above ver. of EdXposed isnt compatible with the latest version of Riru.
I then installed the alpha version of EdXposed 0.5.1.4 (4655) and this installed, but when I went into EdXposed manager it said it was installed but not active
So I have my shiny new SM-G781B, w/custom recovery & rooted, but no Xposed framework. I need Xposed for Xprivacy_lua so not having this running isnt an option. So I am going to try Riru - core 21.3/EdXposed_ 0.4.6.4 and if that fails then going all the way back to Android 10 and starting from the top.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What versions of Android, Twrp, Magisk, EdXposed, Riru - have you got installed? Also regarding your EdXposed bootloop - if you read the supports docs, its does say that YAHFA can cause soft loop, and to try Sandhook. But on my old S7, Sandhook caused a boot-loops so I went to and am using YAHFA with no issues - so as always your mileage will always vary.
ive been trying to root the latest 6.01 UK from (2021) from samsung for the s5 mini 800f with magisk v23
everything says its goes good with the lastest twrp 3.5.2.9-0 but after boot magisk appears to to be not installed
supersu still works.
anyone have any ideas?