[Help] OPPO Reno8 Pro+ bootloop after installing Zygisk Next via DFRoot / KernelSU Next (locked bootloader, data recovery needed)

[whyneedai]

Device information

• Device: OPPO Reno8 Pro+ 5G (PFZM10)
• SoC: MediaTek Dimensity 8100-Max
• OS: ColorOS 15 / Android 15
• Kernel: 5.10.246-android12
• Bootloader: Locked
• Root method: DFRoot (temporary root)
• KernelSU: KernelSU Next, build 33355
• Module installed: Zygisk Next v1.5.2 (release 864)

What happened

My device was working normally before this issue.

1. I successfully obtained temporary root access using DFRoot.

2. I installed Zygisk Next v1.5.2 using KernelSU Next with the following command:

   ksud module install <Zygisk-Next-module.zip>

   The ksud executable was located at /data/adb/ksu/bin/ksud.

3. The installation command completed successfully.

4. I rebooted the device.

5. After rebooting, the phone became stuck in a bootloop.

Important: I did not intentionally enable DFRoot's "Start on Boot" feature.

Current symptoms

The device repeatedly goes through this sequence:

1. OPPO logo appears.
2. ColorOS boot animation appears.
3. Screen turns black.
4. Device automatically restarts.
5. The cycle repeats.

Additional information:

• I can enter the stock ColorOS Recovery.
• Recovery only provides options such as reboot, power off, and format data.
• ADB does not provide a stable connection during the bootloop.
• I have attempted to trigger safe mode using the volume buttons, without success.
• I have not performed a factory reset.
• I have not unlocked the bootloader.
• I have not intentionally modified or flashed the boot partition.

What I need help with

My highest priority is recovering the device without losing any existing user data.

I would greatly appreciate help understanding the following:

1. Since DFRoot provides temporary root and I did not enable "Start on Boot", should KernelSU and its modules become inactive after a full reboot?

2. Could installing Zygisk Next through KernelSU Next's late-load mode introduce persistent changes that cause a bootloop even after temporary root is gone?

3. Does DFRoot modify anything persistent that could affect the next boot on this device?

4. Are there known compatibility issues involving DFRoot, KernelSU Next, Zygisk Next, MediaTek 5.10 kernels, or ColorOS 15?

5. Is there any non-destructive recovery method that could disable the problematic module or repair the system without unlocking the bootloader or wiping userdata?

6. Are there any useful diagnostic logs or USB interfaces I could access while the device is bootlooping or in stock Recovery?

Data preservation requirement

The device contains important personal data that has not been backed up.

I want to avoid:

• Factory resetting the device
• Wiping userdata or metadata
• Unlocking the bootloader if it triggers a data wipe
• Flashing unverified firmware
• Any operation that could destroy the existing encryption keys

I understand that recovery may not be possible, but I would like to investigate all reasonable non-destructive options before considering a factory reset.

Any advice on identifying the root cause or finding a safe recovery path would be greatly appreciated.

Thank you for developing DFRoot and for any guidance you can provide.