Jump to content


Photo

DashLaunch 3.03


  • Please log in to reply
42 replies to this topic

#1 JPizzle

JPizzle

    That Fuckin Guy

  • Administrators
  • 2315 posts
  • LocationRight Behind You

Posted 18 October 2012 - 03:04 AM

As always with the release of a new XeBuild today cOz has released a new version of dashlaunch with some exciting new additions. Corona 4G owners will be happy to know that one of the added features is the addition of the internal storage as a path location, internal corona 4g mu MmcMu:

The new feature I am personally very excited about is the addition of FakeAnim, used in conjunction with the actual FakeAnim app released by BioHazard HERE it allows CUSTOM BOOT ANIMATIONS! No, not just 1 custom animation supplied by the dev but you can use any of your own videos as a boot animation.

I am also very happy to announce that RealModScene.com is now the official support forum for Dashlaunch along with Homebrew-Connection.org, so be sure to post any bugs, comments and suggestions and they will be seen by the dev himself.

================================================================================
ChangeLog
================================================================================
V3.03
- some commented code made contpatch non-functional on untouched demo containers
- added polish translation
- add nohealth option, disables kinect health pseudo video at game launch
- add autofake option, when enabled fakelive functionality is enabled during dash and indie games only (thanks BioHazard!)
- added some failsafe code to lhelper and launch to ensure auto profile signins occur
- moved boot time quick launch button check to lhelper, it now occurs at the point where bootanim freezes (approx)
- removed bootdelay option, it should no longer be required
- add corona 4G memory unit path
- add fakeanim path
- fix bugs related to Guide/Power paths
- add PIRS type content to installer launch item parsing
- add nooobe option, disables setup screens when settings already exist
- dash launch now patches xam to prevent flash updates from appearing when updaters newer than current are on devices
- wired controller poweron causes should now be recognized from all ports for Guide path
- added new option 'farenheit'
- add 16197
- removed button debouncing, A and Y are more useful exiting from miniblades but will be touchy on older dashes
- tweaked boot time button checker, it should now possible to hold a button before the controller syncs (may only be 16197+)
- add corona bl detection to xelllaunch

Attached Files



#2 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 19 October 2012 - 12:38 AM

Okay, hopefully I am not misinterpreting this announcement. Can this possibly mean that my old phatt console with a Falcon (v3.0) MoBo CB: 5771 which means that I have the original RGH which I thought was prevented from implementing a Dash any higher than the one that preceded 15572 can now use the latest and greatest Dash 16197? I did not see any availability of Dash 16197. Has Christmas come early or is this a sick joke on the poor Noobs like myself? :D

#3 JPizzle

JPizzle

    That Fuckin Guy

  • Administrators
  • 2315 posts
  • LocationRight Behind You

Posted 19 October 2012 - 01:28 AM

Okay, hopefully I am not misinterpreting this announcement. Can this possibly mean that my old phatt console with a Falcon (v3.0) MoBo CB: 5771 which means that I have the original RGH which I thought was prevented from implementing a Dash any higher than the one that preceded 15572 can now use the latest and greatest Dash 16197? I did not see any availability of Dash 16197. Has Christmas come early or is this a sick joke on the poor Noobs like myself? :D


http://www.realmodsc...48-xebuild-105/


#4 Judas

Judas

    RMS Freshman

  • Members
  • 1 posts

Posted 19 October 2012 - 04:11 PM

- add nohealth option, disables kinect health pseudo video at game launch

not work for me, anyone try this?
(using FSD3, dashlaunch 3.03, dash 16197)

#5 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 19 October 2012 - 05:26 PM

Okay let's see if I have this correct. Yes, this will allow me with my old phatt Falcon (v3.0) to go to the latest $SystemUpdate from Microsoft which is 16197 after 16197 system files from the zip are combined with my existing NAND image and the NAND is reloaded. I can then apply $SystemUpdate 16197 from Microsoft and then install FSD 3.03. $SystemUpdate 16197 from Microsoft is not available yet on the MS web site as I believe it is being rolled out on a limited basis, perhaps overseas initially. How was the restriction of not going past the Dashboard prior to 15572 overcome on a Falcon (v3.0) CB:5771 original RGH console? I'm curious what the restriction was and how it was overcome. The technical folks that do this work for the scene are incredibly gifted and I certainly appreciate their efforts. Thanks, outofwork

#6 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 19 October 2012 - 08:52 PM

If the Dashboard limitation is due to the way that the original RGH mod was implemented and it's a hardware restriction then I would think that it's almost impossible except in rare occasions for software/microcode (like the XGD3 LiteOn burner mod) to overcome a hardware constraint. So, the more I think about it the more I think I am misinterpreting the last announcement even though it says ALL JTag/RGH consoles can upgrade to $SystemUpdate 16197. Please set me straight on this and I will go away... at least for a while. :) Thanks, outofwork

#7 dnacid

dnacid

    RMS Freshman

  • Members
  • 3 posts

Posted 20 October 2012 - 12:10 AM

I've installed dash 16197 with no any problems on my xbox phat (falcon) rgh1 cb 5771. I used the new Version of xebuild GUI.

#8 JPizzle

JPizzle

    That Fuckin Guy

  • Administrators
  • 2315 posts
  • LocationRight Behind You

Posted 20 October 2012 - 01:08 AM

If the Dashboard limitation is due to the way that the original RGH mod was implemented and it's a hardware restriction then I would think that it's almost impossible except in rare occasions for software/microcode (like the XGD3 LiteOn burner mod) to overcome a hardware constraint. So, the more I think about it the more I think I am misinterpreting the last announcement even though it says ALL JTag/RGH consoles can upgrade to $SystemUpdate 16197. Please set me straight on this and I will go away... at least for a while. :)

Thanks,
outofwork


:( you're still not understanding how your console works. Right now you are NOT running the original MS 15xxx dashboard, you are running FreeBOOT (made with XeBuild) 15xxx dashboard. You can ONLY update your hacked RGH/JTAG console when a new version of XeBuild is released that can create Freeboot for the newer dashboard and this is now possible with 16197. So take your nand dump (current or original) and run it through XeBuild to create a new nand image with 16197 dashboard. Flash it to your xbox using nand flasher 360, install the new dashlaunch and then run the $systemUpdate for the new dashboard and it will install all the new files to your hdd and kinect.


#9 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 20 October 2012 - 10:41 PM

You're absolutely correct. Thanks for clearing that up. So I will give this a shot. Unfortunately the older you get the longer it takes to finally sink in. Actually I never did have a completely clear understanding of how all the different pieces fit together. I'm still not 100% but I am getting there thanks to your assistance. Thanks, outofwork

#10 LvL

LvL

    RMS Freshman

  • Members
  • 5 posts

Posted 21 October 2012 - 01:05 AM

How to make from this FS a one run file? i want to make single install file. Can somebody help?

#11 JPizzle

JPizzle

    That Fuckin Guy

  • Administrators
  • 2315 posts
  • LocationRight Behind You

Posted 21 October 2012 - 05:34 AM

sorry I'm not sure I understand the question but I think you are asking how to install this and F3 together, use the installer that came out with F3 and it will install the latest version of F3 and dashlaunch if you enable the 'download latest' option. You can find it in the F3 release post.


#12 LvL

LvL

    RMS Freshman

  • Members
  • 5 posts

Posted 21 October 2012 - 10:29 AM

sorry for my english.
i ll try to describe
i want to make like: freestyle3 and dashlaunch 3.03 will should install together from one xex file or from GOD container. How?

When i run installer from dashlaunch 3.03 i see orange screen and i cant understand what to do. How to install ? may be somebody can make stap-by-stap instruction? please.

#13 JPizzle

JPizzle

    That Fuckin Guy

  • Administrators
  • 2315 posts
  • LocationRight Behind You

Posted 21 October 2012 - 02:25 PM

what is your native language? Dashlaunch has many translations


#14 LvL

LvL

    RMS Freshman

  • Members
  • 5 posts

Posted 21 October 2012 - 07:23 PM

what is your native language? Dashlaunch has many translations

all problems i decided. thanks a lot

stay true men ;)

