Homebrew ARM9Loader -- Technical Details and Discussion

[Plailect]

How does one dump their O3DS secret sector? Also, the GitHub states to get N3DS firmware CIAs; surely you'd require O3DS ones for an O3DS?

Secret sector is the same for all 3DSs, you can find it on the internet.

 

[Deleted User]

OK.

 

[Mrrraou]

How does one dump their O3DS secret sector? Also, the GitHub states to get N3DS firmware CIAs; surely you'd require O3DS ones for an O3DS?

There is no secret sector on O3DS. Why would you want to dump it ?
You need to use the N3DS ones for O3DS.

--------------------- MERGED ---------------------------

Secret sector is the same for all 3DSs, you can find it on the internet.

Secret sector doesn't exist on O3DS, AFAIK.

 

[Deleted User]

NVM, above post explains.

 

[key1340]

How does one dump their O3DS secret sector? Also, the GitHub states to get N3DS firmware CIAs; surely you'd require O3DS ones for an O3DS?

Google arm9loaderhax data_input then look for the pastebin at the bottom

 

[einhuman197]

Have a problem. I think decrypt9 doesn't dump the 0x4 right. It's named as nand.fat16.xorpad like the normal without 0x4 but at the end it says 0x4 complete. Size is the same.

What should I do?

 

[Mrrraou]

Google arm9loaderhax data_input then look for the pastebin at the bottom

Or just use capito27's fork.

--------------------- MERGED ---------------------------

Have a problem. I think decrypt9 doesn't dump the 0x4 right. It's named as nand.fat16.xorpad like the normal without 0x4 but at the end it says 0x4 complete. Size is the same.

What should I do?

On your version, I think it's not renamed yet.
And the size should be the same. Else there's an issue.

 

[3xkrazy]

Have a problem. I think decrypt9 doesn't dump the 0x4 right. It's named as nand.fat16.xorpad like the normal without 0x4 but at the end it says 0x4 complete. Size is the same.

What should I do?

Compile the latest version from github, or just transfer them 1 by 1 to your pc, renaming them of course.

 

[einhuman197]

Are they the same?

 

[Deleted User]

Odd. My copies of O3DS/N3DS NATIVE_FIRM for 10.2 and 9.0 are both not linking up with the hash - perhaps due to signature differences?

 

[Mrrraou]

Are they the same?

No.

 

[einhuman197]

Use them from capito27's github.

 

[einhuman197]

I think I'll check the md5s, if they are different I'll process

 

[Deleted User]

Well, logically no two files from NUS should be the same. IIRC they use RSA or AES for encryption for cert signing, which isnt like a hash.

 

[einhuman197]

I know, I'm just confused because those file names.
I only want to check the hashs to see if they are different. Unfortunately I deleted the 0x4,so I have to dump it again -.-

 

[Mrrraou]

Well, logically no two files from NUS should be the same. IIRC they use RSA or AES for encryption for cert signing, which isnt like a hash.

Well, if you want to use these to compile ARM9loaderhax, you also need to decrypt these, and use the .firm section inside their exefs.

 

[Deleted User]

Ahh. That would be the same.

--------------------- MERGED ---------------------------

EDIT: Would something like CTRBootManager compiled for this be possible? I'd primarily use this for my CFW, but if a form of CTRB would be able, I'd also be able to run Decrypt9.

 

[einhuman197]

Md5's are different, will process. Thanks for the help.

 

[Deleted User]

Umm.
I just installed this and now when I press the power button it instantly turns off...

EDIT: Didn't have the ARM9 payload BIN file on my SD, but now aswell it wont boot without the SD in, just hangs on blackscreen, nor will it boot my rxTools. Anyone have a copy of Decrypt9 that'll work?

 

[capito27]

Or just use capito27's fork.

--------------------- MERGED ---------------------------


On your version, I think it's not renamed yet.
And the size should be the same. Else there's an issue.

Why always quoting my super illegal fork ? C: