Guys, spam calling someone is not cool. It's annoying and reeks of desperation. Had you done that at the discord nintendo homebrew channel, those folks would have ignored your pleas or booted you off.
If you want to know if someone's online at any given moment, look for the green triangle on that person's avatar at the top-left corner. This depends if that person publicly reveals their online status. There's also contacting me by PM if immediate attention is required. You'll have to excuse my absence from GBAtemp as I needed to decompress. I took leave shortly after knowing for certain @Wesleyy got past the 3D mode brick, believing he would be on his merry way when he would eventually update his 2DS to the latest firmware. It seems that assumption was wrong and too much to hope for.
Also, I took a day away from replying to study and gain experience dealing with 2.1.0 CTRTransfer softbricks as my last run-in with very low version firmware downgrade was this:
There are nuances and special considerations when it comes to resolving 2.1.0 CTRTransfer. For those who aren't familiar with the older A9LH custom firmware, 2.1.0 CTRTransfer can really fuck up a n3DS(XL) by MCU bricking from sleep mode and blue screens of death updating on a frankenfirm and foreign o3DS NSCD nand header injection. I wasn't sure what advice would be appropriate for the o2DS, so I did some digging.
After downgrading my (nephew's eventual) 2018 o2DS [newer revision with the WiFi module baked onto the motherboard] with 2.1.0 CTRTransfer, here are the things that can be verified.
- @zoogie's 2DSaver, in boot.3dsx standard form, doesn't work when creating a new user profile.
- Using devkitARM, cxitool, and makerom, compiling 2DSaver from source code into a *.cia and then GodMode9 injecting its *.app into System Settings does not work.
- This is the same injection technique found in placing FBI to Health & Safety.
- GodMode9 injecting other Homebrew CIAs such as FBI into System Settings do not work.
- GodMode9 injecting 2DSaver (in CIA form) to H&S and other system titles does work as per Inject & Restore Apps gm9 script (the CIA must have icon and banner).
- Recovery Mode doesn't work.
- Luma3DS Rosalina menu doesn't work. Remapping the combo to something simple like a single button (SELECT) or (X) also doesn't work.
- Both Homebrew Launcher and 2DSaver don't work when launching System Settings from HOME Menu with the Luma config.bin set to the region's mset TitleID.
- Updating to the latest 3DS firmware from System Settings does work after you fill out:
- Profile: User Name, Birthday, Region Settings
- Leaving the user profile blank will prevent the o2DS from updating with the message:
***
After closer examination in how 2DSaver works by changing a single value at offset 0x25278 in that configuration savegame's 00000000 from 00 → 01, replicating 2DSaver in gm9 script was almost considered unfeasible due to that file's (really ugly) layers of hash verification. Luck would have it that this crazy ass cat, @aspargas2, took the immense trouble in mapping them out.
The next v1.4 release of CTRTransfer (Type D9) will include the option of bypassing that introduction screen whether your o2DS accidentally downgraded to 2.1.0 or your (o/n)3DS(XL) 3D slider switch broke off.
***
@Wesleyy, because your softbrick states ARM9 prefetch abort (svcBreak) error, I have a strong suspicion one or more your essential NAND files were erased or corrupted from the 2.1.0 CTRTransfer downgrade using Decrypt9(WIP).
Since standard GodMode9 CTRTransfer didn't work and you don't have a backup of a good SysNAND *.bin image, you will need to resort to CTRTransfer (Type D9) - CTRTransfer.
Unfortunately, I have doubts that the currently available v1.3 of CTRTransfer (Type D9) will fix your brick. From past cases of similar bricks, its code base does not have good handling with garbage and blank files.
However, I'm ~90% certain the (yet to be released) v1.4 candidate script will though. I refuse to publicly release v1.4 at this time because it's not compatible with the latest stable GodMode9 v1.8.0.
I'm really reluctant in privately sharing v1.4 if there is the ever so slight chance you decide to leak it and someone runs it on GM9 v1.8.0 with the preventative safety checker turned off... Basically, that person would brick their firmware from the CTRTransfer process stopping halfway. It's not pretty I tell ya.
real sorry bout spamming man didn't realize you were researching i appreciate that, I def wont spam again in the future, Im really new to gbatemp. whenever the new v1.4 Could you help me then so that everything is better and we have a higher chance of fixing it ?
