Hacking New Update Question

[Kurausukun]

I have CFW using A9LH and Luma3DS (I used plailect's 5-step guide before he updated it to the current 3-step one). I'm currently on 11.0; if I update to 11.1, what will become unusable, and can I update it?

 

[Posghetti]

Pretty much everything works on 11.1 besides NTR (AFAIK there's no 11.1 native support for NTR, but there's a way to use NTR on 11.1 ; downgrading the Home Menu Ver) Also 11.1 payloads are out for use with The HBL CIA so yeah, just NTR won't work "natively"

 

[Kurausukun]

Alright, thanks. It's good to know stuff mostly works, just in case I need to update in a pinch. Is NTR still actively being updated, or should I expect it never to work with 11.1?

 

[Posghetti]

Alright, thanks. It's good to know stuff mostly works, just in case I need to update in a pinch. Is NTR still actively being updated, or should I expect it never to work with 11.1?

I'm actually not too sure about that. I barely use NTR at all so hopefully someone with more knowledge than me can answer that for you.

 

[Zyteus]

Alright, thanks. It's good to know stuff mostly works, just in case I need to update in a pinch. Is NTR still actively being updated, or should I expect it never to work with 11.1?

The original NTR is no longer being updated. This NTR is being updated and will be updated to work with 11.1 http://gbatemp.net/threads/release-bootntr-selector.432911/

 

[Kurausukun]

Alright, thanks a lot for the help.

 

[Aroth]

The original NTR is no longer being updated. This NTR is being updated and will be updated to work with 11.1 http://gbatemp.net/threads/release-bootntr-selector.432911/

Is it NTR itself that wont be updated for 11.1, or BootNTR?

 

[Zyteus]

Is it NTR itself that wont be updated for 11.1, or BootNTR?

I'm not too sure, but you might be able to learn more here https://gbatemp.net/threads/release-ntr-cfw-3-2-with-experimental-real-time-save-feature.385142/
All I know is that The New NTR CFW will be updated to work with 11.1.

 

[astronautlevel]

NTR has been updated for 11.1 (I did it a few days ago), see here: http://gbatemp.net/threads/bootntr-11-1-0-34-homemenu-support.441566/

 

[TheCyberQuake]

I'm actually not too sure about that. I barely use NTR at all so hopefully someone with more knowledge than me can answer that for you.

The latest BootNTR works with the newest home menu now. It just needs 11.0 Native firm in order to work, which can be achieve by getting an 11.0 firmware.bin from either the luma wiki or from That ISO Site, and then using the latest stable release of luma-dev (or other compatible CFW, standard luma won't read firmware.bin).
Also afaik NTR.bin is the underlying "CFW", but BootNTR is the only thing needed to keep it running on any firmware.

 

[Kurausukun]

So basically, in order to get it truly working on 11.1, we just need to wait for the person behind BootNTR to update it for compatibility with 11.1 NFIRM, right?

 

[Aroth]

I'm not too sure, but you might be able to learn more here https://gbatemp.net/threads/release-ntr-cfw-3-2-with-experimental-real-time-save-feature.385142/
All I know is that The New NTR CFW will be updated to work with 11.1.

Thought the latest version of NTR was like 3.4, also, where can I find information on this New NTR CFW?

NTR has been updated for 11.1 (I did it a few days ago), see here: http://gbatemp.net/threads/bootntr-11-1-0-34-homemenu-support.441566/

The latest BootNTR works with the newest home menu now. It just needs 11.0 Native firm in order to work, which can be achieve by getting an 11.0 firmware.bin from either the luma wiki or from That ISO Site, and then using the latest stable release of luma-dev (or other compatible CFW, standard luma won't read firmware.bin).
Also afaik NTR.bin is the underlying "CFW", but BootNTR is the only thing needed to keep it running on any firmware.

While this is certainly a viable method, it would be best if the programs involved were updated to work with 11.1 completely. Some people might be wary of messing with a dev version of Luma3DS, and others might mess with things they shouldn't and then expect people here to "fix" it for them.

--------------------- MERGED ---------------------------

Just checked that thread and holy shit. Fuck Margen67. Fuck that dude sideways with a red-hot rusty jet turbine.

As far as I am concerned, this "New NTR" thing is useless since it will be .3dsx only. Won't be able to handle real-time debugging, which is required for any sort of cheat access. This means we are stuck relying on GW for cheats which is fucking bullshit.

 

[astronautlevel]

Thought the latest version of NTR was like 3.4, also, where can I find information on this New NTR CFW?





While this is certainly a viable method, it would be best if the programs involved were updated to work with 11.1 completely. Some people might be wary of messing with a dev version of Luma3DS, and others might mess with things they shouldn't and then expect people here to "fix" it for them.

--------------------- MERGED ---------------------------

Just checked that thread and holy shit. Fuck Margen67. Fuck that dude sideways with a red-hot rusty jet turbine.

As far as I am concerned, this "New NTR" thing is useless since it will be .3dsx only. Won't be able to handle real-time debugging, which is required for any sort of cheat access. This means we are stuck relying on GW for cheats which is fucking bullshit.

I'm not sure where you're getting most of that, even when cell9 was around we just used an older firmware, he never updated it until steveice found the offsets. I do plan on finding the new offsets to make it fully compatible with 11.1. I have no idea what this "new NTR" thing is though, and it's certainly not Anything im making

 

[Zyteus]

Thought the latest version of NTR was like 3.4, also, where can I find information on this New NTR CFW?





While this is certainly a viable method, it would be best if the programs involved were updated to work with 11.1 completely. Some people might be wary of messing with a dev version of Luma3DS, and others might mess with things they shouldn't and then expect people here to "fix" it for them.

--------------------- MERGED ---------------------------

Just checked that thread and holy shit. Fuck Margen67. Fuck that dude sideways with a red-hot rusty jet turbine.

As far as I am concerned, this "New NTR" thing is useless since it will be .3dsx only. Won't be able to handle real-time debugging, which is required for any sort of cheat access. This means we are stuck relying on GW for cheats which is fucking bullshit.

http://gbatemp.net/threads/release-bootntr-selector.432911/ I use this and it allows me to use plugins and debugging. It is .CIA so you can install it onto your homemenu

 

[Aroth]

I'm not sure where you're getting most of that, even when cell9 was around we just used an older firmware, he never updated it until steveice found the offsets. I do plan on finding the new offsets to make it fully compatible with 11.1. I have no idea what this "new NTR" thing is though, and it's certainly not Anything im making

Afaik it was working with the latest Native_firm (11.0, what people refer to when they say firmware.bin). The current method of making NTR work again requires using a developer build of Luma (which some people might not want to mess with, and has tools/features that can likely brick a 3ds if used improperly). The "new NTR" thing is, afaik, cell9's potential new project to port some of the NTR features like video capture/streaming and screenshotting to a .3dsx program.

http://gbatemp.net/threads/release-bootntr-selector.432911/ I use this and it allows me to use plugins and debugging. It is .CIA so you can install it onto your homemenu

That simply lets you select which version of NTR to load (3.2, 3.4, etc) It STILL requires the 11.0 or lower native_firm, which still requires using the dev build of luma3ds if you have updated your system to 11.1 already.

 

[astronautlevel]

Afaik it was working with the latest Native_firm (11.0, what people refer to when they say firmware.bin). The current method of making NTR work again requires using a developer build of Luma (which some people might not want to mess with, and has tools/features that can likely brick a 3ds if used improperly). The "new NTR" thing is, afaik, cell9's potential new project to port some of the NTR features like video capture/streaming and screenshotting to a .3dsx program.

Like I said, there was a long time when it didn't work and we had to use a firmware.bin from 10.2 on n3ds or 9.6 on o3ds

 

[Zyteus]

Afaik it was working with the latest Native_firm (11.0, what people refer to when they say firmware.bin). The current method of making NTR work again requires using a developer build of Luma (which some people might not want to mess with, and has tools/features that can likely brick a 3ds if used improperly). The "new NTR" thing is, afaik, cell9's potential new project to port some of the NTR features like video capture/streaming and screenshotting to a .3dsx program.



That simply lets you select which version of NTR to load (3.2, 3.4, etc) It STILL requires the 11.0 or lower native_firm, which still requires using the dev build of luma3ds if you have updated your system to 11.1 already.

Yeah I'm still on 11.0 and with regular Luma. That's all I know about this

 

[astronautlevel]

Like I said, there was a long time when it didn't work and we had to use a firmware.bin from 10.2 on n3ds or 9.6 on o3ds

Also, I didn't read your post closely @Aroth, but the dev version of luma isn't dangerous (none of the features can cause a brick), and in fact the dev and regular versions have been merged in the latest commits.

 

[TheCyberQuake]

Also, I didn't read your post closely @Aroth, but the dev version of luma isn't dangerous (none of the features can cause a brick), and in fact the dev and regular versions have been merged in the latest commits.

Really no modern CFW can cause a brick as they only read from NAND. The worst I can see happening is using a power-user CFW like corbenik, not enabling firm protection and then updating. But that wouldn't brick, it would just remove A9LH.

 

[astronautlevel]

Really no modern CFW can cause a brick as they only read from NAND. The worst I can see happening is using a power-user CFW like corbenik, not enabling firm protection and then updating. But that wouldn't brick, it would just remove A9LH.

Unless you were on an n3ds and updated, in which case yes, it would brick