Print

[ZprivateZ]

QUOTE(dustin6908 @ May 24 2010, 04:34 PM)

still not working
just nxe over and over

no disc in drive at all

any more ideas?
i got a zephyr 4558 if that matters

I guess best thing to do would be recheck your steps,

1.Rebuilt freeBOOT with supplied patches from dash launch and reflashed console
2.Edit launch.ini to your liking and copy it over to the root of your hdd
3.Copy over flash_installer folder and run default.xex
4.Reboot console

If still not working after this then I have no answer for you and maybe someone else will have an idea.

[dustin6908]

QUOTE(ZprivateZ @ May 24 2010, 09:48 PM)

I guess best thing to do would be recheck your steps,

1.Rebuilt freeBOOT with supplied patches from dash launch
2.Edit launch.ini to your liking and copy it over to the root of your hdd
3.Copy over flash_installer folder and run default.xex
4.Reboot xbox

If still not working after this then I have no answer for you and maybe someone else will have an idea.

those are the same exact steps i took before but i may redo it again.
i just dont like reflashing my nand more than i need to.

thanks for your help.
and if any more suggestions come i will try also.

i may wait a day or two till i redo completely so please give suggestions if you have them.

thanks in advanced
Dustin

[p4r0l3]

QUOTE

[QuickLaunchButtons]
Default = LHdd:\Freestyle\FreestyleDash.xex

It seems to work for me if all you include is the default line.

EDIT: I now know what was the problem for me, and it may be the same for you.
If you are editing the ini file on unix, you will need to write the file in DOS format or use unix2dos to convert your ini. This is due to a difference in the way end of line characters are stored. Once this is done, adding parameters other than the Default line works well.

[dustin6908]

QUOTE(p4r0l3 @ May 24 2010, 10:29 PM)

dustin6908, try editing launch.ini as follows.
It seems to work for me if all you include is the default line.

EDIT: I now know what was the problem for me, and it may be the same for you.
If you are editing the ini file on unix, you will need to write the file in DOS format or use unix2dos to convert your ini. This is due to a difference in the way end of line characters are stored. Once this is done, adding parameters other than the Default line works well.

             

omg dude ima try that i am editing it linux thankkk youu ima try thisss and report back

[dustin6908]

it worked thank you
dude your the fuckin man

thank you peace

[miller420]

QUOTE(rocky5 @ May 23 2010, 04:18 PM)

Mine was all working fine till this afternoon then error 1033 (sync and eject button) have to send it off to get fixed as i don't have the stuff to flash the nand (outside of the 360 software solutions).

i flashed with flash360 and i got the error ... Zeropaired kv so any one else have this problem.

the xbox worked all morning so haven't a bloody clue lol

I just flashed my freeboot image built with ibuild to my falcon with Dash Launch patches. The console booted 3 times with Dash Launch working as normal, then the power went out for a second while i was transferring some games. Now when I boot the console I get secondary error 1033. Either tonight or tomorrow I'm going to solder on my lpt and flash it again to see what happens. With my Zephyr I used the hacked SMC extracted from XBR3, and its been working flawless. With my Falcon I just used the hacked SMC from the Cygnos pack from the usual places. Just wondering if that could be it, or if something went wrong with ibuild. I flashed with flash360 and i didn't get the zeropaired warning with my falcon, I did with the Zephyr and its working fine.

[p4r0l3]

I was told to avoid the cygnos smc collection in conjunction with ibuild. Find another donor smc out there

[miller420]

I just built an image with the xbr3 smc extracted with flashtool. I'll flash that in the morning. When I flashd my Zephyr I hex compared the cygnos SMC to the SMC extracted from XBR and there were a ton of differences, so I opted to use the XBR SMC. Laziness got the better of me this time.

[opticd]

Yeah there's for sure a bug with this that has happened to a few previous members.  Basically the full run down.  I flashed it and it worked great for a lil while.  I unplugged my xbox and WHILE IT WAS NOT HOOKED TO ANY POWER SOURCE, I took the harddriive off and put it back on.  Hooked it up to a wall and powered it on and it E79d on its own.  It's for sure not my wiring because I have used everything perfect and it worked just fine with Freeboot .32 and Dash Launch previously.  Something needs to get fixed.

Hardware used
-512MB Jasper
-Non Hacked 500GB Seagate HDD

*Note: the launch was installed to flash memory.

[kettenschutz]

no one else have the same issue like me ?

i reflashed it completely again with the placed xenon_patchset at the bin folder
but if i holf A,B,X or Y at startup at the xbox logo the XBOX reboots itself and starts in NXE

i i wont press anything the box boots up straight to FSD. so this is fine

maybe the problem could comes from the original nand, cause i didnt have any1
i used another tutorial to flash my 360 without this backup
the freeboot stuff works fine, kernel is updated to 99', but dashlaunch wont work
i tried both ways, flashing the launch.ini and just copy it to HDD and USB
check the path's several times, but this damn thing just reboots if i hold any button

same problem is if i try to boot another dash from the lovely called "miniblade"
it just boots to NXE, whether if i hold RB or RT in combination with A,B,X or Y

maybe someone could have an idea for this :-/
are there a possibilty to check if dashlaunch is correctly installed?
cause it boots in both ways, with the OLD LAUNCH.XEX (from dashlaunch 0.2) and the new LAUNCH.XEX to FSD
its damn strange

[dryan433]

QUOTE(opticd @ May 25 2010, 09:55 AM)

Yeah there's for sure a bug with this that has happened to a few previous members.  Basically the full run down.  I flashed it and it worked great for a lil while.  I unplugged my xbox and WHILE IT WAS NOT HOOKED TO ANY POWER SOURCE, I took the harddriive off and put it back on.  Hooked it up to a wall and powered it on and it E79d on its own.  It's for sure not my wiring because I have used everything perfect and it worked just fine with Freeboot .32 and Dash Launch previously.  Something needs to get fixed.

Hardware used
-512MB Jasper
-Non Hacked 500GB Seagate HDD

*Note: the launch was installed to flash memory.

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

[ddxcb]

QUOTE(dryan433 @ May 25 2010, 01: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

Its the patches you guys did.

[dryan433]

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

Its the patches you guys did.

what you mean patches we did i said that in my post lol or you meaning that we all patched with wrong patch ??

i used falcon patch for my falcon its this patch that's broken as i think my smc is broken from this patch on mine as chip/flash controller is not detected in nandpro

[ddxcb]

QUOTE(dryan433 @ May 25 2010, 02:45 PM)

what you mean patches we did i said that in my post lol or you meaning that we all patched with wrong patch ??

i used falcon patch for my falcon its this patch that's broken as i think my smc is broken from this patch on mine as chip/flash controller is not detected in nandpro

did u use ibuild to apply the patches ?

[dryan433]

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

did u use ibuild to apply the patches ?

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