I made a post on tortuga-cove.com stating the following:

Hello,

I picked up a refurbished xbox360 from gamestop, and when I dumped the nand it was reported as being a zephyr with a 4650 CB. I can't find this CB ANYWHERE on google nor on any piece of documentation of anything even remotely relating to this CB.

So does this mean that this board will never be glitched? I can't even attempt to glitch it at this point, as xell cannot make an ecc for it.

Please advise. thank you.

__________

- I dumped the nand 4 times and compared each one to each other. I even flashed it back to make sure it worked. (My soldering is on ponit)
- When I checked my xbox, the dashboard said said that I was on 14719, but J-Runner says:

6BL[CF] Patch 0: 14717 6BL[CF] Patch 1: 14719
7BL[CG] Patch 0:14717 7BL[CG] Patch 1:14719



Now, looking at Squirt360's RGH_2.0.rar's Xell, it has a CB_a 4560.bin, but xecuter's does not. Sometimes I wonder why I bough a tx coolrunner, as I was never able to get it to work properly with rgh 2.0 (I wound up going with a squirt360). I have a RGH 2.0 squirt3 currently working in my main xbox, but I don't wan't to take it out.

Could I use Squirt360's Xell to make an ECC image that a coolrunner might be able to use? I know that squirt 360 glitches a little differently and i'm afraid to use there build.py to make an ecc. I can provide my NAND for download if need be.

___________

THis is what I get when I try to build the image (output from CMD):

Z:\xbox\SQUIRT_360>python imgbuild\build.py nanddump.bin cdxell\CD xell\xell-ggg
ggg.bin
* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 4560) at 00008000
Found 2BL (build 4560) at 00009fc0
Found 4BL (build 4560) at 000116e0
Found 5BL (build 1888) at 00016760
* found decrypted CD
* found XeLL binary, must be linked to 1c000000

* we found the following parts:
SMC: 1.9
CB_A: 4560
CB_B: 4560
CD (image): 4560
CD (decrypted): 9452

checking for proper 1BL key... ok
decrypting...
* checking if all files decrypted properly... ok
* checking required versions...
Traceback (most recent call last):
File "imgbuild\build.py", line 417, in <module>
assert build(CB_A) in falcon_builds or build(CB_A) in zephyr_builds or build
(CB_A) in jasper_builds or build(CB_A) in trinity_builds, "CB "+str(build(CB_A))
+ " not eligible"
AssertionError: CB 4560 not eligible

______________________

Any suggestions?

EDIT: I notice that in the "cb" folder, there is a cba4650.bin, but there is no cbb4650.bin. I find this just a little annoying. How can you support 4578 and 4577 but not a 4560?

Do you know how the RGH 2.0 works, it uses the old CB_B not the new one.

Honestly no i do not. I have a basic understanding of the old rgh and rgh 2.0.

At the end of the day, I just want an ecc image. I do not mind reading, but I do not know where to start. Google has gotten me far, but now I just need a point in the right direction on how to build a working ECC that I can at least attempt to glitch this console with.

Please call me an idiot, and point me in the right direction. I do not mind reading.

I've been doing some more reading and I have a better understanding of the rgh, but i still don't know what to do to get a working ecc for this cb version.

Am i out of luck?

Instead of being rude and unhelpful, keep your comments to yourself.

He helped him,.....might have came off a little rude but info was not unhelpful,........maybe you should take your own advise.