Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by TheCyberQuake, Aug 17, 2017.
Look at https://3ds.guide/ntrboot
I guess I should explain more. I know how to flash ntrboot to flashcart, but I thought I had to flash a special version to use this.
Thanks! this is exacly what i was searching for, total badass, go to a guy, say "i flash yur 3ds nigga" then flash it, in tha moment whitout computer, then the guy "wow" and you "yeah" and then asking 4 moni and get stabbed cuz being in the wrong neighborhood.
jokes apart, i will be testing 2.0 in some unflashed 3ds and posting reports about it.
You do, the one in the pack.
Well godmode9 has the official release, but unfortunately I've had a serious irl thing come up so I likely won't be able to finalize and push any updates until next week.
For those having issues booting the beta, be sure you name the boot.firm file correctly according to your installed ntrboot. If it won't boot at first, try renaming it to ntrboot.firm. The old version I used was the modified version that boots ntrboot.firm, but the new version is constructed in a way that removes the need for two .firm files meaning by default it will be named boot.firm and will use the standard ntrboot instead of the modified one.
Other than that I've seen a few issues with secret sector detection (falesly flagging a o3ds as having a previous a9lh install), though I've only gotten a report from one person about that.
Isn't supposed to be a .nds file? I don't see one.
The pack has the stuff for your console's SD card, including the files that are flashed to the flashcart, in the ntrboot folder. The nds file is outside the scope of this pack, you can get it from the guide.
I'm sorry, I am NOOB! Do I flash the boot9strap_ntr.firm to the flashcart using the ak2i_ntrcardhax_flasher.nds?
@TheCyberQuake:"Other than that I've seen a few issues with secret sector detection (falesly flagging a o3ds as having a previous a9lh install), though I've only gotten a report from one person about that." I had the same problem. I tried the beta with my o3ds. I updated my o3ds direct from a9lh to b9s, removed it with the guide on 3ds.guide and tried your beta. It says found a previous a9lh install.
Probably because the guide doesn't replace the secret sector on o3ds when updating to b9s. Replacing is not necessary on o3ds, but there is currently no good way that I know of to be able to skip secret sector checks for o3ds without having two separate scripts.
Don't, just restore secret sector on both models. Or neither, doesn't really matter. Once we have flow control it'll be easier.
The real reason for the false positives is precisely because the O3DS doesn't actually use the secret sector, though. A retail O3DS is likely to just have random garbage data on that portion of the NAND. So when it gets checked, it fails. Arguably the check is doing more harm than good at this point, because it's causing installs to fail that would be alright to proceed with, and isn't actually preventing any bricks either.
As AnalogMan has stated previously (and just before me, ninja'd), B9S does not need a valid secret sector on the N3DS either. I have verified this myself. The only point at which you need a valid secret sector is going back to retail. That's where you actually need 3 scripts for now (two of which d0k3 has already written for you, just modify a second copy of the N3DS one to check the SHA on "secret_sector.bin" instead of the actual secret sector and copy it over if it's good). Since there's no need to make absolutely certain it's correct, a simple "cp -o -w -n -s 0:/boot9strap/secret_sector.bin S:/sector0x96.bin" should be enough for your B9S script. If you've got it on the card, it will replace the secret sector. If not, it simply skips it and moves on, since it's not needed by B9S anyway.
I was already thinking about doing something like that. Just don't have time right now to implement these changes. I may be able to get an updated beta out before the end of the week, but no promises on that. After a bit of beta testing to insure it works as planned I could put it as an official update.
For instructions read https://3ds.guide/ntrboot but use the files from the pack instead of the ones it tells you to on the guide. That being said though I think I read above that the new version boots boot.firm so possibly you won't need to flash the flashcart with any special files. Ask @TheCyberQuake
you can use multdownload to download files directly
Not sure if youre aware, but it seems like r4i-sdhc is using your pack for their new r4i b9s cards. I noticed because the instructions they give seems like a copy/paste of yours.
Wow they totally did. Don't know if I should be upset or proud.
Demand money :-)
Agreed, a percentage or he sues xD
Link? I wanna see this, lol.
Edit: If it isn’t allowed, just tell me it isn’t. I’ll look for it myself!
Another edit: Found it.