Announcement

**Maalobs** · 05-02-2019, 04:43 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

As I wrote in an earlier post; this Chinese seller on Ebay replied to me in a direct message that he also sells the Fusion P120 processors:
https://www.ebay.com/itm/Direct-heat...e/273459017141
Why don't you contact him and attach a photo of your specific processor?
He was very helpful in my contacts with him.
My reflow guy suggested to ask the seller if he can ship the processor "pre-balled", he assumed it would be because that's how he always receives BGA-chips himself from Chinese vendors.

Here's a seller in Poland, but it looks like you need a stencil to apply the solder paste yourself:
https://www.ebay.com/itm/FNP102C31-C...1/292955881093

Also, look for PlayStation/XBox repair shops near you, they might have bigger hot air stations and be more experienced in hand-reflowing BGAs because of the heat problems and big chips in the consoles.
That's how I got mine to work on the first try, by not using my own dinky 858D and also letting a professional do the work.

**Maalobs** · 05-02-2019, 04:52 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

I remembered that I had a dusty old firewall device from a dozen years ago stowed away on a shelf, and this particular firewall always ran pretty hot.
I opened it up to see what's in it, and it turns out it had a couple of 54.6mm passive heatsinks with a pretty high profile, complete with the PCB mountings:

That's great, now I have the cooling issue sorted.

**Davi.p** · 05-03-2019, 09:24 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Why don't you contact him and attach a photo of your specific processor?

I have already told why.. For the Console shop i say that i repair for money and resell the TVs, i cant demand big works to others...

**Davi.p** · 05-04-2019, 06:56 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Call me crazy but i think my next step could be a home made reballing, the first difficult part is to measure the original balls, i guess a caliper can't do it right but i'm not sure, then i can not use any stancil and place all balls by my hands..

**Diah** · 05-05-2019, 02:38 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Originally posted by Davi.p View Post

Call me crazy but i think my next step could be a home made reballing, the first difficult part is to measure the original balls, i guess a caliper can't do it right but i'm not sure, then i can not use any stancil and place all balls by my hands..

why not.. for more easy way if you place all balls first under loop on the PCB

**Davi.p** · 05-05-2019, 06:12 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

why not.. for more easy way if you place all balls first under loop on the PCB

my English is bad, but i feel that i have a good company..

**Maalobs** · 05-14-2019, 07:15 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

XGecu released a new version of the software today, and it turns out that they did not add support for the 8 Gbit Micron NANDs as they had suggested that they would, when I emailed them back in April.
I was expecting this outcome so last week I ordered an Ifix RT809H which arrived yesterday, so now I can in fact read the MT29F8G08ABABA chip.

The RT809H is a very different beast in comparison to the simpler TL866II.
A very advanced tool indeed, but sadly the level of Chinglish in the GUI, the documentation, and the manufacturer's forum, is on a higher plane of existence.

Luckily there seems to be a series of instructional Youtube videos from the manufacturer, so maybe the correct usage workflow for complex scenarios can be attained that way.

I guess there are some RT809H owners here already, can anyone please tell me:
1. When do I need to use the 9-12VDC DC-plug to power the device?
2. When used, how many Amperes does the DC power-adapter need to provide?
This basic information is not explained in the "English" version of the instruction, it only states the accepted voltage range and that the plug is center-positive.

Anyway, I noticed that to read the NAND-chip it was sufficient to power the device from the USB-connection to the computer.

I did a series of reads of the chip to different dump-files, with the auto-verification enabled in the software (on by default) and by using the official Ifix TSOP48-adapter.
I noticed that I got a different number of verification errors in each of the reads:
Read 1: 64 errors
Read 2: 53 errors
Read 3: 45 errors
Read 4: 58 errors
Read 5: 51 errors
Read 6: 49 errors

I did a series of comparisons of the reads like this:

Code:

cmp -l read1.bin read2.bin > 1_2.txt
cmp -l read1.bin read3.bin > 1_3.txt
cmp -l read1.bin read4.bin > 1_4.txt
cmp -l read1.bin read5.bin > 1_5.txt
cmp -l read1.bin read6.bin > 1_6.txt

The errors are random bytes that from the value difference seem to have a single bit error in each.

I collected all the outputs together and sorted them:

Code:

cat 1_2.txt 1_3.txt 1_4.txt 1_5.txt 1_6.txt | sort > total.txt

When I inspected the total.txt file, I realised that there were two different errors happening.
First, there were several errors that were unique, where the byte offset only appeared once in one of the read-files.
Second, the same byte offsets would appear in more than one of the read-files (but not always in all of the read-files), and whenever they did, the value difference against the first read-file was always identical.

The number of errors at unique offsets were:

