Print

[chapas5400]

I'm having trouble running rawflash3, I've copied both files to a 256MB FAT32 formatted pen, inserted the pen on the front USB port of my SLIM 360, pressed the eject button, XELL start's but nothing happens, the pen is detected but xenon.elf is not fired?
What I'm doing wrong? This seems to easy to miss....

Thanks for the app Rogero!

[Rogero]

QUOTE(chapas5400 @ Nov 16 2011, 05:41 PM)

I'm having trouble running rawflash3, I've copied both files to a 256MB FAT32 formatted pen, inserted the pen on the front USB port of my SLIM 360, pressed the eject button, XELL start's but nothing happens, the pen is detected but xenon.elf is not fired?
What I'm doing wrong? This seems to easy to miss....

Thanks for the app Rogero!

hello,
today this happened with me too, Rawflash v3 refused to work just like you have mentioned, so i tried all the USB ports of the xbox360, then i have used another USB pen and it worked right away, on other xbox360 machines the first USB pen worked fine, so I say you should keep retrying the process till it picks it up, it could take some retries, and trying with another USB drive may help too.

QUOTE(alamez @ Nov 16 2011, 01:16 PM)

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.

have you dumped a good XBR image, did the program built the new image without problems, in case you have a Jtag installation that uses the alternative AUD_CLAMP points, then you should build an image with the "AUD_CLAMP" option, please give more details of what you have done.

[alamez]

I built the image with flash360 it came up good it had some bad sectors maybe thats where the issue is. Almost positive its not an audclamp. Im gonna take it to someone to take a look at it.

Used the image without fixing bad sectors i believe it had 8. Then used 360 Multi Builder v0.3 and it worked perfectly said it was successful and complete. Then to Flash it i had to use 360 nand flasher instead of rawflash v3 becasue its not supported by xbr. it flashed ignored bad sectors and was 100% complete. when i started the system again it would display nothing and just give me three red lights. tried booting to xell with eject button and nothing

[Rogero]

QUOTE(alamez @ Nov 17 2011, 02:07 AM)

I built the image with flash360 it came up good it had some bad sectors maybe thats where the issue is. Almost positive its not an audclamp. Im gonna take it to someone to take a look at it.

Used the image without fixing bad sectors i believe it had 8. Then used 360 Multi Builder v0.3 and it worked perfectly said it was successful and complete. Then to Flash it i had to use 360 nand flasher instead of rawflash v3 becasue its not supported by xbr. it flashed ignored bad sectors and was 100% complete. when i started the system again it would display nothing and just give me three red lights. tried booting to xell with eject button and nothing

The bad sectors are causing the problem of the red lights, you must remap all bad blocks manually in the new image you built with 360 Multi Builder v0.3 and then your only option now is to use a hardware flasher (LPT or USB) to flash the image again.
about remapping the bad blocks , look for "bad blocks mover" by Redline99 or you can remap them with nandpro manually by reading each bad block from the image (new image) and writing it back to the spare area with the right offsets.

[Rogero]

360_Multi_Builder_v0.4 on 27/11/2011

ChangeLog:
--------------
- Returned to using Dashlaunch v2.25 patch-set to avoid the "PlayDVD" problem  
   with some Liteon Drives that requires the fcrt.bin for proper function.

- Fixed a bug in the Xell/Ecc script regarding Jaspers with CB version 6751.

official site : www.tortuga-cove.com

[scoo]

hello,
anyone can confirm if CB version 6752 will be glitchable?
it is possible?

[Rogero]

360_Multi_Builder_v0.5 on 09/12/2011

ChangeLog :
---------------
- Added Support for xeBuild and latest Dashboard version 14699.
- Updated patches to Latest Dashlaunch v2.27 Patchset.
- now using xeBuild built-in "fcrt.bin" extractor for Trinity images.
- Added RGH smc files for proper RGH image building.
- Added Xenon Retail Image build option.

Credits to xeBuild / Dashlaunch devs, especially cOz.

official site : www.tortuga-cove.com

[ravendrow]

bravo rogero thanks for being so quick on this release works great

[steveo1978]

Yeah, I think his is a little more noob friendly then the xebuild GUI thing thats out.

OT: Rogero do you have a twitter account?

[Rogero]

QUOTE(steveo1978 @ Dec 10 2011, 07:38 AM)

Yeah, I think his is a little more noob friendly then the xebuild GUI thing thats out.

OT: Rogero do you have a twitter account?

I do have a twitter account, but i rarely use it

it's :  _Rogero_

[Rogero]

360 Multi Builder v0.6

Changelog :
--------------
- Removed the pre-patched RGH smc files that were used in version 0.5
- Now using xeBuild to patch the RGH/smc files for better RGH images compatibility.

Credits to xeBuild / Dashlaunch devs, especially cOz.

official site : www.tortuga-cove.com

[steveo1978]

Rogero is it possible to have this make the dashlaunch ini file? I can set one up and all that, but for the all the people that do not know all the little tricks in how to truelly set one up for first use it would be helpful to have an easy to use tool that would allow then to easily setup their 360s to launch either FSD or XeXmenu from first start instead of trying to figure out how in the world to get the alternate dash on the 360 to begin with.

What I am saying is like have this either make the launch.ini or just include an launch.ini that will allow the average user  the ability to copy the launch .ini to a USB Flash drive and load say XeXmenu from the same flash drive.

[Rogero]

QUOTE(steveo1978 @ Dec 10 2011, 10:56 PM)

Rogero is it possible to have this make the dashlaunch ini file? I can set one up and all that, but for the all the people that do not know all the little tricks in how to truelly set one up for first use it would be helpful to have an easy to use tool that would allow then to easily setup their 360s to launch either FSD or XeXmenu from first start instead of trying to figure out how in the world to get the alternate dash on the 360 to begin with.

What I am saying is like have this either make the launch.ini or just include an launch.ini that will allow the average user  the ability to copy the launch .ini to a USB Flash drive and load say XeXmenu from the same flash drive.

Actually I was just thinking about this now...

I will add a nice and easy tool to build the launch.ini file, and i'll make the builder add a default launch.ini file into the Dashboard image by default too.

this will be for version 0.7

[steveo1978]

yeah that would be great. really for the one in Flash it would probably be better to have it boot something like this USB>dash>default.xex or something along those lines as a failsafe I guess. I was playing around with it yesterday just seeing what I could do and its actually pretty cool that I can just have an launch.ini on the USB drive and if I wanted to boot FSD I leave the USB Drive in and if I wanna go to stock dash I can just remove the Flash Drive.

[Rogero]

360_Multi_Builder_v0.7 on 11/12/2011

Changelog:
-------------
- Added a default "launch.ini" to Flash when image is created with Dashlaunch.
* Button_A=Hdd:\FSD\default.xex , default=Usb:\FSD\default.xex , rest=default
* No more need to run the Dashlaunch Installer on 360 at all after flashing the image.
- Added the option to auto-build custom "launch.ini" per user preference.

Credits to xeBuild / Dashlaunch devs, especially cOz.
Credits to ir0nman for this usefull tool : "buildini.exe"

official site : www.tortuga-cove.com