You dont need HBL to downgrade using DSI, after you downgrade 11.0 to 10.4 you can acess HBL using oothax entrypoint of 10.4But how were they able to test it without Homebrew access?
You dont need HBL to downgrade using DSI, after you downgrade 11.0 to 10.4 you can acess HBL using oothax entrypoint of 10.4But how were they able to test it without Homebrew access?
But how were they able to test it without Homebrew access?
That's still being discussed. You're correct tho, we can Downgrade the NATIVE_FIRM to 10.4 but the question is, can we proceed on downgrading the whole system if hbl is still not compativle with 11.1?I've read through this thread but I just want to make sure. I can DSIware downgrade but I can't proceed with Plailect's guide because I can't launch homebrew. Is that correct?
Ah, thanks for the confirmation. I was going to downgrade my friend's console but I guess that'll have to wait.That's still being discussed. You're correct tho, we can Downgrade the NATIVE_FIRM to 10.4 but the question is, can we proceed on downgrading the whole system if hbl is still not compativle with 11.1?
Sent from my SM-N930F using Tapatalk
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.
Sent from my SM-N930F using Tapatalk
I've read through this thread but I just want to make sure. I can DSIware downgrade but I can't proceed with Plailect's guide because I can't launch homebrew. Is that correct?
11.1.0: Browserhax has been patched, you MUST have downgraded your firmware already, then use a non-browser entrypoint
If you are using a game for hax because your browser version is incompatible, you will need to enter Homebrew Launcher using it and install menuhax. After installing menuhax, you no longer need the game to complete the rest of the guide.
The update was JUST released, so probably not yet.Hi , my 3DS is 11.0, I will not be updated for now, do you think that someone working for downgrade to 11.0 → 9.2 ?
A9LH in general is safe with this version release.Maybe a specific situation, but anyone running A9lh with luma region changed sysnand know if it's safe to update? I assume it is since it's not much different, but I don't have a hard mod so don't want to test yet.
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?
That's great! The question now is what payload to install for the secondary exploits.On 11.1 DSiware Downgrade, after you donwgrade the NFIRM to 10.4, you'll have to use the No-Browser version of the guide (as I suspected):
I speak downgrade 3DS version 11.0.0-33 not 11.1.0-34The update was JUST released, so probably not yet.
I thought that blue screen BOOTROM had something to do with the ability to read/write the NAND by the hardmod's card reader. As to say there has to be a rudimentary software running to access the NAND by hardmod./QUOTE]
Well, you can't update the bootrom with a system update.
The forum is not a crystal ball, so you'll have to wait and see. You could always do a NAND backup of 11.0 if you want to update (That is, if you're using A9LH).I speak downgrade 3DS version 11.0.0-33 not 11.1.0-34
OH, oops. Yes, someone's working on a downgrade for 11.0.I speak downgrade 3DS version 11.0.0-33 not 11.1.0-34
That makes things 10x better for me. Is it just the standard 10.4.0-29 payload for oothax?You dont need HBL to downgrade using DSI, after you downgrade 11.0 to 10.4 you can acess HBL using oothax entrypoint of 10.4
Nothing changed in the arm9 code, so the downgrade exploit doesn't change at all.I speak downgrade 3DS version 11.0.0-33 not 11.1.0-34
I do not know if I can make a backup of NAND I have that access hblThe forum is not a crystal ball, so you'll have to wait and see. You could always do a NAND backup of 11.0 if you want to update (That is, if you're using A9LH).
Okay, thank you !OH, oops. Yes, someone's working on a downgrade for 11.0.
I thought that blue screen BOOTROM had something to do with the ability to read/write the NAND by the hardmod's card reader. As to say there has to be a rudimentary software running to access the NAND by hardmod.
Thinking over it that blue screen might also be just a side effect when the card reader accesses the NAND pins, perhaps simply blocking the system from accessing them.
...I remember such a blue screen before the card reader was even connected. I shortened the wires and then the system worked.
That might harden this assumption. If so, a hardmod could never be blocked by a firmware update - if these are simply flash chips with no extra programmable controller inside that would allow some extra communication versus what a simple card reader offers.