the sha for the otp should match the sha for the otp and the sha for the arm9 should match the sha for the arm9
You should add this to the OP. It would have saved me about an hour of confusion.what python version are you using?
try using this in top of the script
import ssl
ssl._create_default_https_context = ssl._create_unverified_context
Why not adding something like this?
A file containing all the SHAs is useful... At least for me lolf = open("sha256.txt", "w")
print >> f, "%s\n%s" % (res.info().getheader('Installer-Sha256'), res.info().getheader('OTP-Sha256'))
f.close()
-So that I can compare them using other softwares. My eyes hurt.Why? it is printed in the end of the execution...
Which branch of A9LH does it compile?
whats the difference between the originl a9lh vs a9lh screen init?It says it in the OP dude. " It is using delebiles fork of a9lh with screen init support."
The orig the screens where off. Now they can make things like ctrbootmanager for itwhats the difference between the originl a9lh vs a9lh screen init?
what is thats screen init? (sorry for being a noob)
what do u prefer to use? original or the screen init?
thanks...
The orig the screens where off. Now they can make things like ctrbootmanager for it
Correcti dont fully understand...
do u mean in the original - boot manager doesnt work?
while
in screen init version - boot manager works?
am i right? (i think im wrong?)
So, I'm providing a online service to compile A9LH, it is very simple, just post your OTP.bin (must be raw bytes) to https://felipejfc.com/a9lh and wait for your arm9loaderhax.3dsx.
Method 1 (Python script):
Requirements:
Python installed.
LINK
Put it in same folder as otp.bin and double click it. done. Just check shasums and you are good.
Method 2 (curl):
curl --data-binary "@otp.bin" -D headers https://felipejfc.com/a9lh > arm9loaderhax.3dsx
the command takes some time to run,
two files will be created, headers and arm9loaderhax.3dsx, in headers, check
Installer-Sha256
OTP-Sha256
These are the sha256 of the OTP the server used to compile arm9loaderhax.3dsx, and arm9loaderhax.3dsx sha256 the moment it leave the server, both should match with your newly created arm9loaderhax.3dsx and the OTP.bin you've sent.
Do not install if the hashes don't match
It is using delebiles fork of a9lh with screen init support.
source
Do you keep the OTP dump after compilation? Just asking because there is unique data in there.
ive follow the method 2 - it produces "arm9loaderhax.3dsx"
but where are the other files?:
---arm9loaderhax.elf
---stage0x5C000.bin
---firm0.bin
---firm1.bin
---sector.bin
someone compiled the original arm9loaderhax (not the init version) and it does have these 5 files...
can i use those 5 files using the init version of arm9loaderhax.3dsx?
thanks :-)
Any chance you could set Access-Control-Allow-Origin to *? I'm trying to build a web-form to make this easier for people.So, I'm providing a online service to compile A9LH, it is very simple, just post your OTP.bin (must be raw bytes) to https://felipejfc.com/a9lh and wait for your arm9loaderhax.3dsx.
Method 1 (Python script):
Requirements:
Python installed.
LINK
Put it in same folder as otp.bin and double click it. done. Just check shasums and you are good.
Method 2 (curl):
curl --data-binary "@otp.bin" -D headers https://felipejfc.com/a9lh > arm9loaderhax.3dsx
the command takes some time to run,
two files will be created, headers and arm9loaderhax.3dsx, in headers, check
Installer-Sha256
OTP-Sha256
These are the sha256 of the OTP the server used to compile arm9loaderhax.3dsx, and arm9loaderhax.3dsx sha256 the moment it leave the server, both should match with your newly created arm9loaderhax.3dsx and the OTP.bin you've sent.
Do not install if the hashes don't match
It is using delebiles fork of a9lh with screen init support.
source
uh no... it was because dark_samus' screen init was merged into the main repoWhy did you start using dark_samus' fork then immediately remove it? Was it because of the extra files required?