#15 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 21 October 2012 - 09:10 PM

There are rewards and punishment to being too conservative and I have recently experienced both. :lol: However, I am now ready to apply $SystemUpdate 16197 from Microsoft to complete the updates. Can I use the default.xex from $SystemUpdate 15574 or are they update specific? I have $SystemUpdate 16197 but I don't have the default.exe for it. Yes, I am being very cautious. Once I finish the 16197 update is there a way to make a complete Ghost-type image of the HDD drive for backup purposes so that I could do a restore in the event of a hard drive failure? Thanks, outofwork

#16 cory1492

cory1492

    TeamFSD

  • Moderators
  • 45 posts
  • LocationI'm right here dude.. no your other here!

Posted 21 October 2012 - 10:10 PM

The default.xex is for installing from "burn your own CDROM", if you are using a usb stick you won't need it. Format your usb stick to FAT or FAT32, copy the folder $SystemUpdate to the root of it (rename it to $$ystemUpdate if you have dash launch option noupdater set to true) and boot with the usb stick plugged in. You should be prompted to update right after the bootlogo - NOTE: this is NOT for updating your system flash from 15574 to 16197, it is ONLY for installing avatar and kinect binaries AFTER you update and reflash your system flash with xebuild. I hope that is clear enough?

Judas:
yes the nohealth problem is known and will be fixed for the next version. AFAIK the only ver it doesn't work for is 16197.

#17 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 21 October 2012 - 10:51 PM

Yes, that's clear and I will use the USB stick. However, given that I am innately curious... is the default.xex update specific? :D Thanks, outofwork

#18 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 22 October 2012 - 01:23 AM

Well I seem to be snake bit yet once again no doubt due to my not having a clear understanding of the process. What would logically seem to be the easiest step in this won't work. I formatted a USB stick FAT32 bootable, copied over the $SystemUpdate folder and renamed it to $$ystemUpdate. Then tried to boot it up (normal power on) by inserting it in one of the USB ports on the front of the console. It went into FSD 3 with no option for any update. I then tried booting with the eject button that kept searching for a xexon.elf file. Clearly that's not the right way. I'm missing something here. How does the console know what to do with a folder named $$ystemUpdate? There is no default.xex file in the root directory except all of those separate ones inside of the now renamed $$ystemUpdate folder which is not what I want to do for sure. This process should kick itself off but I don't know how it can without a default.xex file. Sorry for being a PITA, outofwork

#19 outofwork

outofwork

    RMS Freshman

  • Members
  • 73 posts
  • LocationMaryland

Posted 22 October 2012 - 03:11 PM

I'm still fiddling with this and here is what I just did. I booted up into FSD 3 and then went into the normal Xbox Dashboard went into System Settings, Console Settings, System Info and I inserted the USB stick with $SystemUpdate 16197 with renamed the folder to $$ystemUpdate and got the following: ? Update Required To proceed , security and program updates are required. System updates will be added to ensure security and proper functionality. If you decline, you will be returned to the Xbox Dashboard. Do you want to accept the update? I did not proceed because I'm a little bit concerned about the security wording in the message. Is this the normal update message and is it safe to install the update? I still cannot figure out why the USB stick won't boot. Also, the system info displayed shows the following: Current Setting: Dashboard: 2.0.16197.0 Is this because when I ran XeBuild GUI with the system files for 16197 it updated the NAND (?) but the $SystemUpdate will update the binary code for the functionality for the 16197 update? I'll be damned if I know why this is still confusing. Is there a basic tutorial that goes through the functional description of each of these pieces? Thanks, outofwork

#20 JPizzle

JPizzle

    That Fuckin Guy

  • Administrators
  • 2315 posts
  • LocationRight Behind You

Posted 22 October 2012 - 11:02 PM

when that warning popped up it was working, your nand is already on that dashboard so it wont touch it but it needs to update the files on your Hdd and Kinect if you have one. The system just knows how to install the files, there is a manifest file in that folder that tells the system how to install it.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Change Theme!