Ok, thanks. I'll look into itYeah, that is how Aurora's fork handhelds both screeninit and no-screeninit.
Ok, thanks. I'll look into itYeah, that is how Aurora's fork handhelds both screeninit and no-screeninit.
Ok, I've had a look at Aurora's fork and there's a problem. Her fork works with bootctr9 because the A9LH payload itself doesn't need screen init. It doesn't display anything, so doesn't care whether screen init happens or not. 3DSafe, however, needs screen init. I can't just not init the screen to get bootctr9 to work.Yeah, that is how Aurora's fork handhelds both screeninit and no-screeninit.
I think the former would be a good idea, personally. I, for example, use BootAnim9 which does not have built in screen init (unless it got added and I am unaware). Letting people choose would be best I think.Ok, I've had a look at Aurora's fork and there's a problem. Her fork works with bootctr9 because the A9LH payload itself doesn't need screen init. It doesn't display anything, so doesn't care whether screen init happens or not. 3DSafe, however, needs screen init. I can't just not init the screen to get bootctr9 to work.
I agree. I'll look into de-initing the screen before anything else as that would allow it to work with any payload regardless of whether or not it inits the screen. I don't know if it's possible to do it, however,I think the former would be a good idea, personally. I, for example, use BootAnim9 which does not have built in screen init (unless it got added and I am unaware). Letting people choose would be best I think.
if they have a nand backup from before they installed this then surebtw, mashers, if someone for some reason forgets their pin and loses their otp dump, a hardmod is enough to recover.
nope, no need of a backup, because stage2 of the current a9lh implementation is always in plaintext, so they could totally overwrite it.if they have a nand backup from before they installed this then sure
shhhhh some thief is totally going to be made up you told them that XD....thats it @mashers put a random seed in there and force people to compile their own buildnope, no need of a backup, because stage2 of the current a9lh implementation is always in plaintext, so they could totally overwrite it.
how would that be of any use ? keep in mind that the payload is in clear text, it can be generated differently for everyone, that wouldn't change the fact that it's cleartext ^^'shhhhh some thief is totally going to be made up you told them that XD....thats it @mashers put a random seed in there and force people to compile their own build
btw, mashers, if someone for some reason forgets their pin and loses their otp dump, a hardmod is enough to recover...
Interesting. I didn't know that. So you could literally hard mod, dump the NAND, hex edit in a new stage2 payload, rewrite the NAND and boot? If that's possible then I think we're dealing with a more determined thief than average...no need of a backup, because stage2 of the current a9lh implementation is always in plaintext, so they could totally overwrite it.
yeah I realized what you meant after writing that post hence the edit, but yeah probs good as a last chance recovery methodhow would that be of any use ? keep in mind that the payload is in clear text, it can be generated differently
well, you don't even need to dump nand, an hex editor can open the disk and directly write to nand at the right offset, takes about 30 seconds to load the drive, go the the right offset, copy a new payload, overwrite the current one and savingInteresting. I didn't know that. So you could literally hard mod, dump the NAND, hex edit in a new stage2 payload, rewrite the NAND and boot? If that's possible then I think we're dealing with a more determined thief than average
or simply someone who lost their pin + otp.bin and doesn't want to own a 200 bucks paper weightInteresting. I didn't know that. So you could literally hard mod, dump the NAND, hex edit in a new stage2 payload, rewrite the NAND and boot? If that's possible then I think we're dealing with a more determined thief than average
yeah I realized what you meant after writing that post hence the edit, but yeah probs good as a last chance recovery method
I didn't think of doing it directly to the disk. Ok, well I'm not going to document it as a recovery method. The idea is that this is as bulletproof as possible. I suppose the user could cover all of the hardmod solder points in superglue so it can't be hardmodded...well, you don't even need to dump nand, an hex editor can open the disk and directly write to nand at the right offset, takes about 30 seconds to load the drive, go the the right offset, copy a new payload, overwrite the current one and saving
Yes, well I'll bear it in mind if I get tagged in a post / PMed with a message saying "I FORGOT MY PIN AND LOST MY OTP NOW MASHERS OWES ME A NEW 3DS"or simply someone who lost their pin + otp.bin and doesn't want to own a 200 bucks paper weight
ever heard of solvants ? http://www.supergluecorp.com/?q=removingsuperglue.htmlI suppose the user could cover all of the hardmod solder points in superglue so it can't be hardmodded...
Wouldn't that damage the PCB as well?ever heard of solvants ? http://www.supergluecorp.com/?q=removingsuperglue.html
if you don't drop the whole bottle but use a cotton bud to apply it carefully, it wouldn'tWouldn't that damage the PCB as well?
the V2@mashers what version of safea9lh should we use, the old one or the v2?