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.

Help - Uninstalled Magisk from Android P (Pixel 2 XL) Still no Google Pay

Hello everyone,
I've uninstalled Magisk 16.1 from my Android P firmware (Pixel 2 XL).
Thing is, even if it's uninstalled I still can't use Google Pay.
https://image.noelshack.com/fichiers/2018/26/6/1530382189-screenshot-20180630-200734.png
I installed Magisk without installing TWRP, I just used the fastboot boot xxx-twrp.img with unlocked OEM
Now I relocked the OEM firmware, new fresh install but I still have the error message, it drives me crazy. What can I do to get a fresh firmware again ?
Thanks!

omegear said:
Hello everyone,
I've uninstalled Magisk 16.1 from my Android P firmware (Pixel 2 XL).
Thing is, even if it's uninstalled I still can't use Google Pay.
I installed Magisk without installing TWRP, I just used the fastboot boot xxx-twrp.img with unlocked OEM
Now I relocked the OEM firmware, new fresh install but I still have the error message, it drives me crazy. What can I do to get a fresh firmware again ?
Thanks!
Click to expand...
Click to collapse
Check if your device is certified
You can check that by going to Google Play > Settings > Device Certification

Hello, thanks! It's uncertified. What should I do ? Factory reset ?

omegear said:
Hello, thanks! It's uncertified. What should I do ? Factory reset ?
Click to expand...
Click to collapse
If you have Magisk, the solution would be to use Magisk Hide on Google Play store and then reboot
And if that didn't work, then there are modules that will do the job and fix the issue
If you don't, then your solution is to revert back to stock ROM and factory reset

My playstore is now certified, thanks evertyone!

vbajs said:
If you have Magisk, the solution would be to use Magisk Hide on Google Play store and then reboot
And if that didn't work, then there are modules that will do the job and fix the issue
If you don't, then your solution is to revert back to stock ROM and factory reset
Click to expand...
Click to collapse
have you uninstalled it using your installer? if not surely that will be
Enviado desde mi MI 4S mediante Tapatalk

Suggestion for a custom non-MIUI ROM with working Google Pay and NOT using magisk

1. I don't want to root my phone.
2. I was using lineage 16 (up until 4 hours ago) but using some weird TWRP which can't decrypt internal storage. Seems the this custom TWRP includes sqlite.
3. Currently trying pixel experience but it seems this requires magisk to get Google Pay working.
Thanks

Gpay works without magisk on the latest PE 10

mar.ur said:
Gpay works without magisk on the latest PE 10
Click to expand...
Click to collapse
I tried setting an existing credit card in my google "wallet" and it keeps on saying "this may be because it is rooted or altered in some other way". i don't have magisk installed.
1. using this TWRP (this is the recommended one by the dev)
2. no magisk
3. using PE/Android 10 beta Oct-13 version
Thank you.

@mrjayviper I try 11.10 PE10 a few days ago and it was working for me. I afraid there is only stock miui with working gpay without Magisk. If you want use custom ROMs and Gpay you have to use Magisk to hide state of bootloader

Question Finally got my m11u, 2 more hurdles!

Hi guys, coming from a OnePlus 5t, got my m11u and finally waited the 168hrs! Following the instructions on the first post and finally got the bootloader unlocked, I found that was the hardest part, as I had to figure out on my own how to set up adb and the unlock tool etc. But thanks to YouTube I got through and now on EU 13.0.9.0 stable.
During the first week waiting for the unlock, I was hopeful of seeing if I can just enjoy the CN MIUI 13 ROM...deleted as many CN apps, installed Google Play etc and it seemed to be going well....until I noticed the huge problem w getting call and msg notifications. That was already a dealbreaker and seems like no real solution but to continue with a new ROM.
Now using the EU 13.0.9, everything seems great and working well. Except, I am trying to install Vanced youtube but cannot! On the CN ROM it was simply to turn off MIUI optimization in dev options, but xiaomi.eu has removed that option (cannot get the toggle even by pressing reset multiple times). What are my options at this point? Am I left with only option to root the device?
if so, I will try to learn to do it, but I'm hoping someone can point me towards the correct path. There is a how to thread here but it seems outdated as it refers to MIUI 12 and not 13(a12). So far from what I understand:
- a12 root is done with latest magisk v24+
- however v24 no longer use hide magisk and need to use zygisk and a deny list
- bear in mind I don't understand what the above means yet
- from my current status (newly installed EU ROM), what steps do I take?
- download magisk manager APK and install on phone
- make a patched boot.img - DO I USE THE BOOT.IMG FROM THE EXACT EU ROM I FLASHED?
- use fastboot to boot the patched boot.img?
- after this most tutorials tell me to download hide magisk and such, but v24 will be different
- where to go from here to install Vanced root version, and am I missing any steps? After root, will it affect my banking etc?
any help appreciated! Cheers

VinillaIce82 said:
Hi guys, coming from a OnePlus 5t, got my m11u and finally waited the 168hrs! Following the instructions on the first post and finally got the bootloader unlocked, I found that was the hardest part, as I had to figure out on my own how to set up adb and the unlock tool etc. But thanks to YouTube I got through and now on EU 13.0.9.0 stable.
During the first week waiting for the unlock, I was hopeful of seeing if I can just enjoy the CN MIUI 13 ROM...deleted as many CN apps, installed Google Play etc and it seemed to be going well....until I noticed the huge problem w getting call and msg notifications. That was already a dealbreaker and seems like no real solution but to continue with a new ROM.
Now using the EU 13.0.9, everything seems great and working well. Except, I am trying to install Vanced youtube but cannot! On the CN ROM it was simply to turn off MIUI optimization in dev options, but xiaomi.eu has removed that option (cannot get the toggle even by pressing reset multiple times). What are my options at this point? Am I left with only option to root the device?
if so, I will try to learn to do it, but I'm hoping someone can point me towards the correct path. There is a how to thread here but it seems outdated as it refers to MIUI 12 and not 13(a12). So far from what I understand:
- a12 root is done with latest magisk v24+
- however v24 no longer use hide magisk and need to use zygisk and a deny list
- bear in mind I don't understand what the above means yet
- from my current status (newly installed EU ROM), what steps do I take?
- download magisk manager APK and install on phone
- make a patched boot.img - DO I USE THE BOOT.IMG FROM THE EXACT EU ROM I FLASHED?
- use fastboot to boot the patched boot.img?
- after this most tutorials tell me to download hide magisk and such, but v24 will be different
- where to go from here to install Vanced root version, and am I missing any steps? After root, will it affect my banking etc?
any help appreciated! Cheers
Click to expand...
Click to collapse
- In xiaomi.eu rom, u didnt need to turn off miui opti, they already tweak the rom, so u can install vanced normally (no-root version)
how to root
Installation
The Magic Mask for Android
topjohnwu.github.io
how to hide root : 2:52
- if any app detect root, u can add it in deny list

hungragezone said:
- In xiaomi.eu rom, u didnt need to turn off miui opti, they already tweak the rom, so u can install vanced normally (no-root version)
how to root
Installation
The Magic Mask for Android
topjohnwu.github.io
how to hide root : 2:52
- if any app detect root, u can add it in deny list
Click to expand...
Click to collapse
now that you mentioned it, i went and tried to install it again. I played with some permission settings and now it does work! thank goodness now i don't have to deal with rooting.
thanks!

How to root OSS and still pass safetynet checks (2022)

So I just bought a OnePlus 7T Pro McClaren Edition and its great
But I would really like to have it rooted.
I currently finally have stock rom installed again (after many frustrating hours) and am now passing the safetynet check.
I can:
1. Install Magisk (as an apk),
2. Patch boot.img
3. Unlock oem
4. Flash the patched img file
This works and I can have root access.
So far, unless I flash the original boot.img and wipe data again, I cannot lock OEM again (without seeing the corrupted data message).
Also, without locking oem, I'd keep getting the boot warning about bootloader being unlocked (which I guess is not so bad).
Seems like unless I have stock rom flashed, the safetynet check CTS test fails.
Anyways, I'm trying to find a way to root OOS and still pass the safetynet checks.
Thanks.

You need to enable Zygisk in Magisk, configure DenyList (walletfcrel, walletnfrćrelrimes_lifeboat and gapps and gservices), clear all data from Play Store, Play Services and GPay and reboot

Hi, Gpay updated to Google Wallet this method no longer works.

slapman said:
Hi, Gpay updated to Google Wallet this method no longer works.
Click to expand...
Click to collapse
Hi, yes, it does, i can confirm on both Oneplus 7 and Oneplus 7t Pro. You need to install universalsafetynetfix magisk module additionally and don't forget to wipe the data of gpay, google play and play services

DartGerion said:
Hi, yes, it does, i can confirm on both Oneplus 7 and Oneplus 7t Pro. You need to install universalsafetynetfix magisk module additionally and don't forget to wipe the data of gpay, google play and play services
Click to expand...
Click to collapse
At the time it didn't, and I had to find the the updated safetnet fix especially after updating to Android 12 and I custom ROM crDroid 13.

What Android version /oos version are you using ?