Homebrew Clarification Thread - What is going on?

  • Thread starter Thread starter JustPingo
  • Start date Start date
  • Views Views 647,854
  • Replies Replies 5,356
  • Likes Likes 103
Status
Not open for further replies.
Yet the 3ds is already ultra stable

Not stable enough to keep homebrew from never crashing it. :P
Maybe they let us refuse them because some people really does not have enough time to update.

Couldn't they try forcing you to automatically update if you have Internet access in sleep mode? If I'm remembering correctly it already automatically downloads the updates but waits until you approve them before installing, but maybe it could auto-update after 24-72 hours like how Windows sometimes does?
 
And BL instruction itself has some certain bits, so you might be able to calculate this possibility.
I wanna know how poor the brave is for the arm9loaderhax - to some extent.
@Mrrraou
WHAT? ARM instruction: 1/16=all conditions, or 1/256=a pure BL to whatever. 1/8=any B variants.
Thumb instruction: 1/32=pure BL to whatever, 1/32=pure B to whatever. Just ignore BX this time (1/1024, and Register?)
Though the possibility looks not so bad ...

Hi Syphurith,

Let's look at the probabilities for any random 32-bit value to cause execution to fall into the FIRM0 extra space. We can presume that FIRM0 was corrupted to be maximum size, and FIRM1 was chosen to be smallest size (to maximize FIRM0 portions that remain).
  • Bits 31-28 ==> 5/8 chance of execution
    • There's a 1/8 chance that the BRANCH will be unconditional (bits 31-28 either 1111b or 1110b)
    • There's a 1/2 chance that of execution with any of the other condition bits
  • Bits 27-25 ==> 1/8 chance of being a BRANCH instruction (101b)
  • Bit 24 ==> 1/1 chance of BRANCH being a BRANCH
    • If 0b, then it's a simple BRANCH
    • If 1b, then it also stores next instructions address in LR (return address)
    • But, no effect on actually BRANCH
  • Bits 23-0 ==> Signed BRANCH offset (more detail below)
Thus, there is a 5/64 chance that each instruction will be a BRANCH that executes.

Using only this 5/64 chance, consider next the likelihood that it would branch to a desired location. 2**24 bits for address, but only ~256MiB (~2**18) on N3DS. Thus, 1/64 chance that each BRANCH instruction will attempt to branch to a valid memory location. (very rough, keep the numbers easy.)

Cumulatively: 5/4096 (~1/1024) chance of a valid BRANCH address. Presuming zero'd memory, most will eventually end up in the first byte of memory. Throwing in the small likelihood of branching to the NOPs or intended instructions, and you are correct... this seems low-probability.

I think there's more to this that reduces the complexity...
 
I think you would find it's a legal responsibility thing in reference to updates, if they force you to update then they are responsible for what happens to your system after that, whereas if it's implied that you are agreeing to terms and conditions by clicking yes then the responsibility now falls on you.
 
I think you would find it's a legal responsibility thing in reference to updates, if they force you to update then they are responsible for what happens to your system after that, whereas if it's implied that you are agreeing to terms and conditions by clicking yes then the responsibility now falls on you.
if we accept to terms and conditions before updating, then why does Nintendo block homebrew for the ones who don't update? do we have a right to not update without removal of the freedoms that come with the console? Nintendo is the afgans to the freedom of homebrew...
 
if we accept to terms and conditions before updating, then why does Nintendo block homebrew for the ones who don't update? do we have a right to not update without removal of the freedoms that come with the console? Nintendo is the afgans to the freedom of homebrew...

Well I'm not going to sit there and read through the ToS or documentation, but at a guess part of those conditions would be that they do not consent to you modifying or using the system for anything other than it's intended purpose.
 
  • Like
Reactions: hobbledehoy899
Btw, please don't hype over everyone single commit @Steveice10 pushes.

We've done only ~65% of the work, but the code needs to be understandable.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum