Separate names with a comma.
Discussion in '3DS - Tutorials' started by Plailect, Jan 30, 2016.
So who's bored and wants to give this a go?
So glad I am A. Not a noob and B. Downgraded successfully on first try before 10.4 came out and C. Currently 9.2 sysNAND and 10.5 RXtools emuNAND. May the noobs be dealt with so you guys can work on this frankly exciting project! Good luck!
Can I do dis without hardmod?
Lets hope somebody works on this because it looks like nobody is showing real effort to test it out.
— Posts automatically merged - Please don't double post! —
Yes you can do this without a hardmod but you need to hard mod. ¿Understand?
@Plailect Pretty sure the files that 3DNUS downloads are fully encrypted. In the case of the N3DS files, they are double encrypted. Well technically the native_firms downloaded this way are double encrypted for O3DS and triple encrypted for N3DS, since the cia file itself is encryped, and the actual native_firm file inside that is encrypted as well (and doubly so for the N3DS).
@Plailect the cia files downloaded with 3DNus are encrypted, you need to decrypt it using Decrypt9 in a 3ds with firmware 9.2 or lower.
Wonder if it would be easier to have 3dnus just not generate the cia file and work directly with the 000000XX file it downloads (since that is the actual "contents" that your batch file is extracting in the first place. No idea how this would be impacted by possible encryption though.
Maybe @cearp could help with that or give some insight.
PM me with the process (and it would be even better if you still have the decrypted firmware) and I'll add it, as I said this is completely untested.
Well.... from what I am seeing his batch is expecting the presense of a firm0.bin and firm1.bin, which I am not seeing how those are acquired or where they would come from. I ASSUME they are supposed to be the fully decrypted contents of the firm0/firm1 partitions.
You cannot add firmware files as they are copyrighted and against the rules to upload or link directly to them.
I am aware, I was going to include instructions to find a pastebin with them, similar to the ReiNAND thread.
No hablo Inglés
I had this thought a while ago. It was already known that you could get the xorpads and rewrite FIRM with a hardmod if you had a decrypted version of the same FIRM, I'm surprised no one's thought to use this to downgrade until now. While it is untested I see no reason why it wouldn't work. And it's more or less unpatchable as well.
It was useless before because you could only go between minor revisions, which didn't allow you to go back far enough for CFW.
Question? When and if you downgrade your firm with the new image would Homenuhax or Ninjhax even work or is the only thing it needs to run is lower firm? This sounds too simple and almost like a permanent downgrade solution for all firmwares that ever get released.
Not to mention that all they need to do to fuck it up is make a major revision to the firm. A "2.60" native_firm would likely destroy this.
Me neither... Oh wait!!
Ontopic: Good luck for the ones trying it!!!
It would only allow exploits that were patched by the newer revision to work again (like mch2) and while the overall concept is unpatchable, it is possible for them to make it impossible for us to reach a workable firmware version by making a new kernel version release.
This is amazing seeing that a simple hypothesis from @Apache Thunder became an, although highly untested, and non-noobfiendly, became something that we could work with! Its reasons like this that I'm glad to become part of the community.