I have those too, but I play other gba games (ffvi) from time to time
Is there a reason for the 512 bytes size limit for patches?
Also why use bytecode, instead of compiling C patches. Can't the loader module mark pages as executable?
native_firm is 9.6.0 and my sysnand is 11.0Just to be clear, native_firm, twl_firm, and agb_firm have different keys, and the keys are different between o3ds and n3ds. The keys for twl_firm and agb_firm should be named twl.key and agb.key, respectively.
That's cool. Well, I guess given cygwin you can probably build then.
What patches did you enable, what firmware are you using as native, what system software is on your sysnand, etc? You can just kill the power if it crashes like that, btw. It won't hurt anything.
Also, please upload loader.log if you have it in the folder.
(Corbenik is a little slower to boot than other CFWs, too.)
native_firm is 9.6.0 and my sysnand is 11.0
I don't have that file btw.
Updater (test version, might not work properly).
Instead of deleting the cobernik directory and payload, it renames it using time and date. This will probably be changed in the future.
This *should* allow for different payloads to be used (if your payload is not /arm9loaderhax.bin).
Just write the path in a file named "cobernik-updater.cfg" and place it on the root of the SD Card (ex. "/somefolder/mypayload.bin")
BTW It's a 3DSX, I may make a CIA of it once I'm happy with it overall.
debugWrite(0,100,"Extracting to path...", white, TOP_SCREEN)
if updated == 0 then
System.extractZIP(downloadedzip,appinstallpath)
end
-- You should be copying /corbenik/firmware and /corbenik/keys here.
debugWrite(0,120,"DONE! Press A/B to exit!", green, TOP_SCREEN)
Right, thanks, forgot about that.FYI, your lua code is wrong for the very reason that you chose not to unpack in place. You're not copying the firmware and keys to the new directory, so this will abort next boot. Context:
Code:debugWrite(0,100,"Extracting to path...", white, TOP_SCREEN) if updated == 0 then System.extractZIP(downloadedzip,appinstallpath) end -- You should be copying /corbenik/firmware and /corbenik/keys here. debugWrite(0,120,"DONE! Press A/B to exit!", green, TOP_SCREEN)
Right, thanks, forgot about that.
Ok, it should do the job now.No prob. I just don't want people complaining to me if an autoupdater broke the install or anything.
EDIT: I think maybe next release I'll start adding sha256sums for sanity purposes on github.
Any specific reason, btw, that you don't just 302 to github raw on your server?
I may code my own updater eventually if rehosting starts being a problem. It isn't all that hard to do, and I don't even need a web server (just github would do the job. ;P)
Ok, it should do the job now.
I only rehosted it because afaik, github doesn't have static direct links to the file. Am I wrong?
https://github.com/gnmmarechal/corbenik-updater/blob/master/index.lua
Not sure if it does, actually.That depends on whether LP+ supports 302 redirects. If yes, then you can download releases directly using https://github.com/chaoskagami/corbenik/releases/download/v0.0.5/release.zip URLs with the version changed obviously. These redirect to S3 storage.
It doesn't. It barely supports HTTPS if you use a self compiled build (which I've tried and concluded as "impossible")That depends on whether LP+ supports 302 redirects. If yes, then you can download releases directly using https://github.com/chaoskagami/corbenik/releases/download/v0.0.5/release.zip URLs with the version changed obviously. These redirect to S3 storage. This goes for any project on github, as well.
It doesn't. It barely supports HTTPS if you use a self compiled build (which I've tried and concluded as "impossible")
wget https://github.com/chaoskagami/corbenik/releases/download/v0.0.5/release.zip >log 2>&1
--2016-06-06 18:16:25-- https://github.com/chaoskagami/corbenik/releases/download/v0.0.5/release.zip
Resolving github.com... 192.30.252.123
Connecting to github.com|192.30.252.123|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-cloud.s3.amazonaws.com/releases/60402672/fa144114-2bce-11e6-9a92-99091a836c13.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20160606%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20160606T221506Z&X-Amz-Expires=300&X-Amz-Signature=71df18de60454b80f4fb29fadd87054e7b13450e65f89608a0184593b52ac249&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Drelease.zip&response-content-type=application%2Foctet-stream [following]
--2016-06-06 18:16:27-- https://github-cloud.s3.amazonaws.com/releases/60402672/fa144114-2bce-11e6-9a92-99091a836c13.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20160606%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20160606T221506Z&X-Amz-Expires=300&X-Amz-Signature=71df18de60454b80f4fb29fadd87054e7b13450e65f89608a0184593b52ac249&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Drelease.zip&response-content-type=application%2Foctet-stream
Resolving github-cloud.s3.amazonaws.com... 54.231.66.81
Connecting to github-cloud.s3.amazonaws.com|54.231.66.81|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 325291 (318K) [application/octet-stream]
Saving to: ‘release.zip’
0K .......... .......... .......... .......... .......... 15% 44.6K 6s
50K .......... .......... .......... .......... .......... 31% 173K 3s
100K .......... .......... .......... .......... .......... 47% 189K 2s
150K .......... .......... .......... .......... .......... 62% 1.45M 1s
200K .......... .......... .......... .......... .......... 78% 209K 1s
250K .......... .......... .......... .......... .......... 94% 922K 0s
300K .......... ....... 100% 5.73M=2.0s
2016-06-06 18:16:30 (159 KB/s) - ‘release.zip’ saved [325291/325291]
First if all, thanks a lot for your work, it's great !
Few questions : any plans to bring N3DS CPU OC patches ? Also, do you plan to use the keys from d0k3 homebrews such as Decrypt9 ? That would be nice to have one "standard" to avoid duplicating keys everywhere.