Code:

uniq total.txt | wc -l
129

The number of errors at duplicate offsets were:

Code:

uniq -d total.txt | wc -l
81

The basic operation of loading a chip type and reading the content to a file was documented in the instruction manual so assuming that I am not causing problems by user error, I wondered how I would possibly write something correct to a new NAND-chip out of these dump-files.
But then I realized that the data content of the NAND memory is in fact the filesystems of the Linux partitions, so the filesystems have probably marked some bad blocks on the disk already where there is a permanent error, and the random errors are apparently handled as well since the TV booted successfully after I had the BGA reflow done.

It looks like this chip is on the last leg though, and I already ordered a couple of MT29F8G08ABABA chips from Aliexpress a couple of weeks ago just in case, so right now I'm still waiting for them to be delivered so that I can get years more of reliable use out of this TV.

**Maalobs** · 05-23-2019, 02:26 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

I finally got the "new" chips in my hand today.

They are obviously used and have been desoldered from some other device:

On the first chip:
I dumped the existing contents and verified the dump against the memory contents, they were identical.
I erased the memory and wrote in my "read 3" dump from earlier and verified the dump against the new memory, and they were once again identical.
Looks good.

On the second chip:
I dumped the existing contents and verified the dump against the memory contents, they were identical.
I erased the memory and wrote in my "read 3" dump from earlier and verified the dump against the new memory, and there was 1 bit error.
I read that memory back into a new dump, now it had 2 bit errors compared against the original "read 3" dump!
I wrote in the "read 3" dump into the memory again, read it out to yet another dump, now that dump was identical against the original "read 3" dump.

So the second chip seems to be glitchy already.

At least these are in a far better shape than the original chip.

Next up, dumping both the SPI Flash and the I2C EEPROM as well.
Would be interesting to try that with ICSP actually, since they both have connectors or at least pads for connectors.
I have been studying the instruction videos from iFix while I waited for the chips to arrive.

**Davi.p** · 05-23-2019, 05:12 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Copying nand chips it's a complicate job since every chip borns with various bad blocks, different from each other, so before writing a dump maybe it's mandatory to update the bad block table inside the dump..

**diif** · 05-23-2019, 05:35 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Originally posted by Davi.p View Post

Copying nand chips it's a complicate job since every chip borns with various bad blocks, different from each other, so before writing a dump maybe it's mandatory to update the bad block table inside the dump..

The RT809H and GQ-5X both map bad blocks and program around them automatically. Not complicated at all.

The 9v-12v DC socket isn't used Maalobs

**Davi.p** · 05-24-2019, 03:49 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

This was explained to me by an ebay chip seller..

**diif** · 05-24-2019, 04:06 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Originally posted by Davi.p View Post

This was explained to me by an ebay chip seller..

I'm speaking from first hand experience. Perhaps they were trying to justify their price or put you off from buying your own programmer.

**Davi.p** · 05-24-2019, 10:48 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Today i've downloaded RT809H & F new software, there's a specific procedure to program those NANDs, i followed a YT video but it's in Spanish, maybe have to press first "Verify bad block", then "Settings", then "Skip BB and realign data" or "Skip BB and rebulit BBT", then write the NAND, right?

**Maalobs** · 05-24-2019, 11:28 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Great, I've already soldered a new chip back onto the board.
Those things that you mentioned are not explained in the so-called documentation for the RT809H.

Can you post the link to that Youtube-video?

**Maalobs** · 05-25-2019, 11:05 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

The bad block management is apparently covered in one of the instruction videos from iFix, but I hadn't come that far in the videos yet.
I skipped ahead to this video:
https://www.youtube.com/watch?v=9DngDjI0KNU

The datasheet from Micron also had a brief introduction to the concept.

Based on the instruction video, I have done the following:
1. Desolder the new NAND-chip again so I can work on it in the RT809H.
2. Erase the memory of the NAND-chip.
3. Run Bad block detection. (no errors detected)
4. Click Setting (N) and change copy mode to Skip Bad Block and Rebuild BBT.
5. Write my original "Read 3" dump into the memory again.
6. Read out the memory to a new dump-file.

Have I correctly understood the basic theory of how to use the Bad Block feature in the software?

Here is the log from the iFix software:

Code:

004: The currently selected:MT29F8G08ABABA@TSOP48, capacity: 8640Mbits, 1080Mbytes.
005: Adapter model£ºRT-TSOP48-1, 0.5, 12*18, Pin to Pin
006: http://www.ifix.net.cn/thread-53859-1-2.html
007: Download device programming algorithm......
008: Algo update OK
009: >------------------------------------OK---------------------------------------<
**** Erase begins ****
012: Chip pins contact is detected OK.
013: TotalPageNum: 0x40000,PageNumInBlock: 128,PageSize: 4320
014: Chip ID verification OK.
015: Start erasing chip, please be patient......
016: Erase successful£¬Elapsed time£º1.743 seconds¡£
017: >------------------------------------OK---------------------------------------<
**** Bad block detection begins ****
018: Chip pins contact is detected OK.
019: TotalPageNum: 0x40000,PageNumInBlock: 128,PageSize: 4320
020: Chip ID verification OK.
021: TotalBlockNum: 2048
022: No bad blocks were found.
023: >------------------------------------OK---------------------------------------<
**** Write begins ****
024: Chip pins contact is detected OK.
025: TotalPageNum: 0x40000,PageNumInBlock: 128,PageSize: 4320
026: Chip ID verification OK.
027: Start writing chip......
028: Auto erasing...
029: Erase successful£¬Elapsed time£º1.18 seconds¡£
030: Start writing...
031: Algorithm equal to : Skip Bad Block and Rebuild BBT
032: Write and verify success.
033: Elapsed time: 687.9 seconds£¬average speed of 3292447 bytes/sec.
034: >------------------------------------OK---------------------------------------<
**** Read begins ****
035: Chip pins contact is detected OK.
036: TotalPageNum: 0x40000,PageNumInBlock: 128,PageSize: 4320
037: Chip ID verification OK.
038: F:\Philips\readbbt.bin
039: Start reading chip......
040: Buffer data checksum: 16bits_0xDD76 £¬32bits_0x8198DD76 :
041: Read successful£¬Elapsed time£º536.3 seconds¡£
042: Auto verifying...
043: All bytes verification is consistent.
044: Verification successful£¬Elapsed time£º536.3 seconds¡£
045: Elapsed time: 1073 seconds£¬average speed of 2111703 bytes/sec.
046: >------------------------------------OK---------------------------------------<

I then ran a comparison between the "Read 3" dumpfile and the new dumpfile:

Code:

cmp -l read3.bin readbbt.bin > 3_BBT.txt

Here is how the output of the cmp command works; on each row, the first column is the offset in decimal in the files at which a difference was detected.
The second column is the value in octal in the first file at that offset.
The third column is the value in octal in the second file at that same offset.

This is the output of the cmp command:

Code:

