Remove this line
sha S:/sector0x96.bin 82F2730D2C2DA3F30165F987FDCCAC5CBAB24B4E5F65C981CD7BE6F438E6D9D3
sha S:/sector0x96.bin 82F2730D2C2DA3F30165F987FDCCAC5CBAB24B4E5F65C981CD7BE6F438E6D9D3
If you wanted to, you could build GodMode9 on your own and hardcode that in (https://github.com/d0k3/GodMode9#how-to-build-this--developer-info). You'd have to make sure to also add the option of running the install script at launch, if you want it to work that way. You're still technically copying from yours to the target this wayThanks a bunch It runs pretty well now, feel free to use the script (I kinda theft your code lol, sorry). I added some code to it to remove rxTools, soundhax, any old 3DS folder (I don't know if this should be done though) and make it SD-less after (in case the owner' SD got corrupted).
This needs a valid secret sector to be potent, so any suggestions for that (without the need of copying mine to the target)? Thanks again.
I commented it out. I believe comments are done with a hashtag.The o3ds/o2ds secret sector check is kinda weird. I purchased a new o2ds and the install script stopped because it would have the a9lh previously installed which I am sure that wasn't the case. Though on a 2ds which had a9lh it didn't complain.
@OrGoN3 what did you do to ignore the sector0x96.bin in the script?
set ERRORMSG "Previous A9LH install detected!\nCan't install boot9strap this way!\nPlease use 3ds.guide to install from PC."
sha S:/sector0x96.bin 82F2730D2C2DA3F30165F987FDCCAC5CBAB24B4E5F65C981CD7BE6F438E6D9D3
#set ERRORMSG "Previous A9LH install detected!\nCan't install boot9strap this way!\nPlease use 3ds.guide to install from PC."
#sha S:/sector0x96.bin 82F2730D2C2DA3F30165F987FDCCAC5CBAB24B4E5F65C981CD7BE6F438E6D9D3
I don't know if you're still bothering with this, but when I test this, it gives "line 6: unknown cmd".It's been a while since I've touched this, but I've started messing with it again since I've started playing around with gm9 scripts again.
Currently have almost every change I wanted to implement originally. With the added structure in the scripts I can now properly determine which region the console is and set the appropriate location of certain files.
After these next few changes the only real thing I would want to add is some way to automatically find where dsp1 starts (via a hex match) in order to have it work with any version of MSET, and not just the latest. I don't think godmode9 currently has that ability though, so for now that idea is on the back burner.
Only problem right now is that I don't have a test console anymore and I don't have my compiling setup to compile the custom godmode9.
So for now while I get compiling up and running again, it would be awesome if people could beta test the build below.
This go around I'm using the standard ntrboot version of boot9strap that loads boot.firm.
Should be simple to test. Extract the zip to your flashcard microSD, boot with ntrboot, that should load into godmode9, and from there hit the home button, select scripts, then select Install_NTRPack.
Current changes:
https://mega.nz/#!AJ8yDAJL!2eKQz8AQYCoRz2hdT8oWLpTtYfeFug9llP9QIXKQzl4
- Fixed up the secret sector check. It will detect if you are running on a n3ds, check secret sector, then notify you if you wish to continue. It will also attempt a repair if you have secret_sector.bin in the boot9strap folder. Either way, if it fails it will still continue installation as it's not that important once you install b9s.
- Greatly improved dspfirm.cdc dumping code, which will auto-detect the correct MSET .app to to pull .code from. Currently only supports USA/JPN/EUR 11.5 or newer (will just skip if errors occur)
- Better error handling overall
- Script will continue over non-critical errors
- Updated all homebrew
Let me know of any bugs you find!
Your gm9 may need to be updated. The script uses commands introduced in newer versionsI don't know if you're still bothering with this, but when I test this, it gives "line 6: unknown cmd".
Thanks for this by the way.
Hmmm... it does not work on 1.6.1 , but works fine on 1.6.3 (to what I've tested atleast). From the changelog, I don't see anything major. Anyway, thanks for the help.Your gm9 may need to be updated. The script uses commands introduced in newer versions