- Joined
- Jan 27, 2015
- Messages
- 4,999
- Trophies
- 1
- Location
- Behind a screen reading news
- XP
- 4,885
- Country
Orrrrrrr just don't do it in rxMode and only in devmode/pasta mode.I did my N3DS just fine in Devmode, but bricked an o3ds in Rxmode...lol! so make backups..lol!
That's what I'm saying accidents happen. I knew better and still jacked a system...never Rxmode..lol Thankfully I had a BACKUP.Orrrrrrr just don't do it in rxMode and only in devmode/pasta mode.
the 9/28 from this link RxTools Nightlies by @WhoAmI? is is really stable and fully functionalWhich Rxtools version is stable?
It should be.So is this software safe/foolproof if you do it right or have people had random bricks after following the rules completely and getting the right files? I don't want to risk a Christmas 3ds to unstable software.
Would you know if I could find o3DS update files on that ISO site? Last I hear Nintendo removed the 9.0-9.2 update files from NUS.It should be.
Bricks happen mainly if people run sysupdater while firmlaunch is enabled, or if their update .cias are bad somehow (or let's say they installed the wrong update files for the wrong 3DS, such as N3DS update pack on O3DS, or I think maybe the wrong region files. I don't know if installing a full Japanese .cia update pack on an European or US 3DS could cause a brick, for example.)
Make sure you got the right update pack, make sure the files aren't corrupted, make sure you are in rxTools DevMode/Pasta mode, or Pasta CFW without firmlaunch, then it should be fine.