FW 11.60 - Memory Reads Work, Writes/Freezes Do Not (PS4 Cheater + ps5debug-NG v1.2.5) #13

New issue

Closed

opened 2026-05-31 20:26:14 -05:00 by farscaper11 · 5 comments

farscaper11 commented

2026-05-31 20:26:14 -05:00

(Migrated from github.com)

Firmware: 11.60
Payload: ps5debug-NG v1.2.5
Client: PS4 Cheater 1.5.4.7

Tested Games:

Pragmata v01.200.000
Resident Evil 2 v01.000.003

Results:
✓ Connects successfully to ps5debug-NG on port 9020
✓ Memory scanning works
✓ Exact value searches work
✓ Values update correctly during gameplay
✓ Able to narrow values to a single address

Pragmata Demo:

Successfully tracked HP values from 1000 down to 0.
Address updated correctly while taking damage.
After death/reload, HP moved to a new address as expected.

Resident Evil 2:

Successfully tracked handgun ammo.
Narrowed ammo count to a single address.
Value updated correctly as ammo was consumed.

Issues:
✗ Changing values reverts immediately
✗ Lock/Freeze does not work
✗ Hex Editor Commit has no observable effect in-game
✗ Modified values immediately return to their original value

Examples:

RE2 ammo located and tracked correctly (7 → 6 → 5 → 4 → 3).
Attempting to change ammo value to another number reverts immediately.
Locking the value does not prevent changes.

Observed behavior appears to be read-only memory access. Reading/scanning works correctly, but write operations do not appear to affect game memory.

Firmware: 11.60 Payload: ps5debug-NG v1.2.5 Client: PS4 Cheater 1.5.4.7 Tested Games: - Pragmata v01.200.000 - Resident Evil 2 v01.000.003 Results: ✓ Connects successfully to ps5debug-NG on port 9020 ✓ Memory scanning works ✓ Exact value searches work ✓ Values update correctly during gameplay ✓ Able to narrow values to a single address Pragmata Demo: - Successfully tracked HP values from 1000 down to 0. - Address updated correctly while taking damage. - After death/reload, HP moved to a new address as expected. Resident Evil 2: - Successfully tracked handgun ammo. - Narrowed ammo count to a single address. - Value updated correctly as ammo was consumed. Issues: ✗ Changing values reverts immediately ✗ Lock/Freeze does not work ✗ Hex Editor Commit has no observable effect in-game ✗ Modified values immediately return to their original value Examples: - RE2 ammo located and tracked correctly (7 → 6 → 5 → 4 → 3). - Attempting to change ammo value to another number reverts immediately. - Locking the value does not prevent changes. Observed behavior appears to be read-only memory access. Reading/scanning works correctly, but write operations do not appear to affect game memory.

yamildev01 commented

2026-06-01 04:05:40 -05:00

(Migrated from github.com)

Memory reads but not writing data! Same issue on 10.01 etahen 2.5b

Tested games:
pragmata
Red dead redemption 2

Tested on PS4 Cheater 1.5.4.7

Memory reads but not writing data! Same issue on 10.01 etahen 2.5b Tested games: pragmata Red dead redemption 2 Tested on PS4 Cheater 1.5.4.7

👍 1

OpenSourcereR-dev commented

2026-06-01 04:38:42 -05:00

(Migrated from github.com)

@farscaper11 Thank you for the detailed report.
Please join Team Reaper discord server if you would like to help testing the next release that hopefully will resolve these issues.

@farscaper11 Thank you for the detailed report. Please join Team Reaper discord server if you would like to help testing the next release that hopefully will resolve these issues.

👍 1

farscaper11 commented

2026-06-01 17:11:11 -05:00

(Migrated from github.com)

I will join to help test.

OpenSourcereR-dev commented

2026-06-02 14:57:01 -05:00

(Migrated from github.com)

Please test version 1.2.6 and report if all issues are fixed,
https://github.com/OpenSourcereR-dev/ps5debug-NG/releases/tag/1.2.6

Thank you

Please test version 1.2.6 and report if all issues are fixed, https://github.com/OpenSourcereR-dev/ps5debug-NG/releases/tag/1.2.6 Thank you

👍 1

OpenSourcereR-dev commented

2026-06-03 09:40:02 -05:00

(Migrated from github.com)

I believe the issues have been fixed, but feel free to open a new issue if it hasn't or if there's any other bug. Closing this one.
Please use the latest version (1.2.7 at the time of writing: https://github.com/OpenSourcereR-dev/ps5debug-NG/releases)

I believe the issues have been fixed, but feel free to open a new issue if it hasn't or if there's any other bug. Closing this one. Please use the latest version (1.2.7 at the time of writing: https://github.com/OpenSourcereR-dev/ps5debug-NG/releases)

👍 1