yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] baz1:
Instructions says you have to do reset only after installing magisk for the first time. So If you flash magisk-patched update image you will not have to do factory reset.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] mcn1970:
for those installing viper magisk module and not seeing the viper app in app drawer, install viper apk from xda apps repository after flashing the magisk module. it works just fine.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Groger:
the magisk module doesnt install the driver for me , the apk apperars in the drawer.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] mcn1970:
quite the opposite for me. driver installed but no app in drawer. s10 plus and Nova
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] harjm:
Hi, did as you said and the next attempt to install the patched file via ODIN worked. Thanks

---------- Post added at 09:30 AM ---------- Previous post was at 09:24 AM ----------

Hello all again!

I am installing my applications after rooting but having problems with Titanium Backup. Every other app requiring roots seems to install fine but once installed, the warning "Titanium Backup keeps stopping".

When I look in Magisk, the application has not been granted root.

Can anyone assist?

Regards
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] rp4k:
are you guys using official odin 3.13.1
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] vibrantliker:
So if I'm going to install multiple modules in Magisk that require reboots after each, I need to power off each time and reboot this way:(Power + Bixby + Volume Up) → (Bootloader warning) → (Release all buttons) → (System with Magisk)?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] jimbo77:
Nope. You can actually install all modules and reboot only once you're done installing magisk modules. All will be active after you reboot, also if you reboot from Magisk (reboot button after module installation) it will boot fine.

Other thing you can do is download quick reboot from PlayStore and use the reboot to recovery option.that way you'll boot to system with Magisk easily
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] vibrantliker:
Interesting and good to know.

Just to confirm 100%, rebooting from magisk will reboot to system with magisk(root) -and- finding a 3rd party power menu app and booting to recovery will reboot to system the same (with magisk)?

That would make like a lot easier!!!
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] jimbo77:
Yes sir. Actually there's another option look for Smali Patcher magisk module. You can create a module that will change the behavior of the restart button from the power menu to always boot to recovery (rooted magisk system)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] vibrantliker:
Awesome, thanks again! Going to give this a whirl now.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ianmacd:
There's yet another option: the FireFDS Xposed module, which works very nicely with EdXposed on an S10 with encryption disabled. This will give you a custom power menu with the option to boot to recovery.

---------- Post added at 17:32 ---------- Previous post was at 17:28 ----------

John's rooting procedure for the S10 range neither disables encryption nor requires that it be disabled. The issue of encryption doesn't come into play until the user also wants to run TWRP.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] jimbo77:
You're right I thought I was replying to the TWRP thread :(
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] vibrantliker:
So the 3 button combo wouldn't do anything when I was at the end in stock recovery and I ended up like this (attached).

Can anyone help out?

edit: I got it to boot but checking if I may have to do over
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] rp4k:
Where is that ?

You could try to plug the device into the computer and if adb devices recognize the Device you could do

Adb reboot recovery then hold volume up
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] sperelli:
i was asking about the simple reboot (not to bootloader or recovery). i read it needs a combo to be performed, correct?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
If Magisk is installed in recovery, then to reboot Android and have Magisk active you go through the motions of booting to recovery -- to run the code in which Magisk has been embedded -- but you need to release the buttons at the right time, so that when Magisk "becomes aware" and checks the button status, it will conclude that you are no longer holding down the buttons, and so it will choose to boot the Android system. (If Magisk decides that you are still holding down the buttons, Magisk will turn control over to the "recovery".)

Having said all that, I will now tell you that after installing Magisk in the recovery of my SM-T290, and after booting many times until I hit that magic spot where I got the tablet to try to boot recovery, but I got Magisk to realize that I didn't really want recovery, so I got Android running with Magisk active -- since that time, I can shut down my tablet, and then reboot by holding the power button, and when Android boots, Magisk is active.

I don't know if something special was done to Magisk between the time the installation instructions were written and the time I downloaded a copy of Magisk.apk. I don't know if different devices behave differently. As I said, I think I've seen people report being able to boot Android with Magisk active without the tricky key-combo-and-release dance. I tried to describe what I remember. I tried to describe where I probably read it.

TL;DR The tricky key combo always works. The tricky key combo may not be necessary.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] TricksDJ:
Hi Guys, I have S10 plus rooted via Odin3 for at least 3 years, everything was alright, safety net check, Magisk hide, etc.

But unfortunately I ended up clicking up on the APP update button(only) and got the 25.2 version installed, the app worked well after that but then I realised that Magisk hide was gone on that version.

After that, I pressed uninstall and then installed the version 23 with the same apk I had from the original root and now I can't make it work, even turning phone off, plugging the cable at my laptop and using holding bixby, vol down and power button as I used to do before.

Did I **** the root somehow?

Do I have to do all root process again?

Am. I going to lose data?

If a good soul can help me this would be much appreciated as I don't have much knowledge at this...

Thank you 😊
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
Yes, you screwed up something.

You do not say what version of Magisk you had when everything was fine.

You need to explain in detail how you tried to fix it: Did you still have the magisk-patched-AP.tar from 3 years ago? Is that what you flashed? Have there been any system updates during the 3 years?

If, by uninstalling, you mean you uninstalled the Magisk Manager app and reinstalled the 3y old manager apk, you did not uninstall the Magisk embedded in your [boot, recovery, I don't know which]. I expect a new Magisk to be unhappy with an old manager.

Please confirm that the updated Magisk was working fine before you tried to revert the update. Then explain exactly what you did to revert.

Maybe hold off on trying the next six random things that pop into your head until someone has a chance to advise you.

I think it would be safe to see if adb can recognize your device, and if adb shell gives you the ability to list ("ls") any files.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] TricksDJ:
Sorry, I forgot to give more details...

I had Magisk 23 and everything was fine, then I hit the update button at the APP section only and installed the version 25.2, after the update the root was still working with the root at version 23 and app at 25.2, but as I mentioned, I realised the version 25.2 doesn't have magisk hide and decided to install 23 again😅.

Then I went to the app and pressed uninstall/restore image and then complete uninstall. After that I went to the 23 version apk and installed it again but now the root is gone.

I still got the "AP_G975FXXSBFUF3_CL21644994_QB41014117_REV01_user_low_ship_meta_OS11.tar.md5"

In my ad card and all files I have used to root it 3y ago and I have never updated the phone.

Thanks mate.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
Now you say "the root is gone". Does that mean Android boots fine but you no longer have Magisk installed?

That makes sense, you hit "uninstall / restore images".

I don't know if you are going to lose your data. Back up what you can, or what you care about.

If you really have all the files from 3y ago -- AP, BL, CP, CSC, magisk-patched.tar -- the easiest thing to try is run Odin, giving it magisk-patched.tar, BL, CP, and one of the CSCs. Please READ SOMEWHERE ELSE to figure out which CSC will NOT wipe your data -- I don't trust my memory.

With luck, that will put you back where you were.

A lot of things can go wrong. Some versions of Magisk downloaded the latest as part of the "more setup", you have to set the update channel in the manager, and for a "custom" version -- meaning not the current version -- you need a URL to a JSON file that then points to the right archived files. I think more recent versions of Magisk are self-contained, but I don't remember the version number.

Maybe disable your internet connection before booting to download mode to run Odin.

Maybe wait to hear from someone who has done this more recently than I have.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] TricksDJ:
@J.Michael sorry for the late reply, I got very sick and had to leave this behind.

Anyway, thank for you time sown and help🙏🏻

I haven't tryed yet, I think will do this weekend.

The CSC I remember is the "HOME" version to not wipe the data and keep the phone as it is.

My only questions, that can be a bit stupid is:

Should I install install the magisk apk I had at that time again(3y ago version) , and then patch the firmware(3y ago version) again to get the magisk-patched.tar from phone the way it is now? Does it make any difference erence?

