Print

[antisniperspy]

QUOTE(juggahax0r @ May 27 2010, 12:15 PM)

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.

I think cory1492 said above that the launch.xex has to be in flash so it seems to me like the USB and HDD settings are useless. Plus dont you have to install the launch.xex to flash after you have rebuilt your nand with the new patch? So those three options make no sense at all. Maybe someone can clear them up.

[kettenschutz]

QUOTE(antisniperspy @ May 27 2010, 06:21 PM)

I think cory1492 said above that the launch.xex has to be in flash so it seems to me like the USB and HDD settings are useless. Plus dont you have to install the launch.xex to flash after you have rebuilt your nand with the new patch? So those three options make no sense at all. Maybe someone can clear them up.

its correct that the launch.xex HAS TO BE FLASHED in the NAND directly. DONT put it on HDD or USB0, this could make trouble ..

this option is for the LAUNCH.INI file which define the linked dashboards to the buttons on ur controller
this file can be flashed directly to the NAND, or could be putted on USB and / or HDD
the boot order for this INI is :
USB
HDD
FLASH

there are peoples who reported they ony got full functionality if they flashed this ini (put the edited INI in the FLASH INSTALLER folder on your xbox to directly flash it via the /flash_installer/default.xex)
but normally it should be enough to put it on the USB root

[antisniperspy]

QUOTE(kettenschutz @ May 27 2010, 12:28 PM)

its correct that the launch.xex HAS TO BE FLASHED in the NAND directly. DONT put it on HDD or USB0, this could make trouble ..

this option is for the LAUNCH.INI file which define the linked dashboards to the buttons on ur controller
this file can be flashed directly to the NAND, or could be putted on USB and / or HDD
the boot order for this INI is :
USB
HDD
FLASH

there are peoples who reported they ony got full functionality if they flashed this ini (put the edited INI in the FLASH INSTALLER folder on your xbox to directly flash it via the /flash_installer/default.xex)
but normally it should be enough to put it on the USB root

I still dont see a reason for the three options in freeboot toolbox 2.4 as all you have to do is include the new patch. You still have to run the installer on the xbox 360 and choose where you want your ini files (flash, hdd1 or/and usb0).

[juggahax0r]

Well the three options deal with where you will be putting your ini file from the previous post , as opposed to where you are going to be putting the launch.xex as i said so i was wrong. I had a problem with my Jtag because i did put the launch.xex in my HDD.
 I understand it better now after your explanation cory1492 so I appreciate it. Nothing against team Xedev but for me at least the readme was a little vague or rather just worded in a confusing manner for me.
 I won't be able to test it anymore until next week , I busted a MOSFET from under my GPU trying to put X-clamps on and it's 0001 now and the pad has been lifted so i can't reattach it , it's a bitch but i get my Jtags cheap so i will be rockin again soon.

@antisniperspy

 I think the reason for the option in freeBOOT toolbox maker is to select which version of the patch to use , you will still have to run the installer app , but you also still need to select this option. freeBOOT toolbox maker also is not the only way to build the image the dashlaunch.rar has subfolders for the different patches if i remember correctly.

[antisniperspy]

QUOTE(juggahax0r @ May 27 2010, 12:59 PM)

@antisniperspy

 I think the reason for the option in freeBOOT toolbox maker is to select which version of the patch to use , you will still have to run the installer app , but you also still need to select this option. freeBOOT toolbox maker also is not the only way to build the image the dashlaunch.rar has subfolders for the different patches if i remember correctly.

Yeah the patches folder has these but these only change for the type of nand you have
- patches_falcon.bin
- patches_jasper.bin
- patches_xenon.bin
- patches_zephyr.bin

the patches have nothing to do with where you want to store the ini files

[antisniperspy]

QUOTE(ZerOneX @ May 27 2010, 02:13 PM)

For me did not work aswell.

1) I used "FreeBoot Tool 0.032 Maker 2.4"
2) In the Dash Launch 1.0 patches I used NAND option
3) Using flash360 I wrote my NAND again
4) I built this .INI
5) Using my pendrive I made a copy of this folder "flash_installer" with default.xex, launch.xex and launch.ini inside.
6) Through XeXmenu and running default.xex I flashed launch.xex and launch.ini to my NAND, but nothing happened.

Someone know waht I´m doing wrong?

Thanks folks.

Everything you did sounds correct.

[dryan433]

QUOTE(cory1492 @ May 27 2010, 10:31 AM)

The ini file needs to be ASCII/UTF-8 format, paths are case sensitive. And once again, it was an omission in #1 - with this patch set launch.xex is required to be on FLASH.

Some additional info on SMC, if you use the cygnos SMC without a cygnos it's not going to work... cygnos does it's own JTAG injection instead of relying on SMC to do it. There are two hacked SMC currently, one for xenon (based on xenon smc), one for everything else (based on jasper big block SMC) which can be found in the xbr or xell images - do not use the xenon one on a non-xenon console.
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.

