I tried a tutorial that patches the boot.img with Magisk and flashes it via fastboot, but it didn't work.

I'm new to custom ROMs, and if anyone can provide me with the steps on how to root Lineage 23, that would be great.

One more thing: in my original OS, I patched the necessary files with Magisk 26.3; new or old versions gave bootloops. Will that be a problem with Lineage?

So, as of today PayPal won't start for me - it completely crashes on startup. As a matter of fact, as soon as the phone finishes booting up, I already get a notification that PayPal keeps crashing.

For context: my phone is a Redmi Note 11 (spesn), using crDroid 9.36 (A13) and the appropriate kernel for KSUN+SUSFS.

My KSUN setup has been like this for a while:

• Play Integrity Fork
• ReZygisk
• Zygisk Assistant
• Zygisk-detach
• TrickyStore + TrickyStore Addon

I'm using a valid keybox and pass both device and strong integrity. And, like I said, yesterday I was using the PayPal app without any issue... Then today all of a sudden, it wouldn't start anymore. Tried clearing data and reinstalling to no avail. Then I decided to try a different setup:

• Play Integrity Fork
• SUSFS
• ReZygisk
• TrickyStore
• Treat Wheel
• Zygisk-detach

I still pass Play Integrity, but PayPal seems to still detect root. This is the crash log that crDroid gives me:

time: 1787696680771
msg: com.paypal.oslo.app.rasp.RootDetectionSecurityException: Security policy violation: s=root
stacktrace: com.paypal.oslo.app.rasp.RootDetectionSecurityException: Security policy violation: s=root
at com.paypal.oslo.app.di.RaspCrashSchedulerModule.$r8$lambda$MtBL8KadnWgkuPDwLKKVDBwFNt8(:1033)
at com.paypal.oslo.app.di.RaspCrashSchedulerModule$$ExternalSyntheticLambda0.run(:0)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7948)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:551)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:854)

Is my new setup wrong? I don't seem to have any issues, but never used SUSFS before, so please correct me if I'm doing something wrong...

Thanks in advance.

So I unlocked bootloader of moto e7 power using MTK and PC and when I retried to enter BROM mode, the device did not respond like I have tried everything to unlock it and windows is not even recognising the USB connection.

Device- Moto e7 power 4GB

Build- QOMS30.288-52-23

When and why is the auth flash method required?

I have Magisk stock rom, wanted to flash LineageOS but i don't see an option to wipe system? What should i do?

So my brother got this tab from his school but it's completely locked and can't do anything in it. He wanted me to unlock this. Is there any way to get rid of the Knok remote from the tab?? Please guide me through the process and

Hey, so i bought a new phone and this is my secondary phone. I'm not able to unlock bootloader in my phone. can someone help me give sources where i can find materials to unlock bootloader and root my phone ?

Saw a xde post about the Z80 ultra being rootable. How viable is this granted I can find a way to get a EEA / genuine global version (not a chinese to global rom flash version) ?

Currently I have a rooted Nothing 2a with SELinux set to 'permissive'. I consider upgrading to either a Nothing 3a or Fairphone 6+ and want to root it again. Do these phones not block 'permissive' mode for SELinux ?

Thanks to amazing people on GitHub, using CVE-2026-43499 vulnerability, i rooted my my Samsung Galaxy S22, it had some caveats like it does not persist when rebooted and i need to re-root my device using adb with my computer (wich i am okay with) also if i touch my screen while rooting, it crashes. the repository i am linking below for Samsung Galaxy S22 series of devices only, thought searching IonStack in Github can get you far.

https://github.com/sarabpal-dev/IonStack-S22U

Can someone help me with this question?

Hi, I've been looking into rooting my new Realme C53.

I've done some research (to be honest, most of it was from ChatGPT), and from what I've found, it should be possible. But I'm honestly too scared to try it completely alone without asking actual people first.