Or by using the same magisk-patched.tar I had 3y ago, and Home CSC my phone will keep the way it is now?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
If you are sure you have not updated since you successfully installed Magisk 3y ago, you can use the magisk-patched.tar you made and used 3y ago.

I do not know the rules for using HOME_CSC to avoid wiping data. The installation instructions for Magisk specify reformatting /data between flashing Magisk and the first boot. You might be able to skip that if your /data is already unencrypted. I don't know.

Maybe you should try to find posts from people with your device who have tried to install more recent versions of Magisk. It is possible that the rules have changed.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] TricksDJ:
100% success

I ran Odin with all my files from 3y ago and used HOME_CSC and everything went well.

Magisk 23 running again on my S10plus with Android 11.

Thank you @J.Michael again🙏🏻
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
Is is possible to always boot with Magisk loaded ?

I have rooted my S10+ (Android 12 OneUi 4.1) using Magisk

Now i have to use the Recovery buttons <Bixby> <VolumeUp> <Power> each time i restart the phone

Is it possible to always enable Magisk ?

Will for instance flashing TWRP into recovery help ?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
I do not believe flashing TWRP into recovery will help.

Do you understand that you have installed Magisk in recovery? If you just flash TWRP, that will replace recovery, you will no longer have Magisk.

Read more posts. Some people have installed Magisk in boot on some Samsung devices, in spite of Magisk manager app reporting "Ramdisk: No". If you are able to install Magisk in boot, then you will no longer need to use so many buttons to boot to a system with Magisk running.

I do not know whether it is important to restore the original, unpatched, recovery before replacing boot with a Magisk-patched boot.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
I know it is installed in recovery, i thought that maybe a init script could be modified in a way that if the device is booted without magisk ik could reboot into recovery.

I will do some reading, i haven't found posts yet on flashing boot with no ramdisk

and i am afraid that flashing boot wil brick my device ....
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
Good instinct, something can always go wrong, but you can probably count on being able to flash the stock ROM and start over.

@twiice reported, in this thread, *not* checking "Recovery mode" when patching. I'm not sure he installed Magisk in the boot image, just that he was pleased with the result.

If you follow John Wu's advice and always provide Odin with 4 tar files, you will at least avoid problems like having Magisk still in recovery while trying to put it in boot -- at least you will keep resetting partitions to a consistent state.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
Thanks !

I've tried this method, but unfortunately when i boot i have no magisk

and also can not install when i install the magisk manager manually....

I've reverted to the recovery method, so hopefully there will be a fix so the recovery is automatically loaded...
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] lupin57:
Hi,

To boot always rooted without any combo, just flash a kernel like Cruel or similar (Magisk included in it) !

I'm using it since 2020 on my S10+ (...)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
Thanks i flashed the Ambasadii Cruel kernel, now it works without key combo

Guide TWRP and Ambasadii Cruel Kernel
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] mrbonine:
Hi: Has anyone else had this problem? I attempt to flash dm-verity first 1.0 as listed then the latest (6.1). TWRP returns :

Updater process ended with ERROR: 1

Error installing zip file: [name]

The first time I had Zip signature verification on:

Zip signature verfication failed.

When I turned off verification I got the error listed at top: ERROR 1

Ideas?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
I've had several boot loops on my Samsung S10+ phone and everytime the only thing to recover was to factory reset and flash flashed full stock firmware (BL, AP, CP, CSC) with AP=Magisk_Patched-26100_Recovery.tar

Does anyone have an idea to get out of an bootloop without factory reset (from TWRP for instance ) ?

I've tried to get in Safe mode with key combo, but didn't work

I've tried disabling Magisk by:

touch /cache/disable-magissk
and
touch /cache/.disable-magisk

I've tried deleting modules from /data/adb/modules

/cache/magisk.log

three times the following:

