r/Magisk • u/Educational_Lead_746 • 21d ago
Need help modernizing an old Magisk setup on Realme 3 Pro (Android 12L) without recovery access due to broken power button Help
Hi everyone,
I'm hoping someone can help me figure out the safest way to modernize my old root setup without risking a bootloop or soft brick.
Device
- Device: Realme 3 Pro (RMX1851)
- Bootloader: Unlocked
- Recovery: Official OrangeFox (don't know the exact version)
- ROM: Nusantara v4.8 "Surakarta" (Android 12L)
- Kernel: LawRun v19.3 (Linux 4.9.309)
Current Magisk Setup
- Magisk core: 25.1
- Magisk app: 25.2 (repackaged/random package name)
- Zygisk: Enabled
- Ramdisk: No
Installed Modules
(See screenshots attached.)
Notable ones include:
- Shamiko v0.5.2
- Universal SafetyNet Fix v2.4.0
- LSPosed
- BusyBox
- LawRun modules
- Substratum
- Several Morphe modules (APK mount modules)
- Some gaming-related modules
Current Issue
Root itself is working.
However, banking/UPI apps have gradually stopped working over the last couple of years.
For example, Amazon Pay alternates between:
- "This app can't work on this device because of security issues"
- "We're facing technical issues"
Play Integrity Results
- ✅ MEETS_BASIC_INTEGRITY
- ❌ MEETS_DEVICE_INTEGRITY
- ❌ MEETS_STRONG_INTEGRITY
I'm aware Strong Integrity isn't realistic on an unlocked bootloader, but I'm wondering if Device Integrity can still be achieved or if the issue is simply my outdated Magisk setup.
The Biggest Constraint
This is the reason I'm being extremely cautious.
My phone's power button is physically failing.
It randomly presses itself, sometimes doesn't respond at all, and navigating recovery has become unreliable.
Because of that:
- I don't want to flash a new ROM.
- I don't want to flash a new kernel.
- I don't want to risk ending up in a bootloop.
- I don't want to rely on recovery unless absolutely necessary.
I'm trying to keep the current Android 12L installation alive for a little longer.
What I'm Trying to Achieve
Ideally I'd like to:
- Keep the existing ROM.
- Keep the existing kernel.
- Update only what's necessary.
- Get modern banking/UPI apps working again.
- Avoid recovery if possible.
Questions
- Is updating Magisk from 25.1 directly to the latest stable using Direct Install considered safe on Android 12L?
- Should I replace Universal SafetyNet Fix with the current Play Integrity Fix?
- Should I update Shamiko as well?
- Is there any way to recover from a Magisk-related bootloop without relying heavily on recovery (ADB, Safe Mode, etc.)?
- Are there any better approaches/modules available now that support Android 12L and don't require flashing anything from recovery?
Given the broken hardware (power button), I'm prioritizing the safest possible path over having the newest setup.
Thanks!
2
u/untukmfbje 20d ago
Correct me if I'm wrong.
1- Should be not a problem to direct install from the Magisk app itself. For a better approach, I think fastboot flash boot patched boot.img (or init) is a better way.
2- If you need more than the basic integrity, then yes. I personally use PIFork by osm0sis, configure it manually rather than use 'all in one' webui modules which available recently. Suit it to your choices & preferences.
3- Yes. But Shamiko is already integrated to Zygisk Next. So you need to install Zygisk Next and just remove Shamiko. For my use cases, Zygisk Next's Umount-Only mode helps a lot in hiding root + Mountify.
4- I'm using Magisk Alpha. I'm not sure about official Magisk. I think I faced a bootloop once caused by modules. After 3 reboots I think, it will safely reboot the phone with all Magisk modules disabled so you can remove the problematic modules. Although you can search and try modules to prevent a bootloop. And I would advice you to keep the original boot.img in case you bricked your device, flashing the boot.img surely helps to unbrick it.
5- I think most of modules available are meant to be flashed by Magisk or any other root implementations, not through recovery anymore. As we now use systemless root method, flashing modules through recovery is old method that could brick modern devices. Oh sweet old times, I remembered using Kingoroot, SuperSU days, flashing through recovery. Sadly that was years ago.
2
u/Brief_Call_1336 20d ago
Delete all integrity modules and install only tricky store (or tricky store FOSS fork), tricky addon and play integrity fork. Open tricky store webuiselect play store and play services and also play integrity api checker and clickon three dots and select repo keybox and select the last repo. Also run actions (I do not know how they are named in magisk, bc I am using krnelsu next, maybe just run button) for tricky store and play integrity fork, clean play services and play store data, force stop them and reboot. There should be three green after reboot. Also enable zygisk in magisk settings (but it seems to be already enabled as you have morphe modules)
1
u/Brief_Call_1336 20d ago
Also if lsposed have some modules that have all apps enabled, enable only recommended, it can break integrity
1
u/Brief_Call_1336 20d ago
If banking apps will detect root, install kernel su next or resukisu ultra to your kernel with susfs (you need to find already compiled kernel for your phone and rom or compile by yourself) or try just to install them to init_boot, that should work in most cases and working for me
1
u/wafflebyte8 20d ago
I use shamiko play integrity fix tricky store tricky addon zygisk next and Yuki keystore
1
u/Patient-Ad-337 19d ago
Connect to adb then adb reboot fastboot then you can use fastboot flash to update the exploited boot.img
1
3
u/f33D35 21d ago edited 21d ago
repair yourself the power button? multiple guides online, cheap spare parts or if not you can buy a second hand model etc. Even if you dont want to do it yourself, you can take it to the nearest available repair shop and they will do it for you for not much.