XBox wont boot after RGH attempt

[nemesis436]

OK, heres the story.
Me and a friend work together JTAGGING, RGHing, Flashing and modding xbox's
We received a jasper BB 512 last week and my mate took on that particular job.
He wasnt sure which BB it was but said after looking he had thought it was a 256.
He ripped 256 from the nand, patched it with the new .ecc and hooked it up to get the CPUKEY which resulted in a 0022 rrod error.
Once he had realised what he had done and that it was in fact a 512 he proceeded to flash the original 256 back to the nand in an attempt to return the box to stock which again resulted in a 0022! He then made a 512 rip from that thinking it would result in a clean original 512 rip, is this correct???
Albeit now he had this it still would not boot however he tried
He brought it round to my house and since then we have tried numerous ways of returning the box back to stock so we could get it working again at least.
We discovered that you can now use donor nands so thought anything is better than a dead box, we downloaded a 512 clean nand, used the repair option in jtag too and created a new nand with that and the 256 rip. didnt work
After some time i realised that the supposed 'clean' nand was actually a pre-8955 rip, cb is 7325 so im presuming this is the reason it didnt work.
We also tried creating an RGH again after using the 512 rip he took from after he flashed his clean 256 rip back to the nand and injecting a donor KV i have from another jasper (albeit NOT a 512), alas no more 0022, it would turn on, glitch but still no boot!!!
realised surely we would need a donor config.bin too so injected that in but still no luck, just sits there glitching indefinitly but does not boot to xell AT ALL.

Can someone please help, what can we do to recover this box as i just wanna hit it with a hammer atm

Can we just erase the whole nand with 'nandpro usb: -e512' and then flash back the original 256 leaving the rest 'unformatted' as such?

Just so its known, he did take a few rips of that 256 dump before he realised and they do all match with NO non-matching blocks so that file is GOOD (just the wrong size) we have the kv_enc.bin, and the config.bin, is this recoverable???

Many Thanks

Edit: any soldering that was done is good, we are both technician's that solder most days as part of our job

 

[BL4K3Y]

First of all, why did you read the full NAND?
You only needed to read 64MB, regardless of if it's a 256MB or 512MB unit.

With regards to the donor unit, you would need to build a donor NAND that has the same LDV value your console has. You should still be able to build an ECC image if you use a donor Jasper NAND and from there, you can grab your CPU key and such and then re-build a clean NAND using a donor.

 

[nemesis436]

Ill be honest blakey im new to Lock Down Values, I am aware they are written to the beginning of the nand but what are they, how do i extract them to inject to a clean nand?
I have the config.bin and kv_enc.bin if i can get them from that???

To answer you're question about ripping first 64meg, we have always taken a full dump, i know it is mostly unnecessary but we do it out of habit now.
We will only be taking first 64 in future mind

Does the donor nand we use have to be a 512 or just as long as its 'jasper'??

Thanks for your help so far

 

[Martin C]

"Me and a friend work together JTAGGING, RGHing, Flashing and modding xbox's"

Get another hobby.

It's obvious there are so many holes in your knowledge that you really shouldn't be messing with them.

We have so many guides here - I have a roadmap for noobies guide as a sticky in this very section, which you should have read before even posting.

Whatever level of skill you THINK you have, I guarantee it's not anywhere near high enough to consider doing this as a job.

Get reading ALL stickys and the answer to your problem will be clear.

 

[nemesis436]

Dont be so arrogant Martin, 'so many holes in my knowledge', its a learning process and running into problems is the best way to learn.

Ive been scouring tuts and stuff for days, nothing is applicable to reading a nad as a 256 when it should have been read as 512 so dont start flaming when you have no idea what ive been doing.

And i never 'considered' anything, im confused as to what your talking about, we do this for extra money and this is the first time we have hit a problem in the 30 odd jtags and 12 or so RGHs we have done.

Dont be so quick to start personally insulting people pal, im not some noob who hasnt a clue, im a communications systems engineer who does this sort of sh*t for a living, ive just hit a snag and was HOPING for some help, clearly youre not willing to do that!!!

---------- Post added at 13:09 ---------- Previous post was at 13:05 ----------

oh for the record, ill read all your stickies, and others, again, and see what i can come up with, but while im doing that please take a look at how long ive been on this forum and how many times ive asked for help!!!! Thats because unlike most i DO know how to search.
I appreciate you have retards that have no clue what they are doing but please dont tar me with the same brush?!

 

[Martin C]

You're in the noob section. The rules are simple.

"Read the stickys."

You haven't, clearly. My roadmap for noobies like you is RIGHT THERE in THIS VERY SECTION! It explains how to check console type, what to dump etc.

"Ive been scouring tuts and stuff for days, nothing is applicable to reading a nad as a 256 when it should have been read as 512 so dont start flaming when you have no idea what ive been doing."

If you knew what you were doing, you'd already know it makes no difference whatsoever. You can dump 512 from a 256 or 256 from a 512. You would still get the same result. You're now talking about needing a DONOR NAND, which shouldn't even come into the equation.

Finally, you're confusing arrogance with frustration.

Myself and other have spent HOURS writing up tutorials and guides to help people with this stuff and you don't even bother to read it. Now you want 1:1 attention because of this. You might do it for extra money but there's no monetary compensation for those of us who DO write the guides. All we ask is you read them.

If you read them and didn't understand then you should STOP until you do.

oh and for the record:

" its a learning process and running into problems is the best way to learn"

It's a READING process. The hard work has been done for you. If you want to reinvent the wheel, go ahead. Just don't come here asking for help on how to do it.