Print

[NEO_X]

hmm i am totally confused now

i used my original nanddump put it in te my360 folder with my cpu key


multbuilder made me a file glitcher_image.bin when i flash that back box wont start


bytheway isnt the command -w


10) Now copy the updflash.bin file and paste it to your nandpro folder and flash the new ggbuild image i.e. "updflash.bin" to your nand. eg: "nandpro usb: -w16 updflash.bin" or "nandpro usb: -w64 updflash.bin"
Please note:- Do not use +w here, if used your console will not start, beware

[ernestino]

QUOTE(steveo1978 @ Nov 6 2011, 02:34 AM)

what location are you installing xexmenu to? And since this is most likely not a multi_builder issue start a thread in the newbie section about it.

Xbox creates this files when I format USB stick. But after it is not visible in Game menu.

[Glottiz]

QUOTE(Rogero @ Nov 5 2011, 03:44 AM)

Exactly, it is a must have indeed, that's why i have included Dashlaunch 2.25 patches in the image build process with the 2 files that usually Dashlaunch installs to Flash when used (launch.xex & lhelper.xex) they are added automatically to the final Glitch/Jtag image so I save you the time of installing Dashlaunch after flashing the image to xbox360.

And if you need to verify it is really there, you can simply run Dashlauch after flashing the image and check the output of Dashlauch that will say "All patches are current, no update is needed"  

Also for Jtag images, Xell/Xellous is updated by default to Xell Reloaded

Cheers

I don't agree that automatically including Dashlaunch is very helpful. I think user should be installing Dashlaunch by himself, because installer gives additional options such as configuring various launch.ini settings. DL isn't really automatic application, user should be aware of what things he does and doesn't need from Dashlaunch and configure it accordingly.

Also I don't think updating by default to Xell Reloaded is a good idea, while it does have HDMI support, it's lacking in other stuff such as doesn't have NAND flashing function (NAND flashing is superb in Xellous).

[Rogero]

QUOTE(Glottiz @ Nov 6 2011, 09:02 AM)

because installer gives additional options such as configuring various launch.ini settings. DL isn't really automatic application, user should be aware of what things he does and doesn't need from Dashlaunch and configure it accordingly.

Dashlaunch latest patches are an improvement to freeboot patches, which adds better games compatibility and fixes, so better have your Dash always patched with latest patches.
Also, you can run Dashlaunch installer anytime to configure startup parameters, the patches will be already updated, but other options from launch.ini are always there to configure as the user needs them.

QUOTE

Also I don't think updating by default to Xell Reloaded is a good idea, while it does have HDMI support, it's lacking in other stuff such as doesn't have NAND flashing function (NAND flashing is superb in Xellous).

Xell Reloaded have HDMI support, can auto-launch .elf executables like Libxenon built homebrew/Emulators/etc..  and about the missing Nand Flasher that's why Rawflash v3 was made, to allow Nand flashing from Xell Reloaded (instead of having your updflash.bin image on the USB, all you have to do more is include 1 more file "xenon.elf" from Rawflash also on the USB root with the image to flash and Rawflash will flash it on startup like Xellous does)

[danthaman673]

QUOTE(Rogero @ Nov 5 2011, 01:26 PM)

hi steveo1978,

version 0.2 is already downgrading the cb_6751 to cb_6750 automatically, it means any Jasper that have cb_6751 in the nand image will have the Xell/ECC image built using a donor cb_6750

I had reports from various users with Jaspers/cb_6751 that the Xell image built using the donor cb_6750 is loading fine but it's the Dashboard image that's not loading. (knowing that the program uses the same donor cb_6750 to build both the Xell/ECC and the Dashboard images) so basically both images should work fine.

But for the Dashboard image I think if the nand have some bad blocks, that's what preventing the image from loading fine, and the solution in this case would be to use a Flashing program that can remap bad blocks properly while flashing the image back into the nand like "rawflash v3", the steps would be something like this:

- you must have the Xell ecc image already flashed and loading fine before you continue.
- you must not use a hardware flasher to flash the Dash image because Nandpro can't remap bad blocks
- Download the nand Flashing program "rawflash v3" by cOz from Rawflash v3 by cOz
- put "xenon.elf" with the the Dash/Glitch image renamed to "nandflash.bin" on a USB flash/drive.
- insert the USB into xbox360 and run Xell Reloaded

