m4yur1

Entendi, existe algum regulador que tensão que devo testar antes?(similar ao ps3?), do ps4 nunca efetuei a troca 😕 ,

Boa tarde. Estou com esse ps4 fat na bancada, CECH1215A (inteiro preto fosco), ele não sincroniza nem carrega nenhum controle. As usb's tem 5V, bobinas ok, ao conectar qualquer controle, ele acende o led laranja por 2-3 segundos e apaga (o 5V ainda existe). O curioso é que, no modo segurança, consigo usar o controle normalmente... Minha dúvida é: Existe alguma outra opção com esse sintoma sem ser partir pra troca do módulo bt??, alguém sabe me dizer se o ps4 funcionaria o modo de segurança de o módulo bt estivesse defeituoso?? desde de já agradeço!

@eltssgol Só pra confirmar, ctz que é o L1e não L2?

A ferramenta repairS11 apresentou sucesso, mas o problema continuou identico.. Infelizmente o cliente solicitou o hd de volta, de qualquer forma muito obrigado por todo conhecimento compartilhado!

Bom dia!, teste tudo, sem sucesso (ele até conclui o reparo da ultima ferramenta, mas continua igual).., mas agradeço muito a força, pesquisando por conta nao cheguei nem perto a esses caminhos q vc me passou, muito obrigado!

Peguei ele nesse estado de um cliente, nao tenho a informação do tempo de uso, mas certamente RMA não é uma opção^^; Com esse toolkit eu tento um "Firmware Upgrade"?

