JTAG Damn 0022 & Black screen problems and need help

[jahoodi]

This is my friend's console a 16mb jasper. Everything started OK... I extracted the nand 3 times to find to matching dumps and then made the .ecc image using the Python command and wrote successfully to the nand ..

Programmed my matrix glitcher using a hommade lpt programmer according to GliGli's schem. and it identified and programmed successfully the first time using Impact ..

Wired My glitcher and started the console and it booted to xell in 2-5 sec. just like a dream and I got my CPU and dvd key All OK .. let it set overnight ..

I came back and created my ggbuild image using EasyGGbuild 0.4 by Rogero and wrote the updflash to the nand using nandpro and then started the console to get a black screen with no errors and here is where my problems started !..

I erased my nand ( -e16 ) and wrote the same updflash again and also a black screen with no errors .. I wrote back my original image and removed my glitcher and wires and now it gives me error 0022 after about 30 seconds .. Flashed the image_0000000.ecc that was working and wired my glitcher to get a black screen with no errors !!

So basicly the .ecc image and the ggbuild image all give me a black screen and my stock verified image gives me the rrod 0022 error ..

I've tried everything I could think of and nothing boots right now and I'm totally stuck with my friend's box ..

I hope anyone with experience to post his thought about this as I really need this console working ..

Original nand is 13146 image and my CB is 6750 .. I've jtagged many systems before and I know what I'm doing ..

thanks

 

[dragon_unleashed]

ur are doing this hack ond old dash, flash back ur og nand by -w command, remove glitcher wiring, update ur dash to d latest 13604 dash and now follow the steps from beginning. the new ggbuild supports only 13599 and 13604 dash.

 

[Martin C]

What did you use to dump the NAND?

You say you dumped 3 times - were all dumps matching? What did you check them against?

 

[dedarus]

this is when using sh*ty products like matrix glitcher!

 

[jahoodi]

ur are doing this hack ond old dash, flash back ur og nand by -w command, remove glitcher wiring, update ur dash to d latest 13604 dash and now follow the steps from beginning. the new ggbuild supports only 13599 and 13604 dash.

When I write back my original it gives me 0022 that's why I'm stuck .. Although I thought It supports 13146 dumps .

Thank you

What did you use to dump the NAND?

You say you dumped 3 times - were all dumps matching? What did you check them against?

I used the matrix nand flasher and 2 of my original dumps were matching according to TotalCommander..

I've wrote my original using the same nand flasher and read it back twice to find all three files are matching ( TotalCommander ) ..

Something tells me there is something gone bad on the mobo :mad2:

this is when using sh*ty products like matrix glitcher!

Well it worked fine on my other slim console

I've tried generating a Stock 13604 image using EasyggBuild and writing it to the nand with no success .. Also I tried generating the hacked image based on the stock 13604 image and also fail ..

Why isn't Xell boot now like earlier ? and what about rebuilding a clean stock 13146 nand to start over ?

 

[Martin C]

Remember that the .ecc gets flashed using +w.

The built image gets flashed using -w.

Don't get the two mixed up.

 

[jahoodi]

I'm not :frown:

 

[Martin C]

Flash back the original NAND and make sure it's still working ok. Fix an LED onto pin 15 of the CPLD and ground it. It should pulse as the glitches does its thing. If it doesn't, then wiring or code you've written to the NAND may be to blame. I did a 6750 Jasper yesterday and it glitches within 5-10 secs every time.


Sent from my iPad using Tapatalk.

 

[Nick420]

This is my friend's console a 16mb jasper. Everything started OK... I extracted the nand 3 times to find to matching dumps and then made the .ecc image using the Python command and wrote successfully to the nand ..

Programmed my matrix glitcher using a hommade lpt programmer according to GliGli's schem. and it identified and programmed successfully the first time using Impact ..

Wired My glitcher and started the console and it booted to xell in 2-5 sec. just like a dream and I got my CPU and dvd key All OK .. let it set overnight ..

I came back and created my ggbuild image using EasyGGbuild 0.4 by Rogero and wrote the updflash to the nand using nandpro and then started the console to get a black screen with no errors and here is where my problems started !..

I erased my nand ( -e16 ) and wrote the same updflash again and also a black screen with no errors .. I wrote back my original image and removed my glitcher and wires and now it gives me error 0022 after about 30 seconds .. Flashed the image_0000000.ecc that was working and wired my glitcher to get a black screen with no errors !!

So basicly the .ecc image and the ggbuild image all give me a black screen and my stock verified image gives me the rrod 0022 error ..

I've tried everything I could think of and nothing boots right now and I'm totally stuck with my friend's box ..

I hope anyone with experience to post his thought about this as I really need this console working ..

Original nand is 13146 image and my CB is 6750 .. I've jtagged many systems before and I know what I'm doing ..

thanks

I'm having the very same problem as this. Jasper16mb CB1650. Stubborn **** of a box just would not glitch, tried the longer wire trick and a 10k ohm resistor, probing with finger/meter etc, just black screen.
Removed everything
Flashed my original NAND back,
Console sits at green light black screen then 3red lights 0022 after about 45 seconds :-/
If I read the nand it matches the original.
Any help is much appreciated.
Also the mobo seems fine.
Funny how we both have the same problem with the same type console with the same chip.

 

[dogeatdog]

Any updates on this ? I'm in the same boat and yes, the dumps match. I took four identical dumps before I started and have checked after I wrote back the original dump by dumping it again. And it matches.

So it's not the nand. Son of *** Jasper 16mb, not glitchable by any means and now won't even operate when flashed back to stock.

 

[Martin C]

