I'm really sure that it will because it does indeed make sense.Please, don't take for granted that it will work. It's a pretty odd solution indeed
I'm really sure that it will because it does indeed make sense.Please, don't take for granted that it will work. It's a pretty odd solution indeed
I hope using that command will make sysUpdater better. Mine won't work, and I'm using the latest version.I'm really sure that it will because it does indeed make sense.In any case, this will help a LOT.
fun fact: call consoleInit() twice and the exploit always works
0.2b Downgrading to 9.2.0
0.2b.0 I do NOT guarantee that this works. Continue at your own risk. Follow these steps very precisely and focused. Most important: Stay calm. Almost 100% of all downgrade bricks are made by stupid mistakes. If you just follow these steps exactly, you will most likely (according to reports) not run into any serious issue; I cannot guarantee anything though.
0.2b.1 Update your system to 10.3.0 using the system settings if it's not on 10.3.0 yet.
0.2b.2 Format your system using the system settings. (You will lose apps, DLCs, games and everything, but according to all reports, you will be able to regain them after the download process by relinking your NNID afterwards.) This is optional, but it increases the success rate a lot.
0.2b.3 Turn off your 3DS and remove the (micro)SD card.
0.2b.4 Get the Downgrade Kit , as well as the 9.2.0-20X(Full)_o3DS/n3DS ZIP you will get from the "Manual Update/Downgrade Files" link at the usual place (where some useful links are if you don't know what I mean... Did you already check out my site?), then check the MD5 hash of the 9.2.0-20X(Full) ZIP file.
0.2b.5 Put your (micro)SD card into your computer and make a backup of its content.For checking the MD5 and SHA-1, use the following and http://onlinemd5.com/ or the MD5 check feature of SafeSysUpdater by @cpasjuste :
O3DS 9.2.0-20U:
MD5: 879f437d7c78f09ae565f79f5aa9c421
SHA-1: ccc272c495a84aa49f8db2da6072a79a73053e19
O3DS 9.2.0-20E:
MD5: caec3e015bc065dd0ca512f219c8fc3c
SHA-1: 63f0e83892af0f43d159685b4d775e09360552e4
O3DS 9.2.0-20J:
MD5: a7c14f50e553d99d93efd3a8dd4f8b9d
SHA-1: 422af53b07c270d65bf443d09736f3d1c540641c
N3DS 9.2.0-20U:
MD5: e5f40c3b155cfd12ef38be35d2e81d2e
SHA-1: 377c140377fb6cf31a0c032c4e1196cc521f87fe
N3DS 9.2.0-20E:
MD5: 6dcca8fcbc9a28c82c2a4e5182f3acf8
SHA-1: e7c77bf205137167f1f1befa0c4db9d879a21a2e
N3DS 9.2.0-20J:
MD5: f46677696ed4bf0e182de5a8168b7542
SHA-1: c9a1aaf4a4923fb5e065546da5c4a4da37aafdb2
0.2b.6 Delete everything on your (micro)SD card, then install and launch Minitool Partition Wizard.
0.2b.7 Right-click on your (micro)SD and select "Wipe" to delete the partition(s) on your (micro)SD.
0.2b.8 Right-click on "Unallocated" in your (micro)SD card and select "Create" to create a new partition.
0.2b.9 Select "Primary" where you see "Logical", and then set "Format" to "FAT32".
0.2b.10 In the top-left, click on "Apply" to finish.
0.2b.11 Close the Partition Wizard, then install and launch TeraCopy.
02b.12 Use TeraCopy to copy the updates folder you have extracted from the 9.2.0-20X(Full) ZIP file onto your (micro)SD, as well as the boot.3dsx from the Downgrade Kit (which is the same as the one you can find in smealum's starter kit) and the 3ds folder you have made according to the instructions on the place where you got all the files. (I think you just need to copy the files normally and TeraCopy will automatically become active.)
0.2b.13 Put your (micro)SD card back into your 3DS, follow the instructions on screen, then change the theme, then change it back to default.
0.2b.14 Launch browserhax (See the instructions around the QR code below).
0.2b.15 Once in the Homebrew Launcher, select menuhax_manager, then choose "Install".
0.2b.16 Exit the menuhax_manager, then turn off your system without exiting the HBL, then turn it back on and delete the internet connection settings. Go back to the home menu and turn off your system.
0.2b.17 Move the sysUpdater.3dsx you are able to find in /3ds/sysUpdater to the root of your SD card (besides the boot.3dsx, so to say), delete boot.3dsx and rename sysUpdater.3dsx to boot.3dsx
0.2b.18 So far so good! You will need to repeat this process until sysUpdater loads correctly. Turn on your 3DS and hold [L] to launch sysUpdater, then select Downgrade by pressing (Y), and after you did that, DO NOTHING ANYMORE. Be patient. If it succeeds, congratulations, you are on 9.2.0 now!
Thx to @Dribblejam and @shadowofdarkness
You was at least able to check your files with latest version ?I hope using that command will make sysUpdater better. Mine won't work, and I'm using the latest version.
Yes I was, and they all came back good. After that I went back to using the other version of sysUpdater that I had on my computer and it still doesn't work.You was at least able to check your files with latest version ?
What doesn't work? Do you recieve an error after downgrading or does it freeze before you even get the chance to downgrade?Yes I was, and they all came back good. After that I went back to using the other version of sysUpdater that I had on my computer and it still doesn't work.
It always says failed to get cia info. :/What doesn't work? Do you recieve an error after downgrading or does it freeze before you even get the chance to downgrade?

the files you're using could be bad files thenIt always says failed to get cia info. :/
Is your folder containing the cia files called "updates" and on the root of your SD?It always says failed to get cia info. :/
Make a copy of the updates folder in the root of your sd card and name it update without the s. I remember seeing reports about a bug or something and that fixed it. Give it a try if you can. Tonight I'll test safesysupader on emunand and report back.It always says failed to get cia info. :/
Then you can be 100% sure your files are good, are the right version for your console and at the right place. I also had the "cia error" a lot of times (maybe 40-50) before i get it to work on my n3DS. It's because the hax didn't really succeed and you didn't get "am:u" access. My version of sysupdater report this tough ("can't get am:u service ... try again" instead generic error).Yes I was, and they all came back good. After that I went back to using the other version of sysUpdater that I had on my computer and it still doesn't work.
Is it possible to add an option for it to rapidly reboot/retry x10-x15 times after getting an error like that?Then you can be 100% sure your files are good, are the right version for your console and at the right place. I also had the "cia error" a lot of times (maybe 40-50) before i get it to work on my n3DS.
Unfortunately no, the hax will crash the console after a few try (1 or 2).Is it possible to add an option for it to rapidly reboot/retry x10-x15 times after getting an error like that?
Might really help people like @Damon_girl
Yes it is.Is your folder containing the cia files called "updates" and on the root of your SD?
Okay, I'll try doing that.Make a copy of the updates folder in the root of your sd card and name it update without the s. I remember seeing reports about a bug or something and that fixed it. Give it a try if you can. Tonight I'll test safesysupader on emunand and report back.
So there's nothing I can do except try again? Will using your version improve the odds of it working?Then you can be 100% sure your files are good, are the right version for your console and at the right place. I also had the "cia error" a lot of times (maybe 40-50) before i get it to work on my n3DS. It's because the hax didn't really succeed and you didn't get "am:u" access. My version of sysupdater report this tough ("can't get am:u service ... try again" instead generic error).
it should be around the same successrate as SysUpdaterWill using your version improve the odds of it working?
Which is already a great progress in my opinion. ^^I think I have worded my post badly before. When I said "the exploit will always work", it includes the possibility of it failing. What I meant is that it won't crash
Unfortunately no, the hax will crash the console after a few try (1 or 2).
Perhaps you can try this @cpasjusteI think I have worded my post badly before. When I said "the exploit will always work", it includes the possibility of it failing. What I meant is that it won't crash
Yep i'm trying this but i don't see any progress for now :/Perhaps you can try this @cpasjuste
Maybe that will fix those crashes and you can try quickly forcing it to rety.

