-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ak2i troubles #1
Comments
Yeah, I am aware of this — the AK2i does some kind of detection to determine whether to serve the NTR part of its flash or the TWL part (FIRM is written to the TWL part) but this currently gets the NTR part of the flash, which contains the normal Acekard 2i title (and normal NTR key). I'll work on it. |
@angelsl likely it's just the init order. Iirc, two commands in the initial set of them are actually flipped on TWL vs NTR Yep: DSi cart init sequence: Source: https://hackmii.com/2010/02/lawsuit-coming-in-3-2-1/ EDIT: looks like you handle this already too with ncgc_ninit_order() |
@dark-samus Tried that, but no difference (?) The funny thing is, Boot9 actually inits like a DS phat/lite. |
I have 2 ak2i's (HW 81) flashed with ntrboot and verified manually that they work. When running them with dsfirmveryify, however, the result is the same;
ncgc_nbegin_key1 failed:
-2 0x00000FC2 0x7EAA0570
The text was updated successfully, but these errors were encountered: