Post by: raburton on December 30, 2009, 02:40:00 PM
If degraded reports a bad block that isn't remapped it probably means that it was as a result of a bad read, this does need to be corrected. Also you can have bad reads that degraded doesn't report, so don't assume that a nand read is good just because degraded doesn't show any errors.
The best test is 2 fold
- compare your reads to make sure they match, if they don;t you can use nand compare to build a good image (by pulling blocks from 3 nand read where at least 2 of them match - if it's a simple read error you are unlikely to get 2 matching bad reads, so 2 matching blocks probably means they are good)
- put this image into 360 flash tool and degraded to make sure they don't complain (note what I said first about bad blocks moved to the end being ok)
Your cable is probably fine, mine is but I rarely get cleans reads. Most likely, I think, due to timing issues from the PC/LPT port doing the read.
Post by: dennisv9 on December 31, 2009, 02:43:00 AM
but if i open the nand dump in flashtool i off course get bad key, bad keyvault etc. etc. since i haven't got the cpu key. for that i need to flash xell. so i want to be sure that my nand is good, because i do want to have a good nand dump to at least extract the keyvault etc. and have the opportunity to put the original nand back.
can flash tool give me some usefull information besides telling me which cb etc. i have? that it also does with a bad dump...
i assume i have to remap the bad sector in the xbr.bin image to match the location of my dump...?
Post by: raburton on December 31, 2009, 03:40:00 AM
QUOTE(dennisv9 @ Dec 31 2009, 11:43 AM) 
i assume i have to remap the bad sector in the xbr.bin image to match the location of my dump...?
Yes, use the remapper tool on your new nand image, so that it correctly avoids the defective blocks of your chip.
Post by: dennisv9 on December 31, 2009, 02:18:00 PM
it was an old rrod box that was repaired. perhaps it once again failed, can't think of something else if it even doesn't work with the original nand dump.
will heatgun it in a couple of days, i'll see then.
Post by: raburton on December 31, 2009, 02:56:00 PM
Post by: dennisv9 on January 01, 2010, 11:03:00 AM
QUOTE(raburton @ Dec 31 2009, 10:56 PM)
xbreboot has xell built in so no need to install xell separately first (though you need either a wired controller or a infrared media remote to access it).
mmmm.... it is activated with the back usb port by pressing which button (i have a wired usb controller)... which one is it???
also, do the diodes need to be soldered directly to the mainboard, can they also be soldered in between 2 wires? i messed up the DB1f1 point... (well, not messed op, but scrapped it of too much so that if i solder on it, it makes contact with the ground plate. i had to use the alternative lower point on which i soldered the diode in between two parts of wire)
the one going to the rf board (i also used the alternative on the bottom of the mainboard) is soldered directly on it.
i also soldered a 330 Ohm resistor between J2D2.4 and J2D2.7, didn't work either.
i can't get xbr to boot ,so my jtag wires are not working somehow.
can someone confirm that the diodes not necessarily need to be soldered to the mainboard directly
i also did a xenon board, on which the diodes are inbetween a wire. so they are also not soldered directly to the board. that setup works for the xenon, no need to solder the diodes directly on the mainboard (also no need to use the above mentioned 330 ohm resistor)
Post by: raburton on January 01, 2010, 12:50:00 PM
QUOTE(dennisv9 @ Jan 1 2010, 08:03 PM)
mmmm.... it is activated with the back usb port by pressing which button (i have a wired usb controller)... which one is it???
I think it's the round button in the middle of the remote, just turn on the box using that button and it should boot into xell. On a media remote it's the windows key.