Bootloop on SM-A125F/DSN with BIT 5 Firmware After Root Attempt

Device Information:

Device: Samsung A12 (SM-A125F/DSN) Android version: 12 Magisk version name: 28.0 Magisk version code: 28001

AP Version: A125FXXS5CXE3 CSC Version: A125FOXM5CXE3 BIT (BINARY/U/SW REV.): 5

My device enters bootloop after flash (boot.img) and recovery mode becomes unavailable after updating to BIT/SW/Rev 5.

Below are the relevant details and logs I can provide to help diagnose the problem.

magisk_log_2024-10-19T22.23.49.log

Logs and Files

https://github.com/klaskow/sm-a125f-bit-5

Issue Description:

The most recent firmware that worked properly was A125FXXU2CWC3, which uses BIT 2. However, since upgrading to BIT 5, downgrading to any previous BIT version (e.g. BIT 2) is no longer possible. The bootloader is unlocked, but I am unable to root the device without causing bootloop issues.

Available Logs (Running Stock Firmware without Root):

These logs are from the device running stock firmware A125FXXS5CXE3 (BIT 5), but without root access, so they might not be fully informative:

cat /proc/mounts (proc_mounts)
Boot image for flashing: (boot_A125FXXS5CXE3_BIT_5)
Recovery image from firmware: (recovery_A125FXXS5CXE3_BIT_5)

Available Logs (Previous Working Firmware):

I can also provide logs from the last working firmware (BIT 2), even though downgrading is not an option:

Boot image: boot_A125FXXU2CWC3_BIT_2
Recovery image: recovery_A125FXXU2CWC3_BIT_2

Missing Logs (Due to Bootloop or Recovery Failure):

I am unable to obtain logs when the device fails to boot or enter recovery mode. Specifically, I need help gathering:

dmesg log – How can I retrieve this?
last_kmsg log – How can I retrieve this?
pstore ramoops – How can I retrieve this?
Any other logs that may be helpful – Please advise on how to capture them.

Additional Information:

Issues with bootloop and recovery after flash boot.img:
- It's impossible to provide logs when the device is in a bootloop.
- It's impossible to provide logs when enter to recovery mode fails (bootloop no matter how I true)
Magisk Installation Process:
- No issues during Magisk installation.
- No issues when Magisk patches the boot image.
- Magisk does not crash during the process.

Request for Assistance:

I am looking for a way to capture logs during the bootloop or failed recovery attempts and properly root the device. Is there any method to flash something that would allow me to view logs directly on the phone screen during bootloops? Please guide me on what I can do to capture these logs.

How I Can Help Developers:

I am more than willing to assist the Magisk developers in resolving this issue. I can:

Provide detailed logs from both working and non-working firmware versions, including boot and recovery images.
Test any custom patches or debugging methods you may need to gather additional information.
Run specific commands or scripts to collect logs in any format you require.
Flash firmware, re-install Magisk, or try alternative methods as per your instructions to better identify the root cause of the issue.

I am committed to providing whatever information is necessary to help resolve this bootloop problem for Samsung A125F with BINARY/U/SW REV. 5.

As of today, there seems to be no known method for gaining root access on this specific device with BIT 5. However, I plan to use this phone for a few more years, and I am willing to provide any logs or files necessary to troubleshoot the issue.

Related issues (without a successful resolution): #7654, #7256, #7255, #7254

Information I was able to find

The only post I found that might be helpful is this one: https://xdaforums.com/t/boot-img-for-sm-a127f-and-sm-a125f-with-the-touch-and-mtp-fixed.4536735/post-89627895.

However, not everyone wants to change firmware to the custom roms. I think many people just want to root on the stock rom (just like me).

Additional information about the issue can be found here: https://www.reddit.com/r/androidroot/comments/1adrefd/how_do_you_root_samsung_a12/. While this is a great resource on the issue, it unfortunately does not provide a solution.

Let me quote:

[...] patching the AP file then flash using odin, untick auto reboot and after flashing, hold vol - and power button to restart the phone, then hold vol + and power button to go into recovery mode to factory reset but whenever I restart the phone, the phone boots then the error message pops up with the Samsung logo and it'll just go on a bootloop. It doesn't go to recovery mode.

Here’s a video showing how the process should work on the A127F, but unfortunately, it doesn't work on the A125F- resulting in a bootloop and no recovery (really, it just doesn't work so it is impossible to wipe data after flash boot.img) for the A125FXXS5CXE3 variant. https://youtu.be/EED-jeFj49Q

This is a widespread issue. Many people on XDA are unable to root their A125FXXS3, A125FXXS4, and A125FXXS5* devices.

Here are some related posts (in random order):

In summary

I am eager to assist in resolving this issue. I'm willing to provide any necessary information, logs, and testing to help diagnose and fix the root problem for the Samsung A125F with BIT 5 firmware.

topjohnwu / Magisk