yes i tried all this i had to re-flash the box it was totally messed up power is fine it was just that the nand had corrupt but i had built it with easy freeboot first time i rebuilt with ibuild how i know and it seams fine now as mad as it sound both programs are not working exactly the same as my friend when he did his xbox he had to use easy freeboot for his as a manual build from ibuild just would not work full stop but one from easy freeboot did but with me the opposite by the looks of it so its a strange one

oh i had to short the pins on the nand just to get it to pick it up again so it seams to me that the smc had corrupted its self some how with all the nand version of freeboot iv used the same smc from my compiled xbr image

atm I'm struggling to get it to load the ini its in UTF-8 format as notepad do not save in ASCII

this is whats in my ini so is this correct as i did forget about it being case sensitive but corrected it and still no joy yet the launch.xex is on nand and as far as i know its working because with mini blades if i hold left trig and y it reboot to nxe and if i hold down x at same time if fully reboots my xbox because it cant load something so I'm totally stummbed on this now

[antisniperspy]

QUOTE(ZerOneX @ May 27 2010, 02:20 PM)

mysteries of the beyond eheh, I´m trying to find the solution

ow, thers is one thing, my donor nand is 6717 and not 7371, this could be the source of my problem?

Problem could be that its a donor nand and that its at 6717. Not sure though

[ZerOneX]

QUOTE

[QuickLaunchButtons]
BUT_X = LHdd:\Content\0000000000000000\00000001\00080000\000000010F586558
BUT_Y = LUsb1:\Freestyle\FreestyleDash.xex
Default = LUsb1:\Freestyle\FreestyleDash.xex

PS. YOU HAVE TO SAVE THE .INI FILE IN UTF-8 FORMAT, any other encoding will not work.

5) Using my pendrive I made a copy of this folder "flash_installer" with default.xex, launch.xex and launch.ini inside.
6) Through XeXmenu and running default.xex I flashed launch.xex and launch.ini to my NAND,

7) Everything is working fine.

Thanks folks.

[dryan433]

thanks for all the pointers I'm sorted now fixed all my issues well nearly all lol nearly all is working how it should be now apart from that I'm getting random RROD error 0020 when they was eradicated with freeboot 0.3 but that i can live with everything else is sweet now

[sudeki300]

i have tried to see this in the thread but could not find it. i have freestyle dash as my default, but if i want to go into nxe dash how would i write that on the ini file. would it be "default.xex" or "NXE". thanks............................sudeki300

[dryan433]

QUOTE(sudeki300 @ May 27 2010, 09:44 PM)

i have tried to see this in the thread but could not find it. i have freestyle dash as my default, but if i want to go into nxe dash how would i write that on the ini file. would it be "default.xex" or "NXE". thanks............................sudeki300

when returning to dash with mini blade as soon as you have pressed y and yes press RB immediately after and hold this will take you back to the nxe dash the same wile booting xbox hold same button wile its booting and will go to nxe dash simple well after i managed to get it to work lol

if you want it permanently back to dash you need to remove the ini file i have it on my usb drive so if i want it to be nxe dash only i just unplug my usb hdd to make it simpler

[kettenschutz]

QUOTE(dryan433 @ May 27 2010, 11:18 PM)

...you have pressed y and yes press RB immediately after ...

hmmm, maybe this is my problem.
booting customized dashes at xbox startup works fine (beneath every button works including flash360 via LB), but the miniblade-jump never works.
maybe i pushed the buttons to late
but why there boots no FSD via Y and YES at the miniblade? only NXE :-(

will try the faster button smashing for this

[kettenschutz]

QUOTE(maliceshaun @ May 28 2010, 04:37 PM)

My button shortcuts to switch dashes does not work.  I have original nand dump, created new freeboot 0.32 with dashlaunch patches.  It boots straight to FSD and when I exit to dashboard goes to FSD.  I have my launch.xex and launch.ini in my NAND, launch.ini in the root of my HDD.  When I bring up the mini blade and hit RB + X nothing happens.  What's wrong?

This is the launch.ini and it is in UTF-8.

CODE

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

nah, u have to HOLD X,B,Y or A Button immediately after u press "YES" in the miniblade
RB is only to boot in NXE
next is, u dont have to use the launch.ini on FLASH and HDD, one is enough
the third time i show the boot order of launch.ini :
USB
HDD
Flash
if u got the ini on HDD, the one in the FLASH wont be used

[Inuyasha152]

In Freeboot Toolbox 2.4 it allows you to select for Dashlaunch "nand" or "usb" or "hdd". This is obviously where the .ini file is placed, but what is 'created' or 'done' to the freeboot image that is telling it where to look for the .ini file in that specific place? Also, if one were to follow this tutorial: Link would you simply just replace the patches in the bin folder and continue to build the image, or am I skipping a step that must be done to the patches?

Thanks in advance!


P.S. I get an error that the kv.bin cannot be extracted as the CPU key is invalid with freeboot toolbox, but have confirmed multiple times that the CPU key is correct and its simply a programming error on the creators part. Also, the issue with the MAC address being changed is another reason I wish to take an alternate route (perferably the tutorial mentioned above as I do not have a full backup of my original NAND.)