Print

[ddxcb]

QUOTE(dryan433 @ May 25 2010, 03:06 PM)

no i didn't this time

for the first time i used easy freeboot before hand i used ibuild when i first flashed my box with freeboot but this time i used the easy freeboot app as this worked for my friends box fine when he flashed freeboot the first time as ibuild would not build them right for his box yet easy freeboot works a charm for him

when i try to flash it again will be trying one more time but with ibuild as i did first time round

Any of thoes apps uses ibuild, and did u put the patch in there folder ?

[krizalid]

Let's not get all this confused.

Dashlaunch patches replacement for ibuild works and works well, no issues there.

We are talking about it missing a patch on the xenon.patches that allowed unsigned sata hdd to be mounted properly.

Does work on my Falcon, but not my xenon.

Let's read with more attention please.... I feel like big bird from sesame street saying this  

[dryan433]

QUOTE(ddxcb @ May 25 2010, 11:11 PM)

Any of thoes apps uses ibuild, and did u put the patch in there folder ?

yes i did i written over the existing patches i had and rebuilt my image with easy freeboot was working but then died the day after

QUOTE(krizalid @ May 25 2010, 11:20 PM)

Let's not get all this confused.

Dashlaunch patches replacement for ibuild works and works well, no issues there.

We are talking about it missing a patch on the xenon.patches that allowed unsigned sata hdd to be mounted properly.

Does work on my Falcon, but not my xenon.

Let's read with more attention please.... I feel like big bird from sesame street saying this  

not getting confused mate if this has done this to hdd on one type of console its done something different on mine and killed my xbox after it was working sweet after this patch then died after a full night of it working fine

so no im not talking about the hdd issue but a different issue related to the exact same patch on my falcon 3.0 xbox 360

[antisniperspy]

QUOTE(ddxcb @ May 25 2010, 05:39 PM)

Its the patches you guys did.

Ever going to tell us how you patched your xbox without building a new nand??

[daze81]

CODE

Copy the patch suitable for your console to the bin\ folder of your freeboot image folder, then compile as per the instructions included in the readme for freeboot. After doing so, edit the launch.ini so that it fits your needs by following the examples it sets. Once having done that, launch either Freestyle Dash or XeXMenu and ftp the files to the root of HDD1 turn off your console and turn back on, and the settings you have chosen in the launch.ini will have taken affect.

so i made a launch.ini:

CODE

[QuickLaunchButtons]
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back  = LHdd:\Flash360\Flash360.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex

and copied the launch.ini and launch.xex out of the folder "flash_installer" into the root of the internal HDD.

it defaults every single time into NXE and ignores all defined buttons as well.

so if anyone can enlight me ... i've got no more ideas want could be wrong.

thanks in advance.

[dryan433]

QUOTE(daze81 @ May 26 2010, 12:23 AM)

hi,

so usually i read more instead of posting questions already answered.

i've build my freeboot nand twice now with these new patch and i can't get it to work at all.

here is my config:
 - jasper512
 - extracted crl.bin, extended.bin, kv.bin, odd.bin, secdata.bin and smc_config.bin from original nand
 - extracted smc.bin from xbr3 (because of the known problems with the original smc & freeboot)
 - dash launch 1.0 patches copied to bin directory
 - build updflash.bin by commandline
 - flashed with flash360 & xbrflash

i have chosen the option #1 from the readme:

CODE

Copy the patch suitable for your console to the bin\ folder of your freeboot image folder, then compile as per the instructions included in the readme for freeboot. After doing so, edit the launch.ini so that it fits your needs by following the examples it sets. Once having done that, launch either Freestyle Dash or XeXMenu and ftp the files to the root of HDD1 turn off your console and turn back on, and the settings you have chosen in the launch.ini will have taken affect.

so i made a launch.ini:

CODE

[QuickLaunchButtons]
BUT_B = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558
BUT_X = LHdd:\XM360\XM360.xex
Back  = LHdd:\Flash360\Flash360.xex
Default = LHdd:\FreeStyle\FreestyleDash.xex

and copied the launch.ini and launch.xex out of the folder "flash_installer" into the root of the internal HDD.

it defaults every single time into NXE and ignores all defined buttons as well.

so if anyone can enlight me ... i've got no more ideas want could be wrong.

thanks in advance.

i had this issue before my xbox bricked it self after this patch at first i did not change the last version of dash launch and the ini with new one and if booted into my fsd as before when i put the new version there it wouldn't boot only nxe but next day when i came back to xbox it wouldn't power on and nandpro will not detect so will have to short pins to re flash it now lol fun

wile i was at work there was a power failure too but was back on when i got home

by the looks of it thou you have it correct how you have done it

[soulwarrior]

It appears people seem to be skipping over the part of the readme (the very beginning) that says:

****
    at time of this writing, this is ONLY compatible with freeBOOT 0.03x
    releases built with the included patch set which expects launch.xex
   to be installed to system flash.
