mrrraou / waithax Goto Github PK

There's plenty of ways to calculate how much time is left, but it seems (says the person who knows nothing about hacking on a 3DS) like this should be a fairly trivial addition.

I'm guesstimating 15 lines on the idea of ensuring that at least one ETA line is visible on the screen.

Since the timing seems to be fairly fixed, the timing algorithm wouldn't need to be particularly complicated - (time_now - time_at_last_print) / iterations_per_print * remaining_iterations) should suffice.

Additionally, it'd provide some interesting diagnostic data: it'd be much faster to determine if Waithax is running at N3DS speed or not, and you could tell if the reports of it taking an hour and 40 minutes were in fact that long (as well as whether the process was slowing down or just started that slow -- the former would cause ETA to go up)

(Aside: does the ARM11 do any sort of thermal throttling? I've never felt my DS get warm before though.)

My friend thought it was a good idea to build and run it for fun so I build it for him and he ran it. The thing is, it's been over 1 1/2 hours and it's still not done.

He's not a New 3DS and we shut the 3DS down at 00a1000(he thinks, can't remember)

Known issue. Due to some invalid handle or a corrupted KObjectLink.

My o3ds xl says its complete when i go into to FBI says failed to get kernel access plz help

Section III Step 6 of the new Waithax 11.0/11.1 downgrade method i get the following message after selecting 4swords:

Loading the savedata from SD...
Preparing exploit installation...
Getting AM-module PID...
SVCs will now be used which are normally not accessible, this will hang if these are not accessible.

My o3ds xl says its complete when i go into to its says failed to get kernel access plz help

I've been following the steps with the new 3dsguide, got to the homebrew launcher via soundhax, and launched safehax. I waited fand after a while "Patching ARM11...". It has been there for over an hour and i don't know if it is safe to reboot my console
Running 11.0 o3dsxl

Issue introduced this
and tested with n3ds 10.3

Refs

• nedwill/fasthax#41
• nedwill/fasthax@1a1e73845fb

Take the distance we are from the overflow of the refcount, and use that to incrementally control our speed depending on how far we are from truly pushing over the edge of the counter to zero. By doing this, we can run at max speed for longer. Use while() loops rather than for loops, and do some on-the-fly calculations inside of the loop until we're done?

I have a New 3DS on 11.1 and the waithax 3dsx got stuck on Setting up fake vtable nethod. Can you please help? Thanks, Splatman333.

Cause unknown. Needs investigation.
Probably linked to #2. Maybe related to the used entrypoint ?

If I download a copy of this repo and build it, then deploy it to my 3DS, it just skips over the overflow process. It doesn't bother to try to do anything. It works in Citra for some reason, though.

I don't know what is happening but it is taking around an hour for the exploit to complete. When it supposedly it has to take half of that to complete. It takes 16 sec between updates.

I am on 11.0 if that may cause the issue.

See topic