Database Develop

Samsung S5 Plus Magisk above v12 boot loop stuck on boot logo

Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please

I have also fully reinstalled the ROM with formatting everything and it still don't boot

Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?

ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.

Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.

Flash your stock bootloader then try flashing magisk

I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?

No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?

Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.

Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?

Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.

Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed

Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492

cross the fingers (I hope that you say like that in English)

Fingers crossed they sort it. Would love yo be able to use magisk again

Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.

It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.

Kernal or ROM that hides KNOX Trip?

Hello,
I rooted and installed a custom ROM on my Note 9 a couple of months ago and yesterday I was getting annoyed not being able to use apps like Android Pay, Samsung Pay and Banking apps, So I decided to use Odin to flash the stock ROM back and set OEM Unlock to OFF. To my Horror, I found out the hard way about what a KNOX Trip was. I have no idea how I missed all the warnings on every ROM post about tripping it and not being able to change it back. I can now use my Banking apps, Android Pay and play Fortnite however, Because of the Knox being tripped I can no longer use Samsung Health and Samsung Pay
My Question is is there a way to just install a custom kernel or ROM that tricks apps like Samsung Pay and Samsung Health into working again without installing root and having modifications hidden so I can use my Banking apps and play games??
Any Help is very much appreciated!

After a bit more searching the forums and Google I now understand that no matter what I do I can't get Samsung pay to work which is fine. However any help on the rest is still appreciated! ?

You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query

bober10113 said:
You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query
Click to expand...
Click to collapse
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.

VortexHD said:
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.
Click to expand...
Click to collapse
so for example you went to magisk hide menu and selected your banking app and it didnt work?

bober10113 said:
so for example you went to magisk hide menu and selected your banking app and it didnt work?
Click to expand...
Click to collapse
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.

VortexHD said:
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.
Click to expand...
Click to collapse
how about safety net status, is it passing?

bober10113 said:
how about safety net status, is it passing?
Click to expand...
Click to collapse
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.

VortexHD said:
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.
Click to expand...
Click to collapse
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.

bober10113 said:
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.
Click to expand...
Click to collapse
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?

VortexHD said:
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?
Click to expand...
Click to collapse
for google pay, some actualy revert to an older version. just search the forums. for me magisk hide works great with my banking app. and for games, im not much of a gamer so i realy dknt know. but again you should try with dr. ketan rom just in case it works. just choose to flash kernel and magisk during setup.( do a clean install so factory wipe in twrp before flashing his rom)

Well i decided to just use Stock Rom and lock the bootloader so at least most of my apps then work. I installed a modified apk of Samsung Health but it doesn't contain the heart rate monitor but I suppose that's fine and I just have to accept that Samsung Pay will never work again

Where can i get the old version of Google pay which works with unlocked bootloader?
Sent from my SM-N960F using Tapatalk

S heath can work on a rooted device with a simple change to the build prop , but secure folder and spay remain a dud

help for rooted note 8

Hi guys. I need some help for my rooted galaxy note 8. I had rooted my phone a long ago and all was working good. All apps including banking apps were working fine with magisk hide. But few days ago i wanted to update my phone so i flashed stock rom with odin and updated my device. Earlier my bootloader version was 6 and now its updated to version 8. Then after updating i flashed latest twrp and rooted with magisk. I flashed magisk version 20.1 and magisk manager version was 7.4.0 . Then magisk update was available so i updated to magisk version 20.2 and magisk manager to version 7.5.0 . Now the problem starts. I am facing 3 issues.
1- my phone starts freezing and then reboots randomly. It happens quite frequently atleast 2-3 times in a day. Every time i clear cache partition from twrp but problem persists. I had checked ram also but ram useage is also fine. Please help me with this issue.
2- while searching for the solution of above problem i read somewhere that it might be because of safety net check. Earlier safetynet check was pass but now safety net check was fail. I flashed bypass safety net mod. But when my phone reboot a warning appears that your device has some internal problem. Contact the manufacturer. I pressed ok and phone starts. It seems to work normal but then i realised my device was not connecting to any wifi network. When i click on available wifi nothing happened. So i uninstalled the safety net bypass mod and then wifi start working again.
3- now final thing i want to know. If the above problem did not solve then i have to unroot my phone which i dont want. But if i had to then i dont want to flash stock rom. I want to unroot from magisk app itself. I had edited build.prop file for using samsung health app. So now if i unroot from magisk app will the changes made by me in build.prop file remain or it will revert back. Also will banking apps work or not....
I know its very lengthy post but please help

