Hacking BootNTR current firm not supported

[Sigiz]

so i have been having this issue where , whenever i try opening bootntr it goes to a black screen , shows svcbackdoor check ok then it says unknown firmware access patches failed then lists lots of addresses and ultimately ends at this

Spoiler

dump finished at addr : 00382000
current firmware not supported.
please send feedback to
[email protected]
kversion:02330000
bnBootNTR failed
press home button to return to the menu

edit:- i forgot this wasnt reddit ... i am on 11.0 O3ds at luma + a9lh

edit2:- fixed , had to enable sysnand is updated in luma settings by pressing select on boot , and also disable second emunand

 

[Davidosky99]

You're not providing details. What's your firmware version ?
Are you using a9lh or ntr cfw launcher CIA ?

 

[DjoeN]

BootNTR only works till firmware 10.2, does not work on 10.4/10.5 and up
So you need 10.2 firmware.bin in your Luma folder and have to change your Luma config to use it.

 

[Queno138]

BootNTR only works till firmware 10.2, does not work on 10.4/10.5 and up

However to add on,
It should work on 11.0fw on luma on A9LH,
Due to using an older NTR/firmware.bin (IIRC its 9.2 firm)

Else, it wouldn't explain why I can use my NTR

 

[DjoeN]

However to add on,
It should work on 11.0fw on luma on A9LH,
Due to using an older NTR/firmware.bin (IIRC its 9.2 firm)

Else, it wouldn't explain why I can use my NTR

Yes it does work on FW 11.0 but you have to have a 10.2 firmware.bin in the luma folder and you have to setup your configuration correct in the luma config (depending if you boot sysnand 11.0 or emunand 11.0)

What i meant was you need 10.2 firmware.bin file

 

[Ramzh]

Use this setup if you have A9LH:

• "Autoboot SysNAND"
• "SysNAND is updated"
• "Force A9LH detection"
• "Show current NAND in System Settings"
• "Show GBA boot screen in patched AGB_FIRM"

and for the firmware.bin pick it from the guide linked and download the one for your system and copy it into SD/luma and everything should work fine

 

[temper999]

@Ramzh Are you sure you are allowed to give the links to those files?

 

[Ramzh]

Not quite sure however I am not sponsoring anything just tryna help. They are from the Pailect guide I may as well fix it with the the link of the guide

EDIT: FIXED

 

[Margen67]

There was an issue on the Github repo for adding support to the newest firmware but @cell9 has deleted the issue tracker.
https://github.com/44670/BootNTR/issues
https://twitter.com/CodenameNTR/status/733159640343543808

 

[Sigiz]

Use this setup if you have A9LH:

• "Autoboot SysNAND"
• "SysNAND is updated"
• "Force A9LH detection"
• "Show current NAND in System Settings"
• "Show GBA boot screen in patched AGB_FIRM"

and for the firmware.bin pick it from the guide linked and download the one for your system and copy it into SD/luma and everything should work fine

i had recently removed the emunand partition from previous rxtools+menuhax setup
pretty sure i am on sysnand since i had to update from 9.2 to 11.0
as far as luma settings go i thought luma was supposed to show those in emunand

is it because m in sysnand and in luma- emunand that it shows unknown firm? since it isnt loading the firmware.bin?

 

[Ramzh]

i had recently removed the emunand partition from previous rxtools+menuhax setup
pretty sure i am on sysnand since i had to update from 9.2 to 11.0
as far as luma settings go i thought luma was supposed to show those in emunand

is it because m in sysnand and in luma- emunand that it shows unknown firm? since it isnt loading the firmware.bin?

Weird if you are on sysNAND with the NTR firmware.bin it should work.. I had to change the 5.4 Luma to the latest nightly build to make it work, but that was me, you may try it as well and change the arm9loaderhax.bin to the latest nightly build and see if it is working

 

[Sigiz]

so i use star updater , and yea i am running the latest starupdater to update since it comes with the svcbackdoor patched i guess? since without it , bootntr shows "an error has occurred"

 

[Ramzh]

I have no clue why is doing that, if you follow the configuration posted before, have the nightly build, ntr firmware.bin we should have the same setup. Can you just re-check everything and see?

 

[Jaitsu]

Have you tried rebooting it and then *immediately* going to BootNTR? Because I had the same issue ("current firm not supported"/"unknown homemenu version" etc) and it spontaneously resolved itself when I rebooted. No idea why, but hey.

 

[Sigiz]

I have no clue why is doing that, if you follow the configuration posted before, have the nightly build, ntr firmware.bin we should have the same setup. Can you just re-check everything and see?

lemme do it :3
on a side note , by ntr firmware.bin u mean the ntr.bin right?

edit:- tried updating to unsable luma from star updater , no luck

Have you tried rebooting it and then *immediately* going to BootNTR? Because I had the same issue ("current firm not supported"/"unknown homemenu version" etc) and it spontaneously resolved itself when I rebooted. No idea why, but hey.

pretty much most of the time that's the case , i boot up and go straight to the bootntr

 

[Ramzh]

lemme do it :3
on a side note , by ntr firmware.bin u mean the ntr.bin right?

edit:- tried updating to unsable luma from star updater , no luck



pretty much most of the time that's the case , i boot up and go straight to the bootntr

Wrong I mean the file firmare.bin that should be in your SD/luma folder

 

[Sigiz]

worry not i have the ntr.bin in the root and the firmware.bin in the sd/luma folder

 

[Ramzh]

worry not i have the ntr.bin in the root and the firmware.bin in the sd/luma folder

Did you change the firmware.bin with the one mentioned in the Pailect's Guide that I linked you before?

 

[Sigiz]

Did you change the firmware.bin with the one mentioned in the Pailect's Guide that I linked you before?

yes i tried that and the one listed here

 

[Ramzh]

yes i tried that and the one listed here

I am going to try this myself and report on it here give me 10/15 mins

EDIT: just tried that one for the New 3DS and it dosen't work (?) try this if you have an O3DS