Rawflash v3 should flash your image and remap the Bad Blocks in the nand/image automatically

I hope this helps the users having problems with their Jasper/cb_6751

Thanx for coming over top the dark side Rogero ;-)

 I'm just a little curious, why do say that 6752 will use donor nands and then below say 6752 is unglitchable?


Cheers and thanx again fer the tool/Dan

[Dicko316]

The Image I created made the fans run very loud, is there a reason/fix for this. I went back to easy ggbuild 0.33b and the image there worked perfect and normal sounding fans.
Must be a problem with this version?!?
I flashed with Rawflash v3 too, I also tried to flash it a few times too just to make sure.
Oh and its a Jasper 512, cb 6750.

[Dicko316]

Thanks for the update Rogeron u r the man!

[Rogero]

Updated:

360_Multi_Builder_v0.3 on 13/11/2011
----------------------------------------------------------------
- Updated Dashlaunch patches to latest version 2.26 / thanks cOz
- Added the option to build the image without Dashlaunch patches too.
- Added the option to build the Jtag image with SMC = AUD_CLAMP.
- Added full checks of different CB versions to the Xell/ECC script.
- Added RawFlash v3 / "xenon.elf" to "Data" folder with flashing note.
- Fixed the Fans Speed back to auto (it was 70% in previous version).

Credits to ggbuild/fbbuild/freeboot/360FlashTool/Dashlaunch & Rawflash teams and devs.
Credits and big thanks to BestPig for sharing his awesome fcrt_extractor.exe program.


source: www.tortuga-cove.com

[steveo1978]

Got first post updated and title for you Rogero. If you want to change the way the first post looks or anything just let me know and I will make the changes.

[Rogero]

QUOTE(steveo1978 @ Nov 13 2011, 07:42 AM)

Got first post updated and title for you Rogero. If you want to change the way the first post looks or anything just let me know and I will make the changes.

Thank you steveo1978 for updating first post, it's fine

[alamez]

Can i go from XBR on 8955 to the latest dash with this? Also dont have original nand only the xbr i got from flash360?

[Rogero]

QUOTE(alamez @ Nov 15 2011, 02:24 PM)

Can i go from XBR on 8955 to the latest dash with this? Also dont have original nand only the xbr i got from flash360?

you can simply try to rename your XBR image to "nanddump.bin" and put it with your CPU key as "cpukey.txt" in folder "..Data\my360\" and try to build the image, in general it should work, because the program will only extract the files KV.bin, smc_config.bin and smc.bin (smc.bin may not be needed for Jtag too because hacked smc is supplied from the program) from your XBR nand regardless of what is the type of the source nand.
Please report back in case it worked for you so other users will know this too
Also, you can build a retail image of the original Dash version 13604 if you want also from your XBR image.

cheers

[alamez]

QUOTE(Rogero @ Nov 15 2011, 06:59 AM)

you can simply try to rename your XBR image to "nanddump.bin" and put it with your CPU key as "cpukey.txt" in folder "..Data\my360\" and try to build the image, in general it should work, because the program will only extract the files KV.bin, smc_config.bin and smc.bin (smc.bin may not be needed for Jtag too because hacked smc is supplied from the program) from your XBR nand regardless of what is the type of the source nand.
Please report back in case it worked for you so other users will know this too
Also, you can build a retail image of the original Dash version 13604 if you want also from your XBR image.

cheers

 Okay sounds good i will try but before i try which nand should i use? theres 2 option in flash360 one is full back up and the other one is partial or something like that

[Rogero]

QUOTE(alamez @ Nov 16 2011, 03:02 AM)

before i try which nand should i use? theres 2 option in flash360 one is full back up and the other one is partial or something like that

this option is only for Jasper 256MB or 512MB, and in case you have one you need the partial part which is Flash area only = 64MB (66MB nand dump).
If you have Jasper16MB or older board then the nand dump is only 16MB

[alamez]

QUOTE(Rogero @ Nov 15 2011, 10:19 PM)

this option is only for Jasper 256MB or 512MB, and in case you have one you need the partial part which is Flash area only = 64MB (66MB nand dump).
If you have Jasper16MB or older board then the nand dump is only 16MB

Okay so i got the nand dump used NAND Flasher 360 then it said it was succesfull. when i powered it up though it wont boot to dashboard and i get the 3 red rings. yup im screwed wont even boot to xell. it goes 3 green then they turn red.