seems GBA SRAM has a couple unreliable bytes at the beginning and end, thanks Tepples for the info in the GBA programming newbie’s guide ;-) and thanks Eric for making me look for it :-) this is now fixed for EToolSMS, and will be fixed for ETool 2.x SAP. The first and last couple bytes being unreliable (NULLing sometimes on power cycle) it will simply update the header on the save so that the APPID no longer has any data in the first couple of bytes, fixing this problem transparently for anyone using EToolSMS, and it should fix it on any damaged (0x00 in first 2 bytes) existing EToolSMS file. Still unsure as to why the previous versions would not boot with G6.