PS3 Assistance diagnosing CECHA01 3040 error for frankie candidate

[Patience is a virtue]

I recently acquired a BC CECHA01 model from eBay that has a 3040 error (nand flash) and I am trying to determine if this error was triggered from a RLOD not booting up fully. I'm hoping the flash hasn't been corrupted from someone doing a failed hardware flash or something. I purchased the console knowing it had the RLOD. It doesn't have a YLOD, I've tried booting into recovery or cycling power a few times no dice still immediate RLOD. It has 1001 errors early on, and the most recent errors are 3040. The console has a rather short history of use just looking at the becount. I also need a new clock battery but I think that's ok. Any insight given is greatly appreciated!

Spoiler: ERRLOG

errlog

ofst[120]:err_code:0xffffffff, clock:0x0f488a31 2008/02/15 17:36:49
ofst[124]:err_code:0xa0801004, clock:0x0fc22f39 2008/05/18 00:05:13
ofst[ 0]:err_code:0xa0801004, clock:0x1006716d 2008/07/08 18:41:49
ofst[ 4]:err_code:0xa0801004, clock:0x110f46af 2009/01/25 15:50:07
ofst[ 8]:err_code:0xa0801004, clock:0x113c1df7 2009/02/28 16:08:23
ofst[ 12]:err_code:0xa0801004, clock:0x1141fb68 2009/03/05 02:54:32
ofst[ 16]:err_code:0xa0801001, clock:0x11742e79 2009/04/12 04:45:45
ofst[ 20]:err_code:0xa0801004, clock:0x126515d5 2009/10/11 22:16:53
ofst[ 24]:err_code:0xa0801004, clock:0x1277571b 2009/10/25 18:36:11
ofst[ 28]:err_code:0xa0801004, clock:0x145f39af 2010/10/30 20:16:47
ofst[ 32]:err_code:0xa0801004, clock:0x14c13882 2011/01/13 04:13:54
ofst[ 36]:err_code:0xa0801004, clock:0x15706905 2011/05/26 01:27:33
ofst[ 40]:err_code:0xa0801004, clock:0x15706983 2011/05/26 01:29:39
ofst[ 44]:err_code:0xa0801004, clock:0x15706aa8 2011/05/26 01:34:32
ofst[ 48]:err_code:0xa0801004, clock:0x15706b27 2011/05/26 01:36:39
ofst[ 52]:err_code:0xa0801004, clock:0x15706bce 2011/05/26 01:39:26
ofst[ 56]:err_code:0xa0801004, clock:0x15707297 2011/05/26 02:08:23
ofst[ 60]:err_code:0xa0801001, clock:0x1572d27c 2011/05/27 21:22:04
ofst[ 64]:err_code:0xa0801001, clock:0x0b4886a7 2005/12/31 00:00:39
ofst[ 68]:err_code:0xa0801001, clock:0x0b4887fa 2005/12/31 00:06:18
ofst[ 72]:err_code:0xa08014ff, clock:0xffffffff
ofst[ 76]:err_code:0xa0603040, clock:0xffffffff
ofst[ 80]:err_code:0xa08014ff, clock:0xffffffff
ofst[ 84]:err_code:0xa0902120, clock:0xffffffff
ofst[ 88]:err_code:0xa0603040, clock:0xffffffff
ofst[ 92]:err_code:0xa0801001, clock:0xffffffff
ofst[ 96]:err_code:0xa0603040, clock:0xffffffff
ofst[100]:err_code:0xa0603040, clock:0xffffffff
ofst[104]:err_code:0xa0603040, clock:0xffffffff
ofst[108]:err_code:0xa0603040, clock:0xffffffff
ofst[112]:err_code:0xa0603040, clock:0xffffffff
ofst[116]:err_code:0xa0603040, clock:0xffffffff


bringup

[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2


becount

Bringup : 154 times
Shutdown: 102 times
Power-on: 133day 00hour 45min 35sec

 

[Patience is a virtue]

I noticed A08014FF in there it seems to point to a checkstop. Says associated with RSX and distant second is a failing CELL. I'm really hoping the problem lies within the RSX and CELL, not the flash. I considered nec/tokin's but after seeing they don't fail as often as people think, I assumed it's just the rsx & cell.

 

[Raidmax]

Looks like NAND rather than RSX. Usually 14ff should have a 1601 and 1701 if it was the RSX to fail.

Try getting a hardware flasher and dump the NAND, then test the dump using the Python based dump checker (I forgot what its name was at the moment.).

Best case scenario is the contents being fairly intact, but the NAND is dying, in which case you can source another NAND IC from a dead CECHG01 and write your dump back.

Worst case scenario the A01 NAND might be completely gone. At that point idk how you would be able to get it running.