No one knows yet. It's probably going to be a homebrew. So you just need a *hax entrypoint and you should be good.What actually slowhax is on the 3ds 11.1.0-34J system? Will slowhax requires dsiware software to purchase or only run an program specified for the exploit?
Does that entrypoint needs a game cartidge to work?Or just some files on SD card?No one knows yet. It's probably going to be a homebrew. So you just need a *hax entrypoint and you should be good.
https://plailect.github.io/Guide/get-startedDoes that entrypoint needs a game cartidge to work?Or just some files on SD card?
After the author releases the slowhax exploit for 3ds 11.1.0-34J,does that means i need a game cartidge or something for the program to run?Or using the current entrypoint?But my 3ds 11.1.0-34J haven't hacked from the beginning
>thinks slowhax is ever going to release
Guess thats why its called slowhax
(I know why its called that)
I am on 11.0 too, since I softbricked and i've been waiting for a kernel exploit since march, I dont have any hope leftThe people who have 11.0/11.1 (like me) needs the hope that slowhax is going to be released "Soon ™"
I am on 11.0 too, since I softbricked and i've been waiting for a kernel exploit since march, I dont have any hope left
I thought it will be out till october but that didnt happenSome people said that it's going to be released on/after the 33C3. Every "huge" exploit was released there. The 33C3 take place between Christmas and the New Year. So we still have to wait at least a month.
How safe will it be when it's finished?There are a few different slowhax, actually. Both will get you what amounts to basically arm11 kernel access if exploited correctly. I'm currently working on slowhax myself, and me and someone else are planning to release exploits at the same time, I'll be exploiting the "original" (first publically documented on 3dbrew) slowhax (the other is veryslowpidhax, which will take quite a lot longer)
Estimate for when it'll be done, I honestly have no clue, it'll be done when it's done. On that note, I've just finished my testing setup so I can test without waiting hours (using a CFW and kernel access via it to patch things) and I've been messing around with timing. Looks like on old 3ds it'll be ~2 hours at least. On n3ds, it can be faster (using the extra cores and speed, ofc).
Once the exploit is finished, it'll be able to be run under any *hax entrypoint and should be relatively simple to run, you just have to wait
There are a few different slowhax, actually. Both will get you what amounts to basically arm11 kernel access if exploited correctly. I'm currently working on slowhax myself, and me and someone else are planning to release exploits at the same time, I'll be exploiting the "original" (first publically documented on 3dbrew) slowhax (the other is veryslowpidhax, which will take quite a lot longer)
Estimate for when it'll be done, I honestly have no clue, it'll be done when it's done. On that note, I've just finished my testing setup so I can test without waiting hours (using a CFW and kernel access via it to patch things) and I've been messing around with timing. Looks like on old 3ds it'll be ~2 hours at least. On n3ds, it can be faster (using the extra cores and speed, ofc).
Once the exploit is finished, it'll be able to be run under any *hax entrypoint and should be relatively simple to run, you just have to wait
It'll be as safe or safer than mch2 (since that has the chance of making the kernel crash mid downgrade due to corrupting some kernel objects) and will allow a user to install DSiwarehax using only one console that's on 11.1 or below. I've been working on it on-and-off for a week or so now, though most of that was me messing around with simple stuff, and dealing with a few stupid bugs/mistakes (it helps to enable the "all SVCs available" patch when trying to use an SVC which normally isn't available, heh) my patching code for making things go quick (again, under CFW) only took about an hour to write (and it really shouldn't have taken that long, but I was writing code when sleepy, which never gets me anywhere good) but the last thing I did was make sure that worked, and it was fine... Now comes the harder (arguably more fun, though) part which is actually exploiting the kernel. I have a few ideas, though the details are fuzzy at this point. I'll probably focus on that tomorrow/after I get some sleepHow safe will it be when it's finished?
Edit:Also, how long have you been working on this?
the other is veryslowpidhax, which will take quite a lot longer