Oliver Brooks 0 Posted June 24, 2014 ok i was wondering when the new dashlauch cause i got my rgh for a few days and didnt install it cause of the update and there was meant to be 3.13 but if i used 12 would it work or would it crashed plz reply thank you Quote Share this post Link to post Share on other sites
Swizzy 2083 Posted June 24, 2014 What kernel are you running? if you are running 2.0.16747.0 or older you can run DL 3.12 without any issues, otherwise it'll not work at all... (it'll refuse to start with your dashboard) Quote Share this post Link to post Share on other sites
Y314K 0 Posted June 24, 2014 On my Trinity RGH 2.0 Xbox 360 DashLaunch 3.12 is working fine on 16756. Maybe because of the way I went about upgrading. Started off with 16547 (I think I had DashLaunch 3.12 setup on it) but I could be wrong... I backed up my launch.ini just in case. Then I upgraded to 16747 including the avatar upgrade... Backed up my launch.ini again. I assumed DL was fine since my consose booted to FSD like it should. Then I Upgraded to 16756 with Avatar upgrade & my X360 always loaded to FSD... I then checked to see if I could run & edit DL from FSD or from XEXMenu & sure enough I can edit and safe paths & settings just fine... (Seems I've been running DL v3.11 all this time) Maybe I was just lucky or maybe it had to do with my technique... Specially since this was my guide: https://www.youtube.com/watch?v=HFvQjYxHa3Q Update: Seems I've been running DL v3.11 all this time. And after messing with my DL & FSD folder names & location I screwed something up. Will uninstall DL v3.11 & will try to install DL v3.12 & will see how it goes... Quote Share this post Link to post Share on other sites
saywaking 289 Posted June 24, 2014 did you test the entertainment applications ? maybe you can work with fakelive and up2date apps/ dash Quote Share this post Link to post Share on other sites
Swizzy 2083 Posted June 24, 2014 On my Trinity RGH 2.0 Xbox 360 DashLaunch 3.12 is working fine on 16756. Maybe because of the way I went about upgrading. Started off with 16547 (I think I had DashLaunch 3.12 setup on it) but I could be wrong... I backed up my launch.ini just in case. Then I upgraded to 16747 including the avatar upgrade... Backed up my launch.ini again. I assumed DL was fine since my consose booted to FSD like it should. Then I Upgraded to 16756 with Avatar upgrade & my X360 always loaded to FSD... I then checked to see if I could run & edit DL from FSD or from XEXMenu & sure enough I can edit and safe paths & settings just fine... Maybe I was just lucky or maybe it had to do with my technique... Specially since this was my guide: https://www.youtube.com/watch?v=HFvQjYxHa3Q You have the unofficially patched DL 3.12 which does indeed work on 2.0.16756.0, however... you have no idea what they patched exactly or if everything works out a-ok or not, it might look like everything is working, but it's quite possible that one or more feature is broken... Quote Share this post Link to post Share on other sites
Y314K 0 Posted June 25, 2014 did you test the entertainment applications ? maybe you can work with fakelive and up2date apps/ dash Sorry, no.. Did not test those before I messed something up... Gonna need to uninstall & reinstall DL and see how it goes... You have the unofficially patched DL 3.12 which does indeed work on 2.0.16756.0, however... you have no idea what they patched exactly or if everything works out a-ok or not, it might look like everything is working, but it's quite possible that one or more feature is broken... After checking which version of DL I had it seems to be DL v3.11... I though I was updating DL with the kernel updates but I don't think that was the case. But then I renamed the DL folder on XeXMenu & tried to move the FSD files & now DL boots things normally but I can not run DL from FSD (It gives me a app error & goes into NXE) but I am able to run it from XeXMenu... Will have to uninstall & reinstall DL & FSD & test it again... Quote Share this post Link to post Share on other sites
Swizzy 2083 Posted June 25, 2014 Sorry, no.. Did not test those before I messed something up... Gonna need to uninstall & reinstall DL and see how it goes... After checking which version of DL I had it seems to be DL v3.11... I though I was updating DL with the kernel updates but I don't think that was the case. But then I renamed the DL folder on XeXMenu & tried to move the FSD files & now DL boots things normally but I can not run DL from FSD (It gives me a app error & goes into NXE) but I am able to run it from XeXMenu... Will have to uninstall & reinstall DL & FSD & test it again... There's a difference between running the Dashlaunch installer and Dashlaunch itself... Dashlaunch starts with your console and launches stuff automatically... The installer just runs even if Dashlaunch don't run, and it lets you install dashlaunch, i bet that if you use the installer to update/install dashlaunch it'll NOT work anymore Quote Share this post Link to post Share on other sites
saywaking 289 Posted June 25, 2014 but if he had 3.11 why it works with the new dashboard ? Quote Share this post Link to post Share on other sites
Swizzy 2083 Posted June 25, 2014 but if he had 3.11 why it works with the new dashboard ? I think he's having issues knowing what's what... Dashlaunch installer 3.11 works on ANY dashboard while Dashlaunch itself only runs on the compatible dashboards (as written in the readme for each version) Quote Share this post Link to post Share on other sites
Y314K 0 Posted June 29, 2014 There's a difference between running the Dashlaunch installer and Dashlaunch itself... Dashlaunch starts with your console and launches stuff automatically... The installer just runs even if Dashlaunch don't run, and it lets you install dashlaunch, i bet that if you use the installer to update/install dashlaunch it'll NOT work anymore Finally had some time to do a lot of testing on different kernels & u'r right that updating/installing DashLaunch will not work from K:16756. So you can't install it normally on K:16756. But once you have it working under K:16747 & even from K:16756 it will not crash & it will let you change/save the settings using the installer. And it will load FSD at startup fine & it will enable the FSD pop up menu with the temperatures & file browser within NXE if you reinstall FSD. Running DL v3.12 or v3.11 from K:16756 will gray out the "Unload DashLaunch" and "Uninstall". Do not try the "Install This" option. That creates a 2nd boot option that crashes & sends u to NXE. I had read folks saying DL would crash on them & FSD would not load for them, So to me being able to load FSD fine at startup & being able to change/save settings means it's working fine although it's not fully/correctly installed on the latest kernel. but if he had 3.11 why it works with the new dashboard ? Both worked for me although they are not properly/fully/correctly installed when ran on K:16756. I was just sharing that for me it was not crashing & FSD was/is loading fine at startup. But Swizzy is right. A DL 3.13 version is needed for a full installation. I think he's having issues knowing what's what... Dashlaunch installer 3.11 works on ANY dashboard while Dashlaunch itself only runs on the compatible dashboards (as written in the readme for each version) I guess once the saved Launch.ini is on the root. The auto boot to FSD will work from flash or somewhere. Just tried it. Deleted the DL folder & restarted the XBox but left the Launch.ini & again it booted to FSD. Deleted the Launch.ini & it loaded to NXE. Added the Launch.ini again & FSD loaded. Guess once it's installed correctly on K:16747 all that matters is the root Launch.ini. But the only way edit it from a DL interface is to recopy the DL Installer folder. Eventually I'll reformat my internal drive & clean all cache. Will note how DL behaves then on the wrong kernel when added to it. I know the debug log has a kernel error. But not sure if that means it will crash DL Installer after that. Bottom line, for me, DL v3.11 & v3.12 are functional. Even if they are not correctly installed on K:16756. But would love to take DL v3.13 for a spin when it's ready. Quote Share this post Link to post Share on other sites
Swizzy 2083 Posted June 29, 2014 Dashlaunch consists of 3 parts: 1. The Installer (installer\default.xex) 2. The actual Dashlaunch (launch.xex installed to flash along with it's "lhelper.xex") 3. The configuration file (launch.ini) which tells dashlaunch what to do and so on... Now, The installer/configuration is compatible across ALL versions, the installer will turn to a configuration tool once you've got Dashlaunch installed already... DL 3.11 doesn't work on dashboards > 2.0.16547.0, DL 3.12 works on 16747 aswell but NOT 16756 unless of course you have one of the unofficial versions (patched by the folks that make XBLSE) If you have the "Autoboot F3" (meaning, your launch.ini points to F3 in it's default=...) and it's working on a version not mentioned in the readme file of the dashlaunch version you are using, then you are using one of the unofficial launch.xex files, it doesn't matter what you think you know about how this works, i KNOW how it works because i am in contact with cOz and he's explained it to me in the past... hell, if you tried building 16756 with the latest official xeBuild GUI (found here: http://www.homebrew-connection.org/files/xbox/nand_builder/xeBuild_GUI/dl_xeBuild_GUI_2.093.rar) you'd notice that your autoboot don't work... (you'd have to add the 16756 patches tho) So, as you can see... the OFFICIAL version DO NOT WORK on 16756... it doesn't matter what ppl say on the internet, they have no idea what they're talking about (they THINK they do, but they clearly do NOT) Quote Share this post Link to post Share on other sites
Y314K 0 Posted June 29, 2014 Dashlaunch consists of 3 parts: 1. The Installer (installer\default.xex) 2. The actual Dashlaunch (launch.xex installed to flash along with it's "lhelper.xex") 3. The configuration file (launch.ini) which tells dashlaunch what to do and so on... Now, The installer/configuration is compatible across ALL versions, the installer will turn to a configuration tool once you've got Dashlaunch installed already... DL 3.11 doesn't work on dashboards > 2.0.16547.0, DL 3.12 works on 16747 aswell but NOT 16756 unless of course you have one of the unofficial versions (patched by the folks that make XBLSE) If you have the "Autoboot F3" (meaning, your launch.ini points to F3 in it's default=...) and it's working on a version not mentioned in the readme file of the dashlaunch version you are using, then you are using one of the unofficial launch.xex files, it doesn't matter what you think you know about how this works, i KNOW how it works because i am in contact with cOz and he's explained it to me in the past... hell, if you tried building 16756 with the latest official xeBuild GUI (found here: http://www.homebrew-connection.org/files/xbox/nand_builder/xeBuild_GUI/dl_xeBuild_GUI_2.093.rar) you'd notice that your autoboot don't work... (you'd have to add the 16756 patches tho) So, as you can see... the OFFICIAL version DO NOT WORK on 16756... it doesn't matter what ppl say on the internet, they have no idea what they're talking about (they THINK they do, but they clearly do NOT) Thanks a lot for this info... I should be able to fully get rid of DL to do some better testing. Before, I was just getting rid of the Installer & Launch.ini. I should be able to go into the Flash & copy & delete the "Launch.xex" & "IHelper.xex" to truly uninstall DL without crippling anything else other than DL right? Can both .XEX’s files just be copy back into Flash or would they need to be injected for them to go back to working like before? Not sure what DL 3.11 version my RGH come with, but it seem to continue to do what I asked of it on all 3 kernels I tried it on. I just used the Installer to change the settings for it. It could be that I have a mod DL but since I don't have the original Launch.ini I can't really tell if it ever pointed to F3 as the default. My current .ini points to "Default = Hdd:\Freestyle\default.xex". And I can't find any mention of F3 on the .ini. These are the two hashes for both files in my Flash. I checked them against the two files in the installer & the Launch.xex doesn’t match against v3.07, v3.08, v3.09, v3.10, v3.11 or v3.12. So I probably do have some extra modded .XEX but I have not idea who's modded .XEX. Launch.xex - MD5: 08C533E4288CA6D25398E1235B4A1E43 IHelper.xex - MD5: 34040425A39D892432939D640D2239AE I can upload the Launch.xex if anybody wants it. Let me know... Bottom line, Swizzy was right from the beginning. I seem I have a modded unofficial Launch.xex in my XBox's Flash that just continues to work. That's the way I recieved it. Guess I better not format my internal drive untill DL v3.13 comes out. Thanks for sharing all the knowledge Swizzy. Quote Share this post Link to post Share on other sites
Swizzy 2083 Posted June 29, 2014 The safer way to do this is to reflash your nand rather then mucking about in "flash" as it's dangerous to do In the official release of dashlaunch you'll always have a zip file named "for xxbuild" or something like that, inside of that you'll find the launch.xex/lhelper.xex which the installer/builder(s) put in your nand, these are the files you should check your MD5 against, if they do not match what you expect it to be, it's clearly modified Something you must also keep in mind is that when you upgrade your kernel you reflash the entire nand (meaning whatever was in flash is no longer there, it's been replaced with whatever was in your new nand image) most builders have the latest dashlaunch at the time of the release, if you got the "XBLSE" version of xeBuild GUI it might be updated by the XBLSE Team with their modification... (i have nothing to do with this version other then making the original package which they've added to) Quote Share this post Link to post Share on other sites
Y314K 0 Posted June 29, 2014 The safer way to do this is to reflash your nand rather then mucking about in "flash" as it's dangerous to do In the official release of dashlaunch you'll always have a zip file named "for xxbuild" or something like that, inside of that you'll find the launch.xex/lhelper.xex which the installer/builder(s) put in your nand, these are the files you should check your MD5 against, if they do not match what you expect it to be, it's clearly modified Something you must also keep in mind is that when you upgrade your kernel you reflash the entire nand (meaning whatever was in flash is no longer there, it's been replaced with whatever was in your new nand image) most builders have the latest dashlaunch at the time of the release, if you got the "XBLSE" version of xeBuild GUI it might be updated by the XBLSE Team with their modification... (i have nothing to do with this version other then making the original package which they've added to) Great info again Swizzy... I forgot to check the xeBuild_GUI_2.093 (16756).zip I got from https://www.youtube.com/watch?v=HFvQjYxHa3Q It comes with the same hash modded Launch.xex... Can't tell if it's a "XBLSE" release or not. But it must be theirs since they have the monetary motivation to getting folks on K: 16756. But I just know that it functions fine on my Trinity. Thanks again Swizzy for the patience & knowledge to let me get to the bottom of this. Quote Share this post Link to post Share on other sites
