ERROR 250 Reading Block 3C4?

[roden]

Hi, just installed my 2 nand boards on a falcon motherboard with the old blade dash, read the nand 8 times and i receive this message every time

"ERROR 250 Reading Block 3C4"

I have comapred all 8 dumps and they are identical, does this mean its not reading my nand correctly, or just that it has a bad block?

 

[J2G]

It's a bad block ether remap it or carry on its no big deal..

 

[roden]

So i can just install jtag part and write xell and carry on, ok ill post with progress, only i have a system with a cygnos, and never had any read errors with that, guess i was lucky

 

[J2G]

Just lucky bad blocks can pop depend on the 360 you can remap or carry on its only one.

 

[roden]

Okay well i wrote xell, and i get rrod, i tried all resistor settings, and i get rrod, so i removed xell and wrote the original dump back, so i know its writing ok, i still get rrod, but it boots ok again if i turn the jtag off??

What am i doing wrong?

 

[manwithoutname]

Are you saying you're still getting RROD after writing the original NAND back? Is it just RROD or an actual E error with a number next to it. You need to clarify a bit more what you are doing and what is exactly is happening!!!

Did you disconnect power for 10-30 seconds after writing original NAND before powering console again?

 

[roden]

Ok, here is what is happening...

I click write xell in coolshrimps app, it completes....

When i power the console, i get 3 rings rrod, wether i push power or eject...

Same no matter what resistor setting i use on the jtag selector....

If i disable the jtag board, ie off position, i get 1 red light flashing bottom right.

If i flash back to the dumped nand, it boots if i turn jtag off, butt rrod if i turn jtag on again.

So if i flash my original nand dump back, and disable the jtag board, it boots ok.

What am i doing wrong?

I thought you write xell and power up, and get your cpu key?

 

[roden]

As for error codes, there are none, just a black screen, i just tried it again, removed xell, and turned off jtag, and ther console boots again.

Looks like its a problem with the jtag, or the xell writing?

 

[roden]

CRAP, should have gone cygnos again grrr, i thought this would be easier,

Ok im kinda stuck now, should i be using a certain ohm setting or does it not matter, i just cant understand why i get rrod when i write xell, obviously somthing is going wrong, i do have that bad block, but that would not affect the xell writing correct?.

I even tried the falcon xell image from xbins, still rrod, or e79, hassle man!.

Giving up for today, gonna rest and come back to it, if anybody has a suggestion please let me know.

 

[manwithoutname]

At this point all I could suggest is a) bad soldering joint b) bad block. However seeing that the bad block is towards the end of the NAND memory it is most unlikely the cause of the E79.

I take it you're using ROL & DB1F1 points for the JTAG?

 

[roden]

I take it you're using ROL & DB1F1 points for the JTAG?

Yes i am , i did exactly as was shown, i can say 100% its not bad soldering, trust me, but i will check again. This kind of soldering is a piddle as i did it for 18 years in an electronics job, im certain there is no fault.

Like you i dont think its the bad block, the console has CB 5770, and an early blade dash.

I can flash and read the nand perfectly, when flashing back to the original nand, it boots fine, but the second i write xell, NO GO.

I just dont understand what i am doing wrong, resistor is set a 330ohm, but i have tried everything.

 

[manwithoutname]

Try the alternate points as shown here.

 

[roden]

Ok it looks as if i have no choice, when i have done this i will have to use the audio_clamp & open_tray SMC and ready xell image yes?

I was just wondering, if i supplied my nand image, could somebody create a xell image for me to try, just in case im doing somthing wrong, before i start to resolder stuff

Also i have noticed that when i flash the original nand back, it will only boot if i have the resistor value set to 470, so i left this there, reflashed xell, now i am getting a consistent e79 every time, no more rrod, so i am getting somewhere.

So still the resolder trick, or i hear some tricks can be done for the e79 error but im kinda lost with it?

 

[roden]

Rewired to alternative points as shown...

manwithoutname i took your xell clamp_falcon.bin thingy, and booted the console and volla, i have my cpu key . however i did not have a dvd drive plugged in but i assume that does not matter.

So with both jtag tool, and toolbox maker i have tried making a freeboot image using my cpu key, both e79 on boot, do i have to do somthing to the image becuase of the new wiring?

 

[manwithoutname]

Install Jtag tool 1.74, replaced the SMC folder in there with the one you downloaded from my signature. Create freeboot 9199 dash using your CPU key & original NAND dump and write back to your NAND. If you got that part working let me know and will continue with the update process to 12611 ...

 

[roden]

Ok all, done, bin created, dont have time to flash now as im off out for the day, ill try it later and get back,

Ok all flashed , console now booting to freeBOOT 9199.

Great thanks for your help, all seems simple when you know how, so how do we go to latest?

 

[roden]

Ok, i kinda jumped ahead, i copied the smc that i downloaded from you to the folder for jtag tool 2.20, i then made a 12611 latest freeboot bin from the working 9199 image, and the console boots fine.

Only when i put a game into the dvd drive, "original game" it displays play DVD ???

Did i do somthing wrong?

"IGNORE" i still had the nand-x plugged in, removed it and all fine.

Can you just confirm i did right, as all seems to be running ok, basically the route we followed was just to apply the smc for the updated wiring method?

 

[manwithoutname]

That is one way to do it, the other way we have been doing it is to dump the 9199 live form the console via flash360 tool then use this as a source with Jtag tool 2.12 to create 12611 before flashing it back to the console vla flash360 again. End result has always been successful and stable 12611 dash.

However if this is working fine for you and booting to dash 12611 successfully each time then all ok and good to go.

 

[roden]

Excellent all done, thanks for your help again

 

[roden]

Sorry to be a pain, but one last question, what is my jumper setting supposed to be on, all is working with no problems, but my switch is in the middle and the jumper is on the 470 position i think.

Im just a little confused about this?