Hey, everybody. First post. I need some serious help. I've been rooting and modding for years, but I don't know everything, so please don't assume that I do. Right, my Exynos G973F is rooted with Thunderstorm Kernel, and has TWRP installed. The phone functions perfectly and all of my apps pass root detection. However, if I restart the phone, it gets to the point where all my icons load and I can use the phone, then it suddenly goes back to the Samsung logo. The case used to be that if I left it long enough, it wouldn't continue to bootloop, but recently I'm having to restore TWRP images just to use my phone. I've done a factory reset, and tried to do the same thing with a custom kernel, but it will not pass safetynet. I've got Riru installed, LSExposed, safetynet patch 2.2.0 and Magisk Hide patch, with a different fingerprint set, and it absolutely won't pass cts. So, starting from scratch is not an option, because I've tried everything. How can I figure out what's making it bootloop? As I've said, the phone is perfect, other than this. It's really bizarre. Hope someone can help! Thanks in advance!
Related
Hello! Today I decided I would give Xposed another chance (I tried installing it through Magisk before, resulted in bootloop). After installing it through TWRP, my phone got stuck in a bootloop. I tried using the Xposed Uninstaller. Didn't work. I tried entering Safe Mode. Didn't work. I tried resetting my phone in TWRP. Also didn't work. How can I get rid of it? Please help, I just want to uninstall Xposed so I can use my phone again). Thanks!
Ovidiu05 said:
Hello! Today I decided I would give Xposed another chance (I tried installing it through Magisk before, resulted in bootloop). After installing it through TWRP, my phone got stuck in a bootloop. I tried using the Xposed Uninstaller. Didn't work. I tried entering Safe Mode. Didn't work. I tried resetting my phone in TWRP. Also didn't work. How can I get rid of it? Please help, I just want to uninstall Xposed so I can use my phone again). Thanks!
Click to expand...
Click to collapse
I guess the only way to revert this is to flash the stock firmware over with Mi Tools.
I'm saying this as a layman, because I'm still studying before doing any dangerous experiments with my mido.
But I've read a few minutes ago that there are specific ports of Xposed for mido. Maybe you should try those. I don't have the links right now, but if you dig up in the forums, you'll probably find what you are looking for.
Those videos on YT also helps, but they're not 100% guarantee that will work at all. You should proceed by reading a lot before tinkering with this stuff, you know.
It's my 1st attempt as well, so I just hope I do everything right to do not result in something like you had. ?
Hey guys. Apologies for the username.. not sure when I made that :laugh:
I was running stable on the 007.a3 image with Magisk v20.1 and Manager 7.4.0 when I made the terrible mistake of trying to update them. Since then, I've flashed the factory 200205.002 image in an attempt to get back to a stable setup, but I'm running into errors getting the CTS verification to go green, on a totally blank slate - even if I roll it all back to 007.a3 and the old boot image. I've tried the Props Config module from Didgeridoohan to no avail, and pretty much every (unlocked) factory image that exists. I'm half ready to throw in the towel and send it back under warranty, but I'm less than keen on waiting 7-10 days for what could amount to a simple firmware fix.
To recap: I've tried flashing factory firmware with a full wipe, different versions of Magisk and its Manager, Props Config module (assigned the build number for 200305.003, no bueno), Core-only Mode, toggling Magisk Hide on and off plus targeting the Play Store, and no small amount of frustrated sighing. Hasn't budged an inch.
Curiously, on any image I flash, the Bootloader unlock toggle is grayed out and can't be interacted with - but, the bootloader is still unlocked. Any thoughts on that?
EDIT: Neat. Bootloader toggle is working as normal now, on 200205.002. No idea what did it but hey.
Second edit: Just noticed that the latest few pages of MagiskHide Props is about this same issue. Sorry guys, didn't see it.
I have this problem as well. I think we just have to wait for Magisk to patch this for us
Good to see I'm not crazy. I happened to reset my phone and this issue came up, so I thought I did a bad.
Greetings Magisk fans, I need serious assistance, as I meant to state in the title, here is the situation. On yesterday I decided since the issues Magisk is having with SafetyNet checks, and not solution I found worked, I decided to remove Magisk from my T-Mobile OnePlus 6T. Here is where the trouble begins, upon removal, using the Magisk Uninstall in TWRP, when the phone boots back up, the phone will not move beyond the Bootloader unlocked warning. I had to put Magisk back on to get the phone to bootup. I even used MSM tools to rebuild the phone to factory fresh, root it again and unroot. It happened again, like I figured it would. SO the question, how do I remove Magisk without causing the same issue? Thank you, in advance for your response.
So... I have an interesting situation here
So I have the 1TB Rog Phone 2 WW model. I went through the process of installing magisk, everything worked fine. I installed edXposed as my xposed solution, installing the required magisk modules which also seemed to work just fine. At some point, I would swear the last change I made was to edXposed which caused a bootloop scenario, possibly a module, I wasn't able to isolate the specific cause. However given the nature of the issue, I haven't ruled out some conflicting magisk module as the culprit. I used the fix bootloop recovery option in TWRP (probably a mistake), which did allow me to boot back into the system, but it disabled magisk. Reinstalling magisk causes the boot loop.
And here I am.
Flashing magisk will fully prevent the system from booting normally. I can no longer root it using magisk without it bootlooping.
"did you remove the offending modules"
Well, I used two guides which basically walk you through the magisk recovery manager, adb alternative, and list module paths, (since I can't post the actual links)
to no avail. The magisk recovery manager failed to install and I was unable to locate any modules in any of the specified paths
(/data/media/mm and /sdcard/mm (I am concerned I do not have the correct module path, but the recovery manager also fails to install, so I'm not necessarily sure what is going on other than it can't find any modules either).
Now yes, I do realize I can flash the stock firmware and start again, but this can be a pain in the neck (I assume the VoLTE trick doesn't survive that process not that its a super difficult process), and ideally I'd rather learn more about the system because that was the point of all this.
If anyone has any input or direction as to an alternative solution to a full on factory restore, I would be most humbly appreciative. I like tinkering with my devices, and this seems like something that can be repeated pretty easily, so I'd like to be better prepared.
Hi , sorry if i can't help you.. since i was also having the same problem although not using any modules from xposed.
flashing magisk via twrp or using patched.img will always yield to bootlop but flashing stock.img will fix it.. but ofcourse we want to root but can't seem to pass this barrier..
i hope someone could help and tell us why is this happening
Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem.
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
If you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!
Maspon said:
Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem or I just disabled too many system apps (Galaxy Themes, Bixby Service, Galaxy Friends and stuff).
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
Whether you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!
Click to expand...
Click to collapse
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.
xfakexbloodx said:
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.
Click to expand...
Click to collapse
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?
Maspon said:
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?
Click to expand...
Click to collapse
Based on this post
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.
xfakexbloodx said:
Based on this post
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.
Click to expand...
Click to collapse
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.
Maspon said:
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.
Click to expand...
Click to collapse
Sorry no idea about that. I'm using alexis rom though..
xfakexbloodx said:
Sorry no idea about that. I'm using alexis rom though..
Click to expand...
Click to collapse
Sadly my phone still rebooted this morning. I caught the last kernel message and I hope it will help