Hacking Moonshell 2 Exit to firmware

  • Thread starter Thread starter Black ace
  • Start date Start date
  • Views Views 8,076
  • Replies Replies 21

Black ace

Well-Known Member
Member
Joined
Mar 1, 2010
Messages
490
Reaction score
25
Trophies
1
Age
28
XP
1,585
Country
I'm using the moonshell 2-ysmenu combo and when i press start and do exit to firmware it brings me back to moonshell.
Then I took the TTMENU.DAT(DSTT one not moonshell renamed) to ttio.nds and put it in to the moonshl2/resetmse and replaced it with the one which was already there but when I tried doing exit to firmware again it bought up 2 white screens.
Can someone help

Using DSTT cart
 
I'm using 2.05.Don't want to use 2.05< as they have more complicated of putting games and cheats on
 
go install 2.09 + Normmatt's FIX

and also dont forgot to place nds.*.nds (where * is your ysmenu loader) as is it will be used when you select exit to firmware.
 
dnniwa485 said:
go install 2.09 + Normmatt's FIX

and also dont forgot to place nds.*.nds (where * is your ysmenu loader) as is it will be used when you select exit to firmware.
Wasn't normattsfix meant to be for the acekard
 
You don't rename TTMenu.DAT to ttio.nds
lecture.gif


Here is the file you want :
rolleyes.gif
http://www.megaupload.com/?d=XA87HB1G
yay.gif


Place it in moonshl2/resetmse folder
 
Black ace said:
dnniwa485 said:
go install 2.09 + Normmatt's FIX

and also dont forgot to place nds.*.nds (where * is your ysmenu loader) as is it will be used when you select exit to firmware.
Wasn't normattsfix meant to be for the acekard
Nope... Normmatt's file is a cracked overlay.dll that you put into the \moonshl2\internal\ folder
The only complicated part is, instead of having nds.loadername.nds, you have two copies of THAT file renamed to _hn.HugeNDSLoader.nds and _vh.VeryHugeNDSLoader.nds
 
what i needed was when I do exit to firmware,I want it to go to the DSTT GUI
Moonshell 2 was set to autoboot and was renamed to TTMENU.DAT
 
you mean this right?

http://www.youtube.com/watch?v=XrSlYcJiRbY

if yes. then do what i said earlier. And yeah, also it wont work if you use the moonshell2 comercial rom booting guide found on hombrew section. You wont able to boot commercial roms in DSTT menu (it freeze as soon as you select a rom)

but when i use akari212's moonshell2 as main os guide. wow.. it works sweet.
 
dnniwa485 said:
you mean this right?

http://www.youtube.com/watch?v=XrSlYcJiRbY

if yes. then do what i said earlier. And yeah, also it wont work if you use the moonshell2 comercial rom booting guide found on hombrew section. You wont able to boot commercial roms in DSTT menu (it freeze as soon as you select a rom)

but when i use akari212's moonshell2 as main os guide. wow.. it works sweet.
thanks
 
Can someone help me I thought I did i right but it didn't work.I installed moonshell 2.09 using akari212's guide but It just loads up moonshell again.
 
dnniwa485 said:
go install 2.09 + Normmatt's FIX

and also dont forgot to place nds.*.nds (where * is your ysmenu loader) as is it will be used when you select exit to firmware.
sorry for triple posting but what do you meanby nds.*.nds?
 
Black ace said:
dnniwa485 said:
go install 2.09 + Normmatt's FIX

and also dont forgot to place nds.*.nds (where * is your ysmenu loader) as is it will be used when you select exit to firmware.
sorry for triple posting but what do you meanby nds.*.nds?
"*" is a wildcard, it can mean any number of any letters/numbers/symbols.

For example, Xenon++'s file is nds.YSLoader.nds, and linoul's is nds.YSloaderForMS2.nds
You could call it anything you want, like nds.THISISANAME.nds and it would work, it just needs the proper prefix (nds.) and extension (.nds).

You could also use that for other files, for example, gb.Lameboy.nds for associating with .gb files.
 
twiztidsinz said:
Black ace said:
dnniwa485 said:
go install 2.09 + Normmatt's FIX

and also dont forgot to place nds.*.nds (where * is your ysmenu loader) as is it will be used when you select exit to firmware.
sorry for triple posting but what do you meanby nds.*.nds?
"*" is a wildcard, it can mean any number of any letters/numbers/symbols.

For example, Xenon++'s file is nds.YSLoader.nds, and linoul's is nds.YSloaderForMS2.nds
You could call it anything you want, like nds.THISISANAME.nds and it would work, it just needs the proper prefix (nds.) and extension (.nds).

You could also use that for other files, for example, gb.Lameboy.nds for associating with .gb files.
So what does it mean when he said "as is it will be used when you select exit to firmware"?
 
Black ace said:
So what does it mean when he said "as is it will be used when you select exit to firmware"?
To be honest, I'm not sure...

I have a real R4 with Moonshell 2.09 as firmware with YSMenu (DSTT1.17a12) and Xenon++'s YSLaunch.
My R4TF.NDS\Exit to Firmware option is DSOrganize, and it loads directly without needing to go through YSLaunch.

Maybe because it's a smaller file?
 
jurassicplayer said:
It's the same with the R4 firmware. Moonshell2 just doesn't seem to be able to load it on its own.
Moonshell can load homebrew apps on it's own... under a certain size.
I tested Bunjalloo, dsLibris, DSOrganize and a few others and they all ran through Moonshell2.
To make sure it was Moonshell2 running it, I renamed YSMenu.nds, the file that YSLaunch uses to load ROMs, so that Commercial ROM loading was disabled, and all the homebrew I mentioned above worked.

Now to contrast this... I tried to load Super Smash Bros. Clash, a 5MB homebrew.
That kicked in the YSLaunch loader and failed to load because it could not find YSMenu.nds


Mis-read what you said... lol.
And yeah, I wish I knew why (or even better: how to!) R4's firmware won't load as an NDS file.
The R4li Firmware -CAN- run, if you decrypt it.
 
Black ace said:
So how do you get it to load back to the dstt gui when doing exit to firmware
IMO if you're using linoul or Xenon++'s YSLoader for Moonshell, the only real solution to get to the DSTT menu is to use Xenon++'s YSBoot, since if you use YSMenu.nds to load YSMenu, it will autoboot the ROM you had selected last.
You should be able to use that as the replacement R4TF.nds file, but it's kind of more simple to put it into the Moonshl2\Launch folder.
 
@Black ace

sorry didnt reply on ur PM.. busy you know

..

- anyway.. just follow the akari212's MS2 2.08-2.09 install guide for DSTT/i carts (here)

after that the installation.. and you verified that it can load normally and launch commercial roms, then do this:

- go to "moonshl2/resetmse"
- copy the TTMENU.DAT on that folder
- delete the existing ttio.nds there
- rename the TTMENU.DAT to TTIO.NDS
- after that go back one folder and go to extlink folder
- copy your favorite nds loader there... if you follow akari212's guide.. you can use the YSLAUNCHER on her links. then copy the "nds.YSloaderForMS2.nds" there

after that then its done.. you can now boot DSTT firmware with ease. (without hangups on DSTT menu)
because no matter what i tried.. i followed the guide found on homebrew section. On DSTT menu it just hangs up when i choose a ROM... wtf?, but oh well i tried akari212's guide .. and it works fine.
 

Site & Scene News

Popular threads in this forum