Post by: Xbox-Scene on April 06, 2011, 07:40:00 PM
| cOz released a new version of Dash Launch build for JTAG 360s. 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 |
Post by: CLK Rebellion on April 06, 2011, 08:44:00 PM
Great work.
Post by: ILLusions0fGrander on April 06, 2011, 09:12:00 PM
Post by: moeom on April 06, 2011, 09:46:00 PM
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...
Post by: ILLusions0fGrander on April 06, 2011, 10:05:00 PM
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.
Post by: Twis7eD on April 06, 2011, 11:05:00 PM
Post by: tk_saturn on April 06, 2011, 11:27:00 PM
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.
This post has been edited by tk_saturn: Apr 7 2011, 06:43 AM
Post by: RRoD420 on April 07, 2011, 12:00:00 AM
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.
Post by: cory1492 on April 07, 2011, 12:07:00 AM
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 (IMG:style_emoticons/default/blink.gif)
Post by: Aldanga on April 07, 2011, 01:20:00 AM
Post by: razkar on April 07, 2011, 01:30:00 AM
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 (IMG:style_emoticons/default/smile.gif))
Post by: krizalid on April 07, 2011, 02:11:00 AM
I don't have a way to know at this moment... just asking
thanks!
Post by: shooter54 on April 07, 2011, 03:33:00 AM
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.
Post by: tk_saturn on April 07, 2011, 03:39:00 AM
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.
This post has been edited by tk_saturn: Apr 7 2011, 10:56 AM
Post by: tk_saturn on April 07, 2011, 04:30:00 AM
Post by: krizalid on April 07, 2011, 05:00:00 AM
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!
Post by: SilentBob1638 on April 07, 2011, 09:42:00 AM
Post by: tk_saturn on April 07, 2011, 09:47:00 AM
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?
Post by: antisniperspy on April 07, 2011, 10:11:00 AM
Thanks
Post by: Aldanga 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.
Post by: antisniperspy 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?
Post by: cory1492 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.
Post by: tk_saturn on April 07, 2011, 12:40:00 PM
Post by: moeom 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.
Post by: krizalid on April 07, 2011, 03:01:00 PM
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!
Post by: tk_saturn on April 07, 2011, 04:30:00 PM
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.
Post by: TheRealJPizzle 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
Post by: Aldanga on April 07, 2011, 07:19:00 PM
Post by: TheRealJPizzle on April 07, 2011, 07:27:00 PM
; if not present this is set to TRUE
add this line to your launch.ini
noupdater = false;
Post by: Aldanga on April 07, 2011, 07:30:00 PM
Post by: ars0n on April 07, 2011, 10:03:00 PM
Post by: krizalid on April 07, 2011, 10:17:00 PM
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.
Post by: Aldanga on April 07, 2011, 10:58:00 PM
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.
Post by: cory1492 on April 08, 2011, 02:40:00 AM
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
Post by: SilentBob1638 on April 08, 2011, 04:21:00 AM
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.
Post by: soulwarrior on April 08, 2011, 06:09:00 AM
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.
Post by: iwanttheagrocrag on April 08, 2011, 01:09:00 PM
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.
Post by: tk_saturn on April 08, 2011, 03:35:00 PM
Post by: Glottiz on April 08, 2011, 04:00:00 PM
Post by: tk_saturn on April 08, 2011, 04:26:00 PM
Fatal Exception Intercepted" and then dumps back to the default item in launch.ini. V1 still works fine with ME2 though.
Post by: Jordan23 on April 08, 2011, 04:34:00 PM
Post by: tk_saturn on April 08, 2011, 05:44:00 PM
CODE
------------------------------------------------------------------------
TIME: 22:41:55 GMT Fri, Apr 8, 2011
------------------------------------------------------------------------
Unhandled Exception (last chance):
The thread tried to read from or write to a virtual address for which
it does not have access.
------------------------------------------------------------------------
Faulting Module Info:
FullName : \Device\Package_823D69EBB93C03AECDF9EB80509FF0ED\default.xex
BaseName : default.xex
PEName : BioGame-XeReleaseLTCG.exe
ImageBase : 82000000
SizeOfFullImage: 01530000
EntryPoint : 82C4BF30
------------------------------------------------------------------------
EADDR: 0x82D65B68
ECODE: 0xC0000005
EFLAG: 0 (cont)
NPARM: 2
PARAM 00: 0x00000001
PARAM 01: 0x78AA0000
CFLAG: 0x00000017
------------------------------------------------------------------------
Control Registers:
MSR: 0x0200B030 IAR: 0x82D65B68
LR : 0x8279AEA8 CTR: 0x000000000000019A
------------------------------------------------------------------------
Integer Registers:
CR : 0x42000444 XER: 0x20000000
r0 : 0x0000000000001000 r1 : 0x0000000070227500 r2 : 0x0000000000000000
r3 : 0x0000000078A919A0 r4 : 0x0000000000000000 r5 : 0x0000000000010000
r6 : 0x0000000078AA0000 r7 : 0x00020000001A0100 r8 : 0xFFFFFFFFFFFFFFFF
r9 : 0x0000000000000308 r10: 0x0000000000000010 r11: 0x0000000030012BC0
r12: 0x000000008279B040 r13: 0x0000000080180000 r14: 0x000000007022A020
r15: 0x0000000000000002 r16: 0x0000000000000001 r17: 0x0000000270227F60
r18: 0xFFFFFFFF833D0000 r19: 0x000000006F6E4D00 r20: 0x000000006CD7F004
r21: 0xFFFFFFFF83384660 r22: 0x0000000270227710 r23: 0x000000006DCE0000
r24: 0x0000000000000022 r25: 0xFFFFFFFF833D0000 r26: 0x0000000000000294
r27: 0xFFFFFFFF83400000 r28: 0x000000002EA10000 r29: 0xFFFFFFFF83400000
r30: 0xFFFFFFFF83400000 r31: 0x0000000078A919A0
------------------------------------------------------------------------
Call Stack:
0x82D65B68 (EADDR)
0x8279AEA8 (LR)
0x8279B040
0x8279B1E8
0x828588E0
0x828530A0
0x8285DC08
0x82781B08
0x8276F4A4
0x8276F30C
0x827820C4
0x82781F08
0x8276F4A4
0x8276F30C
0x827820C4
0x827823B0
0x8273A52C
0x8273B130
0x82B76008
0x82B413C0
0x82B65A88
0x82B74134
0x82B413C0
0x82B40174
0x82B3F738
0x82B65B84
0x82B7423C
------------------------------------------------------------------------
Dump Done
------------------------------------------------------------------------
------------------------------------------------------------------------
TIME: 22:41:55 GMT Fri, Apr 8, 2011
------------------------------------------------------------------------
Unhandled Exception (last chance):
The thread tried to read from or write to a virtual address for which
it does not have access.
------------------------------------------------------------------------
Faulting Module Info:
FullName : \Device\Package_823D69EBB93C03AECDF9EB80509FF0ED\default.xex
BaseName : default.xex
PEName : BioGame-XeReleaseLTCG.exe
ImageBase : 82000000
SizeOfFullImage: 01530000
EntryPoint : 82C4BF30
------------------------------------------------------------------------
EADDR: 0x82D65B6C
ECODE: 0xC0000005
EFLAG: 0 (cont)
NPARM: 2
PARAM 00: 0x00000001
PARAM 01: 0x78AA0004
CFLAG: 0x00000017
------------------------------------------------------------------------
Control Registers:
MSR: 0x00009030 IAR: 0x82D65B6C
LR : 0x8279AEA8 CTR: 0x000000000000019A
------------------------------------------------------------------------
Integer Registers:
CR : 0x42000444 XER: 0x20000000
r0 : 0x0000000000001000 r1 : 0x0000000070227500 r2 : 0x0000000000000000
r3 : 0x0000000078A919A0 r4 : 0x0000000000000000 r5 : 0x0000000000010000
r6 : 0x0000000078AA0000 r7 : 0x00020000001A0100 r8 : 0xFFFFFFFFFFFFFFFF
r9 : 0x0000000000000308 r10: 0x0000000000000010 r11: 0x0000000030012BC0
r12: 0x000000008279B040 r13: 0x0000000080180000 r14: 0x000000007022A020
r15: 0x0000000000000002 r16: 0x0000000000000001 r17: 0x0000000270227F60
r18: 0xFFFFFFFF833D0000 r19: 0x000000006F6E4D00 r20: 0x000000006CD7F004
r21: 0xFFFFFFFF83384660 r22: 0x0000000270227710 r23: 0x000000006DCE0000
r24: 0x0000000000000022 r25: 0xFFFFFFFF833D0000 r26: 0x0000000000000294
r27: 0xFFFFFFFF83400000 r28: 0x000000002EA10000 r29: 0xFFFFFFFF83400000
r30: 0xFFFFFFFF83400000 r31: 0x0000000078A919A0
------------------------------------------------------------------------
Call Stack:
0x82D65B6C (EADDR)
0x8279AEA8 (LR)
0x8279B040
0x8279B1E8
0x828588E0
0x828530A0
0x8285DC08
0x82781B08
0x8276F4A4
0x8276F30C
0x827820C4
0x82781F08
0x8276F4A4
0x8276F30C
0x827820C4
0x827823B0
0x8273A52C
0x8273B130
0x82B76008
0x82B413C0
0x82B65A88
0x82B74134
0x82B413C0
0x82B40174
0x82B3F738
0x82B65B84
0x82B7423C
------------------------------------------------------------------------
Dump Done
------------------------------------------------------------------------
------------------------------------------------------------------------
TIME: 22:41:56 GMT Fri, Apr 8, 2011
------------------------------------------------------------------------
Unhandled Exception (last chance):
The thread tried to read from or write to a virtual address for which
it does not have access.
------------------------------------------------------------------------
Faulting Module Info:
FullName : \Device\Package_823D69EBB93C03AECDF9EB80509FF0ED\default.xex
BaseName : default.xex
PEName : BioGame-XeReleaseLTCG.exe
ImageBase : 82000000
SizeOfFullImage: 01530000
EntryPoint : 82C4BF30
------------------------------------------------------------------------
EADDR: 0x82D65B70
ECODE: 0xC0000005
EFLAG: 0 (cont)
NPARM: 2
PARAM 00: 0x00000001
PARAM 01: 0x78AA0008
CFLAG: 0x00000017
------------------------------------------------------------------------
Control Registers:
MSR: 0x00009030 IAR: 0x82D65B70
LR : 0x8279AEA8 CTR: 0x000000000000019A
------------------------------------------------------------------------
Integer Registers:
CR : 0x42000444 XER: 0x20000000
r0 : 0x0000000000001000 r1 : 0x0000000070227500 r2 : 0x0000000000000000
r3 : 0x0000000078A919A0 r4 : 0x0000000000000000 r5 : 0x0000000000010000
r6 : 0x0000000078AA0000 r7 : 0x00020000001A0100 r8 : 0xFFFFFFFFFFFFFFFF
r9 : 0x0000000000000308 r10: 0x0000000000000010 r11: 0x0000000030012BC0
r12: 0x000000008279B040 r13: 0x0000000080180000 r14: 0x000000007022A020
r15: 0x0000000000000002 r16: 0x0000000000000001 r17: 0x0000000270227F60
r18: 0xFFFFFFFF833D0000 r19: 0x000000006F6E4D00 r20: 0x000000006CD7F004
r21: 0xFFFFFFFF83384660 r22: 0x0000000270227710 r23: 0x000000006DCE0000
r24: 0x0000000000000022 r25: 0xFFFFFFFF833D0000 r26: 0x0000000000000294
r27: 0xFFFFFFFF83400000 r28: 0x000000002EA10000 r29: 0xFFFFFFFF83400000
r30: 0xFFFFFFFF83400000 r31: 0x0000000078A919A0
------------------------------------------------------------------------
Call Stack:
0x82D65B70 (EADDR)
0x8279AEA8 (LR)
0x8279B040
0x8279B1E8
0x828588E0
0x828530A0
0x8285DC08
0x82781B08
0x8276F4A4
0x8276F30C
0x827820C4
0x82781F08
0x8276F4A4
0x8276F30C
0x827820C4
0x827823B0
0x8273A52C
0x8273B130
0x82B76008
0x82B413C0
0x82B65A88
0x82B74134
0x82B413C0
0x82B40174
0x82B3F738
0x82B65B84
0x82B7423C
------------------------------------------------------------------------
Dump Done
------------------------------------------------------------------------