Homebrew [ANNOUNCE] Yellows8 has updated the 3ds_browserhax_common to support >=9.9 O3DS, n3DS

[Psi-hate]

@MassExplosion213 When you said that we can't downgrade past 9.6 due to NATIVE_FIRM being locked by ARM9, you're (probably) wrong.

 

[DiegitusXD]

@MassExplosion213 When you said that we can't downgrade past 9.6 due to NATIVE_FIRM being locked by ARM9, you're (probably) wrong.

Why?

 

[Psi-hate]

Why?

@shinyquagsire23 and their team are one of the "most" reliable public sources when it comes to asking about what we can and can't do (They've told us so much, yet we took it for granted like always). He has been tinkering with the 3ds back when KARL was a thing and knows quite a bit since him and his team have been working on their own CFW and have researched so much. I had a convo with him a while ago, back when I thought we couldn't touch Native_Firm unless arm9hax but he stated otherwise giving a small explanation. If he could clear it up a little, I'm sure some of the people will comprehend that at least downgrading should be achievable.

 

[shinyquagsire23]

@shinyquagsire23 and their team are one of the "most" reliable public sources when it comes to asking about what we can and can't do (They've told us so much, yet we took it for granted like always). He has been tinkering with the 3ds back when KARL was a thing and knows quite a bit since him and his team have been working on their own CFW and have researched so much. I had a convo with him a while ago, back when I thought we couldn't touch Native_Firm unless arm9hax but he stated otherwise giving a small explanation. If he could clear it up a little, I'm sure some of the people will comprehend that at least downgrading should be achievable.

Basically, all you need to install .cias is ARM11 kernel access. But these can only be signed .cias, ARM9 kernel is needed for unsigned .cias. There is downgrading protection with system apps and normal apps, however it's flawed: You can delete an app and then install it directly afterwards, effectively making these protections void. Thus the MSET downgrade hack was formed. So in theory, if you had ARM11 kernel access you could do this remove->install trick on all system apps and modules, including the NATIVE_FIRM title. To remedy the two stored straight on the NAND used by the bootloader, you actually already have the xorpads needed for those. If you know what version you're already on, you can use that NATIVE_FIRM image to retrieve an xorpad for it, and use that xorpad to write an older NATIVE_FIRM (note, these are still signed FIRM images here). This probably isn't possible though for the N3DS, due the fact that the 9.6 and up NATIVE_FIRM binaries are stuck behind new encryption. You could at least though return some usermode exploits I suppose.

You might say though, why not just write the NATIVE_FIRM only? This could maybe work for a few firmware versions with minimal updates relying on new stuff in the FIRM, but if the firmware introduced any significant changes it will most likely fail to work.

 

[NeoSlyde]

Basically, all you need to install .cias is ARM11 kernel access. But these can only be signed .cias, ARM9 kernel is needed for unsigned .cias. There is downgrading protection with system apps and normal apps, however it's flawed: You can delete an app and then install it directly afterwards, effectively making these protections void. Thus the MSET downgrade hack was formed. So in theory, if you had ARM11 kernel access you could do this remove->install trick on all system apps and modules, including the NATIVE_FIRM title. To remedy the two stored straight on the NAND used by the bootloader, you actually already have the xorpads needed for those. If you know what version you're already on, you can use that NATIVE_FIRM image to retrieve an xorpad for it, and use that xorpad to write an older NATIVE_FIRM (note, these are still signed FIRM images here). This probably isn't possible though for the N3DS, due the fact that the 9.6 and up NATIVE_FIRM binaries are stuck behind new encryption. You could at least though return some usermode exploits I suppose.

You might say though, why not just write the NATIVE_FIRM only? This could maybe work for a few firmware versions with minimal updates relying on new stuff in the FIRM, but if the firmware introduced any significant changes it will most likely fail to work.

I didnt understand anything!!!
In english please??

 

[guitarheroknight]

