Topic: Dash Launch v2.20 (Read 734 times)

krizalid · « **Reply #15 on:** April 07, 2011, 05:00:00 AM »

WARNING!!! I found a BUG! a nasty one to my taste.

After flashing with freboot0.20 using 12625 and applying DashLaunch2.20, all is good, but if you apply DashLaunch2.20 again to setup the extra settings like LIVE DNS blockage, etc it will boot into E79.

This happened to my Falcon CB 5770... Will be reflashing via LPT tomorrow morning.

It's 3am and I'm sleepy

Just a heads up Guys!!!

Notes: This effect of booting to E79 did not happen using freeboot 12625 built with the unofficial fbbuild0.12, it only happens on freeboot 12625 built with fbbuild0.20...

Now I don't know why, but it happened!

SilentBob1638 · « **Reply #16 on:** April 07, 2011, 09:42:00 AM »

What are the differences between the normal LIVE "blocker" and the alternate "strong" DNS list? What about an external HOSTS file we can manually update (dynamic blocklist)?

tk_saturn · « **Reply #17 on:** April 07, 2011, 09:47:00 AM »

ignore what I posted, I made a schoolboy error and i'ev had 0 sleep.

In FSD2 on the Avatar tab it tells you if the ping patch is active, which is useful. Would it be possible for them to determine what version of DashLaunch is installed and which patches are active and have that information displayed on that tab?

antisniperspy · « **Reply #18 on:** April 07, 2011, 10:11:00 AM »

Hi, Is this for 12611 dash or 12625 dash or both? I still have 12611 and have had no reason to update.

Thanks

Aldanga · « **Reply #19 on:** April 07, 2011, 10:37:00 AM »

QUOTE(razkar @ Apr 7 2011, 01:30 AM)

If you have a freeboot image with 12625 kernel you will need the full m$ 12625 update and rename it $$systemupdates (it's written in the nfo

)

I still have a 12611 kernel. I've read the nfo and messed with settings trying every combination I could think of, but the update still wouldn't take. I'll probably just update to 12625 later today and add the avatars then.

antisniperspy · « **Reply #20 on:** April 07, 2011, 11:25:00 AM »

QUOTE(tk_saturn @ Apr 7 2011, 01:03 PM)

Both and 9199 (remember, DL now patches the version checks). It's fine on my 12611, If I had more sleep I probably would have the common sense not build and flash a fb0.20 12611 when it already had 12611...

Thanks so this fb0.20 is offical and not the onther one released about a month ago?

cory1492 · « **Reply #21 on:** April 07, 2011, 12:14:00 PM »

QUOTE(tk_saturn @ Apr 7 2011, 02:39 AM)

There may be a slight bug, it may just be from how it works or I may just be misunderstanding it. Since 12611 like others i've had the issue where using the NXEmini to change to FSD2/ NXE etc would only work from within FSD2/ games/ homebrew etc and not from the NXE itself. Changing nosysexit to true it fixes this. However, if you do that selecting System Settings from NXEmini takes you back to your default item and not System Settings unless you are already in NXE. Not be able to go to system settings from NXEmini I can live with, but not being able to use NXEmini to go back to FSD from NXE was driving me up the wall. Might be better to have nosysexit default to true instead of false.

set (or don't set it to true)
dvdexitdash = false
there is no way for dl to tell the difference between dvd exit and normal miniblade exits, unfortunately.

tk_saturn · « **Reply #22 on:** April 07, 2011, 12:40:00 PM »

Correct as ever, bugger. You could have mentioned it in the previous thread, I even posted the launch.ini

moeom · « **Reply #23 on:** April 07, 2011, 01:46:00 PM »

QUOTE(ILLusions0fGrander @ Apr 7 2011, 12:05 AM)

FreeStyleDash (FSD) the alternative dashboard for JTAG 360s has its own sources for screenshots and boxart, they are completely separate from xbox live and retail xbox 360's.

I knew that.....woops....I thought I was missing something in the original MS dashbaord. Lol. My bad, I got excited for a second.

krizalid · « **Reply #24 on:** April 07, 2011, 03:01:00 PM »

Ok guys, as to my previous post here: POST17

I got it fixed and working all good. Here is what really happened.

I didn't just use the new fbBuild0.20 with new DashLaunch2.20, I also happened to use smc_util_v1.1 for the first time.

I thought if I extracted my own SMC corresponding to the mobo, etc, and patch it and flash it with freeboot it would be better, but I guess NOT!.

DashLaunch2.20 currupted my smc on NAND when ranned the setup the second time to add the LIVE DNS blocks and other extra feature settings. I was able to reproduce this this morning cause I was curious.

So what I decided to do is use the old SMC files I was using before (extracted from xell free60 images and patched with smc_io) and created my freeboot image and I ranned DashLaunch2.20 three times after flashing freeboot image 12625 and all is going well.

Now, I don't know if this is a DashLaunch incompatiblity with the SMC created with this tool or the SMC created with this tool cannot launch xam.xex using DashLaunch patches. I leave this for the pros.

Here's some information for you all! Have a great day!

tk_saturn · « **Reply #25 on:** April 07, 2011, 04:30:00 PM »

I've a couple of consoles all of which have hacked SMC's generated by blackaddr's tool, and have been so for several months. So far none have had any issues with DL and those SMCs. Out of curiousiy I updated my Jasper 512MB to 12625, and after running the DL installer several times the console is still booting. If it were to bugger any console up, i'd imagine it would be a BB Jasper.

I'd query if you're using blackaddr's tool correctly, as for a start you're using the wrong version. You also mention using smc_io, which means you haven't read smc_util's readme.

TheRealJPizzle · « **Reply #26 on:** April 07, 2011, 07:15:00 PM »

QUOTE(Aldanga @ Apr 7 2011, 12:37 PM)

I still have a 12611 kernel. I've read the nfo and messed with settings trying every combination I could think of, but the update still wouldn't take. I'll probably just update to 12625 later today and add the avatars then.

name the folder $$ystemupdate

Aldanga · « **Reply #27 on:** April 07, 2011, 07:19:00 PM »

I tried that already. I'm going to try again tonight (I've redownloaded the update and I'll see if that works), but just update to the newest rebooter if it doesn't work.

TheRealJPizzle · « **Reply #28 on:** April 07, 2011, 07:27:00 PM »

; when set to false, xbox will be capable of finding system updaters
; if not present this is set to TRUE

add this line to your launch.ini

noupdater = false;

Aldanga · « **Reply #29 on:** April 07, 2011, 07:30:00 PM »

I've done that too. Believe me, I'm no idiot. I've read the information which was released with Dash Launch and have tried what is recommended. None of it has worked. So I've concluded that either (1) my update was corrupted, (2) my USB stick hates me, or (3) there's a bug. I highly doubt there's a bug, so I'm going to try again tonight using some different methods and a freshly downloaded update.

Author Topic: Dash Launch v2.20 (Read 734 times)