Hacking BootNTR New Version Research

  • Thread starter Thread starter astronautlevel
  • Start date Start date
  • Views Views 54,091
  • Replies Replies 257
  • Likes Likes 24
Yep, I'll do it tomorrow, didn't yet configure git on my new laptop, and my bed is really calling me out. :P

Code:
if (kernelVersion == SYSTEM_VERSION(2, 51, 2) || kernelVersion == SYSTEM_VERSION(2, 52, 0)) {
            // new3ds 11.1
            ntrConfig->firmVersion = SYSTEM_VERSION(11, 1, 0); //Your error lies here
                        ntrConfig->PMSvcRunAddr = 0x00103150;
            ntrConfig->ControlMemoryPatchAddr1 = 0xDFF88598;
            ntrConfig->ControlMemoryPatchAddr2 = 0xDFF8859C;
         
            bnConfig->SvcPatchAddr = 0xDFF8226C;
            bnConfig->FSPatchAddr = 0x0010F024;
            bnConfig->SMPatchAddr = 0x0010189C;
        }

Try with:
Code:
if (kernelVersion == SYSTEM_VERSION(2, 51, 2){
            // new3ds 11.1
            ntrConfig->firmVersion = SYSTEM_VERSION(11, 1, 0);
                        ntrConfig->PMSvcRunAddr = 0x00103150;
            ntrConfig->ControlMemoryPatchAddr1 = 0xDFF88598;
            ntrConfig->ControlMemoryPatchAddr2 = 0xDFF8859C;
         
            bnConfig->SvcPatchAddr = 0xDFF8226C;
            bnConfig->FSPatchAddr = 0x0010F024;
            bnConfig->SMPatchAddr = 0x0010189C;
        }
if (kernelVersion == SYSTEM_VERSION(2, 52, 0){
            // new3ds 11.2
            ntrConfig->firmVersion = SYSTEM_VERSION(11, 2, 0);
                        ntrConfig->PMSvcRunAddr = 0x00103150;
            ntrConfig->ControlMemoryPatchAddr1 = 0xDFF88598;
            ntrConfig->ControlMemoryPatchAddr2 = 0xDFF8859C;
         
            bnConfig->SvcPatchAddr = 0xDFF8226C;
            bnConfig->FSPatchAddr = 0x0010F024;
            bnConfig->SMPatchAddr = 0x0010189C;
        }
Same goes for Old3DS config. ;)
Jeez, I must be really out of it today, thank you :P
 
  • Like
Reactions: Nanquitas
Okay this one shouldn't auto downgrade.

@ih8ih8sn0w: Are you saying that it's working fine on a 11.2 firmware ?

N3DS here, sometimes using this it will hang and I will have to force reboot. Doesn't seem to have the issue if I hit 3.4 before it auto loads.

Let me clarify - If I start the selector and let it run by itself it will freeze when trying to auto boot 3.4 but if I touch 3.4 before the timer runs down it seems to boot ok.

e:It does work sometimes though..


edit2: seems to work without pressing anything... not sure why there is any inconsistency.

will test more
 
Last edited by roflpwnt,
@astronautlevel ok works in Luma stable on my O3DS bothe Mode0 and Mode3 (well Mode3 boots normal but i think breaks because i have a seperate .bin for that to test which is loaded by a bootloader, using depreciated pathchanger)

and before i regret doing this again, since i kinda had to deal w/ Butnutters, here's a Compiled version that i can confirm working for US O3DS atleast.
 

Attachments

Last edited by Dracari,
@astronautlevel ok works in Luma stable on my O3DS bothe Mode0 and Mode3 (well Mode3 boots normal but i think breaks because i have a seperate .bin for that to test which is loaded by a bootloader, using depreciated pathchanger)

and before i regret doing this again, since i kinda had to deal w/ Butnutters, here's a Compiled version that i can confirm working for US O3DS atleast.

Hangs on "patching svc check" when I attempt to use that on my n3DS. (11.2 USA console)
 
Using Luma CFW. Will not be using older firmware.bin so if it doesn't work with latest Luma I will be waiting till the issue is fixed on BootNTR's end.

Currently using Luma 6.2.2-c4e5f441. Default settings mostly except it's set to autoboot sysnand and show GBA boot screen for GBA VC titles. I'll update Luma provided that doesn't introduce new issues.

EDIT: Can't use latest Luma because a newer patch it wants to use breaks as a result of 11.2. (I think it's the anti-dg patch. Need to find the version of Luma that doesn't have this patch and try that one instead)
 
Last edited by Apache Thunder,
so, what does 11.2 breaks? ntr still works fine here on old3ds
home menu address are same as 10.4
 
so, what does 11.2 breaks? ntr still works fine here on old3ds
home menu address are same as 10.4
Reading all 4 pages, I am making an educated guess: NFIRM was renamed to a recent version, and all they have to do is to rename the address to load from that version.
 
  • Like
Reactions: astronautlevel
Reading all 4 pages, I am making an educated guess: NFIRM was renamed to a recent version, and all they have to do is to rename the address to load from that version.
well, all address are back to 10.4 address
old ntr should work fine
 
they are the same for me 10.4 11.0 11.2 at least for o3ds

ok maybe for luma ppl that needs firmware.bin
"luma people on Nightly/N3DS that needs firmware.bin"

Using Luma CFW. Will not be using older firmware.bin so if it doesn't work with latest Luma I will be waiting till the issue is fixed on BootNTR's end.

Currently using Luma 6.2.2-c4e5f441. Default settings mostly except it's set to autoboot sysnand and show GBA boot screen for GBA VC titles. I'll update Luma provided that doesn't introduce new issues.

EDIT: Can't use latest Luma because a newer patch it wants to use breaks as a result of 11.2. (I think it's the anti-dg patch. Need to find the version of Luma that doesn't have this patch and try that one instead)

Stable 6.3.1 works w.o needing to load a firmware.bin
 
Last edited by Dracari,
Ok updated to 6.3.1 release build and BootNTR works now. Do NOT update to any of the newer nightly builds. There's a new patch in those builds that fails due to 11.2 change regarding the anti-dg functions Nintendo added (they rewrote/altered that function so Luma can't find it for patching anymore). Luma's patch for that is borked and it Luma will show an error.
 
Last edited by Apache Thunder,
I'm getting an WSACancelBlockingCall error now when trying to connect to the 3ds capture
 

Site & Scene News

Popular threads in this forum