Riru (core) is causing random soft boot - Samsung Galaxy Note 10 Lite Questions & Answers

Riru core magisk module is causing random soft reboots in my Samsung Galaxy Note 10 Lite (running Android 10). Can anyone help regarding this issue?
I have tried both EDxposed and LSposed. Whenever I only tick the Riru core within magisk app then soft reboots occur randomly.
The developer of Riru said that it might be a Samsung's Kernel problem.
Does this issue occur in all the Samsung phones? Or a few phones face this issue?
Can this problem be solved if I upgrade to Amdroid 11?

I use riru core with no problems with android 11, so I guess that updating to android 11 will solve that problem

Newtonsart said:
I use riru core with no problems with android 11, so I guess that updating to android 11 will solve that problem
Click to expand...
Click to collapse
Is you device also Samsung Galaxy Note 10 Lite?

kaisar1994 said:
Is you device also Samsung Galaxy Note 10 Lite?
Click to expand...
Click to collapse
Yep

kaisar1994 said:
Riru core magisk module is causing random soft reboots in my Samsung Galaxy Note 10 Lite (running Android 10). Can anyone help regarding this issue?
I have tried both EDxposed and LSposed. Whenever I only tick the Riru core within magisk app then soft reboots occur randomly.
The developer of Riru said that it might be a Samsung's Kernel problem.
Does this issue occur in all the Samsung phones? Or a few phones face this issue?
Can this problem be solved if I upgrade to Amdroid 11?
Click to expand...
Click to collapse
Hello Kaisar, I'm too having the same problem with my Note 10 lite. Have you found the solution?

bajra said:
Hello Kaisar, I'm too having the same problem with my Note 10 lite. Have you found the solution?
Click to expand...
Click to collapse
I have not been able to find the solution.

Same here, I think that the problem is LSposed.
And I'm running latest update

Newtonsart said:
Same here, I think that the problem is LSposed.
And I'm running latest update
Click to expand...
Click to collapse
No, the problem is the "Riru" magisk module. Whenever I turn this module on, random reboots occur. Even if the LSposed is turned off in Magisk, then also I face the problem.

Newtonsart said:
Yep
Click to expand...
Click to collapse
How did you flash the boot.img after patching it with the Magisk original apk? For me it didn't get flashed. I had to patch it using canary version of Magisk before flashing the boot.img file.
And how long could you use Riru Core without facing the reboot problem? At first you said that the reboot problem wasn't there for you.
I am getting crazy to solve this problem. As I will not be able to use GravityBox without Riru.

kaisar1994 said:
How did you flash the boot.img after patching it with the Magisk original apk? For me it didn't get flashed. I had to patch it using canary version of Magisk before flashing the boot.img file.
And how long could you use Riru Core without facing the reboot problem? At first you said that the reboot problem wasn't there for you.
I am getting crazy to solve this problem. As I will not be able to use GravityBox without Riru.
Click to expand...
Click to collapse
I used Odin, And I had no problem flashing it.
I started having this problem one month ago, at first I had no problem with it.
It happens to me twice or 3 times a day. And it's pretty annoying.
I use Riru for LSposed disabling flag secure and Xprivacy Lua. I'm experiencing this issues with the module of LSposed disabled, so yeah, it must be Riru core

Newtonsart said:
I used Odin, And I had no problem flashing it.
I started having this problem one month ago, at first I had no problem with it.
It happens to me twice or 3 times a day. And it's pretty annoying.
I use Riru for LSposed disabling flag secure and Xprivacy Lua. I'm experiencing this issues with the module of LSposed disabled, so yeah, it must be Riru core
Click to expand...
Click to collapse
Did you update firmware before facing this issue?

kaisar1994 said:
Did you update firmware before facing this issue?
Click to expand...
Click to collapse
It started without updating. And now, using latest firmware it keeps happening

Newtonsart said:
It started without updating. And now, using latest firmware it keeps happening
Click to expand...
Click to collapse
The day before yesterday I flashed United Kingdom (BTU) version of firmware and rooted it by magisk canary version. Till now no reboot issue. May the Almighty make this work. You can try this.

It happened again. No hope for now.

