Hacking Are hardmod downgrades dead?

  • Thread starter Thread starter Deleted User
  • Start date Start date
  • Views Views 2,451
  • Replies Replies 18
D

Deleted User

Guest
I am curious, can you still hack version 11.4 with a hardmod?
Not that it matters to me but yeah.
 
You need a kernel exploit also.
That doesn't make sense, if you are wired up to a nand chip I don't see why not?
What if someone backed up their nand (without arm9loaderhax) upgraded to 11.4, and tried to restore there nand, could they then hack their 3ds?

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

Hardmod downgrade are basically dead. 11.4 added a NATIVE_FIRM requirement to the homemenu. This basically black screens the system if the respective NATIVE_FIRM isn't present.
Couldn't a hard mod user patch NATIVE_FIRM?
 
That doesn't make sense, if you are wired up to a nand chip I don't see why not?
What if someone backed up their nand (without arm9loaderhax) upgraded to 11.4, and tried to restore there nand, could they then hack their 3ds?
Couldn't a hard mod user patch NATIVE_FIRM?
If you've already backed up your NAND, you can still restore that previous NAND.
You just can't inject the older NATIVE_FIRM into 11.3+, which was how the hardmod used to work. Basically hardmod downgrades worked by dumping the NAND, then injecting an exploitable NATIVE_FIRM into the NAND. Then you could downgrade the system with that NATIVE_FIRM.
11.4 added a NATIVE_FIRM requirement to the system, so you can't inject an exploitable NATIVE_FIRM.
 
  • Like
Reactions: proflayton123
If you've already backed up your NAND, you can still restore that previous NAND.
You just can't inject the older NATIVE_FIRM into 11.3+, which was how the hardmod used to work. Basically hardmod downgrades worked by dumping the NAND, then injecting an exploitable NATIVE_FIRM into the NAND. Then you could downgrade the system with that NATIVE_FIRM.
11.4 added a NATIVE_FIRM requirement to the system, so you can't inject an exploitable NATIVE_FIRM.
there must be a way if you have access to the nand chip, it would be easy if somebody could find out what makes a nand image only work on that system, then you could just edit a nand image on the version you want and make it work.
 
there must be a way if you have access to the nand chip, it would be easy if somebody could find out what makes a nand image only work on that system, then you could just edit a nand image on the version you want and make it work.
SigHAX is aiming to allow something like that. But we still lack the BOOTROM to make sigHAX a reality.
 
SigHAX is aiming to allow something like that. But we still lack the BOOTROM to make sigHAX a reality.
If the bootrom was editable, arm9loaderhax would be obsolete, and every single thing would be unlocked. That would be awesome. It is still only a matter of time before somebody extracts and decrypts the bootrom.
 
  • Like
Reactions: adrifcastr
If the bootrom was editable, arm9loaderhax would be obsolete, and every single thing would be unlocked. That would be awesome. It is still only a matter of time before somebody extracts and decrypts the bootrom.
lml you make that sound so easy
 
there must be a way if you have access to the nand chip, it would be easy if somebody could find out what makes a nand image only work on that system, then you could just edit a nand image on the version you want and make it work.
Not really, as most of the NAND is encrypted with console unique keys, resulting in the old problem of requiring the keys to be able to edit the NAND to be able to dump the keys
 
Not really, as most of the NAND is encrypted with console unique keys, resulting in the old problem of requiring the keys to be able to edit the NAND to be able to dump the keys
even if it is encrypted, it can be decrypted.
 
even if it is encrypted, it can be decrypted.
Then, finding the way to do it.
CTRtransfer need to run using that console arm9 cause it need console self decryption fucntion to be able to write new fw file to nand.
If it's that easy to decrypted nand, people would be able to do hardmod CTRtransfer on any console already.
 
If you've already backed up your NAND, you can still restore that previous NAND.
You just can't inject the older NATIVE_FIRM into 11.3+, which was how the hardmod used to work. Basically hardmod downgrades worked by dumping the NAND, then injecting an exploitable NATIVE_FIRM into the NAND. Then you could downgrade the system with that NATIVE_FIRM.
11.4 added a NATIVE_FIRM requirement to the system, so you can't inject an exploitable NATIVE_FIRM.
11.3 is the one which added.

I am curious, can you still hack version 11.4 with a hardmod?
Not that it matters to me but yeah.
No. 11.3 was the death for the Hardmod and DSi downgrade.
 
Hardmod downgrade are basically dead. 11.4 added a NATIVE_FIRM requirement to the homemenu. This basically black screens the system if the respective NATIVE_FIRM isn't present.
Uhh 11.4 just crashes when a non home menu title launches when a 11.3 nfirm is present (unless someone tested on "real" ofw). Theoretically something could come of it if we can install system titles (test menu allows for titles to load, and I was able to get to the point where homebrew just produced an error using cn).
 
Uhh 11.4 just crashes when a non home menu title launches when a 11.3 nfirm is present (unless someone tested on "real" ofw). Theoretically something could come of it if we can install system titles (test menu allows for titles to load, and I was able to get to the point where homebrew just produced an error using cn).
I feel like everyone is just nutshelling all of my posts in this thread, lol.
That's what my post was saying, it needs a the 11.4 NATIVE_FIRM to work.
I am pretty sure sigHAX is suppose to be something like that.
 

Site & Scene News

Popular threads in this forum