Homebrew Arm9 homebrew. With the web browser!

  • Thread starter Thread starter shutterbug2000
  • Start date Start date
  • Views Views 26,869
  • Replies Replies 156
  • Likes Likes 19
If its using the Web browser exploit it should work shouldn't it?

The web browser exploit is the entry point. 9.3/9.4 patched two other exploits used to gain Arm11/Arm9 access. The entry point is not yet patched. The region free exploit you have seen does not make use of the exploits that were patched in 9.3/9.4. Thus the reason that still works. If Arm9 homebrew could be done on 9.3/9.4, Gateway would have announced that/released support for it by now. ;)
 
Hmm hmm. The program you requested is telling me "asm" is undeclared. Feel like i'm missing something here.

That might be something you have to ask the source code's creator about. Perhaps it's compiled with something different then what you are using now.

As for the FS calls, that would be disappointing if that's true. Suppose you can always try it anyway. But might have to wait till the new ones are documented. :(

Might have to use Arm11 code for that (if possible). Code size for Arm9 is much larger compared to the old 4.5 exploit, so there's hope the decryption tools once ported over might actually function better/have more features then it's 4.5 counterpart. :D
 
"The main difference is that this runs on the kernel, not on Process9, so actually all the FS functions should be broken at this rate." That's what the problem is.
 
Well you could always do a Wifi type of thing. Transfer xorpads to PC via FTP. Would be slow as ***k. Might be more trouble then it's worth when finding the new FS calls could take less work to do. :P

EDIT: lol forgot you need FS calls to read the source files as well. You'd have to transfer data both ways if done via WiFi.....yeah better we wait for the FS calls. :D
 
"The main difference is that this runs on the kernel, not on Process9, so actually all the FS functions should be broken at this rate." That's what the problem is.
Oh that different then. I thought the calls are just different.
I guess this means that you run as the kernel and the kernel, at that point , is broken. So you have to do everything yourself.
I don't see why we can't just take over p9 and pass kernelmode code.
Well you could always do a Wifi type of thing. Transfer xorpads to PC via FTP. Would be slow as ***k. Might be more trouble then it's worth when finding the new FS calls could take less work to do. :P

EDIT: lol forgot you need FS calls to read the source files as well. You'd have to transfer data both ways if done via WiFi.....yeah better we wait for the FS calls. :D
That's way more complicated. Why'd you expect network to work when even fs is broken?
 
Oh that different then. I thought the calls are just different.
I guess this means that you run as the kernel and the kernel, at that point , is broken. So you have to do everything yourself.
I don't see why we can't just take over p9 and pass kernelmode code.

That's way more complicated. Why'd you expect network to work when even fs is broken?

lol, I was just throwing around ideas. As for Arm9 kernel vs Process9, I assumed Gateway's new launcher takes over Process9 already. So it's odd that this doesn't as well....
 
Well. Sadly, it appears Multi-Decryptor doesn't want to boot like this... Probably needs that FS access or something. Any other ideas?
 
This is what it is by default:

#define TOP_LEFT_FRAME1 0x20184E60
#define TOP_LEFT_FRAME2 0x201CB370
#define TOP_RIGHT_FRAME1 0x20282160
#define TOP_RIGHT_FRAME2 0x202C8670
#define SUB_FRAME1 0x202118E0
#define SUB_FRAME2 0X20249CF0
 

Site & Scene News

Popular threads in this forum