Hacking NTRPack: PC-less b9s install using ntrboot

  • Thread starter Thread starter TheCyberQuake
  • Start date Start date
  • Views Views 45,853
  • Replies Replies 227
  • Likes Likes 28
Its probably China based, so I most likely won't get anywhere. Plus the only items that are mine are the instructions, scripts, and the process in general.

Exactly. And if there was any money in scripts, I could make a fortune selling my direct movement AHK ones for the Diablo and Torchlight series. I've never even bothered to release them (I hate typing documentation). Well, you know what they say. "Imitation is the greatest form of flattery."
 
Last edited by Kazuma77,
  • Like
Reactions: TheCyberQuake
I'm testing the beta 2.0 pack. My first test case was an old O3DS clunker that I previously had A9LH on it. I got the payload booting just fine but the script tells me that it detected a previous installation of AL9H and that it cannot proceed (to use the PC method). I restored a backup NAND of the system when I first got it, on firmware 7.2 without keeping A9LH but the script still gives me the same warning/error.

I reflashed my Acekard with the 1.2 payload and retried on the non-XL O3DS (that I had removed A9LH) and it worked without an issue.


I've got an O3DS XL which I'm almost positive has never been hacked at all before and the beta 2.0 payload gave me the same error about A9LH. I'm going to leave that one as-is in case there is something you would like me to test on it.
 
Last edited by zanetheinsane,
  • Like
Reactions: Quantumcat
I'm testing the beta 2.0 pack. My first test case was an old O3DS clunker that I previously had A9LH on it. I got the payload booting just fine but the script tells me that it detected a previous installation of AL9H and that it cannot proceed (to use the PC method). I restored a backup NAND of the system when I first got it, on firmware 7.2 without keeping A9LH but the script still gives me the same warning/error.

I reflashed my Acekard with the 1.2 payload and retried on the non-XL O3DS (that I had removed A9LH) and it worked without an issue.


I've got an O3DS XL which I'm almost positive has never been hacked at all before and the beta 2.0 payload gave me the same error about A9LH. I'm going to leave that one as-is in case there is something you would like me to test on it.
I'll be removing the a9lh check and will instead just be doing an attempted copy of the secret sector file. If it fails the script will just continue. I've been meaning to get that done, and had it planned a week or so ago but had someone close die so I'm getting my life reorganized. Other irl things took priority. I believe I should have time to get it done this week though
 
I'll be removing the a9lh check and will instead just be doing an attempted copy of the secret sector file. If it fails the script will just continue. I've been meaning to get that done, and had it planned a week or so ago but had someone close die so I'm getting my life reorganized. Other irl things took priority. I believe I should have time to get it done this week though

The original pack is working just fine for now. I'll be happy to shelve my clean 3DS and test whenever you put out anything new.
 
  • Like
Reactions: illest
I guess I'll give an update just to explain a few things.
Currently the project has been placed on hold for various reasons.
I've lost some people in my life due to various things, including the recent mass shooting that occurred in my city.
I'll still be in these forums, but I'm not being as active as usual. Life has gotten busy, and at this point I'm just trying to wrap my head around all of the chaos and changes that are happening all at once.
I apologize for the several times I've stated I would work on it, and I really did want to. It's just every time I want to something pops up in my life that need my attention more than this pack.
I hope to eventually get this thing back up and with a proper 2.0 release with the fixes I want to add, and hopefully sooner rather than later. I hope everyone understands.
 
I guess I'll give an update just to explain a few things.
Currently the project has been placed on hold for various reasons.
I've lost some people in my life due to various things, including the recent mass shooting that occurred in my city.
I'll still be in these forums, but I'm not being as active as usual. Life has gotten busy, and at this point I'm just trying to wrap my head around all of the chaos and changes that are happening all at once.
I apologize for the several times I've stated I would work on it, and I really did want to. It's just every time I want to something pops up in my life that need my attention more than this pack.
I hope to eventually get this thing back up and with a proper 2.0 release with the fixes I want to add, and hopefully sooner rather than later. I hope everyone understands.
Hope you feel better and everything goes back to normal for you soon :-(
 
Right now I'm trying to go back through the thread and figure out what need to be fixed in the beta.
So far I know I definitely need to fix secret sector detection (or rather remove and replace with just a copy attempt that won't stop the script if failed).
I also see a few problems with dspfirm dumping, but I haven't gotten any info on what regions and consoles were having issues. If anyone has previously had the script fail at dumping dspfirm.cdc, I'd greatly appreciate console and region info to better troubleshoot the issue. I'll try to be looking into it throughout the week, seemshow I get some enjoyment from doing things like writing scripts, and the current known issues are fairly easy to fix. Probably no release updates coming this week though, but who knows maybe I'll be in the mood to crank that out.
 
I guess I'll give an update just to explain a few things.
Currently the project has been placed on hold for various reasons.
I've lost some people in my life due to various things, including the recent mass shooting that occurred in my city.
I'll still be in these forums, but I'm not being as active as usual. Life has gotten busy, and at this point I'm just trying to wrap my head around all of the chaos and changes that are happening all at once.
I apologize for the several times I've stated I would work on it, and I really did want to. It's just every time I want to something pops up in my life that need my attention more than this pack.
I hope to eventually get this thing back up and with a proper 2.0 release with the fixes I want to add, and hopefully sooner rather than later. I hope everyone understands.

Of course we understand. Take as much time as you need. This can wait. Life won't. I can't even imagine what you're going through right now. But if there's anything I can do, let me know.
 
I've had a strange issue with the beta. I was installing on an old 3DS, so naturally the secret sector check failed, but after modifying the script to remove it, the old version of the script with the check included still ran?... I can't find more than one copy on the card, and no copies at all on the 3DS. Interestingly though when I ran the normal GM9 instead of the one that auto-runs scripts, then went to the script folder and ran the exact same file, it was behaving normally? Does something here copy the scripts to some well-hidden location that GM9 checks first?
 
I've had a strange issue with the beta. I was installing on an old 3DS, so naturally the secret sector check failed, but after modifying the script to remove it, the old version of the script with the check included still ran?... I can't find more than one copy on the card, and no copies at all on the 3DS. Interestingly though when I ran the normal GM9 instead of the one that auto-runs scripts, then went to the script folder and ran the exact same file, it was behaving normally? Does something here copy the scripts to some well-hidden location that GM9 checks first?

Standalone script runners don't run any of the scripts in the "gm9/scripts" folder. They have an "autorun.gm9" embedded directly into them. The only way to change their contents is to recompile GM9 with a new "autorun.gm9" in the data folder. It's possible that he forgot to put the checks into the copy of the script he used to generate the SSR, or that he's already fixed the SSR.
 
After testing the beta 2.0 on two diferent 2ds(old)EU whit the lastest firmware, in both cases detect a A9LH Installation, but neither of the two 2ds have that, where vanilla, never flashed never nothing, cfw-free, "clean" 2ds, i tried multiple times and the same.
sorry for the english, used to read/hear not used to write/talk in it.
 
Thought I'd share this as people in this thread may be interested, but I've started a discussion on reddit about 3DS speed runs for installing CFW along with an example video. In my setup used for the speed run, all the needed files are contained directly in the BootNTRHax flash cart making it a PC-less install as well as not needing to swap SD cards: https://www.reddit.com/r/3dshacks/comments/76g1ze/proposal_for_cfw_speed_runs/

EDIT: Post is getting auto-removed, so I also posted it here: https://gbatemp.net/threads/3ds-cfw-install-speed-run-proposal.486831/
 
Last edited by DocKlokMan,
  • Like
Reactions: Quantumcat
Thought I'd share this as people in this thread may be interested, but I've started a discussion on reddit about 3DS speed runs for installing CFW along with an example video. In my setup used for the speed run, all the needed files are contained directly in the BootNTRHax flash cart making it a PC-less install as well as not needing to swap SD cards: https://www.reddit.com/r/3dshacks/comments/76fxv8/proposal_for_cfw_speed_runs/
Link doesn't work

Sent from my ONEPLUS A3010 using Tapatalk
 
Thought I'd share this as people in this thread may be interested, but I've started a discussion on reddit about 3DS speed runs for installing CFW along with an example video. In my setup used for the speed run, all the needed files are contained directly in the BootNTRHax flash cart making it a PC-less install as well as not needing to swap SD cards: https://www.reddit.com/r/3dshacks/comments/76g1ze/proposal_for_cfw_speed_runs/
I think your post got deleted
 
I tested the beta (11.5.0-38E O3DS) and i got the "No supported MSET version found!\nThis only works for EUR/JPN/USA for firmwares\n9.6.0 - 11.5.0" error message, i do have a emunand installation (i do not know if it matters or not)
 
I've got two suggestion (request?), one is for checking if an Emunand exists, and ask the user if he/she wants to copy it to the sysnand. The other is for removing old cfw (if present), like rxTools, cakes, and Gateway.
Edit: My browser bugged and it quadruple posted, sorry.
 
Last edited by MiiJack,

Site & Scene News

Popular threads in this forum