Okay. Good. Didn't see this.
Actually, the Temporary.gm9 script takes care of this. The Temporary.gm9 script also pits the Original Firmware in the correct location on the SD Card, allowing the uninstall script to work.
But it shows the problem: All members helping in the 3DS section are used to the "official guide" and the scripts and everything. If a new guide pops up, with custom scripts, this means spending hours to analyse it and maybe test it.
You can blame me only partially for not sacrificing even more of my free time. (Same with the videos – it is so tedious to react to problems caused by random YouTube guides.)
Why would this be a good idea? Improving on existing methods and descriptions is something different than reinventing the wheel. Understanding all this (and comparing it to the known guide) is hard work for anybody wanting to help users.
I really don't want to offend you or anything like that. I can clearly see that you spent hours too. The question is: Why?
It took years for The Guide to become what it is now. Thoroughly tested and as noob-proof as possible. The guide is not long because it is complicated. It is long because it is extremely simplified and holds the users hand on every step while maintaining a maximum of security providing links to the latest versions of the needed software. Creating a new guide, possibly easier and faster, with the same good quality would require a lot of testing – including the reactions of some beginners. Being short is not sufficient for being noob-friendly. I get it, many people nowadays don't want to read. "tl;dr
" But this does not change the fact, that softmodding a console requires at least a basic knowledge and therefore a somewhat detailed explanation.
I've now noticed that the Temporary.gm9
self-deletes (makes sense with that name). What if Luma3DS or GodMode9 gets an update? That would mean updating boot.firm
manually (or adding the Megascript). It is hard enough convince beginners to update Luma on SD and CTRNAND while having an semi-automatic option (link to here
). Still there have been a lot of cases with "Failed to apply 1 FIRM patch(es)
" on corrupted SDs while the failsafe on CTRNAND was outdated. With manual copying… no way.
Fine. The temporary script takes care of proving native firm for uninstallation with the other custom script. Neither your guide nor the script contains any warning about what can happen on B9S removal while the uninstall option is included.
Writing a new guide from scratch is not that easy. Please address these problems.