Homebrew ARM9Loader -- Technical Details and Discussion

[dark_samus3]

Thanks for clarifying. Just one more question are the Arm9 gurus such as yourself, in your programming, are wiping firm1 and firm0 before writing new files to it? Or should we be restoring nand before a new flash to avoid having residual files left in firm0 and firm1?

we don't wipe it, but it is overwritten and there isn't really any worry about any data left after then end of the binary

 

[hacksn5s4]

https://plailect.github.io/OTP/
To get your OTP.

https://github.com/delebile/arm9loaderhax
To compile and install A9LH.

how program do you use to complie it

 

[Supster131]

how program do you use to complie it

Install DevKitPro and Python 2.7 with pycrypto.

Then just compile using the "make" command in CMD.

 

[hacksn5s4]

Install DevKitPro and Python 2.7 with pycrypto.

Then just compile using the "make" command in CMD.

very annoying cause all these different things require different python versions and other tool use requires a different version of it

 

[dark_samus3]

very annoying cause all these different things require different python versions and other tool use requires a different version of it

My branch can use any version of Python

 

[hacksn5s4]

eh to bad it requires me to back up both nands when emunads on my sd and there not enough space

 

[dark_samus3]

eh to bad it requires me to back up both nands when emunads on my sd and there not enough space

what?

 

[liomajor]

@dark_samus3

Any plans when recovery menu will be integrated?

 

[hacksn5s4]

it says you need to back up synnand and emunand but my sd does not have enough space to back them all up when emunands on it

 

[dark_samus3]

@dark_samus3

Any plans when recovery menu will be integrated?

Well if you check my github the initial groundwork (really all of the code for launching the payload) is implemented, just pushed it a bit ago , if you write a payload at sector 0x5A000 it will launch when you hold the home button and boot the console

 

[solsolis]

here... https://mega.nz/#!yEoAzAqD!6bA4PefqiBkCr1UYPKYp8vpfE5DKpCj_0p_zpJqpUZc

I'm having trouble with this. I can't seem to get it to extract. Windows keeps throwing errors.

Could you post the .bin file directly?

EDIT: Never mind using 7zip seemed to remedy it I don't know why I didn't think of it sooner.

 

[liomajor]

Well if you check my github the initial groundwork (really all of the code for launching the payload) is implemented, just pushed it a bit ago , if you write a payload at sector 0x5A000 it will launch when you hold the home button and boot the console

Basicly using your installer.bin and add Stage0x5A000.bin for installation a backup, correct?

 

[dark_samus3]

Basicly using your installer.bin and add Stage0x5A000.bin for installation a backup, correct?

nope, won't work. That installer doesn't look for or write anything to sector 0x5A000, and it's not ready so I don't recommend it if you don't know what you're doing (I used my hardmod to flash it into my NAND manually) however if you know what you're doing, and know the number of bytes per sector and how to write things into NAND, you could probably embed a Decrypt9 payload or something in there, though that wouldn't have screen init, so it'd be fairly pointless

 

[liomajor]

nope, won't work. That installer doesn't look for or write anything to sector 0x5A000

Ah i guessed it could work since the installer.bin mentioned the file, i've a hardmod so i can do it manualy

 

[dark_samus3]

Ah i guessed it could work since the installer.bin mentioned the file, i've a hardmod so i can do it manualy

The installer mentions the file stage0x5C000

 

[Cydget]

Hello, Im on step 19 of this tutorial https://github.com/Plailect/Guide/wiki/Part-4-(New-3DS).
I have not actually done step 19(coping a 2.1 emunand.bin to sysnand.bin), and I was wondering if it is normal that I can not boot into emunand in the state that its in right now. I have already run OTPHelper to unbrick FW2.1 emuNand, but emunand is still bricked. Is this normal? Should I proceed with coping emunand to sysnand anyways?

 

[dark_samus3]

Hello, Im on step 19 of this tutorial https://github.com/Plailect/Guide/wiki/Part-4-(New-3DS).
I have not actually done step 19(coping a 2.1 emunand.bin to sysnand.bin), and I was wondering if it is normal that I can not boot into emunand in the state that its in right now. I have already run OTPHelper to unbrick FW2.1 emuNand, but emunand is still bricked. Is this normal? Should I proceed with coping emunand to sysnand anyways?

it's normal, there's no CFW that knows how to handle 2.x so it'll never boot

 

[Cydget]

it's normal, there's no CFW that knows how to handle 2.x so it'll never boot

ok, crossing my fingers.

EDIT: Do you have the MD5 checksum of the N3ds 2.1 download pack?

 

[Suiginou]

ok, crossing my fingers.

EDIT: Do you have the MD5 checksum of the N3ds 2.1 download pack?

Please stop using outdated crypto. MD5 is extremely broken; a matching MD5 checksum doesn't necessarily mean the pack is good, given that an attacker could mess with the pack and still have a matching MD5. Go get yourself a tool that does SHA-256.

 

[Cydget]

Please stop using outdated crypto. MD5 is extremely broken; a matching MD5 checksum doesn't necessarily mean the pack is good, given that an attacker could mess with the pack and still have a matching MD5. Go get yourself a tool that does SHA-256.

I was going to use SHA-256 to confirm, but I thought that md5 was more common and more people would likely have that information available.

EDIT: downgrade to 2.1 was successful.