Print

[krizalid]

Build XeLLous v0.1 (uses ibuild, nandpro2b and donor files)

- Simply start the app and type the motherboard type you want it for and it will build it for you.

Final size is in 50 blocks (hex), or 80 16kb blocks. NAND area is 0 > 4F


- NOTE and WARNING: This will make a fully working XeLLous to flash for the first time to your 360.
Keep in mind that it's based on FreeBoot's ibuild and it will look to launch the rebooter if you power on
with the "power button", please power on with the "eject button" and drive attached.


What's the main idea?

- Rapidly build Xellous.bin for your console so you may acquire "fuses.txt" and "flashdmp.bin" via FTP and create your FreeBoot or XBR Image and flash, instead of flashing all from PC (may take forever using LPT  (IMG:style_emoticons/default/ph34r.gif) )


This version does have both Jasper's South Bridge versions of the SMC so that you may build for Jasper16 or JasperBB and not having a black screen boot up on you (IMG:style_emoticons/default/tongue.gif)

Cheers.

Nknave/Krizalid

DOWNLOAD

This post has been edited by krizalid: May 18 2010, 08:19 AM

[WarriorSan]

Thanks for the app!

(IMG:http://img576.imageshack.us/img576/6025/buildxellousv01.jpg)

This post has been edited by WarriorSan: May 18 2010, 04:35 PM

[liteon6x]

i lost my original nand for my xenon (yes it jtaggable)
can i just flash it with this and get my files
or do i need to patch it with my kv and stuff

This post has been edited by liteon6x: May 19 2010, 05:46 AM

[krizalid]

If you just flash, you're gonna loose your KeyVault block and cannot get back.

Best to do is to dump your nand with flash360 if you are already in homebrew, or via LPT dump the blocks where this will flash into.

nandpro lpt: -r2 backup80.bin 0 50 (dump at least 3 times and compare)

than for your KV

nandpro lpt: -r1 rawkv.bin 1 1 (three time to compare files)

than flash XeLLous built with this package

nandpro lpt: -w2 xell.bin 0 50

and your rawkv

nandpro lpt: -w1 rawkv.bin 1 1

Than you may boot to XeLLous when you power on with Eject button, and via HTTP  obtain fuses.txt so you may create a nand of choice via freeboot and ibuild.

[cory1492]

I'm surprised they posted the link to the front page, as the first thing this does is extract a whole mess of files (that could plausibly cause trouble for the site) including most CB/CD groups as well as ibuild from freeboot.

QUOTE

This version does have both Jasper's South Bridge versions of the SMC so that you may build for Jasper16 or JasperBB and not having a black screen boot up on you

You really should check again, the xell images use 2 versions of smc code - xenon (a modified xenon smc) and everything (zephyr, falcon, jasper and jasperBB) else ( based on a modified jasper BB smc.) Oh yeah...  (IMG:style_emoticons/default/tongue.gif)

This post has been edited by cory1492: May 19 2010, 06:17 AM

[krizalid]

True on the illegal files, but than again JTAG Tool 1.70 has far more and the most of them and still in front page.
They just need to remove main link on front page.

As for the SMCs, these are the same in free60 images release that worked well on Jaspers16/16a and BB.

No issues at all, will work.

[royvedas]

NAND area is 0 > 4F

- but what if I got three bad blocks in my original dump in this area, relocated to the "back" of the nand?

How should I handle that situation?

[lefty420]

Might give this a miss I tried installing xellous with flash360 on my freboot.032 yesterday and I got a black screen with the middle green light lit up lol. Had to reflash xbr and then reinstall freeboot.

[krizalid]

@rovedas:

Blocks from 0 > 3F is where most of Xellous code is.
If you need to remap bad blocks within this area, just remap anywhere between 40 to 4F (in nandpro would start from 50 as the last block and down.

@lefty420:

This is meant for first time JTAGers, meaning that most likely will flash via LPT where this issue will not happen.

If you wanted to flash via Flash360 or XeLLous onboard, you'd need to have a 16mb.bin file and using nandpro's virtual device, flash xell.bin to this file, remap bad blocks if any, and than flash it.

[scuba156]

QUOTE(lefty420 @ May 19 2010, 09:43 PM)

Might give this a miss I tried installing xellous with flash360 on my freboot.032 yesterday and I got a black screen with the middle green light lit up lol. Had to reflash xbr and then reinstall freeboot.

because you overwrote the kv. Freeboot has Xellous already included in it, press eject on boot time to boot it. If you dont know what your doing or dont understand it, dont do it

[RRoD420]

So after building the xellous image for board, i have to flash "-w16 kv.bin 1 1" correct? otherwise xellous will be unable to read/write my flash? That should be noted on the front page as there is no readme with this.

[krizalid]

QUOTE(RRoD420 @ May 20 2010, 05:32 PM)

So after building the xellous image for board, i have to flash "-w16 kv.bin 1 1" correct? otherwise xellous will be unable to read/write my flash? That should be noted on the front page as there is no readme with this.

Actually it is not necessary but useful.

If this is the first time your going to flash FreeBoot, I suggest the following procedure:

- nandpro lpt: -r2 backup.bin 0 50  (do it multiple times to make sure you have a good dump)
- nandpro lpt: -w2 xell.bin 0 50 (will flash xellous that is 80blocks in size)
- PowerOn your 360 with Eject Button and DVD Drive preferably.
- HTTP to obtain fuses.txt and flashdmp.bin (rawflash dump)
- using nandpro2b for virtual device: nandpro flashdmp.bin: -w2 backup.bin 0 50 (you will now have an original dump)
- rename your flashdmp.bin to orig.bin (this is optional)
- build your FreeBoot image using this and your cpu key obtained from fuses.txt
- using xellous, flash your freeboot image.

This is how I do it and it works flawlessly.
Flashing rawkv.bin over XeLLous will only add your DVD Key to the fuses.txt, that's all, and since your only running Xellous temporary to obtain files to build freeboot, this is not a must at this point.

Also, wrong keyvault will throw off Christmas lights if you power on with Power Button.

Not having keyvault has nothing to do with reading and writing to nand via XeLLous.

This post has been edited by krizalid: May 21 2010, 10:45 PM

[raburton]

Tried this on Xenon - worked, and JasperBB - didn't work.

[SNAAAKE]

noob alert!

where do put my KV and nand bin files? do I need those or it will just create the xell for my falcon system? and how do I flash the created file? put it on usb flash drive and boot with eject?

yes I did read the whole thread here but I didnt really understand everything lol..