umount2 /system/bin/bu failed with 22: Invalid argument
umount2 /system/bin/appwidget failed with 22: Invalid argument
** zygote restarted
zygisk64: replaced com/android/internal/os/Zygote#nativeForkAndSpecialize
zygisk64: replaced com/android/internal/os/Zygote#nativeForkSystemServer
zygisk32: replaced com/android/internal/os/Zygote#nativeForkAndSpecialize
zygisk32: replaced com/android/internal/os/Zygote#nativeForkSystemServer

Phone Samsung S10+ SM-G975F ( NO RAMDISK / Android 12 / OneUI 4.1 / G975FXXSGHWC1 )

I've installed:

flashed full stock firmware G975FXXSGHWC1 (BL, AP, CP, CSC) with AP=Magisk_Patched-26100_Recovery.tar

(G975FXXSGHWC1 => OS patch level: 01 march 2023)

Magisk 26.1 ( Zygisk=Yes / Denylist=No / Ramdisk = No )

Ambasadii_Cruel-HVJ5-G97xF-v6.9-S Kernel ( OS patch level 01-03-2023 )

TWRP v3.7.9_9.2 in recovery

TWRP_Bootlogo_patcher_v1.7

safetynet-fix-v2.4.0-MOD_1.2

Shamiko-v0.7.1-166-release

LSPosed-v1.8.6-6712-zygisk-release

KnoxPatch-v0.5.2.apk

KnoxPatch-Enhancer-v0.3-fix.zip

BluetoothLibraryPatcher_magisk_2.6.3
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
How long can you run before the boot loop starts? Any idea whether something you do triggers the boot loop?

Have you tried flashing unpatched ROM, to make sure it doesn't boot loop?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
It does not start, just a Bootlogo / Samsung image and then loop after a while

First time the multidisabler-samsung-3.5-corsicanu.zip gave me bootloops when installing LSposed / Knoxpatch

Last time removing an magisk module triggered the boot loop

Flashing an unpatched ROM works, but loses root (and data)
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] dcaondyer:
Me too.

Using S10 (beyond1lte) I've already had boot loops for about four times: the last one with your same firmware version, but for S10 (G973FXXSGHWC1) and a similar Magisk modules configuration.

Magisk 26.1 ( Zygisk=Yes / Denylist=No / Ramdisk = No )

Ambasadii_Cruel-HVJ5-G97xF-v6.9-S Kernel ( OS patch level 01-03-2023 )

TWRP v3.7.9_9.2 in recovery

TWRP_Bootlogo_patcher_v1.7

safetynet-fix-v2.4.0

Shamiko-v0.7.1-166-release

LSPosed-v1.8.6-6712-zygisk-release

BluetoothLibraryPatcher_magisk_2.6.3

MagiskHidePropsConf-v6.1.2.zip

storage-isolation-zygisk-v28.1.0-release.zip

Maybe boot loops were triggered by unplugging and reinsert power cable during phone startup at about 2% charging level: this is the only thing that I've done before the problem appeared.

Precedent times boot loops appeared also with different modules configuration, for example with acc or Naptime doze module and without storage-isolation and Shamiko, or also without Ambasadii kernel (stock kernel and recovery patched by Magisk). What would appear to have done the problem the previous times seems to be rebooting into recovery with releasing the buttons to start Magisk or updating a Magisk module or charging phone when it was off and then rebboting to recovery using adb.

It never happened to me with the Cruel kernel and I think it's a problem of the stock rom or the Magisk integration with it. There must be something that modifies some file in the /data partition, since to restart the phone it is sufficient to delete all the contents of /data (even leaving out /data/media/0).

Reading kernel logs is difficult to trace back the cause, because starting device physically or from recovery causes different boot fails.

Thanks for everyone will help me.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] dcaondyer:
However I've tried to disable Magisk, to disable modules, uninstall LSPosed and finally to unistall Magisk from TWRP recovery. I've also tried to flash multidisabler and to reboot in safe mode and then to redo the procedure for updating with the custom kernel (flashing Magisk, Ambasadii kernel, multidisabler and TWRP Bootlogo given on this site). I've tried to flash original boot and recovery patched by Magisk. Nothing of these seam to work. When the problem appeared with a stock kernel (and recovery patched) I had also tried to boot without keycombo in normal OS (without Magisk), but system didn't started.

