|
What's new/fixed: * export option info along with the rest of dash launch info struct export * add multi version compatibility to installer and plugin * add 12625 patch set and offsets * new LIVE content hook patching, does auto yaris swap as well as extracted XBLA should work more consistently (hopefully) - added unhandled exception handler, dumps except info to UART/file and exits to dash/default item when apps don't have their own exception handler (instead of crash), disable by setting 'exchandler = false' in ini file. * added ini path setting (dumpfile) for capturing crash logs to a file, capture device must be connected at console boot time * added 'safereboot' option for those who have JTAG that have applied blackaddr's smc reboot fix, instead of 'hard' reboot * added option to enable debug strings to print to UART * adjusted patches to remove default UART hooking (less chance of string collision/overlap using DbgPrint via debug out option) * corrected a bug in the flasher ini update settings in regard to noupdater, it was setting nosysexit instead of noupdater value * added live "blocker", reroutes requests to resolve DNS names to loopback * added "livestrong" option to use an alternate list of DNS to block * added ini option to set how long buttons are watched for at boot time * embedding current versions external files into installer, no more messy directory; original paths still work and take priority over embedded files Official Site: n/a, by cOz Download: n/a (built with XDK) Full Readme/NFO: xbins.org |
Full Version: Dash Launch v2.20
I'm not too familiar with JTAG stuff, but it seems as though this had a lot of the stuff that people were really looking for such as "blocking" LIVE connection.
Great work.
Great work.
Very nice - I keep my XBL blocked at the router level which kinda sucks for weather/game icon and pic sets. I will feel less paranoid with the new DNS features =D
QUOTE(ILLusions0fGrander @ Apr 6 2011, 11:12 PM) 
Very nice - I keep my XBL blocked at the router level which kinda sucks for weather/game icon and pic sets. I will feel less paranoid with the new DNS features =D
Wait a minute...how are you supposed to get these features if you cannot connect to LIVE? I'd like to have these...
QUOTE(moeom @ Apr 6 2011, 11:46 PM)
Wait a minute...how are you supposed to get these features if you cannot connect to LIVE? I'd like to have these...
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.
Nice job again. Does anyone know if this will support real time editing/memory editing and Xbox1 games together on the 12625 kernel? I don't see a point in updating unless I can keep my current features. I don't want to lose things like memory editing.
QUOTE(moeom @ Apr 7 2011, 04:46 AM)
Wait a minute...how are you supposed to get these features if you cannot connect to LIVE? I'd like to have these...
FSD2 retrieves screenshots and game covers from catalog.xboxlive.com [65.55.42.202]. All you have to is block all of Microsoft's IP range (65.54.0.1-65.55.255.255) in your routers firewall and then add an exception for that single address.
It's what i've done for ages.
Would prefer the files to be seperate rather than embeded in a default.xex, I prefer to build FreeBoot images with DashLaunch in from the start.
QUOTE(tk_saturn @ Apr 7 2011, 01:27 AM)
FSD2 retrieves screenshots and game covers from catalog.xboxlive.com [65.55.42.202]. All you have to is block all of Microsoft's IP range (65.54.0.1-65.55.255.255) in your routers firewall and then add an exception for that single address.
It's what i've done for ages.
Would prefer the files to be seperate rather than embeded in a default.xex, I prefer to build FreeBoot images with DashLaunch in from the start.
Really, what's the difference if you build the freeboot image with the dash launch patches pre installed or if you run the installer .xex after flashing freeboot? You have to do a second flash I guess but i've never had any problem. They embedded all the files into the installer on this one.
QUOTE(tk_saturn @ Apr 6 2011, 10:27 PM)
FSD2 retrieves screenshots and game covers from catalog.xboxlive.com [65.55.42.202]. All you have to is block all of Microsoft's IP range (65.54.0.1-65.55.255.255) in your routers firewall and then add an exception for that single address.
It's what i've done for ages.
You should really check a bit more often than once... a catalog is pulled from catalog.* which usually points to other servers depending on region. During busy times the DNS will be routed to datacenters outside the IP range you mention, but usually closer to your location.
QUOTE
Would prefer the files to be seperate rather than embeded in a default.xex, I prefer to build FreeBoot images with DashLaunch in from the start.
<cough>xextool<cough>extract resources<cough>
Wow, I really should get my throat checked I think
Should the applied patches prevent me from updating avatar data with the 12611 update? I got a new HDD and updated Dash Launch. Now my console won't run the update. I tried USB, but don't have any newer games with the update so I can't check if USB is the issue.
QUOTE(Aldanga @ Apr 7 2011, 08:20 AM)
Should the applied patches prevent me from updating avatar data with the 12611 update? I got a new HDD and updated Dash Launch. Now my console won't run the update. I tried USB, but don't have any newer games with the update so I can't check if USB is the issue.
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
)
Is the hacked xbox 1 emulator fixed with this yet?
I don't have a way to know at this moment... just asking thanks!
I don't have a way to know at this moment... just asking
thanks!
QUOTE(krizalid @ Apr 7 2011, 10:11 AM)
Is the hacked xbox 1 emulator fixed with this yet?
I don't have a way to know at this moment... just asking
thanks!I think NO, when i load a Xbox One game the Box shut´s down.
It's clear [c0Z] has been busy with this, and it is... appreciated.
I have an issue with Crackdown and it's DLC with my normal profile (but not with a fresh profile). On starting the game I get a corrupt DLC messege then the console hard reboots (which doesn't look good). Went to see if soft reboot was nicer to the console as I assumed Crackdown would crash as usual; Dashlaunch handles the error and the game continues (and the DLC still works). Nice feature to have added (I know, it's mentioned in the ini).
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.
I have an issue with Crackdown and it's DLC with my normal profile (but not with a fresh profile). On starting the game I get a corrupt DLC messege then the console hard reboots (which doesn't look good). Went to see if soft reboot was nicer to the console as I assumed Crackdown would crash as usual; Dashlaunch handles the error and the game continues (and the DLC still works). Nice feature to have added (I know, it's mentioned in the ini).
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.
Is there a limit to how much you can reduce boot delay to? I tried 0x1 and it's no faster than 0x1A (auto sign in still works regardless, and I can still control what it boots into). My console has taken an extra 2-3 seconds to sync controller on startup for the last few DL revisions, and dropping the boot delay fixes it. But I was expecting bootdelay to control the delay after it syncs controller?
Hi cOz,
many games cannot be paused during cutscenes, tutorial-parts... and so on.
It would be awesome if the game can be paused (freezed) by a button-combo.
Is it possible to write a "pause plugin"?
many games cannot be paused during cutscenes, tutorial-parts... and so on.
It would be awesome if the game can be paused (freezed) by a button-combo.
Is it possible to write a "pause plugin"?
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!
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!
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)?
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?
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?
Hi, Is this for 12611 dash or 12625 dash or both? I still have 12611 and have had no reason to update.
Thanks
Thanks
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.
If you go to SysExt device in FSD2, you should be able to see what is in the System Cache.
On my Samba'd 12611 I have:
Volume in drive Y is SysExt
Volume Serial Number is 0B30-0A45
Directory of Y:\
26/02/2011 06:22 <DIR> .
26/02/2011 06:22 6,100 system.manifest
26/02/2011 06:22 <DIR> Content
26/02/2011 06:22 <DIR> 20314300
26/02/2011 06:22 <DIR> 32000100
1 File(s) 6,100 bytes
Directory of Y:\Content
26/02/2011 06:22 <DIR> 0000000000000000
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000
26/02/2011 06:22 <DIR> FFFE07DF
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000\FFFE07DF
26/02/2011 06:22 <DIR> 00008000
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000\FFFE07DF\00008000
26/02/2011 06:21 15,048,704 FFFE07DF00000002
26/02/2011 06:21 10,170,368 FFFE07DF00000006
26/02/2011 06:21 33,116,160 FFFE07DF00000008
26/02/2011 06:21 978,944 FFFE07DF00000001
4 File(s) 59,314,176 bytes
Directory of Y:\20314300
26/02/2011 06:21 15,503,360 AvatarEditor.xex
26/02/2011 06:21 4,345,856 BiometricSetup.xex
26/02/2011 06:21 114,688 Dash.AttractionScreen.xex
26/02/2011 06:21 835,584 dash.ExtraAVCodecs.xex
26/02/2011 06:21 421,888 Dash.FieldCalibration.lex
26/02/2011 06:21 1,736,704 dash.firstuse.xex
26/02/2011 06:21 466,944 Dash.MP.Offline.lex
26/02/2011 06:21 434,176 dash.natalpregame.xex
26/02/2011 06:21 1,458,176 dash.NuiFirstUse.xex
26/02/2011 06:21 278,528 dash.nuihub.xex
26/02/2011 06:21 1,454,080 Dash.NuiTroubleshooter.lex
26/02/2011 06:21 1,404,928 dashnui.xex
26/02/2011 06:21 413,696 Guide.AvatarMiniCreator.xex
26/02/2011 06:21 249,856 Guide.NuiTroubleshooter.xex
26/02/2011 06:21 2,756,608 livepack.xex
26/02/2011 06:21 11,485 mediasite.xzp
26/02/2011 06:21 16,384 natalsu.xex
26/02/2011 06:21 24,576 nuihud.xex
26/02/2011 06:21 126,976 Xam.Community.xex
26/02/2011 06:21 81,920 Xam.LiveMessenger.xex
26/02/2011 06:21 20,480 Xam.WordRegister.xex
26/02/2011 06:21 573,440 XimeDic.xex
26/02/2011 06:21 69,632 XimeDicCh.xex
26/02/2011 06:21 368,640 ximedicex.xex
24 File(s) 33,168,605 bytes
Directory of Y:\32000100
26/02/2011 06:21 512,000 Xna_TitleLauncher.xex
1 File(s) 512,000 bytes
Total Files Listed:
30 File(s) 93,000,881 bytes
7 Dir(s) 122,863,616 bytes free
SysExt will let you see what is in there and if the avatar etc extensions are installed. If that doesn't work, I'd clear the system cache, build a fresh NAND image and start from scratch.
Also make sure you're using the correct update, the CD version has the default.xex while the USB version doesn't.
Hi, Is this for 12611 dash or 12625 dash or both? I still have 12611 and have had no reason to update.
Thanks
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...
On my Samba'd 12611 I have:
CODE
Volume in drive Y is SysExt
Volume Serial Number is 0B30-0A45
Directory of Y:\
26/02/2011 06:22 <DIR> .
26/02/2011 06:22 6,100 system.manifest
26/02/2011 06:22 <DIR> Content
26/02/2011 06:22 <DIR> 20314300
26/02/2011 06:22 <DIR> 32000100
1 File(s) 6,100 bytes
Directory of Y:\Content
26/02/2011 06:22 <DIR> 0000000000000000
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000
26/02/2011 06:22 <DIR> FFFE07DF
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000\FFFE07DF
26/02/2011 06:22 <DIR> 00008000
0 File(s) 0 bytes
Directory of Y:\Content\0000000000000000\FFFE07DF\00008000
26/02/2011 06:21 15,048,704 FFFE07DF00000002
26/02/2011 06:21 10,170,368 FFFE07DF00000006
26/02/2011 06:21 33,116,160 FFFE07DF00000008
26/02/2011 06:21 978,944 FFFE07DF00000001
4 File(s) 59,314,176 bytes
Directory of Y:\20314300
26/02/2011 06:21 15,503,360 AvatarEditor.xex
26/02/2011 06:21 4,345,856 BiometricSetup.xex
26/02/2011 06:21 114,688 Dash.AttractionScreen.xex
26/02/2011 06:21 835,584 dash.ExtraAVCodecs.xex
26/02/2011 06:21 421,888 Dash.FieldCalibration.lex
26/02/2011 06:21 1,736,704 dash.firstuse.xex
26/02/2011 06:21 466,944 Dash.MP.Offline.lex
26/02/2011 06:21 434,176 dash.natalpregame.xex
26/02/2011 06:21 1,458,176 dash.NuiFirstUse.xex
26/02/2011 06:21 278,528 dash.nuihub.xex
26/02/2011 06:21 1,454,080 Dash.NuiTroubleshooter.lex
26/02/2011 06:21 1,404,928 dashnui.xex
26/02/2011 06:21 413,696 Guide.AvatarMiniCreator.xex
26/02/2011 06:21 249,856 Guide.NuiTroubleshooter.xex
26/02/2011 06:21 2,756,608 livepack.xex
26/02/2011 06:21 11,485 mediasite.xzp
26/02/2011 06:21 16,384 natalsu.xex
26/02/2011 06:21 24,576 nuihud.xex
26/02/2011 06:21 126,976 Xam.Community.xex
26/02/2011 06:21 81,920 Xam.LiveMessenger.xex
26/02/2011 06:21 20,480 Xam.WordRegister.xex
26/02/2011 06:21 573,440 XimeDic.xex
26/02/2011 06:21 69,632 XimeDicCh.xex
26/02/2011 06:21 368,640 ximedicex.xex
24 File(s) 33,168,605 bytes
Directory of Y:\32000100
26/02/2011 06:21 512,000 Xna_TitleLauncher.xex
1 File(s) 512,000 bytes
Total Files Listed:
30 File(s) 93,000,881 bytes
7 Dir(s) 122,863,616 bytes free
SysExt will let you see what is in there and if the avatar etc extensions are installed. If that doesn't work, I'd clear the system cache, build a fresh NAND image and start from scratch.
Also make sure you're using the correct update, the CD version has the default.xex while the USB version doesn't.
QUOTE(antisniperspy @ Apr 7 2011, 05:11 PM)
Hi, Is this for 12611 dash or 12625 dash or both? I still have 12611 and have had no reason to update.
Thanks
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...
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?
It's kosher, it can build FB 9199/ 12611/ 12625 images. What's interesting though is the date of the files, 16/03/2011 on mine. Guess they must have been pissed or perhaps they were waiting for [c0z] to be ready.
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.
Correct as ever, bugger. You could have mentioned it in the previous thread, I even posted the launch.ini 
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.
QUOTE(tk_saturn @ Apr 7 2011, 11:40 AM)
Correct as ever, bugger. You could have mentioned it in the previous thread, I even posted the launch.ini
When you mentioned the option today, it was better looked into, reproduced, debugged and hopefully an all round good solution will be found for that option to be refined better
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!
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!
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.
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.
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
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.
; 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;
; if not present this is set to TRUE
add this line to your launch.ini
noupdater = false;
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.
I think Aldanga is right. I couldn't get the update to work either, but as soon as i deleted launch and ihelper from the flash using fsd, the update went through. Then i just reinstalled dashlaunch afterwards.
Ok, so I thought that there was no point in updating to 12625 because of this dashlaunch update. So why are people even bothering? There is nothing to the 12625 update, I thought it just implemented more anti hacking junk?
QUOTE(tk_saturn @ Apr 7 2011, 05:30 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.
Yes, those are the SMCs I've been using for quite some time and now again.
The issue is with the SMCs hacked with smc_util v1.1 that are created.
QUOTE(soulwarrior @ Apr 7 2011, 08:42 PM)
I think Aldanga is right. I couldn't get the update to work either, but as soon as i deleted launch and ihelper from the flash using fsd, the update went through. Then i just reinstalled dashlaunch afterwards.
I just tested this and can corroborate the results. Without Dash Launch, the update is recognized. Once Dash Launch is installed, regardless of settings in launch.ini, it doesn't accept the update. Once Dash Launch is removed, it recognizes the update again. Renaming the update folder doesn't make a difference.
I don't know if this is limited to 12611 or is across the board, but it appears to be a bug.
QUOTE(Aldanga @ Apr 8 2011, 12:58 AM)
I don't know if this is limited to 12611 or is across the board, but it appears to be a bug.
It's not limited to 12611 because I tested it after I updated to 12625.
QUOTE(Aldanga @ Apr 7 2011, 09:58 PM)
I don't know if this is limited to 12611 or is across the board, but it appears to be a bug.
The deal is, the blocker is working far too well
QUOTE(soulwarrior @ Apr 8 2011, 02:42 AM)
but as soon as i deleted launch and ihelper from the flash using fsd, the update went through. Then i just reinstalled dashlaunch afterwards.
On #freeboot i was told yesterday that manually editing/writing the flash will corrupt it. It should be reflashed completely instead. Not sure if this is correct.
QUOTE(SilentBob1638 @ Apr 8 2011, 06:21 AM)
On #freeboot i was told yesterday that manually editing/writing the flash will corrupt it. It should be reflashed completely instead. Not sure if this is correct.
That's what I did actually. My exact steps were:
1. Build 12625 image with fbbuild (first I manually extracted the resources from the dash launch default.xex and transferred the patches to the correct places) .
2. flashed image.
3. realized the official 12625 update would not install no matter what settings I had in the ini or what i named the update folder.
4. Thought to myself, maybe something is wrong with dash launch, so i deleted the ihelper/launch files from the flash using fsd.
5. Ran the update successfully.
6. reflashed the original image from step 1.
QUOTE(tk_saturn @ Apr 6 2011, 11:27 PM)
FSD2 retrieves screenshots and game covers from catalog.xboxlive.com [65.55.42.202]. All you have to is block all of Microsoft's IP range (65.54.0.1-65.55.255.255) in your routers firewall and then add an exception for that single address.
It's what i've done for ages.
Would prefer the files to be seperate rather than embeded in a default.xex, I prefer to build FreeBoot images with DashLaunch in from the start.
Some people have shitty routers, or just can't get it to block at all. So people like me with a router that I payed $150 and ended up with a completely crappy user interface but the router itself is great. My router just doesn't let me adjust what is needed to completely block live access. I am very thankful for the option to block LIVE without beating my router till my fists are bloody.
Also I Jtag peoples 360's so for me its another great option to be able to enable so I won't have people getting banned then asking me what happened, because they apparently didn't hear me the 10 times I told them not to try to sign into LIVE.
I found a bug. c0z's disk swapper plugin doesn't work anymore in fbbuild 0.20 12625 and DL 2.20, this is on a 512MB Jasper if it makes any difference.
Doesn't work for me either. But it's still working on fbBuild v0.20 12611 + DL v2.20, so drop back to that as it doesn't make much difference.
Or get the new one from xbins, 1.1 fixes the version specific issue.
Yet another amazingly fast update from c0z, thanks.
It doesn't work on ME2 Cory, haven't tried any others. Gives me 3x " 
Fatal Exception Intercepted" and then dumps back to the default item in launch.ini. V1 still works fine with ME2 though.
Fatal Exception Intercepted" and then dumps back to the default item in launch.ini. V1 still works fine with ME2 though.
Ok, so I've never really messed with FSD or dashlaunch before, but my newer games won't play now so I got this to fix the problem. The problem is I can't get it to work, everything still gives me a dirty disc error. Can't figure out why, any help?
QUOTE(tk_saturn @ Apr 9 2011, 01:26 AM)
It doesn't work on ME2 Cory, haven't tried any others. Gives me 3x "
Fatal Exception Intercepted" and then dumps back to the default item in launch.ini. V1 still works fine with ME2 though.maybe because you are on 12611 ?
disk swapper 1.1 works fine for me now, I tested with Dead Space 2, Star Ocean 4 and Castlevania LoS.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.