360 Multi Builder for all Xbox360 Image Types

[dewana]

have sent you msg wit nanddump link and keys kindly check ur msg

[Rogero]

have sent you msg wit nanddump link and keys kindly check ur msg

you only have to put "nanddump.bin" + "cpukey.txt" into "Data\my360\" folder, you don't have to put the "smc.bin" file, the program will get it from the nand dump, just give it a try and let me know if it worked

[M37R01D]

thanks for filling my request of the AUD_CLAMP fix
keep up the great work

I added this the very last minute with eyes almost closed
Please test it and confirm if it's working as it should.

Worked perfectly on my falcon. I selected option 3 for Dashlaunch & AUD_Clamp patches then flashed with flash360 and everything booted up great. Keep up the great work

[Rogero]

thanks for filling my request of the AUD_CLAMP fix
keep up the great work

I added this the very last minute with eyes almost closed
Please test it and confirm if it's working as it should.

Worked perfectly on my falcon. I selected option 3 for Dashlaunch & AUD_Clamp patches then flashed with flash360 and everything booted up great. Keep up the great work

Thank you for the confirmation, i'm glad it worked as it should.

[Rogero]

have sent you msg wit nanddump link and keys kindly check ur msg

you only have to put "nanddump.bin" + "cpukey.txt" into "Data\my360\" folder, you don't have to put the "smc.bin" file, the program will get it from the nand dump, just give it a try and let me know if it worked

hello,
man, are u sure you have a Slim ???? your nand dump is 64MB but a Slim nand dump should be only 16MB ???????

maybe you have used the wrong command to dump your nand if u used nandpro ( used -r64 instead of -r16 )

again, a Slim nand is only 16MB that's why the program tells you wrong file size.

[eldon]

first thx for the nice tool

i was willing to give it a try to upgrade one of my old xenon jtag, but after checking our options.ini file i can't find a way to specify a "no dvd drive" option.

That xenon has a dead dvd controller so there's no dvd plugged in, and it makes the "xell startup" with eject button useless unless i specify that the box has no dvd drive in the xell thing.

So i was wondering if you could tell me if the option exists, if it wasn't documented in your options.ini or if it's not present and would require to be added.

thx again

-- edit --

seems that the nodvd option is not required with xell reloaded, at least it works now when i boot with eject i do get into xell reloaded.

thx again for this nice tool.

[Rogero]

first thx for the nice tool

i was willing to give it a try to upgrade one of my old xenon jtag, but after checking our options.ini file i can't find a way to specify a "no dvd drive" option.

That xenon has a dead dvd controller so there's no dvd plugged in, and it makes the "xell startup" with eject button useless unless i specify that the box has no dvd drive in the xell thing.

So i was wondering if you could tell me if the option exists, if it wasn't documented in your options.ini or if it's not present and would require to be added.

thx again

-- edit --

seems that the nodvd option is not required with xell reloaded, at least it works now when i boot with eject i do get into xell reloaded.

thx again for this nice tool.

Hi, i'm glad it worked fine with your machine that have no dvd drive, and Yes Xell reloaded does have many fixes over the previous Xell/Xellous.
Cheers

[anhxco]

Hi, there is the problem about xell building for jasper CB6751 on V0.3. I couldn't boot xell if using V0.3. I tried to build xell with V0.2 and it work fine.

[Rogero]

Hi, there is the problem about xell building for jasper CB6751 on V0.3. I couldn't boot xell if using V0.3. I tried to build xell with V0.2 and it work fine.

Hi, thanks for reporting this, I have re-checked the code now and fixed a bug where the the CB_A was still being decrypted even if the donor CB_6750 was used.

In version 0.3 folder,
Please replace the file called "build.py" in folder "...\Data\" with this version "build.rar" ( Clicked 155 times )
and then you can build the ECC/Cell image again and test it if possible because I don't have any Jasper with CB_6751 to test with.

N.B: unrar the build.rar and overwrite the old build.py with this one.

Thanks.

edit: build.rar file updated

[anhxco]

Hi, there is the problem about xell building for jasper CB6751 on V0.3. I couldn't boot xell if using V0.3. I tried to build xell with V0.2 and it work fine.

Hi, thanks for reporting this, I have re-checked the code now and fixed a bug where the the CB_A was still being decrypted even if the donor CB_6750 was used.

In version 0.3 folder,
Please replace the file called "build.py" in folder "...\Data\" with this version "build.rar" ( Clicked 153 times )
and then you can build the ECC/Cell image again and test it if possible because I don't have any Jasper with CB_6751 to test with.

N.B: unrar the build.rar and overwrite the old build.py with this one.

Thanks.

Thank you!
I will check that and report you late.
Thanks again!