[05:53] <IMADV8> There isn't one for the forum in general, though?
[05:54] <SiD> http://team-xecuter.com/new-guides-new-irc-support-channel/
[05:54] <SiD> you're already on
[05:54] <IMADV8> Yeah, this is just for RGH $#!t though
[05:55] <IMADV8> Basically I asked in the SONUS thread if it was possible for MS to detect custom sound files

So u consider RGH $#!t? Nice. And expect ppl to be kind. I c..

do you need a cuddle?

There is no way the glitch 1BL at this time. There is no way to glitch a slim, or dual cb console, without the original CB_B or CPUKEY. Sorry mate but for now it's just a peace of junk.

I believe rogero's multibuilder or xebuildgui rc3 actually use a donor cb (at least they do for 6751 jasper). Try one of those to create ecc. You can still create ur ecc manualy with python, just dig a bit more into it..

Man, it's not only a matter of smc, it's a matter of cb! Find a correct cb for which the hack was made. Timings on any other cb than will not work!

On fat 4.7UF

Yes, u can still glitch it. U can program any 16mb nand, for example taken from another xbox, flash a generic ecc and resolder in place of the faulty! Then load xell, get cpu key, get ldv, etc.. u can then use any fb created nand with same ldv

He named the topic LDV/Invalid Secdata. To solve it one can easily use xebuild with cpukey (forget live if 've logged already with secdata flagged or tampered). The OSIG is not updated. If he gets unsupported with original discs possibly there's an issue with wrong dae.bin.

With xebuild u can create a clean stock nand.

The only thing i could do is:

http://www.xboxhacker.org/index.php?topic=17443.0

But on mine hdd was working fine..

Yes. U can use a zephyr nand donor.

if it does not work with an ecc donor, which u know worked fine, then there's something else..

Use any jasper donor ecc to get ldv of fs 07 from xell. Create fb starting from any jasper corresponding to ur nand size fixing only ldv found in xell.

And i bet that if u read the post code it will show 0x44. Can you confirm?

Changing the cap now will not solve the problem. If it's an LDV issue, the xbox will not try to burn it again. It expects that te update burned it, so i believe u can only glitch it. Get the cpukey. Using xebuild you can then restore an original nand if you wish. You might need to fix the ldv value in options.ini of xebuild to match the "F"s on fuseset 07 shown in xell.

Nice.. but why dont u try on ur own? It's not that difficult...

Get it from a jasper donor, u need to know the cpukey of the donor. Then open it with 360 flash tools and extract it.

There are many ways, the one i tested, working and easy it's to do, this will maintain your kv:

1) nandpro yourecc.ecc: -r16 kv.bin 1 1
2) Inject it into any 16mb jasper donor
3) Launch 360 Flash Tools
4) Input CPUkey
5) Extract KV (only this, the rest is NOT usable as cripted with another CPUkey)

Now you have your kv in .bin format. Uses now xebuild to build manually your image by editing the options.ini (remeber LDV= count F on fuseset 07 in xell). Put kv.bin in data folder and have all 14699 files in the corresponding folder.

Hope this helps.

Use any jasper created ecc. get cpu key.

When uve done with the glitch get back here or write me a pm

Sorry mate, i still havent understood what is your problem..

1) Are u good at soldering?
2) What console model have u got?

Let's start with these 2 simple question.