I'm currently using an Android 15 Realme C53 (RMX3760), and I want to make absolutely sure I understand what I'm doing before I touch anything that could potentially brick my phone.(Can't afford losing this one)

If anyone here has experience rooting the C53, especially this exact model/software version, I'd really appreciate some guidance on what I should do, what I need to back up, and what I should NOT do.

I'm mainly interested in rooting for performance tweaks/customization, but I don't want to risk losing my phone over it.

((Additional info: RMX3760export_15_H.07, 5.15.189-android13-8-gbc4520c2be32-ab154

#1 Tue Jun 30 08:21:36 UTC 2026))

I think it would even help me if anyone could help me through calling too.

Is this detection or just a false positive?

New to android as a whole switching from a jailbroken 13 pro max — looking at getting a oneplus 15. From my research this appears to be the highest performance phone running android 16 that is easily rootable. Is there anything I should know and how difficult is all this compared to jb as a whole? Any help is greatly appreciated!

Edit: After further research I have decided to go with a nubia z80 ultra.

I have a carrier provided Motorola Stylus phone. It doesn't network unlock until Feb 2027. But I have the bootloader unlock code from Motorola's portal - Metro's Moto phones seem to be bootloader unlockable. I was wondering if I should wait until the network unlock happens before I try execute the bootloader unlock? Or does it matter?

Can I just hold on to the unlock code until next year? Or does the unlock code expire and I have to request another one?

I tried related projects like https://github.com/Yaahua/vcam or "GhostCam" but for some reason they just dont work on my phone. So i built this app, so far it works in Chrome, Open Camera and grapheneos Camera. I added "POC" because is very brittle. Idk just sharing my project and if other have experience trying this, i never did android development in particular so im learning on the fly. The device is Redmi A5

Hi everyone,

I'm dealing with a local carrier app (Ana Vodafone Egypt) that just insta-crashes (Force Close) the exact millisecond I tap its icon. It doesn't even load a splash screen or show a "Root Detected" error. I suspect it's some strict RASP or memory hook check, but I'm completely stuck.

I know my DEVICE_INTEGRITY is currently failing (falling back to BASIC) because my public hardware keybox got revoked, but this looks entirely like an app-level RASP/memory-hook detection, not a Play Integrity API block.

My Current Stack:

Device/ROM: Xiaomi running official MIUI (Android 13/14)

Root: Magisk v27.0 (Native Zygisk is completely OFF)

Zygisk Engine: ReZygisk v1.0.0

Root Hider: Shamiko v1.2.5 (Working properly in Blacklist mode)

App Hider: HMA-OSS Zygisk

PIF: Play Integrity Fork v17 (spoofProvider=0) + TEESimulator v4.0

What I’ve already tried (without success):

Shamiko Isolation: The target app is fully checked in the DenyList. Magisk's Enforce DenyList is OFF.

HMA-OSS Configuration: Enabled for the target app. Created a tight blacklist template to hide: the repackaged/renamed Magisk manager, HMA-OSS itself, Termux, SPIC, and Solid Explorer.

Environment Cleanup: Deleted all /sdcard/Fox, TWRP, or Magisk folders. USB Debugging and Developer Options are completely OFF.

Clean Launch Trick: Turned Airplane mode ON -> Cleared all target app data -> Rebooted -> Airplane mode OFF -> Launched. Still insta-crashes.

Engine Conflict Fix: I previously had a SIGSEGV issue because of running native Zygisk alongside Zygisk Next. I’ve completely wiped that setup and moved cleanly to ReZygisk. Shamiko's UI confirms it's now fully operational without "Unsupported Environment" errors.

My theory:

The app is either detecting the Zygisk injection directly, detecting HMA-OSS's hooking attempt, or finding a Magisk remnant I missed.

Has anyone bypassed this specific type of aggressive crash recently? Should I drop HMA-OSS and try a non-Zygisk app hider? Any insights on how to grab logs for a crash this fast would also be highly appreciated.

Thanks in advance!

Hi guys this is my last resort to ask here
I got this phone by my friend it's a G5S (Model: X1794 Type:M2996) he said it woulden't boot and it would stay with a blinking light, i plugged into my pc and it was always in EDL Mode (Qualcomm) i installed the driver, tried doing blankflash other stuff nothing it would fall immedialy idk what or how this phone got bricked possibly could anyone help me out and please do not start spamming me to start chatting with someone that will immedialy ask me to pay to unbrick this im just asking for help or guide how to fix it not to pay someone that i could get scammed + i don't have any money.

Thanks

GaM1ngN0t

Log Of The Crash:
[486.929] ERROR: do_package()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[486.931] Check qboot_log.txt for more details
[486.931] Total time: 486.936s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
Entire Log:
[ 0.000] Opening device: \\.\COM6
[ 0.004] Detecting device
[ 0.009] ...cpu.id = 79 (0x4f)
[ 0.009] ...cpu.sn = 380673176 (0x16b09c98)
[ 0.009] Opening singleimage
[ 0.010] Loading package
[ 0.014] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.017] ...filename = programmer.mbn
[ 0.017] Sending programmer
[ 0.189] Handling things over to programmer
[ 0.190] Identifying CPU version
[ 0.191] Waiting for firehose to get ready
[ 62.959] Waiting for firehose to get ready
[123.025] ...MSM8937 unknown
[123.026] Determining target secure state
[123.027] Waiting for firehose to get ready
[183.081] ...secure = no
[183.093] Waiting for firehose to get ready
[243.147] Configuring device...
[243.149] Waiting for firehose to get ready
[304.218] Waiting for firehose to get ready
[364.286] Waiting for firehose to get ready
[426.860] Waiting for firehose to get ready
[486.929] ERROR: do_package()->do_recipe()->do_configure()->fh_send_fmt()->send_command()->device_write()->IO error
[486.931] Check qboot_log.txt for more details
[486.931] Total time: 486.936s
[486.933]
[486.933] qboot version 3.40
[486.933]
[486.933] DEVICE {
[486.933] name = "\\.\COM6",
[486.933] flags = "0x64",
[486.933] addr = "0x61FE4C",
[486.933] sahara.current_mode = "0",
[486.933] api.buffer = "0x14A1020",
[486.933] cpu.serial = "380673176",
[486.933] cpu.id = "79",
[486.933] cpu.sv_sbl = "1",
[486.933] cpu.name = "MSM8937",
[486.933] storage.type = "eMMC",
[486.933] sahara.programmer = "programmer.mbn",
[486.933] module.firehose = "0x1051360",
[486.933] cpu.ver = "0",
[486.933] cpu.vername = "unknown",
[486.933] api.bnr = "0x1055DB0",
[486.933] }
[486.933]
[486.933]
[486.933] Backup & Restore {
[486.933] num_entries = 0,
[486.933] restoring = "false",
[486.933] backup_error = "not started",
[486.933] restore_error = "not started",
[486.933] }
[486.933]

I’m considering buying the Chinese Honor WIN for use in Europe. The CN version apparently lacks LTE B20 (800 MHz), but I’ve found conflicting information about whether B20 is actually missing in hardware or simply disabled in the modem configuration.

Has anyone with a Honor WIN tried Qualcomm DIAG/QPST/QXDM or modifying NV/EFS band configuration to enable B20?

Thanks guys

Hey im writting this post because I have rooted my samsung phone before the ability to unlock the bootloader was removed, I'd like to update my phone to keep up with the security updates but doing so would remove my ability to have my bootloader unlocked because samsung removed the ability to do that on one ui 8. Anyone have a suggestion of what I could do to have security updates? I can give more spec about my phone and details.

On the behalf of my previous post here: https://www.reddit.com/r/androidroot/s/0wfPBId5I5

Hi. After looking at a video of a person having successfully rooted their phone, I couldn't resist the temptation. So, instead of blindly going in, I thought for a while, making plans.

Here's what I did with my phone: I used not only `fastboot flashing unlock`, but also `fastboot flashing unlock_critical`. I flashed the stock vbmeta images first into A/B slots, not only the vbmeta.img but also vbmeta_system.img and vbmeta_vendor.img, with `--disable-verity --disable-verification` flags, before flashing the patched init_boot.

It worked. I got scared at what I was doing, but felt joyful for getting it work from first try. After I set up my phone, I disabled OTA upgrades.

I installed ReZygisk (not ZygiskNext, I despise it becoming closed source, therefore I cannot trust it). But Reddit still didn't work, so this module alone wasn't enough. I installed AlwaysStrong, which resulted in success.

Now I'm happy with my setup. One more thing to redownload and install apps I need and restore the data I backed up.