Homebrew DevMenu as Launcher.dat possible?

  • Thread starter Thread starter WateredFire19
  • Start date Start date
  • Views Views 5,592
  • Replies Replies 31
  • Likes Likes 1

WateredFire19

Banned!
Banned
Joined
Aug 23, 2014
Messages
642
Reaction score
215
Trophies
0
Age
41
XP
291
Country
United States
Just wondering :/ I know we can use ROP MULTILOADER .nds to run either a homebrew or a MT/GW launcher, and the MSET exploit has full kernal access, so can't we make a DevMenu/BigBlueBox as a Launcher.dat?
 
  • Like
Reactions: Margen67
Just wondering :/ I know we can use ROP MULTILOADER .nds to run either a homebrew or a MT/GW launcher, and the MSET exploit has full kernal access, so can't we make a DevMenu/BigBlueBox as a Launcher.dat?

Not too useful, actually DevMenu is only for CIA installing when you're on Emunand, so, if you have it as a launcher, you will be able to install CIAs, but not to launch them.
 
  • Like
Reactions: leerpsp
Just wondering :/ I know we can use ROP MULTILOADER .nds to run either a homebrew or a MT/GW launcher, and the MSET exploit has full kernal access, so can't we make a DevMenu/BigBlueBox as a Launcher.dat?

I'm pretty sure they'd become too large of a binary to work.
 
Not too useful, actually DevMenu is only for CIA installing when you're on Emunand, so, if you have it as a launcher, you will be able to install CIAs, but not to launch them.

I dont really understand.... You'd just install them but not launch them?
 
I dont really understand.... You'd just install them but not launch them?

No no, hum, when you use DevMenu you want to install CIAs as a channels, no? Well, the only way to open those channels is via Emunand. So, if you have Bluemenu as launcher.dat, then, how do you think you'll be able to open it if you use your *.dat for the devmenu and not for the launcher of the emunand? I don't know if you understand my point.
 
No no, hum, when you use DevMenu you want to install CIAs as a channels, no? Well, the only way to open those channels is via Emunand. So, if you have Bluemenu as launcher.dat, then, how do you think you'll be able to open it if you use your *.dat for the devmenu and not for the launcher of the emunand? I don't know if you understand my point.

I understand :) Thanks for explaining But after it installs the CIA file can't you plug your SD card into your computer and then replace the CIA program Launcher.dat with MT's or Gateway's to boot into EmuNAND.
 
I understand :) Thanks for explaining But after it installs the CIA file can't you plug your SD card into your computer and then replace the CIA program Launcher.dat with MT's or Gateway's to boot into EmuNAND.


In order to run the illegitimate CIAs, you'd need gateway (or MT) mode. Which requires a card, and you'd just be able to run devmenu on that anyway. Which defeats the purpose of using it as a launcher.dat.

No no, hum, when you use DevMenu you want to install CIAs as a channels, no? Well, the only way to open those channels is via Emunand. So, if you have Bluemenu as launcher.dat, then, how do you think you'll be able to open it if you use your *.dat for the devmenu and not for the launcher of the emunand? I don't know if you understand my point.

This is somewhat correct. If you make/find/install 'legit/clean' CIAs (which just recently started popping up online), you can install using devmenu, and then run using sysnand or even after a system transfer. This is because they aren't tied to the ticket and are signed correctly, so they can be run without the exploits. The trick would be installing them. Which devmenu could do.

Either way, there's not really a point to devemenu as a launcher.dat, since if you can run the launcher.dat, you can boot up into CFW or gateway mode and run devmenu in there (which would be needed for illegitimate CIAs anyway).
 
This could work if you patched the system and booted back into sysnand instead of emunand, but at that point you can still just run devmenu...
 

Site & Scene News

Popular threads in this forum