Has anybody found the solution?

bajra said:
Has anybody found the solution?
Click to expand...
Click to collapse
Nope bro

Newtonsart said:
It started without updating. And now, using latest firmware it keeps happening
Click to expand...
Click to collapse
Zygisk LSposed is working I guess.

kaisar1994 said:
Zygisk LSposed is working I guess.
Click to expand...
Click to collapse
Yep, I'm using it. No random reboots

Related

Flashed NVIDIA's WiFi 4.1 (MM 6.0.1) update, and now Xposed won't work

So I updated my newer Shield Tablet to 4.1, and restored everything, flashed SuperSU and Xposed and Viper4Android.. It was working fine until I enabled some Xposed modules and rebooted. It gets stuck on the NVIDIA logo and nothing happens. I got it to boot once after flashing Xposed, but the app said that Xposed was installed but not enabled ("see the logs," which made no sense to me). It said there was an update to the app, so I updated it, then downloaded the zip once again and flashed it, and got the NVIDIA logo stuck again. This is horsh!t. Why is it suddenly not working? I'm using the latest, xposed-v85-sdk23-arm zip.
Bump? Been a day and no response??
GuyInDogSuit said:
Bump? Been a day and no response??
Click to expand...
Click to collapse
Maybe nobody knows HERE?
Xposed is working here with NVIDIA-Update 1.2 (6.0.1) without problems. Did the modules you installed work before the update? A bootloop is a common problem with Xposed.
I doubt that this is ROM problem but an Xposed problem. I would try to find help in the Xposed section. Maybe you should try to find the logs...
edisso10018 said:
Maybe nobody knows HERE?
Xposed is working here with NVIDIA-Update 1.2 (6.0.1) without problems. Did the modules you installed work before the update? A bootloop is a common problem with Xposed.
I doubt that this is ROM problem but an Xposed problem. I would try to find help in the Xposed section. Maybe you should try to find the logs...
Click to expand...
Click to collapse
No, it's a ROM problem. They worked fine before.
I'm also using the 6.0.1 update and the latest xposed with no problems. I'd say it's one of your modules not being compatible, not a ROM problem at all, except that the module doesn't seem to be updated to work on mm.
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
I'm also using the 6.0.1 update and the latest xposed with no problems. I'd say it's one of your modules not being compatible, not a ROM problem at all, except that the module doesn't seem to be updated to work on mm.
Click to expand...
Click to collapse
I use the same modules on my phone running 6.0.1, with no issues. It's not a module.
did you flash arm version or arm-64 version? cuz arm-64 and intel wont work and there is a systemless xposed try using that if all else fails. I can use xposed myself on 6.0.1 myself btw.
m666p said:
did you flash arm version or arm-64 version? cuz arm-64 and intel wont work and there is a systemless xposed try using that if all else fails. I can use xposed myself on 6.0.1 myself btw.
Click to expand...
Click to collapse
As I stated in the op, it's the xposed-v85-sdk23-arm zip.
Tried reflashing the ROM, the USA LTE version this time, and I'm STILL getting stuck at the boot screen, after enabling modules. I got it to boot with JUST Xposed, no modules.
GuyInDogSuit said:
Tried reflashing the ROM, the USA LTE version this time, and I'm STILL getting stuck at the boot screen, after enabling modules. I got it to boot with JUST Xposed, no modules.
Click to expand...
Click to collapse
As stated before, a module your using isn't updated to work with our implementation of 6.0.1. now reinstall modules one at a time until you figure out which one is causing problems and then ask in the xposed section for that module. Glad you finally figured it out tho
Sent from my SHIELD Tablet K1 using Tapatalk
Exile1975 said:
As stated before, a module your using isn't updated to work with our implementation of 6.0.1. now reinstall modules one at a time until you figure out which one is causing problems and then ask in the xposed section for that module. Glad you finally figured it out tho
Click to expand...
Click to collapse
Well, it was BootManager, but it's working fine on my phone with 6.0.1.
Nope, wasn't BootManager, either. Just not working, at all.

Unofficial Xposed

Dunno where else to put this but so far none of the unofficial xposed solutions support the pixel phones because no one seems to want to work with the A/B file layout so if anyone here wants to pick up a project id greatly appreciate that one and i know ive seen a number of others asking for it in different magisk and unofficial xposed threads. Thanks for reading my post and potentially contributing to a fairly noble cause.
Unknown if this is a pixel success. Anyone who knows please do reply.
https://www.xda-developers.com/official-xposed-framework-android-nougat/
alladinscastle said:
Unknown if this is a pixel success. Anyone who knows please do reply.
https://www.xda-developers.com/official-xposed-framework-android-nougat/
Click to expand...
Click to collapse
Doesn't support A/B partition layout yet. No version of xposed except magisk systemless will even flash and even then the magisk systemless xposed also doesn't seem to work right for pixel phones yet
KittyRgnarok said:
Doesn't support A/B partition layout yet. No version of xposed except magisk systemless will even flash and even then the magisk systemless xposed also doesn't seem to work right for pixel phones yet
Click to expand...
Click to collapse
The couple of xposed modules I tried seemed OK (Greenify, youtube adaway...). I just didnt like it because it seemed to break Facebook and Facebook Messenger Apps (caused constant crashes for some reason) and also broke SafetyNet too, which defeats the purpose of even using Magisk. But overall you're most likely correct the modules still need to be updated for Nougat.
Damn...and I was so thrilled when the Nougat version came out.
Guess I stick with rooted Oreo was thinking about reinstall nougat cause of framework but sounds like it's not that great for pixel
cgrimm9 said:
Guess I stick with rooted Oreo was thinking about reinstall nougat cause of framework but sounds like it's not that great for pixel
Click to expand...
Click to collapse
Yeah xposed was my main reason for rolling back but for me none of the modules were being read as properly activated. Its fine though because I have my custom ROM back since there aren't any for Oreo yet.
A thread at pixel xl is saying yes and no with various install methods
UPDATE: added pie controls from xposed to my pixel running RR ; )
Resolved: Systemless Xposed (SDK25) module in magisk now flashes and sticks without fail. Installing the modded Xposed provided in the module description allows the framework/app/modules to interface properly. With both the Systemless framework and the modded app all modules updated as of this month will work
If you haven't already replaced SuperSU with Magisk, do that.
ItWasAllIntended said:
If you haven't already replaced SuperSU with Magisk, do that.
Click to expand...
Click to collapse
Well, choice is good, choice is what it should be, glad I have a choice to use what I want.
SR5-SuperSU-v2.82-SR5-20171001224502
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Well, choice is good, choice is what it should be, glad I have a choice to use what I want.
SR5-SuperSU-v2.82-SR5-20171001224502
Click to expand...
Click to collapse
I highly recommend switching to magisk at least until we get a proper non magisk Xposed and this is coming from someone who has used SuperSU their whole life
KittyRgnarok said:
Resolved: Systemless Xposed (SDK25) module in magisk now flashes and sticks without fail. Installing the modded Xposed provided in the module description allows the framework/app/modules to interface properly. With both the Systemless framework and the modded app all modules updated as of this month will work
Click to expand...
Click to collapse
Works on Oreo?
xneuromancer said:
Works on Oreo?
Click to expand...
Click to collapse
No nougat only, Xposed is not supported on Android Oreo at all yet

What version of Magisk works with the Honor 8?

Hey Guys, can someone tell me what Magisk version works and does not result in a bootloop or has other negative effects? The last time I used Magisk I had problems with 15.x, are all issues are now fixed or are there still some remaining?
Lukke2804 said:
Hey Guys, can someone tell me what Magisk version works and does not result in a bootloop or has other negative effects? The last time I used Magisk I had problems with 15.x, are all issues are now fixed or are there still some remaining?
Click to expand...
Click to collapse
I am using v15. 3 without any problems..
Magisk hide is having some problem with fingerprint recognition.. Some times when magisk hide is on finger print wont work. Its a problem with all the magisk versions i tried . So i turned it off.
Latest version works for me, although it doesn't pass the Safety net checks. Therefore some finance programs may not work, but root and modules work fine.

Does anyone meet the random restart problem?

I am on Oxygen OS 9.5.8.GM21AA. Recently I met the random restart problem. And it become more and more frequent. I have Magisk and EdXposed installed, but I have not update or install new modules recently.
The problem most time happened when I swipe from bottom screen to switch apps. And the whole phone become black. And several seconds later. It will automatically restart. The phone is showing "The phone is restarting" message.
I was tried to disable EdXposed modules one by one, but still not found any incompatible.
einverne said:
I am on Oxygen OS 9.5.8.GM21AA. Recently I met the random restart problem. And it become more and more frequent. I have Magisk and EdXposed installed, but I have not update or install new modules recently.
The problem most time happened when I swipe from bottom screen to switch apps. And the whole phone become black. And several seconds later. It will automatically restart. The phone is showing "The phone is restarting" message.
I was tried to disable EdXposed modules one by one, but still not found any incompatible.
Click to expand...
Click to collapse
Are you using a custom kernel? Updating to 9.5.9 might also help.
harpin14789 said:
Are you using a custom kernel? Updating to 9.5.9 might also help.
Click to expand...
Click to collapse
I am using ElementalX kernel. And i just update this kernel to 1.11, let's me check any problem than.
einverne said:
I am using ElementalX kernel. And i just update this kernel to 1.11, let's me check any problem than.
Click to expand...
Click to collapse
I also have the same issue as you.
This issue is a kernel related issue, oneplus is aware and will push an update in the near future.
As far I know, Fraken kernel is the only that seems to have fixed this issue, so I suggest you flash that, atleast till, OP pushes an update to fix this issue. I have tried all the kernel 7pro and have the issue with every single one. But hvae not the issue in over a week with fraken.
Good Luck!:good:

Question Solved - C.44 update won't install after magisk boot

Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Edit: Thanks for all the responses..using canary magisk instead has worked.
chinbags said:
Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Click to expand...
Click to collapse
You have to fastboot flash the stock untouched boot.img back. Magisk patched the boot partition to root. Therefore the partition is modified. Ota fails. Try uninstall Magisk and see if it restores stock boot image. Or get full build run payload him through payload extractor and nab boot.img there.
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
Wrong magisk was used. You must use canary magisk.
MrSteelX said:
Wrong magisk was used. You must use canary magisk.
Click to expand...
Click to collapse
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working
in order for magisk to work on A12 and booting to an inactive slot it has to be the alpha build ill post it but its also in the root guide for oos on 12 the table shows the only one that works on 12 is this build, same thing happened to me
chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
no need for any of that
mattie_49 said:
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working
Click to expand...
Click to collapse
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.
MrSteelX said:
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.
Click to expand...
Click to collapse
Everyone does want bleeding edge.
Thanks for all the info guys, sounds like a bit more reading needed on my end but all of the above should steer me in the right direction.
I was able to jump from rooted 11.10.10 to c44 using canary magisk.
Downloaded the 4gb c44 from oxygen updater, then local udpate and DONT reboot then install magisk in inactive slot.
Ok, this has worked, original posted uodated, thanks everyone.
One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?
chinbags said:
One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?
Click to expand...
Click to collapse
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12
jruizdesign said:
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12
Click to expand...
Click to collapse
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone
chinbags said:
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone
Click to expand...
Click to collapse
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you
jruizdesign said:
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you
Click to expand...
Click to collapse
No dice, v23 will install and the option is available in settings, I just still can't find where I add an app to the hidden list. Bank apps not loading.
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
Have you tried using USNF? https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
I'm also having troubles updating to c44 with magisk v23, but don't wanna lose the magisk hide option. While looking for alternatives, I came across this the USNF solution in here :
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Didn't try it myself yet...
I can confirm USNF works for me, and I have some very strict apps detecting root access, DenyList hides the root from the apps, but it doesn't try to fix safetynet, with USNF I have no more problems even in apps that didn't work with DenyList only (remember to turn on Zygisk and Enforced DenyList).
If you are using permissive mode on SELinux you will also need SELinux switch to get back to enforcing mode for some apps, but that is an edge case
EDIT: It seems if you are on custom ROM MagiskHidePropsConf might help, not sure if USNF is enough but I can't test it

Categories

Resources