ROM Hack Need Help Making SX OS Cheats

[Deleted member 474010]

So, I found the address I wanted to write to in my game with SX OS. It is [HEAP+0x56C04AC4]. However, looking at the guide here (here), it says that HEAP values are often unstable. I want to write a 1 byte value of 0xA to this heap address. I'm not sure, but I think I'd do so via this:
01100000 56C04A90 0000000A

Using this code crashes my game

The guide however said to trace it to a value in MAIN, so I found the nearest pointer to it. I found the pointer [MAIN+0x00D5D620] at address [HEAP+0x56C04A90], which is 0x34 away from my address. To write a 1 byte value of 0xA through these pointers, I think I'd do so via this:
580F0000 00D5D620
780F0000 00000034
610F0000 00000000 0000000A

The cheat above does nothing. What am I doing wrong? It just isn't writing a value to the current address for the value I'm trying to hack. Writing to it using SX OS's RAM Editor works, however.

 

[Stoned]

So, I found the address I wanted to write to in my game with SX OS. It is [HEAP+0x56C04AC4]. However, looking at the guide here (here), it says that HEAP values are often unstable. I want to write a 1 byte value of 0xA to this heap address. I'm not sure, but I think I'd do so via this:
01100000 56C04A90 0000000A

Using this code crashes my game

The guide however said to trace it to a value in MAIN, so I found the nearest pointer to it. I found the pointer [MAIN+0x00D5D620] at address [HEAP+0x56C04A90], which is 0x34 away from my address. To write a 1 byte value of 0xA through these pointers, I think I'd do so via this:
580F0000 00D5D620
780F0000 00000034
610F0000 00000000 0000000A

The cheat above does nothing. What am I doing wrong? It just isn't writing a value to the current address for the value I'm trying to hack. Writing to it using SX OS's RAM Editor works, however.

Try Replaceing the F whit 0

 

[Deleted member 474010]

Try Replaceing the F whit 0

Still didn't work... I might try changing the 8 to a 4.

 

[dsrules]

the guide says try trace it back to Main, not using a Main near the address as a pointer

 

[Deleted member 474010]

the guide says try trace it back to Main, not using a Main near the address as a pointer

All results I've found (on several occasions) have been in [HEAP+0x56C04AC4], and I've narrowed the result count down to 3.

 

[dsrules]

All results I've found (on several occasions) have been in [HEAP+0x56C04AC4], and I've narrowed the result count down to 3.

current known way to find pointers is use this
https://gbatemp.net/threads/noexs-remote-debugger.512668/page-9#post-8331260

 

[Deleted member 474010]

current known way to find pointers is use this
https://gbatemp.net/threads/noexs-remote-debugger.512668/page-9#post-8331260

That was EXACTLY what I was looking for! I prefer using my computer to scan memory anyways. Also, my SD card was in exFAT and it just corrupted. My codes might not have been working because of the format type. So, I'll just format my SD Card to FAT32 using Powershell and I'll get back to what I was doing. Fortunately I kept backups.

 

[dsrules]

That was EXACTLY what I was looking for! I prefer using my computer to scan memory anyways. Also, my SD card was in exFAT and it just corrupted. My codes might not have been working because of the format type. So, I'll just format my SD Card to FAT32 using Powershell and I'll get back to what I was doing. Fortunately I kept backups.

you could also install games using usb if you are on fat32, then there's no need to worry about corrupting your microsd

 

[Deleted member 474010]

you could also install games using usb if you are on fat32, then there's no need to worry about corrupting your microsd

Thanks for the advice. I also often find I'm backing up my eMMC too as I'm afraid of things like this. Plus, I use it to inject saves onto my clean SysNAND. Could've made for an even faster SD Card corruption considering 30GB was constantly being written and deleted. So SX OS can pick up FAT32 USB Drives? That's cool.