Check my LDV thread.

 

[dogeatdog]

Will do

edit : Ah, yes. That. Problem is, I CAN'T get this one to glitch.. and I don't have the cpu key. So good luck counting fff (you could count my numer of fffuuuuuuu, but that didn't help much) or rebuilding the nand.

I got this from another modder who was tired trying after too many hours and so it was my turn. After redoing a few solder points and even swapping another coolrunner and (I was desperate !) a Matrix glitcher, using 680pF, 68nF, 47nF and longer/shorter wires/placement.. bladiebla, you know the drill I just wanted it to return to stock to see if it was working before I got the nanddumps from him and just flashed that back.

So.. my only option out is to try and glitch it.

I was wondering however, could it be (he said it was a jasper 16mb and the dumps he took were 16mb) this is actually a jasper bb. How can I tell ? I only have the metal casing and the mobo here. And obviously I can't go in the dashboard and see how much free memory it has

 

[Martin C]

Easiest way to check (and I'll be doing a sticky on this soon too).

Take your NAND dump. Open it in 360 Flash Dump Tool.

Go to the Edit Config screen.

If the values are all FFFs, then you have the wrong size dump (if you have a 16MB it should be a 64MB and vice versa).

 

[dogeatdog]

Ok, just checked that. All normal values in edit config. So it is actually a 16mb jasper. With 13604 dash (according to the nand).

Will generate ecc again with mb 0.7 and see what it gives.

 

[jahoodi]

No update with me here my friend .. that console is now setting in the dust since I gave up on it believing it was a short under the cpu due me holding and carrying the mobo by the cpu heatsink most of the time ..

So 1 lesson learnt .. Phat units must allways run with fan and shroud on ..

Althogh I did a bunch of jaspers afterwards and some glitched fine from the beginning and some would glitch after you get sick of it and about to blow it and some did not glitch whatever I do so the ones that would not glitch peacefully I would just add the 68nf cap and all the problems immediately disappear and stubborn jaspers become like falcons so that what got me thinking it's a short under the cpu with that unit ..

one thing that I haven't tried yet though is the POST bus monitor thing .. Can anybody post a quick giude on doing it on those jaspers ? I really don't get the whole thing by reading the nandpro's readme file .

Good luck with you I hope it's not A hardware issue that you're experiencing.

 

[dogeatdog]

Just a small update. I give up.

That might be too small

I looked at PLL_BYPASS closely and saw it might be damaged. There was also no continuity from that point to the resistor below it, so I did the alt fix. Which helped nothing. I also fiddled around with some more caps (100nF on D, 47nF on D, with and without GND). Nothing helped. Also couldn't get it to boot the stock dash anymore. The nanddump was good (and 16mb) and it was on 2.0.13604 when it was dumped and not upgraded since then. I'm at a complete loss here and so I send it back to my modder friend to let him disappoint his customer. It's too bad a few experts will claim it's due to soldering skills, noob this and noob that, while the ones who actually have had these cases know it isn't. Something fishy is going on and it defies all logic (I agree that writing back a stock nand which you dumped before should never give any problems.. but somehow it does.. in rare cases.)

Anyway, thanks for all your answers, too bad the problem remains for me, my friend and a lot of other people.

 

[Martin C]

There is absolutely nothing 'fishy' at all. If you cannot boot a console by writing the NAND back, then you have something else wrong. It's that simple. You've blown/shorted/killed something in the process. I've lost count on how many of these I've done and can tell you first hand if you solder the wires incorrectly you will have issues. More than likely a mis-hap with the CPU_PLL_BYPASS, however it WAS something you did. Trust me.

 

[dogeatdog]

There is absolutely nothing 'fishy' at all. If you cannot boot a console by writing the NAND back, then you have something else wrong. It's that simple. You've blown/shorted/killed something in the process. I've lost count on how many of these I've done and can tell you first hand if you solder the wires incorrectly you will have issues. More than likely a mis-hap with the CPU_PLL_BYPASS, however it WAS something you did. Trust me.

Read my posts again. I was never something I did in the first place. But I'll relay the message to the one who sent me the console in this state

 

[Martin C]

" It's too bad a few experts will claim it's due to soldering skills, noob this and noob that, while the ones who actually have had these cases know it isn't. Something fishy is going on and it defies all logic (I agree that writing back a stock nand which you dumped before should never give any problems.. but somehow it does.. in rare cases.)"

This complete statement is bullshit - that's my problem.

If you get a good NAND read and the console hasn't updated its LDV, writing it back works EVERY TIME. Telling people otherwise is inaccurate. I have restored countless systems with no problems whatsoever.

Soldering will ALWAYS be the problem, since a majority of these problem installs are being carried out by kiddies with the wrong kit. No reading is being done and no practicing. Like most kiddies, they think they will just be able to pick something up for the first time and make it work. Even better than all of this, with the stock NAND in place and CR installed, you console should be able to boot still which will prove the wiring before messing with the NAND. Anyone worth their salt knows this.

 

[dogeatdog]

Soldering will ALWAYS be the problem, since a majority of these problem installs are being carried out by kiddies with the wrong kit. No reading is being done and no practicing. Like most kiddies, they think they will just be able to pick something up for the first time and make it work. Even better than all of this, with the stock NAND in place and CR installed, you console should be able to boot still which will prove the wiring before messing with the NAND. Anyone worth their salt knows this.

Yes, I know this. And glad you confirmed it. So, the fishy part must have been some soldering error by my modding colleague in the field then. Apart from the PLL_BYPASS alt fix I performed to no avail, are there other usual suspects to look at should I get more of this duds from other modders to look at ?