Same, but I was on 9.2 and I didn't know there was cfw.
I had a 9.2 O3DS XL that was running rxTools... And it was stolen. Bought a n3DS that was 9.5, that's the game.
Same, but I was on 9.2 and I didn't know there was cfw.
finally its time for N3DS/XL 9.3+ firmware exploits, if its real its a BIG SLAP on the face for Gateshit lol cant wait for it
No, there is no (public) kernel exploit for 9.3+ right now.So there's no exploit or vulnerability?
9.9 arm11 kernel vulnerability is dead for now?
> If you know how to find the actual code of SVC, please tell me.You really shouldn't make a thread until you at least have something. Anything...
What does this mean?> If you know how to find the actual code of SVC, please tell me.
See?
So I need other developers help. I don't know 3DS well and I don't have so much time.What does this mean?
the SVC code is in native firm... It's already been pointed out that this is useless... it can't be exploited...So I need other developers help. I don't know 3DS well and I don't have so much time.
I want to confirm that. The results of my experiments conflict with the description on 3dbrew.org.the SVC code is in native firm... It's already been pointed out that this is useless... it can't be exploited...
If you mean your first post's experiments then no they don't...I want to confirm that. The results of my experiments conflict with the description on 3dbrew.org.
A question are you sure you can go anywhere with this?I want to confirm that. The results of my experiments conflict with the description on 3dbrew.org.
If you mean your first post's experiments then no they don't...
According to 3dbrew.org, s32_processorid should be larger than -4, which is the code-reversed value of the number of n3ds core.Update on 3dbrew.org
The previous version also allowed large negative s32_processorid values(negative processorid values are special values not actual procids), but it appears using values like that won't actually do anything(meaning no crash) besides the thread not running / thread not running for a while(besides triggering a kernelpanic with certain s32_processorid value(s)).
He isn't, that's the whole point of doing research. He needs to know for sure if it can be exploited or not.A question are you sure you can go anywhere with this?
I'm not sure "go anywhere" means, but if it means whether I can write the data anywhere, I'm not sure.A question are you sure you can go anywhere with this?
Oh I see but if your "experiments" work out do you know what to do next ?I'm not sure "go anywhere" means, but if it means whether I can write the data anywhere, I'm not sure.
Oh I see but if your "experiments" work out do you know what to do next ?