Com esse programa ele reconheceu, o log de erros: smartctl 6.6 2017-11-05 r4594 [x86_64-w64-mingw32-w10-b17763] (sf-6.6-1) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: SATAFIRM S11 Serial Number: 50026B76820CA1A6 LU WWN Device Id: 5 0026b7 6820ca1a6 Firmware Version: SBFK71W1 User Capacity: 240.057.409.536 bytes [240 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 4 SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Wed Oct 30 20:56:11 2019 HB SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Disabled Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Total time to complete Offline data collection: (65535) seconds. Offline data collection capabilities: (0x00) Offline data collection not supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate -O--CK 099 099 000 - 51 9 Power_On_Hours -O--CK 100 100 000 - 6135 12 Power_Cycle_Count -O--CK 100 100 000 - 25 148 Unknown_Attribute ------ 255 255 000 - 101 149 Unknown_Attribute ------ 255 255 000 - 53 167 Unknown_Attribute ------ 100 100 000 - 3 168 Unknown_Attribute -O--C- 100 100 000 - 0 169 Unknown_Attribute ------ 100 100 000 - 57 170 Unknown_Attribute ------ 100 100 010 - 10 172 Unknown_Attribute -O--CK 100 100 000 - 0 173 Unknown_Attribute ------ 100 100 000 - 4718701 181 Program_Fail_Cnt_Total -O--CK 100 100 000 - 0 182 Erase_Fail_Count_Total ------ 255 255 000 - 78 187 Reported_Uncorrect -O--CK 100 100 000 - 30 192 Power-Off_Retract_Count -O--C- 100 100 000 - 15 194 Temperature_Celsius -O---K 068 055 000 - 32 (Min/Max 20/45) 196 Reallocated_Event_Count ------ 100 100 000 - 108 199 UDMA_CRC_Error_Count -O--CK 100 100 000 - 0 218 Unknown_Attribute ------ 100 100 000 - 0 231 Temperature_Celsius PO--C- 100 100 000 - 92 233 Media_Wearout_Indicator PO--C- 100 100 000 - 12401 241 Total_LBAs_Written -O--C- 100 100 000 - 7074 242 Total_LBAs_Read -O--C- 100 100 000 - 62196 244 Unknown_Attribute ------ 100 100 000 - 72 245 Unknown_Attribute ------ 100 100 000 - 109 246 Unknown_Attribute ------ 100 100 000 - 744770 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 51 Comprehensive SMART error log 0x03 GPL R/O 64 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log SMART Extended Comprehensive Error Log Version: 1 (64 sectors) Device Error Count: 11 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 11 [10] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 02 60 6c d6 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x02606cd6 = 39873750 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 02 60 6c d6 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 02 60 6c 56 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 02 60 6b d6 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 02 60 6b 56 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 02 60 6a d6 e0 00 00:00:00.000 READ DMA EXT Error 10 [9] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 5b 6a b0 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x095b6ab0 = 156986032 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 5b 6a b0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 6a 30 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 69 b0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 69 30 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 68 b0 e0 00 00:00:00.000 READ DMA EXT Error 9 [8] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 57 95 98 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09579598 = 156734872 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 57 95 98 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 95 18 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 94 98 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 94 18 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 93 98 e0 00 00:00:00.000 READ DMA EXT Error 8 [7] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 55 5c 00 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09555c00 = 156589056 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 55 5c 00 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5b 80 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5b 00 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5a 80 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5a 00 e0 00 00:00:00.000 READ DMA EXT Error 7 [6] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 53 21 68 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09532168 = 156442984 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 53 21 68 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 20 e8 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 20 68 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 1f e8 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 1f 68 e0 00 00:00:00.000 READ DMA EXT Error 6 [5] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 51 8f 50 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09518f50 = 156340048 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 51 8f 50 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8e d0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8e 50 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8d d0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8d 50 e0 00 00:00:00.000 READ DMA EXT Error 5 [4] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 5b 43 b0 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x095b43b0 = 156976048 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 5b 43 b0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 43 30 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 42 b0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 42 30 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 5b 41 b0 e0 00 00:00:00.000 READ DMA EXT Error 4 [3] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 57 95 98 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09579598 = 156734872 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 57 95 98 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 95 18 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 94 98 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 94 18 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 57 93 98 e0 00 00:00:00.000 READ DMA EXT Error 3 [2] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 55 5c 00 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09555c00 = 156589056 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 55 5c 00 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5b 80 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5b 00 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5a 80 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 55 5a 00 e0 00 00:00:00.000 READ DMA EXT Error 2 [1] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 53 21 68 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09532168 = 156442984 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 53 21 68 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 20 e8 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 20 68 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 1f e8 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 53 1f 68 e0 00 00:00:00.000 READ DMA EXT Error 1 [0] occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 71 00 80 00 00 09 51 8f 50 e0 00 Device Fault; Error: UNC 128 sectors at LBA = 0x09518f50 = 156340048 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 00 00 00 80 00 00 09 51 8f 50 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8e d0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8e 50 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8d d0 e0 00 00:00:00.000 READ DMA EXT 25 00 00 00 80 00 00 09 51 8d 50 e0 00 00:00:00.000 READ DMA EXT SMART Extended Self-test Log Version: 1 (1 sectors) No self-tests have been logged. [To run self-tests, use: smartctl -t] Selective Self-tests/Logging not supported SCT Commands not supported Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 25 --- Lifetime Power-On Resets 0x01 0x010 4 6135 --- Power-on Hours 0x01 0x018 6 14836328492 --- Logical Sectors Written 0x01 0x028 6 130436462474 --- Logical Sectors Read 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 51 --- Number of Reported Uncorrectable Errors 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 32 --- Current Temperature 0x05 0x020 1 45 --- Highest Temperature 0x05 0x028 1 20 --- Lowest Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x018 4 0 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == 0x07 0x008 1 7 --- Percentage Used Endurance Indicator |||_ C monitored condition met ||__ D supports DSN |___ N normalized value SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 4 2 Transition from drive PhyRdy to drive PhyNRdy 0x000a 4 2 Device-to-host register FISes sent due to a COMRESET 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRC

@nelsonhf com o SSD Manager da Kingston o ssd nem é reconhecido... No gerenciador de disco ele está conforme a foto a seguir:

Tentei, só com ele, iniciar uma instalação limpa, após formatar é informado que não há espaço suficiente... Como faria isso exatamente?, se for problema na nand, só substituindo a mesma?

Sim é SATA, realmente vi muita gente reclamando! Tranquilo, vou ver oque consigo, eu já peguei ele com defeito, isso dificulta muito mais as coisas...

Farei isso e ja retorno com os resultados, grato!

Para garantir, tentei o mesmo procedimento pelo AOMEI Partition Assistant Standard Edition 8.4, tb sem sucesso,acredito que seja problema físico...

Entendi, o problema é que no passo "create partition primary" ele me retorna "there is not enough usable space", isso que me preocupa.

Bom dia. Chegou na bancada esse SSD kingston 240gb apresentando os defeitos conforme a foto. Para ser sincero, primeira vez que trabalho com recuperação de SSD, existe mais algum procedimento a ser feito para faze-lo funcionar novamente? Desde já agradeço qualquer ajuda!

Pessoalmente nao recomendo o uso desse chip nessas placas, o x360run vermelho é barato e funciona perfeitamente. O ace utilizo nos fat's e as vezes também não funciona, e não importa oque eu faça, não vai!.