Nintendo SWITCH Cheat Codes Download

Avoid creating cheat Request Topic​

Request cheats are made in :​

cheat-codes-ams-and-sx-os-add-and-request-general


This group provides cheat code authors to post works, share experience, learn and exchange

This group also provides cracking game players to get the latest and most complete cheats, and assist in testing

Since GBATemp is the most famous place in the industry, we hope to improve the content quality of this group

The main contents of this group include:
1. Publish personal originals.
2. Improve the quality of secondary creation (including version updates, repairs, and enhancements)
3. Request to create game cheats
4. Tutorial sharing on developing game cheat codes

For technical exchanges, sharing the code of others must attach the URL of the webpage published by the original author (do not copy the complete code)

Although the content of this group is very precious, it is provided for free, and it is not allowed to reprint it to commercial places or paid membership websites for profit.
Nintendo SWITCH Cheat Codes Download
Nintendo SWITCH Cheat Codes Download

Atmosphere's GDB

  • Thread starter Thread starter TomSwitch
  • Start date Start date
  • Views Views 10,498
  • Replies Replies 155
  • Likes Likes 29
So doing this I got main + 46AB9C for experience for KOTOR...However, I noticed that from start of heap, its static so far on 3 different dumps lol
 
  • Like
Reactions: ZeusX
@Eiffel2018 thanks to making tutorial.
I was at a loss coz I didn't know hot to use elf file with gdb
So It is very helpful for me.

@TomSwitch thanks to updating SE tools.
gdb and SE tools make searching and creating code more easiler.
By the way,does Edizon SE support code type 0xC0?
When I use code type 0xC0,EdizonSE shows cheat list,but key condition seems to be corrupted.

cheat sample
[4.ExperimentalASMCode]
20000000
[ 4.1 RP減らない/Inf RP]
20000000
[ 4.1.1 RP減らないOn/Inf RP On]
C1000F30
040F0000 01DFA4B4 71000129
[ 4.1.2 RP減らないOff/Inf RP Off]
C1000F30
040F0000 01DFA4B4 6B160129
SS
2021112112375200-CCFA659F4857F96DDA29AFEDB2E166E6.jpg
 
@Eiffel2018 thanks to making tutorial.
I was at a loss coz I didn't know hot to use elf file with gdb
So It is very helpful for me.

@TomSwitch thanks to updating SE tools.
gdb and SE tools make searching and creating code more easiler.
By the way,does Edizon SE support code type 0xC0?
When I use code type 0xC0,EdizonSE shows cheat list,but key condition seems to be corrupted.

cheat sample

SS
View attachment 286037

Normally, I open 2 ida pro simultaneously,
one for elf
one for gdb

all changes are marked in elf, and will be used for further version upgrade

and there should be a cheat code file in NS machine.
Every time I start the game,
and load the cheat files by Edizon SE,
then detact the dmnt and exit Edizon SE
Afterward load GDB and start debugger
 
Normally, I open 2 ida pro simultaneously,
one for elf
one for gdb

all changes are marked in elf, and will be used for further version upgrade

and there should be a cheat code file in NS machine.
Every time I start the game,
and load the cheat files by Edizon SE,
then detact the dmnt and exit Edizon SE
Afterward load GDB and start debugger
Thanks for your advice.
If I get confused about changing the base address, I'll try two windows.

I have a question about IDA pro.
When program stops by breakpoint, the disassembly text at PC chaged to DCB instruction in my enviroment.
Is it same in your enviroment?

In this case,disassembly text at 364D4B8E0 is MOV instruction before stopping by breakpoint.
break_before.png
and changed to DCB instruction after stopping by breakpoint
after_break.png
 
Thanks for your advice.
If I get confused about changing the base address, I'll try two windows.

I have a question about IDA pro.
When program stops by breakpoint, the disassembly text at PC chaged to DCB instruction in my enviroment.
Is it same in your enviroment?

In this case,disassembly text at 364D4B8E0 is MOV instruction before stopping by breakpoint.
View attachment 286068
and changed to DCB instruction after stopping by breakpoint
View attachment 286069
Yes, the same bug we have got. But it only display wrongly in IDA. Do not affect the code in NS machine

