RGH Jasper BB 256 w/ dvd drive issue...

[Martin C]

Kernel version shouldn't matter.

If you've also tried the one built with the OSIG set to Samsung, then there's either something REALLY wrong or just something obvious being missed. I've never heard of a phat console having so many problems.

Flash the stock NAND back and try the Samsung (remembering not to spoof) with a non AP2.5 game.

 

[grpracing]

ok to be clear, loading the target fw in jf and manually spoofing the dvd key into it is the wrong way to apply the key? just want to make sure that the issue isnt in the way im applying the dvd key to the fw.

 

[x360ccm]

all you have to do is load the fw i sent into source,it should auto load the right sammy fw.

then write to drive.

 

[grpracing]

ok. ill try it after work. gotta head back.

Thank you all for all the help with this issue. hopefully something will drop in correctly soon and cure this issue.

 

[grpracing]

Still no good. did just as you said and still the same. only when i reloaded my original nand back in I once again saw the bad blocks message. Ive never had that till today. ive been booting xell and letting it flash from there.

dgenx had me try a 14699 nand which booted but was the first time i have seen bad blocks message while flashing the nand. I used jf again on the drive and did not spoof it. just let it do its thing.

Im not gonna go buy a lite-on drive for this machine if it is supposed to be able to take any drive after the RGH. There is some kind of problem with a setting or something so I guess im gonna keep looking thru the logs for something strange.

Ive epromed car ecu's , been building my own circuits for 20 years for projects. I am not gonna let a game console beat me. If M$ wasnt involved with this thing i know the task would have been done. Anyone that has ever loaded a copy of xp or any of the others onto a computer knows what i mean. one install goes fine.... another takes years to get it to work right.

 

[x360ccm]

have you got teamviewer

nand i sent had no bad blocks this end.

 

[RavenPhoenix]

If you got bad blocks then I don't think putting an original LiteOn in there will fix the problem. At least now we've got something to work with. Can I get you to redump the nand with the nand-x to find out exactly where the bad blocks are and then we can try to remap them manually?

 

[grpracing]

No, but would be a pain anyway cause i build the nand on the laptop and flash the drives on the desktop. What you thinking?

---------- Post added at 18:39 ---------- Previous post was at 18:36 ----------

raven the reply above was to dgenx. lol not you. Ill dump the nand and up right now.

 

[RavenPhoenix]

No, but would be a pain anyway cause i build the nand on the laptop and flash the drives on the desktop. What you thinking?

---------- Post added at 18:39 ---------- Previous post was at 18:36 ----------

raven the reply above was to dgenx. lol not you. Ill dump the nand and up right now.

Great, please ensure that you copy/paste the bad block locations exactly as nandpro shows them into a text file. That way we can be sure that there are no typo's and the locations are all correct for the remapping.

Cheers.

 

[grpracing]

Great, please ensure that you copy/paste the bad block locations exactly as nandpro shows them into a text file. That way we can be sure that there are no typo's and the locations are all correct for the remapping.

Cheers.

It will take me a few cause i do 4 reads and wasnt thinking when i pasted my commands to cut it down to 2 reads for the compare. Will nandpro show bad blocks as it reads or at the end of the reading? its on the second nand read with no bad blocks reported in the nand1 read.

 

[RavenPhoenix]

Nandpro will show bad blocks as it reads the NAND so for example you will see nandpro reading through the blocks and as soon as it has a problem reading any block it will give an error similar to the following e.g.:

Error: 250 reading block 1C2

Just copy/paste the contents of the error and block location so we can know where they are.

 

[grpracing]

Nandpro will show bad blocks as it reads the NAND so for example you will see nandpro reading through the blocks and as soon as it has a problem reading any block it will give an error similar to the following e.g.:

Error: 250 reading block 1C2

Just copy/paste the contents of the error and block location so we can know where they are.

OK, well no bad blocks and the compare goes just fine as well. could it be xell isnt writing the nand correctly or completely? this just started today. the nand has been written to this jasper allot over the past 2 weeks.

 

[RavenPhoenix]

So you didn't get any bad blocks at all???

Did you dump 64MB or the full 256MB?

 

[grpracing]

So you didn't get any bad blocks at all???

Did you dump 64MB or the full 256MB?

64 cause thats how all the nands have been built from.

 

[RavenPhoenix]

Ok, so we are back at square one..........doh!

I can't think of what may be the problem but have you tried using a donor nand image? Maybe we could try a donor image then write the OFW with the donor DVD key spoofed to the drive and see if that will at least get the drive to play an original disc.

This issue has really got me scratching my head but it is a really good challenge.

 

[x360ccm]

i ask you for teamviewer so i could flash your drive for you.

i think it user error tbh now

 

[Martin C]

I would use nandpro to write the image TBH. I've had rawflash throw the odd curveball.

If a block is genuinely bad you'll see error 202 when writing to it.

When reading, Error 240 is a block marked as bad (but may still have data in there).

Either reading/writing, Error 250 is an empty block.