Basically, all you need to install .cias is ARM11 kernel access. But these can only be signed .cias, ARM9 kernel is needed for unsigned .cias. There is downgrading protection with system apps and normal apps, however it's flawed: You can delete an app and then install it directly afterwards, effectively making these protections void. Thus the MSET downgrade hack was formed. So in theory, if you had ARM11 kernel access you could do this remove->install trick on all system apps and modules, including the NATIVE_FIRM title. To remedy the two stored straight on the NAND used by the bootloader, you actually already have the xorpads needed for those. If you know what version you're already on, you can use that NATIVE_FIRM image to retrieve an xorpad for it, and use that xorpad to write an older NATIVE_FIRM (note, these are still signed FIRM images here). This probably isn't possible though for the N3DS, due the fact that the 9.6 and up NATIVE_FIRM binaries are stuck behind new encryption. You could at least though return some usermode exploits I suppose.

You might say though, why not just write the NATIVE_FIRM only? This could maybe work for a few firmware versions with minimal updates relying on new stuff in the FIRM, but if the firmware introduced any significant changes it will most likely fail to work.

So basically if someone were to publicly release an ARM11 kernel between 9.2 - 9.5 the downgrade function could be viable again? What about ARM9?

 

[Psi-hate]

Basically, all you need to install .cias is ARM11 kernel access. But these can only be signed .cias, ARM9 kernel is needed for unsigned .cias. There is downgrading protection with system apps and normal apps, however it's flawed: You can delete an app and then install it directly afterwards, effectively making these protections void. Thus the MSET downgrade hack was formed. So in theory, if you had ARM11 kernel access you could do this remove->install trick on all system apps and modules, including the NATIVE_FIRM title. To remedy the two stored straight on the NAND used by the bootloader, you actually already have the xorpads needed for those. If you know what version you're already on, you can use that NATIVE_FIRM image to retrieve an xorpad for it, and use that xorpad to write an older NATIVE_FIRM (note, these are still signed FIRM images here). This probably isn't possible though for the N3DS, due the fact that the 9.6 and up NATIVE_FIRM binaries are stuck behind new encryption. You could at least though return some usermode exploits I suppose.

You might say though, why not just write the NATIVE_FIRM only? This could maybe work for a few firmware versions with minimal updates relying on new stuff in the FIRM, but if the firmware introduced any significant changes it will most likely fail to work.

I really appreciate the explanation! Since N3DS is borked until those keys are out and about, that's one downside but at least O3DS users have a chance at downgrading.

 

[DiegitusXD]

So basically if someone were to publicly release an ARM11 kernel between 9.2 - 9.5 the downgrade function could be viable again? What about ARM9?

But only 9.5?,what about 9.9?

 

[Jwiz33]

Maybe. But gotta test it first.

This allows arm11 kernel on the latest firmware? How?

 

[leerpsp]

So basically if someone were to publicly release an ARM11 kernel between 9.2 - 9.5 the downgrade function could be viable again? What about ARM9?

with 9.9 as well if he can get the ARM11 Kernal working like he was talking about.

 

[Psi-hate]

So basically if someone were to publicly release an ARM11 kernel between 9.2 - 9.5 the downgrade function could be viable again? What about ARM9?

But only 9.5?,what about 9.9?

O3DS is able to do 9.9 downgradin if Arm11 kernel is achievable, while N3DS is 9.5 and below due to encyption 9.6+

 

[guitarheroknight]

But only 9.5?,what about 9.9?

Sadly the 9.6 encryption keys need to be broken, until then no >9.5 EmuNand (and no possible downgrading).

 

[leerpsp]

I would just like to downgrade so i can back up my 3ds games i have to install on my 3ds so i don't have to carry around all my 3ds cards with me.

 

[DiegitusXD]

Sadly the 9.6 encryption keys need to be broken, until then no >9.5 EmuNand (and no possible downgrading).

So for 9.9...nothing!?

 

[NeoSlyde]

So for 9.9...nothing!?

Only for new 3ds
Old 3ds is easy

 

[Carnelian]

Just question do it will possible to get cia files in 9.9.0-26 one day or never?

 

[guitarheroknight]

So for 9.9...nothing!?

On the N3DS sadly no, but O3DS could be downgradeable.

 

[Psi-hate]

So for 9.9...nothing!?

For N3DS, yes until there's an arm9 exploit but that would make downgrading even more pointless.

 

[DiegitusXD]

On the N3DS sadly no, but O3DS could be downgradeable.

Really!!??

 

[VegaRoXas]

Only for new 3ds
Old 3ds is easy

"easy" xD