Eeprom dump thread!
Collapse
This is a sticky topic.
X
X
-
Re: Eeprom dump thread!
Connected to FlashcatUSB Mach, firmware version: 2.29
Voltage set to: 3.3V
Detecting connected Flash device...
Initializing Parallel NAND device mode
I/O mode successfully initialized
Attempting to automatically detect Flash device
NAND clock speed set to: 20MHz
Mode NAND X8 ASYNC returned ident code: 0xECD5847250
Successfully detected device in NAND mode
Connected to Flash (CHIP ID: 0xECD5847250)
NAND device failed to load ONFI table
Flash detected: Samsung K9GAG08U0E (2,176,843,776 bytes)
Programming mode: Parallel I/O
Page Information: 128 total pages; 8,192 bytes per page; 436 bytes extended size
Block Information: 2,076 total blocks; 1,104,384 bytes per block
Device interface: NAND (X8 3.3V)
Loading NAND memory map for valid memory
Total bad blocks: 1467
NAND memory map complete: 77,952 pages available for access
Flash device successfully detected and ready for operation
Sent memory erase command to device: Samsung K9GAG08U0E
Successfully erased NAND Flash device
What should I do? I didn't find any log files in the program files / FlashCat folder.Comment
-
Re: Eeprom dump thread!
Here is an approximate programmer log for bad blocks, indicating at which addresses they are located:
Request for bad blocks...Normal
Number of bad blocks: 6
Block 0x000D (13) address 0x00D00000 (0x00DB1200) Bad block
Block 0x057B (1403) address 0x57B00000 (0x5C5ABE00) Bad block
Block 0x058E (1422) address 0x58E00000 (0x5D9AEC00) Bad block
Block 0x0645 (1605) address 0x64500000 (0x69A6C200) Bad block
Block 0x06BE (1726) address 0x6BE00000 (0x719DCC00) Bad block
Block 0x0819 (2073) address 0x81900000 (0x88754A00) Bad blockComment
-
Re: Eeprom dump thread!
Erased 3 times in a row. This is my full log what FlashCat software produces:
Welcome to the FlashcatUSB interfacing software, build: 645
Copyright 2023 - Embedded Computers LLC
Running on: Windows (64 bit)
FlashcatUSB Script Engine build: 312
Serial NOR memory database loaded: 502 devices supported
Serial NAND database loaded: 67 devices supported
Parallel NOR memory database loaded: 405 devices supported
Parallel NAND memory database loaded: 273 devices supported
Connected to FlashcatUSB Mach?, firmware version: 2.29
OTP/UV EPROM memory database loaded: 46 devices supported
Voltage set to: 3.3V
Detecting connected Flash device...
Initializing Parallel NAND device mode
I/O mode successfully initialized
Attempting to automatically detect Flash device
NAND clock speed set to: 20MHz
Mode NAND X8 ASYNC returned ident code: 0xECD5847250
Successfully detected device in NAND mode
Connected to Flash (CHIP ID: 0xECD5847250)
NAND device failed to load ONFI table
Flash detected: Samsung K9GAG08U0E (2,176,843,776 bytes)
Programming mode: Parallel I/O
Page Information: 128 total pages; 8,192 bytes per page; 436 bytes extended size
Block Information: 2,076 total blocks; 1,104,384 bytes per block
Device interface: NAND (X8 3.3V)
Loading NAND memory map for valid memory
Total bad blocks: 1455
NAND memory map complete: 79,488 pages available for access
Flash device successfully detected and ready for operation
About the full chip erase it doesn't provide detailed information, only 2 lines:
Sent memory erase command to device: Samsung K9GAG08U0E
Successfully erased NAND Flash device
I'll try to find where it logs the BBs list. Or is it not worth that because is it a highly damaged NAND beyond 'point of no return' ?Comment
-
Re: Eeprom dump thread!
2-13, 137, 215-377, 471-497, 499-510, 512, 514-518, 520-522, 524-532, 534-535, 537-561, 563-568, 570-584, 586-619, 621-626, 628-632,
634-640, 642-699, 701-753, 755-768, 770-790, 792, 794-835, 837-847, 849, 851-896, 898-916, 918-959, 961-1024, 1026-1051, 1053-1106,
1108-1140, 1142-1152, 1154-1195, 1197-1206, 1208, 1210, 1212-1221, 1223-1271, 1273-1280, 1282-1291, 1293-1408, 1410-1428,
1430-1487, 1489-1515, 1517-1521, 1523-1530, 1532, 1534-1536, 1538-1650, 1652-1664, 1666-1787, 1943, 2033-2040, 2043, 2074.Last edited by img1; 09-16-2023, 03:40 AM.Comment
-
Re: Eeprom dump thread!
But there cannot be so many physical Bad Blocks, it can be the remains of a dump and in it these BBs or the programmer considers them as ECC.
Try to thoroughly clean all the legs of the Nand Flash from flux, rinse it in isopropyl alcohol and acetone, here you need good contact between the legs and the adapter itself.Last edited by lotas; 09-16-2023, 05:15 AM.Comment
-
Re: Eeprom dump thread!
But there cannot be so many physical Bad Blocks, it can be the remains of a dump and in it these BBs or the programmer considers them as ECC.
Try to thoroughly clean all the legs of the Nand Flash from flux, rinse it in isopropyl alcohol and acetone, here you need good contact between the legs and the adapter itself.
Something I don't understand: when the software recognising the NAND the message is "loading NAND memory map for valid memory, total bad blocks: 1455". And when I fiddled with the "Analyze" button in the "NAND memory map" menu, a window popped up with "Warning, this operation will erase and overwrite all blocks, continue?". Yes, of course and the process finished less than a second and then the displayed green-black blocks changed to yellow with a question mark in them, and the title says "NAND blocks analyzed (0 bad blocks found). But if I redetect (reinitialize) the NAND, the number of the BBs remains 1455.
Comment
-
Re: Eeprom dump thread!
Yes, it’s strange here either the nand flash is completely dead (try to find exactly the same used or new one) or the programmer does not understand the algorithm of this nand, I have never had more than 10 physical BBs in this NAND.Comment
-
Re: Eeprom dump thread!
137, 657, 1943, 2033, 2039, 2040, 2074.Comment
-
Re: Eeprom dump thread!
Edit: As I found I can manually discard blocks as bad blocks, so I discarded the 2073.
Edit 2: It is just temporary so not written onto the BB table. After I redetected the NAND the manually disabled block disappeared. Or maybe I did something wrong.Last edited by img1; 09-16-2023, 09:30 AM.Comment
-
Re: Eeprom dump thread!
Hi Lotas, I have this Roku 43" TV that the standby light is on but do not respond to power ON, I replace the CPU with a good one from a similar good board of a 32", problem was the same then I put the NAND from the 32" and the 43" turn ON, backlight turn ON, respond to remote control but no picture, then I read the original NAND and programmed on the new NAND, now the TV have stand by light and does not turn ON, I suspect those Roku TVs are reading the CPU serial number so they do not work with a new CPU, here are the 2 files:
https://drive.google.com/file/d/1yvU...usp=drive_link
https://drive.google.com/file/d/1T8m...usp=drive_linkComment
-
Re: Eeprom dump thread!
Hi Lotas, I have this Roku 43" TV that the standby light is on but do not respond to power ON, I replace the CPU with a good one from a similar good board of a 32", problem was the same then I put the NAND from the 32" and the 43" turn ON, backlight turn ON, respond to remote control but no picture, then I read the original NAND and programmed on the new NAND, now the TV have stand by light and does not turn ON, I suspect those Roku TVs are reading the CPU serial number so they do not work with a new CPU, here are the 2 files:
https://drive.google.com/file/d/1yvU...usp=drive_link
https://drive.google.com/file/d/1T8m...usp=drive_link
Software/firmware is 1st step then hardware.Comment
-
Comment
-
Re: Eeprom dump thread!
If it does not go into operating mode, then most likely your firmware is damaged, you read the contents (dump) of your 25Q16BSIG and show it to me, I will restore it and it will be operational and then you will download my corrected dump and your TV will work again, when provided that the problem is in the firmware.Last edited by lotas; 09-22-2023, 02:46 PM.Comment
Related Topics
Collapse
-
by (0)_(0)Hello, This might be a long shot, but I'm looking for an EEPROM dump for a HP Photosmart C4280 All-in-one printer.
The printer seems to be in cartridge alignment mode. Sometimes it print the alignment page and then hangs during the scanning step, sometimes it hangs during the printing process and sometimes it hangs during the boot process. If I let it idle for a while then it flashes the back-light of the top screen and there's a letter E. Bottom screen is asking me to restart it to no avail. I have to remove the power cable from the printer for a couple of minutes to make it work...02-17-2022, 09:09 PM -
by my2k2Good day to every one,
I have AVR 171 the IC1504 (24C32) eeprom is corrupted not able to read.
Does anybody have an eeprom dump file? I really appreciate any help.
Thanks in advance.-
Channel: Troubleshooting Audio Equipment
07-01-2024, 09:04 PM -
-
P14s Gen 2
HT4B0/HP4B0/HT5B1/HT4B2
NM-D352 Rev 1.0
sn PF-35P15W
Requesting thunderbolt dump
also attached is the tbt dump. I extracted the bin from the cap file and modified it, not sure if it's correct. also didnt work....-
Channel: BIOS Requests ONLY!
-
-
by Ancient1Hi
I was working all day on a 42" with no backlight = Driver is bad . LED Tester. Image exists
As I was reassembling, I discovered faults on the screen ( used the LED Tester to power the strips).
Right distribution board, 2 Flexs, near them:
The one near the center has 1" line on screen. Pressing on the board-side or Panel side of the Flex bonding place results in some change, I sensed heating one time, but main fault line remains
The other, pressing on the Panel to the Chassey and the lines disappears 99.99%
I... -
by jimhaHi ,
I'm looking for a dump to repair my screen
Thanks-
Channel: Troubleshooting Computer Displays
12-09-2024, 03:52 PM -
- Loading...
- No more items.
Comment