****

ie you must use the flash installer in addition to creating your freeboot image with the new patches. You don't need to install the ini to flash though.

That being said, I also have not gotten the quicklaunch buttons to work. I have freestyle dash as the default and it returns to fsd just fine. I have xexmenu set for A but for some reason it only goes back to nxe. Pretty sure I don't have typos either.  

[ZprivateZ]

QUOTE(dryan433 @ May 25 2010, 04:49 PM)

so i guess this patch don't work as well as it says then as my nand had corrupted on me after power cut xbox was off at the time and when i came back to it to play on i got nothing wont power on like the smc has fucked up but yet it was working just fine before this happened with this patch as after i re flashed my box i was playing on it for a few hours just fine then out the blue this happened to me so unless this is fixed i would advice to stay away

What smc did you use? Because I could be wrong but if I remember correctly when freeboot first released for single nand people were having this issue also due to either using the wrong smc.bin or using the smc_enc.bin instead of using the smc_dec.bin. I myself have a jasper 512mb and have not had problem one I extracted my smc from the xbr image for my board type. I have unplugged my box for 30 minutes and reconnected and powered on after seeing your post and still have no issues. So it just makes me curious as to what smc.bin you used.

[daze81]

QUOTE(dryan433 @ May 26 2010, 01:35 AM)

i had this issue before my xbox bricked it self after this patch at first i did not change the last version of dash launch and the ini with new one and if booted into my fsd as before when i put the new version there it wouldn't boot only nxe but next day when i came back to xbox it wouldn't power on and nandpro will not detect so will have to short pins to re flash it now lol fun

you have to use the SMC out of XBR because the SMC out of your original nand backup does not work. had the same issue some time ago.

QUOTE(soulwarrior @ May 26 2010, 02:53 AM)

It appears people seem to be skipping over the part of the readme (the very beginning) that says:

****
    at time of this writing, this is ONLY compatible with freeBOOT 0.03x
    releases built with the included patch set which expects launch.xex
   to be installed to system flash.
****

thanks. you're right i did not see that. i'm courious that they/he did not point it out in the option list.

[Lisko]

While playing I rebooted my box because the game exited to NXE, now I have 3RLOD and secondary error 0020.  Can this be caused by Dashlunch? Xell doesn't work so i need LPT for reflashing. Warning on Xenon, this patch still needs a lot of work on this MB...

[dustin6908]

this patch can be applied and a new nand created with easy freeboot v2 dont have to use i build....cant say for any other front end but scene some of the other are using internalized files then no would be a know unless you change them.

[BrooksyX]

love what this patch promises but it just seems like it is causing way to many issues. I think im gonna wait it out until they iron out some of the bugs and they come out with it already part of freeboot. Shouldnt be to much longer now.

[cory1492]

QUOTE(BrooksyX @ May 26 2010, 12:28 PM)

love what this patch promises but it just seems like it is causing way to many issues. I think im gonna wait it out until they iron out some of the bugs and they come out with it already part of freeboot. Shouldnt be to much longer now.

Out of about a dozen testers with approx 6 weeks test time, this build has the only issue found (aside from user error) mentioned in the readme - some consoles just behave slightly differently than others and wind up in NXE without ODD envolved, though turning the controller on or closing the tray at exactly the wrong time can cause problems too. The rebooting box mentioned once above was a failsafe, if subversion happens too early without the reboot patch the cosole will freeze (with patch it reboots instead so one doesn't have to get up and such), if it happens to late (more common, especially with disk in ODD) then NXE will appear instead of default setting.

dryan433: the only question I can ask, is have you repeated the outage too? Usually a brown out or power outage is accompanied by a surge (which is part of why it is recommended to unplug electronics from wall outlet in a storm, lightning arcing through wall aside.) If the box is turned off, the patches and launch aren't running and can have no effect while a surge can easily cause all sorts of random havok. I assume you pulled the power plug and any cable going to a powered video unit (applies to hdmi/vga) for a half minute or so before trying reflash.

krizalid: open the patch set you used with a hex editor and search for

CODE

0012837800000002386000014E800020

It should be at 0x6EC in the xenon patches - this is the hdd sig skip. If it's not working change the 00128378 to 0012837C and let me know if that makes a diff. It shouldn't but you never know, allowing LR to be moved to %R12 may be required.

[ZerOneX]

Guys, what does mean in FreeBoot Tool 0.032 Maker 2.4 the Dashlaunch 1.0 patch from flash, HDD and USB?

I did not undertand the differences between then.

I tried to connect with Xbins several times but I couldn´t... I don´t know why.

Many thanks.

[juggahax0r]

Yes i to was having xbins issues.
 I think the NAND USB and HDD settings in freeBOOT toolbox has to with where you are going to be installing your launch.xex in the NAND USB or HDD.