The screen of my 3ds is exactly like that and I have the exact same problem the tutorial says how to fix. But it's not just the Settings menu but the hole System. If I follow the guide, will my 2DS be normal again?
Sorry for the bad english.Ok, we've found a fix for those who use 2dsaver, but also don't have a nand backup and are experiencing problems with updating from 2.1:
Special thanks to @Shad0w for help with the movable.sed editing and @Nigleet for compiling these instructions.
This post will be linked from the OP to keep it from being any more cluttered than it already is.
Pre-requisites:
A. Use 2DSaver ( https://gbatemp.net/threads/2dsaver-beta-fix-your-2ds-format-brick-testers-needed.457828/ )
B. Install the latest setup of B9S and stop after you finish the "Installing boot9strap" page(https://3ds.guide/installing-boot9strap-(2xrsa) ).
C. Complete a 9.2.0 CTRTransfer ( https://3ds.guide/9.2.0-ctrtransfer )
ON SOURCE UNIT
1. Using another functional 2DS boot into GM9 by holding start and selecting it from the luma chain loader menu
2. Navigate to CTRNAND/private/ and copy the movable.sed
3. Paste it to the root of the SD.
4. Select it and choose "show in Hexeditor"
5. Change the last 4 values on the first line to 00 00 00 00. The text at the end should read "SEED ".
6. Save your changes.
ON TARGET UNIT
7. Insert this SD into the affected unit and boot into GM9, selecting your SD card.
8. Copy the "movable.sed" file.
9. Backout of the SD, and navigate to the CTRNAND/Private.
10. Delete the "movable.sed" file in here.
11. Paste the new "movable.sed" file.
12. Press start to reboot.
13. Go through the initial setup.
14. If you had a NNID linked to the source unit, it will show up on the affected unit. Mitigate this by formatting the system memory (Settings>Last Page>Format System Memory).
15. Update the System.
Sorry for the bad english.
I have a friend with a 2ds formatbricked, he not have a nand backup.
I use a 2Dsaver, unlock it installing boot9strap using ntrboothax.
When a try system update, it give me a error and cancel the update.
When a try a 9.2 CTRTransfer, hi dont boot (black screen, an error ar occurred, i dont remember)
To fix it i need do this tutorial?
Thanks por any help.
I have acess to another 2ds here if necesarry.Hey there!
I actually had a problem either similar to this or exactly like this.
What I did was delete my movable.sed, (BE SURE TO BACK THIS UP, you'll have to edit it later if you want eshop and other things to work), and it let me get in after the 9.2 CTRTRansfer. After this, it should boot successfully, after going through it's initial setup.
Just to recap.
I used godmode9 and navigated to SYSNAND CTRNAND, and went to "private", and inside of there is the movable.sed file that you should back up somewhere before you delete.
After deleting that, the 2ds loaded fine and started the initial setup. From there, you should be able to update with system settings.
I hope this works for you!
If anyone finds any error in this, please correct me.
I have acess to another 2ds here if necesarry.
What i need do is:
1-9.2 CTRNAND Transfer
2-Backup and delete my movable seed
3-Boot and update to 11.5
4-Reinsert the backup of movable.seed
?
where is the instructions for editing? In the post what i first quot of zoogie?That does sound right to me
I think you can delete your movable.sed before or after, it's just important that you back it up. Also, there should be instructions on editing the movable.sed above too, that's what the backup is for
I do suggest that you set your date, time, nickname, etc. before updating with the system settings though. ^^
where is the instructions for editing? In the post what i first quot of zoogie?
Can't you use ntrboot on the bricked one?So i successfully nodded another 2ds but I kept the bricked one. Is hard modding my option?
Can't you use ntrboot on the bricked one?
ntrboot will get you into any ARM9 homebrew on any system that is not physically broken, so yes. Hardmods are obsolete for that purpose.Ntrboot works with a 2.1 2ds cart update brick?
welp time to get a r4 cart either that or wait for the power save version. since i have one already modded and that one is bricked and still usable im staying patient. btw thanks guys for your help and hardworkntrboot will get you into any ARM9 homebrew on any system that is not physically broken, so yes. Hardmods are obsolete for that purpose.
Any news on your research? I got a formatted 3DS with a broken 3D slider and I'd like to skip the 3D calibration step.Thanks for the tips! I found the value to alter that caused system setup to run once again, but oddly enough when I went back to restore the value, it had already reverted to how it was, but I still needed to do system setup. Restoring a backup I had resolved it. So now I'm going to make the change once again and compare the backup to the newly modified file and see what differences there are.
Edit: Yeah, this is fruitless. Modifying just about anything in the config save makes the 3DS go through setup but when it does, hundreds of changes are made. I assume the system call modifies multiple things at once and is likely the only feasible way to do it. Injecting another person's config likely would work but the config also stores the screen flicker values which can mess things up. For the 2DS stuck on a low firmware, this is no problem as you can update and then restore your original config and then resume setting it up as intended, but for 3DS's with broken 3D Sliders (which is why I was researching this) this is not a good work around. I'll see about changing 2DSaver into a FIRM payload or something similar.
EDIT2: Also, I wiped my Mii's. That's my fault for thinking that running the system setup wouldn't affect more than one thing and thinking that backing up just the config file would be enough.
EDIT3: Forgot that I used 3DSMiiModifier to change some names and so I had a backup save in JK's Save Manager, so no data lost. But I know my lesson now.
What is the issue exactly?Help me please beg them, today they gave me a 2ds was formatted not to spend a single day that they gave me my 2ds I only have Luigi's Mansion 2 please help me....
I have no idea for sure, but I guess he needs help for a 2ds format brick.What is the issue exactly?
I have been looking for instructions on how to accomplish this with ntrboot (no NAND backup), and I can't find any, so suggesting people use ntrboot isn't terribly helpful. I'm assuming a ctrtransfer wouldn't skip the setup, since it transfers over settings and such.I have no idea for sure, but I guess he needs help for a 2ds format brick.
This project is dead, however, and I suggest ntrboot as its replacement.
I'll add that to the OP.
To review: fixing this is all about changing a certain value in the config savegameI have been looking for instructions on how to accomplish this with ntrboot (no NAND backup), and I can't find any, so suggesting people use ntrboot isn't terribly helpful. I'm assuming a ctrtransfer wouldn't skip the setup, since it transfers over settings and such.
If you know how to do it, maybe add that to the OP as well? I'm asking because of this thread: https://gbatemp.net/threads/how-to-skip-the-3d-check-on-a-o3ds.526036/
And this is the first (and only relevant) thread that pops up when you search for this issue, so it would be useful information to have in the OP here.
Which requires doing some config file editing or replacement with Godmode9 I presume. I really don't know how people would go about this. Maybe just replacing the savegame with one from a healthy system? Don't know of any side effects, so make backups I guess. I don't know about ctrnand transfer, other than it seems to always have negative side effects, and you claim it might not work ... so forget that I guess.https://www.3dbrew.org/wiki/Config_Savegame said:0x00110000 0x4 0xC The low u16 indicates whether the system setup is required, such as when the system is booted for the first time or after doing a System Format: 0 = setup required, non-zero = no setup required