I was planning on working on it today as I was actually starting to feel better, then my dog suddenly had to be put down yesterday and I fell like crap again. Hopefully that was the end of 2017 overlapping into 2018 and this isn't indicative of how 2018 will be. Getting real tired of life pulling this kind of nonsense whenever I start to not feel like crap.
Don't worry about it. I'll probably get around to working on it either this weekend or next week.
I think I'm missing something. Your files start on an SD card that you have to loan to the unhacked system. At the end, how do you get all of the hacked files over to the owner's SD card? Is there any easier way than loading up GM9, copying, unmounting, swapping cards, mounting, pasting? I feel like at the end of your steps the SD card that you prepared has to stay in the newly hacked system?
With the auto-run script baked into gm9, it installs b9s and copies files from your sd to temporary system memory, it prompts you to eject, which you do and then insert the owners SD card, at which point the script continues and copies the files from temporary memory to the owners sd.
Yeah. After I posted that I re-read the directions and realized I skipped over the part where it does exactly that. Sorry about that buddy. Here's thinking of you, hoping you're okay!
I never realised that, the couple of people I've installed B9S for I've told them to download the files from your mega link, and just skipped that part
My main goal for this pack was to be able to carry just a few things in my edc (every day carry) and be able to install cfw on any 3ds on the fly. It's designed to be able to hack systems on a whim without requiring an internet connection or computer (which isn't always available). With the way it sets everything up, you can take a stranger's system and have it running cfw with things like freeshop, and my personal release even includes freeshop pre-configured which I can't include in the temp release due to linking to the title keys site.I never realised that, the couple of people I've installed B9S for I've told them to download the files from your mega link, and just skipped that part
You are missing the "end". Should be something like
Thanks 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).I wonder if you know why or you can shed some light onto this. I just hacked someone's O3DSXL using this pack. First off, thanks again, I love it. His system was A9LH'd, and he didn't tell me. So when the script ran it detected A9LH via slot0x96 hash. So, I used the scripts from 3ds.guide to uninstall CFW from an O3DS. I ran your script again after, and it gave me that error still. I updated the system and updated in recovery mode. I ran your script again, same error.
Its a known error. What it tries to detect doesn't exist in a vanilla o3ds. I need to update the script. I should now be able to detect if it's o3ds or n3ds and then attempt a repair for n3ds if it finds the replacement file. I need to see if I can find my WIP file so I can start working on that.I wonder if you know why or you can shed some light onto this. I just hacked someone's O3DSXL using this pack. First off, thanks again, I love it. His system was A9LH'd, and he didn't tell me. So when the script ran it detected A9LH via slot0x96 hash. So, I used the scripts from 3ds.guide to uninstall CFW from an O3DS. I ran your script again after, and it gave me that error still. I updated the system and updated in recovery mode. I ran your script again, same error.
Remember, this is an O3DSXL. I commented out the line in your script that detects A9LH. The script ran perfectly and everything worked 100%.
Why would someone with an O3DSXL have an A9LH'd slot0x96.bin? Is there a way to "fix" this incorrect slot key so that the script runs as intended?
Thanks TheCyberQuake! I hope you're feeling better.
Worst case you can attempt a copy that won't throw an error nor stop the script if it fails.
I just stole the if n3ds and invalid secret sector, copy over sector_sector to blah blah blah, if o3ds, do nothing. Although I did add a check to make sure the sector_sector.bin file exists first before attempting to copy it over. call me old fashion but I have no idea how GM9 handles errors.
