Homebrew ARM9Loader -- Technical Details and Discussion

[Supster131]

Sorry. Wasn't aware of your jingle idea when I uploaded that.

As for the payload I'm using. It's private right now yes. It was given to me by someone who instructed me not to make it public. So for the moment I won't be sharing the payload I'm using.

Any word on when this might become public? Or anyways of "beta testing" this privately?

 

[capito27]

Any word on when this might become public? Or anyways of "beta testing" this privately?

we don't even know "if", so when it a bit of a leap of judgement

sure, alternatives may come out eventually, but what we are using right now with a9lh, don't hold to much hope for it.

 

[Supster131]

we don't even know "if", so when it a bit of a leap of judgement

Wouldn't be a bad idea to have a few people test this out though (in my opinion) to make sure it's stable enough for the public.

 

[RednaxelaNnamtra]

I added a additional payload to arm9loaderhax, it should allow to create a full updatable bootloader, will try to write one and push my changes to my fork.

Edit:
I now pushed the changes to my fork
At the moment its only a messy copy of the sector code, but now I will start to make it a bootloader.

 

[capito27]

Wouldn't be a bad idea to have a few people test this out though (in my opinion) to make sure it's stable enough for the public.

well, there are about 25 people with access to the payload, so we should be fine with private testers ^^'

 

[AHP_person]

well, there are about 25 people with access to the payload, so we should be fine with private testers ^^'

Almost 30.

 

[WilliamO7]

well, there are about 25 people with access to the payload, so we should be fine with private testers ^^'

So can we have 10.5 sysnand CFW like the salty team did or not yet?

 

[Vappy]

Almost 30.

Hardly even seems 'private' at that point. Any particular reason for keeping it under wraps?

 

[Apache Thunder]

Yeah. I can have a 10.5 sigpatched sysnand I wanted. But if I did, I'd be stuck on it because at the moment there isn't any arm9 hooks added yet to allow booting emunand/other arm9 homebrew. So I'd be stuck on 10.5 sysnand. For my o3DS I'm happy with it being just a simple sig patched 9.2 sysnand. That way I can use emunand when I need it.

 

[ketal]

+ all the other people that have already done on their own (I wrote a payload with some people but I'm not really satisfied of it, might release it when the downgrade situation is more clear)

 

[AHP_person]

Hardly even seems 'private' at that point. Any particular reason for keeping it under wraps?

Not my code, can't really say. We just have an extremely large group chat -0-

 

[shinyquagsire23]

Hardly even seems 'private' at that point. Any particular reason for keeping it under wraps?

I find this particularly amusing when so many of the private testers are quick to criticize other private projects.

 

[WilliamO7]

I find this particularly amusing when so many of the private testers are quick to criticize other private projects.

*Ahem* hint hint

 

[Suiginou]

I find this particularly amusing when so many of the private testers are quick to criticize other private projects.

Pot, kettle, black, etc.

 

[Audioboxer]

I find this particularly amusing when so many of the private testers are quick to criticize other private projects.

It's pretty newly developed stuff right? Isn't it always best things stay under wrap until they are fool proof/as bug free as can be?

Sure some devs keep things private forever, but meh, it is ultimately up to them to release or not. Us peasants should always be grateful for any scraps we get No one owes us anything, and sure no one likes unnecessary boasting in the face of keeping something private, but it's not the end of the world.

 

[Vappy]

Not my code, can't really say. We just have an extremely large group chat -0-

Maybe you could invite Govanify or relys into your group, I hear they're REALLY good at keeping things secret.

 

[WilliamO7]

It's pretty newly developed stuff right? Isn't it always best things stay under wrap until they are fool proof/as bug free as can be?

Sure some devs keep things private forever, but meh, it is ultimately up to them to release or not. Us peasants should always be grateful for any scraps we get No one owes us anything, and sure no one likes unnecessary boasting in the face of keeping something private, but it's not the end of the world.

True even though most of us don't like to admit it

 

[AHP_person]

Govanify

GASP

 

[Supster131]

well, there are about 25 people with access to the payload, so we should be fine with private testers ^^'

That's good, the more the better. That way the dev can get more results, and for different systems at that.

 

[lefthandsword]

Hardly even seems 'private' at that point. Any particular reason for keeping it under wraps?

Probably to prevent 8 year olds from 'experimenting' with it w/o knowledge about what they're doing, then come back and complain when they have a $200 paperweight.