Also I forgot to mention that my phone originally was OMN branded, but since I rooted it for the first time I only use ITV roms to avoid Vodafone bloatware.

Maybe this is releated to this other problem https://xdaforums.com/t/tutorial-ro...e-ui-4-1-stock-firmware.4394629/post-88652007
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
Did you for any chance tried to hide Magisk using an third party app ?

I am not sure, but i suspect this could cause the bootloop together with the multidisabler
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] ReMiOS:
# cat /sys/firmware/devicetree/base/firmware/android/fstab/system/status

disabled
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] dcaondyer:
To solve the problem I've noticed is sufficient to delete /data/system.

I attach the list of files contained in /data/system directory: maybe someone could guess what is the cursed file.

I think the problem arose with some wrong configuration in this directory (/data/system) that will cause Magisk to stop the zygote precess.

These two lines:

08-26 16:19:12.953 5220 5222 E : umount2 /system/bin/appwidget failed with 22: Invalid argument

08-26 16:19:12.959 5220 5222 E : umount2 /system/bin/bu failed with 22: Invalid argument

are always the latest one of every crash log.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] dcaondyer:
If is not possible to obtain a better workaround, I hope there will be a way to avoid /data/data deletion. Maybe some /data/system files to keep before reboot
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] bruram:
I have an S10e (SM-G970F) with android 13 last firmware HWC1 security patch 1March23, and root with magisk 26.1, Twrp 3.7.0_9.2 from Corsicanu.

Magisk Modules SafetyNetFix, MagiskHidePropsConfig in order to use Google Pay (Wallet).

All perfect until 3 days ago when Wallet (GPay) suddenly refused to make payments caused by existing root.

the actual Wallet is 2.203.562839265

All tentatives I made to have Wallet once again running was without effect.

Somebody noted the same problem?

Has Google changed something?
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] luy0:
Hi. I just got a G973F, really really good, 0 scratches nor cracks, it came with hydrogel screen protector and everything works and all the original tests has passed, only con the battery that drains a bit quicker. Just 1 week of delightful use and coming from a S5 but after that Champ a ****ty a03, this is mind boggling. Im totally satisfied with it. Im in Root/Jailbreak stuff since 2010, i mean i know what its, but this S10 is so awe that i doubt if it worths rooting. I rejected Snapdragon versions just to have the F rootable most supported version, but even the bloatware is not bothering me. By now i could only think of it to have TWRP, Viper4Android and Game Guardian. Even the amazing Xposed Edge is covered by the native gestures. Well sorry for the TL, but to you to be able to evaluate better and help me to choose, a bit of background was needed. Info: locked boot, stock unbranded open ARO ROM, Andy 12, XXSGHWA1 and it was/is very expensive, the most expensive mobile i paid for until now, to have an idea, i care for it as if it were an unanimated carbon rod lol and bought a case just 3 days after getting it. Thanks
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] evl01:
I've tried all methods to root my S10+ G975F but nothing seems to work for me. when the device boots, have no root acces at all. What am i doing wrong? i have twrp installed.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] J.Michael:
Try to describe "all methods".

If one method you tried involved installing Magisk in your recovery, you need a special button sequence to boot to a system with Magisk active.
[Samsung Galaxy S10 ROMs, Kernels, Recoveries, & Ot] Abdullah_Niloy:
Hi, could you please tell me how can I install Magisk with TWRP or Without TWRP?

I tried with ODIN by Magisk patched AP it did not work for me then somehow It was installed but I don't think it is going well cause it crashes sometimes and whenever remove any module the Magisk app crashes right after removing any module.

Even when I installed lsposed it showed that the magisk is installed partially.

What can I do in this situation?

I don't think Magisk was flashed properly.

Please help me with some guidance.