Wow...
70 views no comment..... it seems all the developers and tech people are enjoying winter break

Try going back to previous version of Magisk. I have Snapdragon N8 so I have supersu. But I did update my A20g with newest Magisk and had an issue. I know you have N8 but was just saying maybe could be new Magisk.
My SM-N950U Still Rooted Note 8

Any solution for Rooting lineageos android 10 with magisk

Hi,
Recently I installed lineageos android 10 on Samsung Galaxy S3 Neo Duos
Then tried to use magisk to gain root privileges but simply can't do that
SafetyNet Check: All False
Installation Failed: UnSupported / UnKnown Image Format
I search about this problem and found the next link
LineageOS is dropping its own superuser implementation, making Magisk the de facto solution
I read it but can not figure why lineageos team drop superuser, but this is not my problem
I just need to know I there any way to root my device Even if without magisk
Or I Will need to downgrade to android 9
Also if the answer is I must downgrade to android 9
Does this mean any new rom start from android 10 + will not have any way to gain root privileges ???
Thanks.
---------------------------------------------------------
To 73sydney
First: Thank You
I take the next steps
Download lineage From Here
Install TWRP latest version TWRP-3.3.1-1-s3ve3g.img.tar With Odin3_v3.14.1
Use TWRP to install lineage_s3ve3gds: and everything worked correctly
Download Magisk-v20.3.zip
Copy it to my sd card
Open Device In Recovery mode and then use TWRP to install magisk
and it does not show any error messages
Install magisk.apk
Open magisk app
Show me: Magisk is not installed
Press Checking SafetyNet Status
Show CtsProfile: false, basicIntegrity: false
This is how I install android 10 and Magisk

Nothing to do with Android 10 as we just got LineageOS 17 on my Note 4, and i have Magisk running fine, only needed to fix CTS issue with MagiskHide Props Config as per following video
https://youtu.be/wKYC0r-m0Mo
It could be the way youre flashing magisk, or the way the ROM is built, because im just guessing because the Note 4 is unofficial LineageOS, the S3 build would be too. Frankly im surprised anyone would bother with the S3..
To get to the main issue though, lets get the basics... just how are you trying to install Magisk?
Just found your devices forum, theres like 3 threads/guys spraying LineagesOS builds into it. Perhaps tell them to work together for starters....
And really ideally they'd test for the possibility of rooting and root solutions before releasing because gets what question number 1 is going to be, how do i root this? Again, perhaps get them to work on it together
LineagesOS dropped their SU simply because its outdated, doesnt do what Magisk can do (modular addons to customise) and prolly mostly, its not used by anyone

I edit my post to explains all steps i take to install lineageos & magisk
Thank you for your reply
First I Edit my post to all steps you asked
Second: I am not an android professional
I tried to figure out what you means but can not.
I just want to know steps to gain root access
Please Notice: OEM option does not appear in developer options
So please if you can give me a link/resources to know how to root my device [Samsung Galaxy S3 Neo Duos With lineageOs 17.1] this will be very helpful
Thanks.

It's perfectly possible that it isn't possible to root your ROM with Magisk. It depends on how it's created... If it's using fake dts Magisk won't work. References:
https://twitter.com/topjohnwu/status/1226644269261213696?s=20
It was the same case for LineageOS 17.1 on the Nexus 4, but that was fixed. See the ROM thread for more details:
https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
None of this is something that you as the user can do anything about. It has to be fixed by the developer, so let them know (if it is a case of the ROM using a fake dts).

Magisk 20.4 with the 7.5.1 manager is working perfectly in a Nexus 5 with LineageOS 17.1.

Magisk and encryption help

Hi,
I'm using Havoc OS on my redmi note 3 which is on Android 11. I'm also using the latest Magisk. Currently, I need to use Google health connect, which req my phone to be encrypted. So can I go to settings and encrypt my phone? Or must I uninstall Magisk, encrypt, and then reinstall backMagisk?
I have been searching for this info but most of them are old posts and each mtd is different.
Hope someone can give an updated solution.
Thanks.