Not really, had to try it four times before the CFW starts. I think nothing really changed
(modifiyng the Palantine CFW... how? There`s no source)
any news about the rune factory 4 undub? how is your project coming along?
Not really, had to try it four times before the CFW starts. I think nothing really changed
(modifiyng the Palantine CFW... how? There`s no source)
As someone who knows the ins and outs of yellows8's leaked CFW quite well (from before karl3ds times), I can tell you that nothing worthwhile is changed in this. You changed the stage that loads boot.bin from arm9, a stage that never had any issues in the first place. If you actually wanted to make their CFW stable, you'd fix the arm11 hooking in boot.bin. Or just write your own loader based on it.
They're completely free of obfuscation, throw them in IDA and take two seconds to look and you'll know what everything does...could you tell me a basically what each file does? i know the boot order launcher.dat -> arm9_code.bin -> boot.bin -> arm11_code.bin but what is the basic purpose of the files? which one boot the emunand, which one loads the over the air cia instaler, which one patches the sig checks, etc
They're completely free of obfuscation, throw them in IDA and take two seconds to look and you'll know what everything does...
not really that handy at assembly, but i guess i can give it a shot.
Are there really any differences between the leaked CFW and palantines?
There are no differences between this CFW and the Palantine CFW. It seems that only the arm9.bin got a little change. I can't notice any changes in use.
There are no differences between this CFW and the Palantine CFW. It seems that only the arm9.bin got a little change. I can't notice any changes in use.
I understand that, though I mean the leaked one and palantines
I understand that, though I mean the leaked one and palantines
have you tried it. It does work if you follow the instructions 100 percent of the time. I'm not trying to be a dick.
indeed that is part of it. But, I'm telling you that this time is different. Is very detailed instructions for a reason.I'm saying the issue with yellows8's ancient leaked work is that it fails to hook arm11 most of the time. Loading the arm9 payload in a different way won't resolve that issue.
I will try this. never done it before, but couldn't be too difficult. I will also explain what changes I have made and why in more detail as best I understand them. I'm going on hunches if you must know, but I believe that thinking outside the box and not just changing the way it hooks can fix the problem more easily and simply.Hello bannana2, I do not want to question your work, but I would be grateful if you could open up a github reposity with your work, to understand exactly what you're going to change.
In my opinion, one of the many problems that this CFW is not stable, is the fact that each of us, more or less, working alone without relating to others.
I think it would be better to open a reposity and enter the job, so that maybe someone else can see, instantly, and maybe comment on the changes and rework, to make it more stable.