Do I lose anything like my NNID by downgrading to 4.5 and then upgrading like this? I want to do it but am worried about loosing saves or other stuff. I have a Link Between Worlds o3DS with the game pre-installed, so I worry I'm going to loose that as well...
Me as wellMy 3DS is spending a long time on "Preparing to start the HOME Menu..." without any progress on the progress bar! I hope I didn't brick it
Me as well
There's no standardization in what 3dnus actually downloads as an update. Some titles may bug out and not download. Some may not pack correctly. And of course, 9.2 actually gives you 9.0, so yellows8 soap list can't be relied upon.Yeah, this method semi-bricked my 3DS. No more hacks for me.
The solution to this is pre-downloaded and vetted update packs so you know that you are getting a correct title combination that works. Or maybe safety checks in sysupdater to only install pre-prepared, checksumed update/downgrade packs.
Little too late for you guys but for future reference to others who may encounter the same fate.
Even those can't always be trusted. I decrypted the update partition out of smash bros 9.2 (with rxtools) installed it with sysupdater and 'bricked' my nand mod system going from 4.5 to 9.2. I suspect not all titles were decrypted properly.
Maybe profi200 has been noticing all these brick reports lately, he updated sysupdater a few hours ago. I'll test it in a little while.
- Joined
- Oct 7, 2007
- Messages
- 4,458
- Trophies
- 3
- Age
- 36
- Location
- Levelland, Texas
- Website
- www.mariopc.co.nr
- XP
- 6,888
- Country
rxTools will occasional corrupt a block of data in romfs decryption. (so some files might have gotten corrupted)
But more likely is that you used sysupdater while in gateway mode. That's where all the bricks come from. The dev uses a different InstallFirm service command that is broken in Gateway mode. (he seems to have no interest in fixing this issue). Also don't use this on emunand/rednand. It's meant to be used directly on sysnand.
Also if you're going to update via CIAs, use CIAs made from 3DNUS/UpdateCDN. Cartridge updates will not install/update your browser and other things like eShop and such aren't updated either.
But more likely is that you used sysupdater while in gateway mode. That's where all the bricks come from. The dev uses a different InstallFirm service command that is broken in Gateway mode. (he seems to have no interest in fixing this issue). Also don't use this on emunand/rednand. It's meant to be used directly on sysnand.
Also if you're going to update via CIAs, use CIAs made from 3DNUS/UpdateCDN. Cartridge updates will not install/update your browser and other things like eShop and such aren't updated either.
Hi, I'll obviously have to try get another 3DS for this, but just for future reference. How to ensure that this is used directly on sysnand and not on emunand/rednand?
Also, what's Gateway mode? If I don't have a Gateway, I don't have to worry about that, right?
Thanks a lot
No I didn't and I don't expect this recent rash of bricks has anything to do with gateway update bricks. These are people without gateway that want to use pasta on 9.2.
I think that the bricks are happening to people who :
- Has no Cubic Ninja
- Is using the 4.5 Pasta CFW MSET Launcher.dat
- Used 3DNus to download the system update files
- Used Sysupdater to install the CIA update files
So somewhere in there is the issue. Maybe it's either sysupdater or the 4.5 Paste MSet launcher.dat
Ninja Edit : I do remember that the people who bricked mentioned using the encrypted launcher.dat. Perhaps it has something to do with it? I remember that nop90 released first an unencrypted launcher.dat (Works on MultiROP), which doesn't work on Palantine CFW users because it uses an encrypted launcher.dat. Then someone gave an encrypted launcher.dat that works has a copy and paste job for people who we're using Palatine CFW.
- Has no Cubic Ninja
- Is using the 4.5 Pasta CFW MSET Launcher.dat
- Used 3DNus to download the system update files
- Used Sysupdater to install the CIA update files
So somewhere in there is the issue. Maybe it's either sysupdater or the 4.5 Paste MSet launcher.dat
Ninja Edit : I do remember that the people who bricked mentioned using the encrypted launcher.dat. Perhaps it has something to do with it? I remember that nop90 released first an unencrypted launcher.dat (Works on MultiROP), which doesn't work on Palantine CFW users because it uses an encrypted launcher.dat. Then someone gave an encrypted launcher.dat that works has a copy and paste job for people who we're using Palatine CFW.
- I have Cubic Ninja
- I'm not using the 4.5 Pasta CFW MSET Launcher.dat
- I did use 3DNus to download the system update files
- Also used Sysupdater to install the CIA update files
My 3DS is now semi-bricked
Please be careful updating to 9.2, guys
I'm so sad
- I have Cubic Ninja
- I'm not using the 4.5 Pasta CFW MSET Launcher.dat
- I did use 3DNus to download the system update files
- Also used Sysupdater to install the CIA update files
My 3DS is now semi-bricked
Please be careful updating to 9.2, guys
I'm so sad
Then I'm stumped..... Sorry man.
Yeah I used mset pasta to update to 9.2 and it worked more or less fine (got to 9.0, hehe)Then I'm stumped..... Sorry man.
1) Yeah I don't have CN
2) Yes I used the pasta MSET port
3) I did use 3DNus to download 9.2 but instead got 9.0 which is also fine
4) Yeah used 0.3 Sysupdater to upgrade.
So yeah the process works fine
For some reason the cias we get from 3dnus (in my case i downloaded the 9.2.0-20EUR cias) don't appear to be all the correct updated versions, cause I also updated with those cias and my 3ds also showed version 9.0 instead of 9.2.
But then I used cooking mama 5 which updated me to 9.2.0-10.
I then used the same 3dnus cias I used before with sysupdater again and it did install some new titles, but others it did not install because the installed version from cooking mama was higher (It looks like 3dnus isn't downloading all the updated titles and so it only updates to 9.0), after it finished my 3ds was at 9.2.0-20 like it was supposed to.
But then I used cooking mama 5 which updated me to 9.2.0-10.
I then used the same 3dnus cias I used before with sysupdater again and it did install some new titles, but others it did not install because the installed version from cooking mama was higher (It looks like 3dnus isn't downloading all the updated titles and so it only updates to 9.0), after it finished my 3ds was at 9.2.0-20 like it was supposed to.
Hey guys, I think I used SysUpdater 0.4 to update to 9.2. He/she must have just uploaded it and I no idea. I only read 0.3 afterwards. That could be why my 3DS is now semi-bricked, maybe not. My bad.
Just don't use SysUpdater 0.4. :/
Just don't use SysUpdater 0.4. :/
