Just wanted to verify hardmod still working under 11.1 by myself. Tests on a 2DS-EUR.
I "downgraded" with an old 10.3 native (=no hacks) hardmod image I had in backup, then let the system upgrade to 11.1.
After checking 11.1 was "native" (no luma, no CIA-icons) I downloaded it with my hardmod (I like archiving this stuff) then wrote a 11.0 A9LH-sysNAND.bin back to the EEPROM.
The 2DS came up with the luma splash screen and CIAs showing up again. I was able to upgrade again to 11.1 - this time with A9LH intact.
So I think chances are good to "downgrade" a 11.1 image's NATIVE_FIRM to 10.4 (see Plailect's tutorial).
Or in other words: the 11.1 upgrade did not inhibit the blue BOOTROM-screen when a hardmod is plugged in - or shorter: hardmod still working (on my 2DS).
But without being able to start homebrew you cannot go further if you want to do an A9LH installation.
[EDIT]Sweet!
I'm out of my office until next sunday so I couldn't test... in cases like this, I usually test by myself... thanks for the confirmation!
they just added in a SVC access Patch in the dev branch pretty much restoring these exploits things like NTR and such used, and in theory for emulators that needed these would get dynarec back./Why the DEV branch of Luma?
No, not quite. Normal luma patches svcBackDoor, also.they just added in a SVC access Patch in the dev branch pretty much restoring these exploits things like NTR and such used, and in theory for emulators that needed these would get dynarec back./
Normal branch doesn't load firmware.bin, dev branch does.Why the DEV branch of Luma? to use boot NTR with 11.1? I thought Luma reapplied SVC backdoor no matter the branch...
We would've downgraded the firm but how can we access sysdowngrader/plaisysupdater if hbl entry is 'broken' on 11.1? (Sorry for noob question)[EDIT]
While I was writing this, @Plailect updated the hardmod downgrade page and it is confirmed that it Works with 11.1:
https://github.com/Plailect/Guide/wiki/Hardmod-Downgrade
[/EDIT]
What made you think that a firmware update would block your access to hardmod (Reading NAND chip)?
If a FW update was able to block access to the NAND chip (via hardmod), don't you think it would also block A9LH access?
It was confirmed, DSI Downgrade still working
https://github.com/Plailect/Guide/wiki/DSiWare-Downgrade
Does DSiWare downgrading still work? (since one would have to update to latest FW to do the system transfer)
Does DSiWare downgrading still work? (since one would have to update to latest FW to do the system transfer)
It was confirmed, DSI Downgrade still working
https://github.com/Plailect/Guide/wiki/DSiWare-Downgrade
We would've downgraded the firm but how can we access decrypt9 if hbl entry is 'broken' on 11.1? (Sorry for noob question)
Sent from my SM-N930F using Tapatalk
yes its confirmed in the plailect guideDoes DSiWare downgrading still work? (since one would have to update to latest FW to do the system transfer)
But how were they able to test it without Homebrew access?yes its confirmed in the plailect guide
They'll wait. Probably won't take too long for BrowserHax to come backBut how were they able to test it without Hombrew access?
So we still use the 11.0 payload for the secondary exploits? Because that's what I've been using on DSiWare downgrades before this new update came.I may be way wrong but after you downgrade the NFIRM to 10.4, won't it be possible to use the payload of it on CART *Haxs (Oot, V, CN, whatever)?
If not, I'm seeing the whole procedure in a very twisted way.
someone a few pages Said it worked.Has anyone who still has rxtools updated to this latest firmware? Is it working fine?