send it to mass.This is not related to this specific exploit, but about a research i'm doing that can lead to the same results.
So, i need help and have a fcram dump from a old3ds firmware 10.1.
This can be easily achieved with an emunand and a cfw i guess, maybe rxtools.
No, I confirmed it's actually "Data Abort" with CakesFW."besides triggering a kernelpanic with certain s32_processorid value(s)" <--- That's probably the crash you're getting.
So this has some water still?No, I confirmed it's actually "Data Abort" with CakesFW.
A thread such as this, with an interesting idea and maybe potential to be looked further into, has simply turned into a huge clusterfuck cuz ppl can't hold their willies and simply wait for something relevant to be said.
I'm sure that "Yay, I can't wait to use it" or "Please halp, I already updated" will greatly contribute to this thread...
To everybody: This does nothing. This is nothing. This isn't an exploit. We still need to find one. This just shows it "might" be possible. Even though we've known about this before 10.0 even released.
12:44 <@profi200> And the ARM11 kernel thread is still not dead but it was confirmed multiple times that the vuln is useless.
12:47 <@profi200> That vuln does nothing which could be useful.
huh? a little more explanation please.And isn't it impossible to downgrade from 9.9 to 9.2 due to the new encryption anyway? At least on n3DS.
I was told the lowest you could downgrade to was 9.6 or so on n3DS. As that's when the new encryption was introduced. I don't know if that's correct or not though. I think it is.huh? a little more explanation please.
Since the 9.6 update, the N3DS NATIVE_FIRM uses a new encryption. That's the reason emuNAND can't be updated higher than 9.5 on New 3DS.huh? a little more explanation please.
Since the 9.6 update, the N3DS NATIVE_FIRM uses a new encryption. That's the reason why emuNAND can't be updated higher than 9.5 on New 3DS.
Ah, I read that wrong, thanks guys!I was told the lowest you could downgrade to was 9.6 or so on n3DS. As that's when the new encryption was introduced. I don't know if that's correct or not though. I think it is.
English pleaseNo, I confirmed it's actually "Data Abort" with CakesFW.
He's not a native english speaker. But a really nice guy.English please
I quoted the wrong post I wanted to quote @Steveice10, what does that even mean "besides triggering a kernelpanic with certain s32_processorid value(s)"?He's not a native english speaker. But a really nice guy.
ah, ok bud l8r!I quoted the wrong post I wanted to quote @Steveice10, what does that even mean "besides triggering a kernelpanic with certain s32_processorid value(s)"?