Jasper NAND Issue

[ando2k9]

Sorry for this very long post but it needs explaining

Right iloveme28 brought me round his jasper he'd been trying to jtag but wasn't having any luck (in this thread http://www.team-xecuter.com/forums/showthread.php?t=62019)

we couldn't get the board to accept the xell no matter how many times we flashed over the xell with the alt points etc the console would simply refuse to turn on no power at all psu would stay orange when pressing the power button.

So we tried flashing over a falcon xell and a zephyr xell just to see what happened, this time round it turned on but rrod after say 30 seconds with 0022 code.

We flashed over the jasper xell again to give it another go and still couldn't get anything, so i disconnected it all and checked for anything obvious on the board anywhere couldn't find anything so was put away for a bit (to give it another go later).

Before i know it iloveme28 came to collect after leaving it with me for a few hours, he got it home and it's now stuck with can't detect a flash controller.

We've both tried on a few different pc's and laptops but simply can't get it to see the nand, we've bother resoldered the wires a few times and cleaned up the board etc and still no go.

does anyone have any suggestions on why this happened?

obviously the jasper was problematic from the get go but why should the nand be no longer detectable?

I've found this thread over on xbox-hacker with people in the same situation shorting the nand to get it recognised again but neither of us really want to do that.

heres 2 pictures of the soldering just to show it's not that as me and iloveme28 have bother done various consoles but jaspers always seem to be a problem.

any help at all to why this could of happened, i think it's a corrupt nand,iloveme28 thinks it's incorrect smc but surely it should still be detectable?

 

[J2G]

why would you flash over a falcon xell and a zephyr xell to a jasper nand is corrupt no two ways about it.

Bad Flash To Nand ? How To Recover ! By big_ted

 

[seanr28]

looking at your pictures the soldering is appauling to say the least. I would start there and use single lengths of cable, most issues are casued by poor quality soldering, try using the underside of the board etc first for reading the nand

 

[ando2k9]

looking at your pictures the soldering is appauling to say the least. I would start there and use single lengths of cable, most issues are casued by poor quality soldering, try using the underside of the board etc first for reading the nand

nothing wrong with the soldering at all

been over it so many times i've seen a lot worse than my soldering, the soldering isn't the issue as i said above

 

[seanr28]

you have joined sections of cable to various other cables and have probably introduced high resistance to some of them, check with a multimeter,

All in all now though it does sound lilke the wrong SMC, i did have similar problems with a jasper, i was using the alternative points

 

[ando2k9]

you have joined sections of cable to various other cables and have probably introduced high resistance to some of them, check with a multimeter,

All in all now though it does sound lilke the wrong SMC, i did have similar problems with a jasper, i was using the alternative points

you mean the original nand-x wire to kynar?

find it so much easier to solder kynar to the board

thats the way i've always done it never ran into a problem like this

 

[J2G]

you mean the original nand-x wire to kynar?

find it so much easier to solder kynar to the board

thats the way i've always done it never ran into a problem like this

You have being messing to much with writing to the nand ando2k9 and not even the right Xell for that matter so in the process you ended up with a corrupt nand its not rocket science its very easy to corrupt a nand bro i have seen it umpteen times before.
The hard part is trying to get it back now as it can be tricky.

 

[M AzeeM K]

I have been seeing much of these Jaspers which don't even turn on once XeLL is written to them.

In this case there are 2 options:

1. Write XeLL, then update it to XeLLous. The Xbox360 should turn on now.
2. Instead of writing XeLL, write XBR. Then turn on the Xbox360 by using the Eject button and you should be in XeLL.

Anyways, in your case, the error you are having is due to the wrong SMC. Use the link given by Johnny2good and follow the tutorial. Erase the NAND, then put back the original NAND image. When everything is back to normal, start from the beginning of the process.

 

[Martin C]

Holy mother of crap - what's with the soldering???

All that exposed wire - it won't take much for it to touch something and short out. Seriously, improve your soldering skills or stop d**king around with electronics. You're gonna damage something/someone eventually.

 

[Martin C]

I thought this thread deserved a proper reply.

The console in question has now been repaired (by me) and is winging it's way back to its owner.

I'll start with the easy stuff first : the reason you couldn't boot it after flashing Xell is probably down to the smc used. Coolshrimp's jtag tool has the same smc Xell file for jasper, falcon and zephyr consoles, which I believe to be the fault. I therefore flashed XBR 8955 jasper16_3a to it and injected the keyvault. This worked first time. I was then able to get the CPU key, build the freeboot image and write it back. It's now working fine.

However (and this is where my previous post comes into play), I had to repair the board before I could even start.

You had managed to break three traces in the process of trying to solder (as an attempt is all it's worthy of describing it). One was where the x NAND wires go (couldn't detect flash controller), one was pin 2 where the diode/transistor goes (preventing the system from booting) and the aud_clamp pad had been lifted completely. Not to mention you managed to blow the ring of light board, probably by shorting something with your less than adequate soldering. Unless you get some serious hours in to practice soldering (as well as a half-decent iron, solder and other tools needed to do the job right), you will continue to cause unnecessary damage. I hope others will read this and consider against coming to you until your skills improve.

 

[BGAMods]

nice one martin.

 

[BGAMods]

nothing wrong with the soldering at all

been over it so many times i've seen a lot worse than my soldering, the soldering isn't the issue as i said above

obviously you rate your soldering skills too high.

 

[ando2k9]

no offence mate but iloveme28 has told me the story of what happened and he himself has even said the ROL was working fine as for my soldering

yes it mightent be the best but all the jtags in the past have always worked the way i was doing it, iloveme28 is using the same kit i was using (as it's his own kit) he's done a few more jtags this week with it and not had a problem

all in all i'm glad its sorted yes but pointing the finger at me is wrong, if traces were broke the only thing i can think of is from me removing the nand x kit off the board as the soldering iron i use is a 15w iron and to burn/break traces with that would take some time

 

[modmonster]

As my little lad would say, maybe it was Mr Nobody that did it.

 

[ando2k9]

As my little lad would say, maybe it was Mr Nobody that did it.

it could of well been

 

[Martin C]

no offence mate but iloveme28 has told me the story of what happened and he himself has even said the ROL was working fine as for my soldering

yes it mightent be the best but all the jtags in the past have always worked the way i was doing it, iloveme28 is using the same kit i was using (as it's his own kit) he's done a few more jtags this week with it and not had a problem

all in all i'm glad its sorted yes but pointing the finger at me is wrong, if traces were broke the only thing i can think of is from me removing the nand x kit off the board as the soldering iron i use is a 15w iron and to burn/break traces with that would take some time

Read my post again and then look at your original post.

The reason you went from being able to flash it to 'could not detect a flash controller' is because you broke a trace during your messing with it.

Was the console booting before you got it? Yes, because you said as such in your post. Therefore you also broke the trace on J2D2.1.

It wasn't through removing anything, since you experienced these symptoms DURING your work.

Lastly, just looking at your soldering tells me right away it's not good enough. Just be grateful in this instance that your arse was saved by someone else. Next time you might not be so lucky.

 

[BGAMods]

arguing with the guy that sorted your mess wont get you anywhere. believe me, if martin says your soldering was poor then it was poor, he knows what hes talking about.

 

[Martin C]

Once iloveme28 has tested it as working ok (he'll need to replace the RoL board for that but he knows that already), you're welcome to go over and open it. Carefully peel back the insulating tape on the bottom of the board and you can see what proper soldering looks like.

If you're having problems with Jaspers, where are you flashing XeLL from?