1131360260 61 377
1131360261 164 377
1131360262 142 377
1131360263 102 377
1131360264  1 377
1131360369 137 377
1131360370 251 377
1131360371 344 377
1131360372 264 377
1131360373 140 377
1131360374 163 377
1131360375 247 377
1131360376 52 377
1131360377 354 377
1131360378 207 377
1131360379 311 377
1131360380 32 377
1131360381 246 377
1131360382 141 377
1131360383 137 377
1131360384 251 377
1131360385 344 377
1131360386 264 377
1131360387 140 377
1131360388 163 377
1131360389 247 377
1131360390 52 377
1131360391 354 377
1131360392 207 377
1131360393 311 377
1131360394 32 377
1131360395 246 377
1131360396 141 377
1131360397 137 377
1131360398 251 377
1131360399 344 377
1131360400 264 377
1131360401 140 377
1131360402 163 377
1131360403 247 377
1131360404 52 377
1131360405 354 377
1131360406 207 377
1131360407 311 377
1131360408 32 377
1131360409 246 377
1131360410 141 377
1131360411 137 377
1131360412 251 377
1131360413 344 377
1131360414 264 377
1131360415 140 377
1131360416 163 377
1131360417 247 377
1131360418 52 377
1131360419 354 377
1131360420 207 377
1131360421 311 377
1131360422 32 377
1131360423 246 377
1131360424 141 377
1131360425 137 377
1131360426 251 377
1131360427 344 377
1131360428 264 377
1131360429 140 377
1131360430 163 377
1131360431 247 377
1131360432 52 377
1131360433 354 377
1131360434 207 377
1131360435 311 377
1131360436 32 377
1131360437 246 377
1131360438 141 377
1131360439 137 377
1131360440 251 377
1131360441 344 377
1131360442 264 377
1131360443 140 377
1131360444 163 377
1131360445 247 377
1131360446 52 377
1131360447 354 377
1131360448 207 377
1131360449 311 377
1131360450 32 377
1131360451 246 377
1131360452 141 377
1131360453 137 377
1131360454 251 377
1131360455 344 377
1131360456 264 377
1131360457 140 377
1131360458 163 377
1131360459 247 377
1131360460 52 377
1131360461 354 377
1131360462 207 377
1131360463 311 377
1131360464 32 377
1131360465 246 377
1131360466 141 377
1131360467 137 377
1131360468 251 377
1131360469 344 377
1131360470 264 377
1131360471 140 377
1131360472 163 377
1131360473 247 377
1131360474 52 377
1131360475 354 377
1131360476 207 377
1131360477 311 377
1131360478 32 377
1131360479 246 377
1131360480 141 377
1131913220 102 377
1131913221 142 377
1131913222 164 377
1131913223 60 377
1131913224  1 377
1131913329 137 377
1131913330 251 377
1131913331 344 377
1131913332 264 377
1131913333 140 377
1131913334 163 377
1131913335 247 377
1131913336 52 377
1131913337 354 377
1131913338 207 377
1131913339 311 377
1131913340 32 377
1131913341 246 377
1131913342 141 377
1131913343 137 377
1131913344 251 377
1131913345 344 377
1131913346 264 377
1131913347 140 377
1131913348 163 377
1131913349 247 377
1131913350 52 377
1131913351 354 377
1131913352 207 377
1131913353 311 377
1131913354 32 377
1131913355 246 377
1131913356 141 377
1131913357 137 377
1131913358 251 377
1131913359 344 377
1131913360 264 377
1131913361 140 377
1131913362 163 377
1131913363 247 377
1131913364 52 377
1131913365 354 377
1131913366 207 377
1131913367 311 377
1131913368 32 377
1131913369 246 377
1131913370 141 377
1131913371 137 377
1131913372 251 377
1131913373 344 377
1131913374 264 377
1131913375 140 377
1131913376 163 377
1131913377 247 377
1131913378 52 377
1131913379 354 377
1131913380 207 377
1131913381 311 377
1131913382 32 377
1131913383 246 377
1131913384 141 377
1131913385 137 377
1131913386 251 377
1131913387 344 377
1131913388 264 377
1131913389 140 377
1131913390 163 377
1131913391 247 377
1131913392 52 377
1131913393 354 377
1131913394 207 377
1131913395 311 377
1131913396 32 377
1131913397 246 377
1131913398 141 377
1131913399 137 377
1131913400 251 377
1131913401 344 377
1131913402 264 377
1131913403 140 377
1131913404 163 377
1131913405 247 377
1131913406 52 377
1131913407 354 377
1131913408 207 377
1131913409 311 377
1131913410 32 377
1131913411 246 377
1131913412 141 377
1131913413 137 377
1131913414 251 377
1131913415 344 377
1131913416 264 377
1131913417 140 377
1131913418 163 377
1131913419 247 377
1131913420 52 377
1131913421 354 377
1131913422 207 377
1131913423 311 377
1131913424 32 377
1131913425 246 377
1131913426 141 377
1131913427 137 377
1131913428 251 377
1131913429 344 377
1131913430 264 377
1131913431 140 377
1131913432 163 377
1131913433 247 377
1131913434 52 377
1131913435 354 377
1131913436 207 377
1131913437 311 377
1131913438 32 377
1131913439 246 377
1131913440 141 377

Looking at the output, what stands out is that there are two ranges of almost linear offsets, and that on every single line, the new value is 0377, which is the same as 0xFF.

The difference is more clearly visualised here in WinMerge, a graphical diff tool in which I am comparing the "Read 3" dumpfile on the left and the new dumpfile on the right:

And here again at the second range:

I wonder if that is perhaps the result of the Bad Block Table from the old and worn chip now having been cleared, when the dump was written into the new chip?

**Davi.p** · 05-25-2019, 04:53 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

I think you have understood the method, but the first erase is unuseful 'cause is done by the writing process..

**Davi.p** · 05-26-2019, 01:35 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Hi Maalobs, can i ask you a pleasure? Can you ask to your repairer which is the size of the balls he used? So i can put hands on the board only one time... I have too many TVs to fix, it's a problem here! Bye!

**Maalobs** · 05-26-2019, 09:12 PM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

He did not do a "reball" or "reflow" with a stencil, all he did was to re-heat the BGA chip with a powerful hot air station, and then when the chip was "dancing" on the molten balls, he gently tapped a corner of the chip to make it break surface tension on any balls that were not in contact with the upper or lower pad.
I don't know what it's called so I just referred to it as "reflow", sorry for the confusion.

This is more art than science I guess, he explained how he had become quite proficient in this method on PS4 repairs over the years.

So I have no answer to your question, sorry.

**diif** · 05-27-2019, 02:18 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

You're correct Maalobs, the procedure your guy did was a reflow.

Davi.P The ball sizes are usually indicated on the stencil.

**Davi.p** · 05-27-2019, 03:23 AM

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Which stencil?? I have no stencil obviously.. I will not use it..
My reflow worsen the situation so i go for reballing and if does not work maybe a new chip ordered..

Announcement

Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment