Hacking [Release]BootNTR Selector

[IngeniousDefault]

I noticed after using BootNTR, it takes a little longer now to power off my O3DS. Usually when I power off, the power indicator (blue light) immediately turns off, but now it stays on for a little while.

Anyone experience the same thing? Is this normal?

Yeah that happens sometimes. It's a general "problem" with NTR CFW.

 

[hiten]

Yeah that happens sometimes. It's a general "problem" with NTR CFW.

Ok, thanks.

 

[IngeniousDefault]

I'm using NTR CFW 3.2 very often but since I updated to Selector 2.1 it doesn't auto-boot most of the time. It works if I select it manually.

 

[Nanquitas]

The auto updater doesn't work, at least for me. It doesn't change its status from "Getting infos".

Edit: Works now!

Getting infos is the step when the updater follows the redirections made by GitHub before accessing the file then read the size to download.
If it bugged it was either a GitHub bug as I had just uploaded the file or an updater bug.

It's my first updater, and I probably didn't well handled all the errors that can be returned.
I'll rework it to be more stable. Thanks for the feedback and sorry for the inconvenience.

I noticed after using BootNTR, it takes a little longer now to power off my O3DS. Usually when I power off, the power indicator (blue light) immediately turns off, but now it stays on for a little while.

Anyone experience the same thing? Is this normal?

Yeah that's probably due to the NTR's main thread.
Prefer to shutdown the 3DS with the power menu in the NTR Menu.

I'm using NTR CFW 3.2 very often but since I updated to Selector 2.1 it doesn't auto-boot most of the time. It works if I select it manually.

That's weird. What do you mean by it doesn't auto boot ? You have a message on the left ?

The timer stop only if a key is pressed (any) or if the screen is touched.

 

[IngeniousDefault]

The Selector searches for an update and after that it shows the three icons for the three version of NTR CFW on the left while on the right I got the message that NTR CFW 3.2 will start in one second. But after that the app freezes. The previous version of the Selector had an almost 100% boot rate.

 

[Nanquitas]

Okay, I'll check that too then...

 

[IngeniousDefault]

Okay, I'll check that too then...

I'm really sorry to bother you with that.
I also noted that sometimes if I push a button to switch to another NTR CFW the entire app freezes. But his only happens sometimes while I always can reproduce the "bug" with version 3.2. I deleted all versions of NTR CFW and the config file and launched the app after that so that it can create the files again but the freezes still happen. I'm using a New 3DS with FW 11.2 if this is important to know.

EDIT: The auto-boot freeze also happens sometimes with 3.4.

 

[Nanquitas]

Hmmm, really annoying bugs then.

I'll see what I can do.

 

[temper999]

@Nanquitas why are you using a seperate folder for the config while there will be also the ntr folder under sdmc:\3ds\ntr\ ?

Could the config also be under sdmc:\3ds\ntr\ ?

 

[Nanquitas]

Because I need a folder which is the same for every configuration.

The Nintendo 3DS folder will be on every SD Card as it's created by the console, the 3ds folder is created only by those who use a 3dsx homebrew.

 

[Nanquitas]

Version 2.2 is out.

Hopefully it'll correct the freeze some of you have encountered.

 

[IngeniousDefault]

Version 2.2 is out.

Hopefully it'll correct the freeze some of you have encountered.

Awesome! Will it appear as an update in the app? There is no update message at the moment.

 

[Sonansune]

Version 2.2 is out.

Hopefully it'll correct the freeze some of you have encountered.

weird..... 2.2 freeze at 1 second all the time for 3 tries

 

[Nanquitas]

Hmm, 2.1 broked the updater, I fixed it in the last version.

But it seems unstable. I'll stop uploading the updates until we've confirmed it's 100% working...

 

[IngeniousDefault]

Hmm, 2.1 broked the updater, I fixed it in the last version.

But it seems unstable. I'll stop uploading the updates until we've confirmed it's 100% working...

Yeah. Now it's completely broken. Strange. I guess 11.2 was not that nice to NTR CFW after all.

 

[Nanquitas]

We restraint the problems to one parts (hopefully) so it shouldn't be that long to have a build working.

In the mean time, I suggest you use the previous firmware.bin, even the 2.2 shouldn't have a problem with it.

 

[IngeniousDefault]

We restraint the problems to one parts (hopefully) so it shouldn't be that long to have a build working.

In the mean time, I suggest you use the previous firmware.bin, even the 2.2 shouldn't have a problem with it.

Yeah I should have created a firmware.bin with Decrypt9 before updating. Ah well, not a problem. I can wait for a fixed version. 2.1 worked sometimes so I use this version until a fully working Selector is here.

 

[hiten]

Yeah I should have created a firmware.bin with Decrypt9 before updating. Ah well, not a problem. I can wait for a fixed version. 2.1 worked sometimes so I use this version until a fully working Selector is here.

How to create firmware.bin with Decrypt9?

 

[Sonansune]

How to create firmware.bin with Decrypt9?

sysnand/emunand options ==> miscellaneous ==> ncch firms dump
find native firmXXXXX.bin under file9 directory

 

[Kamui]

version 2.1 works better than 2.2 in my case... 2.2 always stuck