Y314K

We get the names from xbox.com. you could do it on pc if you want, you can use an sqlite application to edit the content.db located in the data/databases folder.

Could even write a replace query for that like replace " ®" with "" or something.

Great unexpected supprise...

Are the games on the vid extracted ISO's or god format ??

MMC coronas are ONLY with consoles that have 4GB Internal Memory (no HDD generally), there are however Trinity also with 4GB memory (they have a small addon module instead of the MMC controller/eMMC)

Good info....  Gonna need to to keep an eye out for those.  Got a friend that wants my help finding a modded XBox 360.  Gonna try my best to make it a Nand version.

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.

Hell yeah, MMC consoles can be a royal pain in the ass sometimes... there are several more points you have to connect to, you have to find compatible hardware (a MMC compatible SD reader) it's also quite common for windows to cause you trouble aswell (BSOD), another somewhat common issue is antivirus software causing inconsistencies while reading/writing (corrupting the data for you on-the-fly)

Now the MMC consoles are mostly the non HDD Slims that come with the 4GB internal MU's right ?  The ones without a inernal HDD.

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.

If the patches causes the console to mangle the SMC it's not so easy to just "reflash" the dump you've got... and, how would we know what's wrong if you simply reflash the NAND?? how do you fix such issues with the patches if you have no idea what the cause is?

Also, MMC consoles can be harder to fix then NAND consoles even if you have a dump from it...

 

This guide only works with NAND consoles, MMC consoles won't work with that guide

Ahh...  Glad I've never had to deal with a MMC console yet....  Guess Nand's are just much easier to deal with...

Personally i do NOT recommend setting static fan speed, use the option to change your temp tresholds instead, it's by far safer because it'll raise the speed when it's needed...

I understand that thresholds supposed to be the normal & best option for the cooling vs fan longevity debate.  But after trying it with thresholds set @ CPU: 60c/GPU: 60c/EDRam: 60c, in practice it just not good on the noise front.  Everything is fine at boot up but once the CPU hits 60c it sounds like an old helicopter is about to take off.  And it takes a good amount of time for the temp to get a couple of degrees below 60c for it to start to wind down.  I am not sure @ what level the fans run when they haven’t hit the threshold but I think keeping them @ a constant 45% should still last a while.

I did notice something...  Since the CPU controls the GPU fan on the slims...  It seems the staggering of the temp should always have a 4 degree for GPU & 6 degree for EDRam difference at whatever you set the CPU temp too...  For example... If I set the CPU to 60c.  Then I notice the GPU & EDRam would run about 4-6 degrees cooler then the CPU.  Just something I notice... Will test thresholds some more but I really don't like the continue changing of the noise ranges when using it.  It gets annoying fast.  Maybe of one would keep the XBox in a entertainment cabinet or if you always run your games crazy loud this would not be a problem.

That only works if you have nothing mapped to the B button, you can use any button that has no entry to bypass the default option, this includes:

A, B, X, Y, Start, Back and LB... RB is NEVER mapped to anything, it's the button that is used to bypass the default path...

Right...  But the button remaps are when rebooting or restarting.  On top of those options.  The big X "Guide" button between Start & Back will give you the two choices to go into "Family Settings" & "System Settings" that are only located in the NXE Dash...  They are in the last tab of the Guide Menu.  So once in "Family Settings" or "System Settings" you are back in NXE.  You just hit ( B )  to back up into the full/front NXE menu.

One way is how to do it on the front end with rebooting or booting & this other way is how to do it from any program/game/dash from the X "Guide" button...  With this option even if DL was not working properly you would still be able to go into XEXMenu start an app/homebrew & still would be able to choose to go back into NXE without rebooting.

From Prayer @ http://www.realmodscene.com/index.php?/topic/1092-fan-speed-trinity-fsd-problem/#entry8071

 

1. Open Dashlaunch 2. In Dashlaunch find the "System Info" tab by pressing LB or RB3. In the System info tab You'll see the CPU, GPU and EDRAM Target Temperatures. They indicate on which temperature the fan will kick in. So let's say you set all your temps at 60, if the GPU, CPU or EDRAM go beyond 60°c the fan will start spinning faster and thus lowering the temperature to its desired point that you have selected.4. Check the small box beside the "CPU Fan Speed Override". This will make your fan spin at an auto speed.5. On the bottom of the screen select "Save Config" and by pressing B you'll exit Dashlaunch.And that's it!By the way, I usually keep my fan overriden. It is spinning at a constant speed of 45% and my temperatures never go beyond 60°c! You can do that by not checking the box that stands beside the "CPU fan override" and by setting your desired fan speed in that very same tab

The 45% override option has given me the best fan noise vs. temperatures results.  It keeps the CPU temp right around 58.4c & the rest even lower.  Perfect.  Will have to test it out when gaming in the future but it should still keep it at a good range.

Even at 40% override my CPU temp stays around 62.4c when I use to hit 72c idling.  And the noise level is constant so you don't get the helicopter is taking off fan affect like you do when using auto targets.

There is more info from Prayer here too:  http://www.realmodscene.com/index.php?/topic/401-what-is-the-proper-temperature/page-2

Problem solved. Thank you Swizzy. your help is much appreciated.

Another option if you don't want do a full reboot of the XBox..  From FSD or any other program hit the middle X button & scroll to the right till the last part of the menu called "Settings".  Then choose either "Family Settings" or "System Settings".  This will get you to NXE.  Hit ( B ) until you get to the main NXE Menu.

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.

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...

We've already got a whole team of testers, and each of them have the ability and know-how to reflash their console in case of total disaster... are you like that? do you know how to fix possibly unknown issues where your entire NAND is f*cked up? if not; don't ask to be something that could potentially be dangerous as f*ck

I myself plan to wait for an official release of DL v3.13 but all they will have to have  to do is have a backup of anything they don't want to loose content wise & a good nand backup...  And just follow this guide:

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...