When I iron out some bugs. And also multitest the recovery options.And when this 3.0.0 is planned ?
if it released it will be RCM-less ?
RCM-les? no.. It doesn't work like this
When I iron out some bugs. And also multitest the recovery options.And when this 3.0.0 is planned ?
if it released it will be RCM-less ?
ok i understand autoboot is like sx os boot immediately if no button pressed .When I iron out some bugs. And also multitest the recovery options.
RCM-les? no.. It doesn't work like this
When I iron out some bugs. And also multitest the recovery options.
RCM-les? no.. It doesn't work like this
If you're using CTCaer's hekate it will verify the dumps with a green progress bar. You can also dump your bis keys and use HacDiskMount to verify your dump.Would it be advisable to use the hacky method of getting exFAT support on the lower firmwares [3.0.2 in my case] to do proper NAND / etc dumps to 32GB+ microSD cards in preparation for Atmosphere? I tried the 2-GB piece-meal method but for some reason am weary of the results...
Is there a way to verify I got proper dumps??
Hekate has built-in exFAT support. You don't need the exFAT micro update for this. The micro update is needed only in Horizon.Would it be advisable to use the hacky method of getting exFAT support on the lower firmwares [3.0.2 in my case] to do proper NAND / etc dumps to 32GB+ microSD cards in preparation for Atmosphere? I tried the 2-GB piece-meal method but for some reason am weary of the results...
Is there a way to verify I got proper dumps??
Unfortunately, yesterday when I was fixing some more bugs around, I found out that the verification is not working.If you're using CTCaer's hekate it will verify the dumps with a green progress bar. You can also dump your bis keys and use HacDiskMount to verify your dump.
It was broken though. But if you had mostly empty eMMC it would continue to check because of the 00s.@CTCaer
So the memcmp is the slowing down part.
Maybe using a hashing algorithm like xxhash would be faster?
It's not out of reach. It's how you launch HOS actually. You enable CCPLEX and let it run secmon and then you give control to it with the FLOW register.@CTCaer
So probably the fastest and most reliable way for vrification would be to utilize the CCPLEX for this task instead of the BPMP. But the CCPLEX is out of reach with the current state of hekate, right?
He already has a solution for the battery desync problem:@CTCaer Something to add to CTCaer mod v3.0?
https://github.com/crystalseedgba/BatteryFix/commit/5b1aa3bc39c70485687c8730b75640ec39964e07
The thread of this release:
https://gbatemp.net/threads/fix-for-linux-battery-issue.508715/
Ah, I thought he must have found it somewhere. An user with 1 post isn't gonna release something of that complexity.He already has a solution for the battery desync problem:
https://github.com/CTCaer/hekate/commit/52506def30d2ea18ce4ccad3546567fa082cfc2f
Care to explain your configuration?Hey
So after a while of using hekate
I decided to launch another switch game and it instead crashed my entire switch.
Any reason why that happens?
It does not work like this.Could you make the payload to autoclean logs before start any firmware? (cfw, layered compatibily or ofw)
His work is independent. Because I only told to my test group, that this is a possible solution, but I never gave them the source code.Ah, I thought he must have found it somewhere. An user with 1 post isn't gonna release something of that complexity.
Nope, it looks like his very own solution/workaround and has nothing to do with CTCaer's his code.Ah, I thought he must have found it somewhere. An user with 1 post isn't gonna release something of that complexity.
This ^Nope, it looks like his very own solution/workaround and has nothing to do with CTCaer's his code.
I'm not sure, but maybe xxhash would be faster in generating the two hash values needed for comparison than a memcmp on these two 4MiB buffers.a full check that can take 4.5 hours.
nwert told me that SE will probably be extremely fast because it seems to run on ram's clocks.I'm not sure, but maybe xxhash would be faster in generating the two hash values needed for comparison than a memcmp on these two 4MiB buffers.