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.
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
Hello,
The last couple of months and completely out of no where my 4g data randomly stops working. The status bar icon shows that it's stuck on upload and won't download any data. The only way I've found to fix it outside of restarting the phone is to change the cell band type from auto to wcdma then back.
Anyone have any ideas on how to fix this?
Second issue is with Magisk and I know this is for Samsung but I figure why not ask anyway. As of yesterday after a reboot I lost root. Magisk apps shows I need to install magisk and install the app even though I'm in the app. Also a bunch of my apps are acting like I've never uzed them before and they need to be setup again. I haven't installed any updates so I'm not sure what caused it.
I've tried completely uninstalling Magisk and reinstall and that didn't do anything. The install went through fine but after launching the app it still says no root.
Any ideas?
Thanks
Hi, I think it has been updated and Magisk is useless due to new layers of security. I guess we'll wait until a new rom is made for the new update, including stock. I don't know if Magisk can release a new version and overcome this.
Thanks.
Reflashing the custom firmware then also Reflashing Magisk did get it working for me again.
I've since updated to the newest firmware, flashed OneOS and Magisk and it's been working fine until a little while ago when Magisk randomly shows as not installed again after a reboot.
I take it no one else has had this issue still?
Thanks
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Backup your data, then do a factory reset.
Thanks, I've tried that multiple times actually. Unfortunately it doesn't fix it
Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?
hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
I have this exact same issue.....
I dont know why this happend and how to fix this annoying issue!!
Which ROM do you have installed?
Oceanone said:
Same problem here. Flashed my phone with EU ROM, it will reboot to recovery mode several times before it starts up with normal MIUI. Note: Bootloader was in unlock status. Anyone has a solution?
Click to expand...
Click to collapse
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.
Same issue, same topic:
Phone-Root boots into the Miui recovery with root (NON-TWRP)
Hi, Im testing my phone without, NON-TWRP. After root, and shutdown/restart the phone, the phone boots automaticly to Miui recovery instead of starting the phone normally... After 10 min, the phone starts in the normall mode with root. How to...
forum.xda-developers.com
aygul12345 said:
Could you explain what your situation is right now?
Im also flashed to EU ROM of Xiaomi Official. And phone boots into to the recovery on every reboot, after a few reboots the phone boots in to the normal OS.
Click to expand...
Click to collapse
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
I'm smashing my head around....
Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
I'm smashing my head around this... Exact same issue....
Flashing the latest EEA from, and installing 2 modules to hide that I'm being unlocked the boat loader, from that point if I restart than occurs the recovery boot loop.
Same moment not 30 days later.
Oceanone said:
Same with yours. My phone was purchased in China. In order to use Andriod Auto (Chinese rom does not have AA), I flashed my phone to EU rom (V13.0.7). Because of the region restriction, I have to keep the bootloader unlocked. Then installed Magisk to hide the root in order to use Google Pay. It can reboot without any problem for the first month. Then suddenly it will reboot to recovery mode several times before reboot to normal OS. Never update the rom after flash to EU rom. So I have no clue why it works well at first.
Click to expand...
Click to collapse
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).
hympe said:
Hi guys,
Hope someone can help. It's been month now that this issue has started and I have no clue what it is. So basically I have unlocked my phone and flashed with a custom ROM. However, every time I switch on the phone (I'm one of those who likes having it off at night) it reboots several times to recovery mode, so I have to reboot it again (like 3 or 4 times) until it finally starts up normally to Miui.
Anyone has any clue please??
Thanks a lot
Click to expand...
Click to collapse
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.
aygul12345 said:
Did you test if you flashed fresh your EEA ROM, and doesnt installed one of the modules, does it then also reboot into the recovery bootloop? Im troubleshooting maby the module is corrupt (Magisk props hide / fingerprint).
Click to expand...
Click to collapse
I didn't text that, because I need to use both Android Auto and Google Pay. To use AA, I have to unlock bootloader. To use google pay, I have to install a module to hide root.
Oceanone said:
I installed Universal SafetyNet Fix v2.2.1 (Author: kdrag0n) on my phone.
Click to expand...
Click to collapse
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?
aygul12345 said:
Im testing a few days, and it seems to be that the Universal Safetynet fix Author Kdrag0n , gives this bootloop Recovery. If I flash fresh a EEA ROM from scratch, and install ONLY this module, then it boots into the recovery WITHOUT TWRP into Recovery MUIU 5.0 and with TWRP in to Recovery TWRP.
Can you test it for me by disabling ONLY this module Safetyfix, and give your phone a reboot, if this still happens boots into the recovery?
Click to expand...
Click to collapse
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.
aygul12345 said:
Did you also installed the module Safetynet fix: v2.3.1?
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Click to expand...
Click to collapse
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
Thanks for the confirmation!!
aygul12345 said:
Thanks for your confirmation.
As we speak im writing right now an issue. to the author. Let you know when its done.
Click to expand...
Click to collapse
I saw your post on Github. Thanks for the effort! https://github.com/kdrag0n/safetynet-fix/issues/216
hympe said:
Thanks for the confirmation!!
Click to expand...
Click to collapse
hympe said:
I actually have. I've got the v2.2.0. and I see there is no point in updating it cause you also have the same issue with the newer version. But great that we now know the source of the issue!! Definitely needs to be flagged to the devs
Click to expand...
Click to collapse
Oceanone said:
I reboot my phone several times after disabling SafetyNet. It all works fine. So you are right. The SafetyNet caused the bootloop. Maybe we can leave a comment on github to the author. Hope he can fix it in the next release.
Click to expand...
Click to collapse
The cause of this issue is being logged on to the author github:
Xiaomi Mi 11 Pro - Installing this module boots into the recovery continuously · Issue #216 · kdrag0n/safetynet-fix
Describe the bug A clear and concise description of what the bug is. After having Root enabled by TWRP OR Flashing Magisk_modified_boot.img, there is no problem with Root on this device. But after ...
github.com
@Oceanone
@hympe Don't need to update, if it happens below then it also is happening on the latest version.
But @hympe can you confirm when you disable the Safetynet fix module, the phone reacts normally and boots normally?