Hacking FW 11.0 and NTR plugin?

  • Thread starter Thread starter naddel81
  • Start date Start date
  • Views Views 2,992
  • Replies Replies 25

naddel81

Well-Known Member
Member
Joined
Dec 14, 2009
Messages
2,590
Reaction score
429
Trophies
1
XP
4,739
Country
United States
hi @ all,

I use reinand and would like to know if I can safely update my emunand or is NTR plugin still not working on 11.0?

best wishes!
 
11.0 doesn't work with NTR due to svcBackDoor being patched, the exploit that made it run
This is only correct if you're using the new NATIVE_FIRM. Most CFWs are using 10.2 FIRM and can use NTR on 11.0 because they're using an exploitable FIRM.
hi @ all,

I use reinand and would like to know if I can safely update my emunand or is NTR plugin still not working on 11.0?

best wishes!
You should be fine using NTR with ReiNand because it uses 10.2 FIRM.
 
Last edited by RedBlueGreen,
It's still 11.0, but loads 10.2 FIRM. 11.0 EmuNAND is not the same as vanilla 11.0.
Of course it's not the same as vanilla 11.0, it's a custom firmware after all

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

works fine on 11.0 emunand
do you even use ntr?
On my 9.2 sysNAND yes
 
i'm using luma3ds + a9lh + NTRFirmware + Downgraded nativefirm (Native104.cia) in sysnand 11.0, Working Fine :p
 
emuNAND is a second NAND. You have to copy your sysNAND to emuNAND first, but unlink them later by generating a new sysNAND. Then you can update emuNAND to whatever version you want. If you brick your emuNAND, just reflash a backup. You never even touch sysNAND when you have emuNAND
 
What exactly do you mean with emuNAND version 11.0? I thought emuNAND was just a clone of your sysNAND, and it isn't a hack that gets updated?

You can update your EmuNAND without updating your SysNAND. That's one of the main points of having an EmuNAND in the first place.
 
But what's so bad about updating sysNAND? My friends did it and they had no problems at all?
Chances of messing/losing the exploit or brick due to some messing around. If emuNAND messed up you can simply copy sysNAND to emuNAND again.

In case of A9LH you may keep using just the sysNAND and still be safe but like I said messing with emuNAND is still safer than messing with sysNAND.
 
But what's so bad about updating sysNAND? My friends did it and they had no problems at all?

Because if you are, let's say, running a 9.2 SysNAND with a 10.7 EmuNAND and update your SysNAND, you will simply lose kernel access which is available on 9.2 to the *hax, and lose access to your EmuNAND. Since 9.3, *hax lost kernel access, that's why 9.2 is so popular and precious (EDIT: speaking about mainstream entry points, not memchunkhax2)

Also, you don't want to mess with the SysNAND since if it breaks, you can only fix it with a hardmod.

Of course, I'm not talking about updated SysNAND with A9LH, which is completely different and safe.
 
Last edited by Kyojin,
I have 11.0 on my new3ds and NTR dont work. I dont know about this "nativefirmware" and i cant find a "Firmware.bin". Can anyone help me?
 

Site & Scene News

Popular threads in this forum