Hi everyone, OK I've tried everything in other threads, here's the situation:
Note 4 Sprint
cf-auto-root worked fine, everything working well for a week (stock recovery, stock ROM, just root). Then installed xposed (accidentally used the experimental 2.7 version) and RootCloak module. This threw me into a boot loop.
I recovered from it by redoing cf-auto-root/odin. That got me out of the loop, but-
Ever since then:
- Phone lags for a few seconds every few seconds - making it hard to even type in a phone number, let alone watch a video,
- Fingerprint doesn't work - when launching the menu from settings I get an error that it's unavailable.
I've tried everything in the other threads:
- build.prop change (disabling securestorage)
- successfully installed 2.6 xposed and tried:
- wanam xposed to disable securestorage
- and the xsecurestorage module
- flashed stock rom from sammobile with odin
- even tried disabling selinux with wanam
No matter what, these same issues. I haven't tried anything other than the stock rom. Any ideas at all? Is there a different ROM out there I should try? Does that even have a chance of working?
I'm not sure I understand why flashing stock didn't fix it - even though it caused me to lose root...
Right now I have TWRP with root and stock ROM.
Any ideas or suggestions really appreciated.. I'm out of ideas. Thanks
I have the Same Problem
I had the same problem, haven't bothered installing it again since, don't suppose anyone has heard from the developers?
Hope maybe the devs can shed some light here. Is there anything else I can do? Flashing stock didn't even help. What's left?
So after not touching anything for about a week - things started running smoothly. Very odd - didn't change anything. Xposed was uninstalled for that time.
But, after SuperSU updated (and updated the binary/rebooted), the lag came back. So, this is telling me this may be related to root/SuperSU instead.
Hello,
I'm using MIUI 8 on my phone, its based on marshmallow 6.0.1. I rooted my device using supersu stable 2.78 as systemless mode. The problem is all need-root apps take long time to call supersu at first time it launched. Sometimes need-root app crash if it does not get superuser access for long time. The culprit is on systemless supersu, Superuser.apk installed inside /data partition instead of /system so it won't load on system start. Although i already add SuperSU in startup list, but it was not much help. I did not get this issue on CM13 based rom. Temporary solution is I need to open SuperSU first before open need-root apps for first time.
How to get rid from this issue?
Cc: @Chainfire
Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..
herecomesmaggi said:
Have you found solution yet. Me too facing similar problem, some of my personal apps crashing, I found a system based super Su zip let me flash and report back..
Click to expand...
Click to collapse
Yes. Use phh superuser + magisk latest version. :good:
actually this is not the right answer, wrong thread
Hi
I'm sorry for bumping old thread, I've same issue with very same ROM, MIUI 8 8.1.6 run on mi4W device, magisk 13.3
how I managed to solve this is somewhat ridiculously simple yet make me wandering over the internet for about 4 hours in 2AM,
I forgot to activate the "install from unknown source". after that everything run like magic.
FYI: I've done everything via adb shell via TWRP before the "what if" idea come to my head
Click to expand...
Click to collapse
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