After several days my experience tell me:
1. Reduce setting breakpoints on the code, use F4 as much as possible.
2. If a breakpoints need to be set, disable it immediately after it in effect
3. For manual define segment, only main and heap and stack is enough. (don't add sdk or nsldr)
since it is a multi thread processor, the register PC will switch between threads,
if there is no SDK segment, only main code will be show on the screen, it is easy to use F7/F8 to trace the codes. (may be press 2 or 3 times F8, for one command step)

Tip: to check what call the current function, take a look on Stack, the X30 (returning point) always store in stacks, we can fastly find out the parent function
 
Click on the address line 364D4B8E0 and press "c" and the code will be show.
No,I can't.
Data bytes of "MOV W20,W2" should be "f4 03 02 2a",not "ff ff ff e7".
So I think data bytes of break point is set can't get correctly for now.

Yes, the same bug we have got. But it only display wrongly in IDA. Do not affect the code in NS machine

After several days my experience tell me:
1. Reduce setting breakpoints on the code, use F4 as much as possible.
2. If a breakpoints need to be set, disable it immediately after it in effect
3. For manual define segment, only main and heap and stack is enough. (don't add sdk or nsldr)
since it is a multi thread processor, the register PC will switch between threads,
if there is no SDK segment, only main code will be show on the screen, it is easy to use F7/F8 to trace the codes. (may be press 2 or 3 F8, for one command step)
Thanks for information:)
Using F4 sounds good!!
I'll try it.
 
  • Like
Reactions: jhmiller
Click on the address line 364D4B8E0 and press "c" and the code will be show.
That is a bug by IDA or GDBstub, not sure.
When the breakpoint in effect, it refresh the codes there,
but the result is 1 bit/byte only, the other byte become FF in the 64-bit command, that ida cannot translate to correct code.

To correct the wrongly display, Need disable the breakpoint and press F8 once, and then refresh memory
 
That is a bug by IDA or GDBstub, not sure.
When the breakpoint in effect, it refresh the codes there,
but the result is 1 bit/byte only, the other byte become FF in the 64-bit command, that ida cannot translate to correct code.

To correct the wrongly display, Need disable the breakpoint and press F8 once, and then refresh memory
F4 works fine,and also confirmed F8 can correct disassembly text:)
thank you for advices!!
 
  • Like
Reactions: jhmiller
@Eiffel2018 DId you get PINCE set up on windows? I may try to install it on my linux machine to test it out. It looks really promising. I'd just love to get it going on windows.
 
@Eiffel2018 your tutorial is great. I've got my system working with it minus the crashes when attempting a breakpoint. But I can see everything needed on IDA when using it. May have to update to a newer version of IDA though, mine doesn't look like yours while going through the setup though. But a quick question for you guys while I'm here. The address needed is to not make infinite points but just add some, I shouldn't NOP it correct? That would just either make it not go down correct?
 
Keep getting this error all the time though...

Oops! internal error 1338 occured.
Further work is not possible and IDA will close.
Would you like to create a crash dump for a bug report?
 
Keep getting this error all the time though...

Oops! internal error 1338 occured.
Further work is not possible and IDA will close.
Would you like to create a crash dump for a bug report?


Errors causes by Breakpoints mostly,
Switch it off manually and immediately , when it fire.

Otherwise, the NS machine seems store a wrong breakpoint. and alert you frequently.
Then, you need to detach and attach again to erase the wrong breakpoint.
 
Errors causes by Breakpoints mostly,
Switch it off manually and immediately , when it fire.

Otherwise, the NS machine seems store a wrong breakpoint. and alert you frequently.
Then, you need to detach and attach again to erase the wrong breakpoint.
After I set the breakpoint, I press f9 to continue and then f9 immediately correct
 
So I've got PINCE set up on my Linux machine, but it's pretty buggy. GDB connects and attaches, but commands to continue or run just throw errors, so you can't actually search for anything once you've attached. Shame, I'll keep working with it, but I'm running out of patience haha.

If it can somehow attach properly, then it will be a game changer, because it will basically be cheat engine for the switch..

Edit: I don't think it can be done at the moment without some kind of update to the software. It needs gdb-multiarch to run properly and only has gdb.
 
Last edited by FloDoc,
So I've got PINCE set up on my Linux machine, but it's pretty buggy. GDB connects and attaches, but commands to continue or run just throw errors, so you can't actually search for anything once you've attached. Shame, I'll keep working with it, but I'm running out of patience haha.

If it can somehow attach properly, then it will be a game changer, because it will basically be cheat engine for the switch..

Edit: I don't think it can be done at the moment without some kind of update to the software. It needs gdb-multiarch to run properly and only has gdb.
I wonder if PINCE support ARMv64:rofl:
 

Group statistics

Group owner:
matias3ds
Members:
86104
Threads:
7780
Messages:
42300
Photos:
0

Site & Scene News