Problem When trying to start CFW through hekate

  • Thread starter Thread starter Bl_BR
  • Start date Start date
  • Views Views 1,509
  • Replies Replies 17

Bl_BR

Member
Newcomer
Joined
Mar 23, 2023
Messages
16
Reaction score
2
Trophies
0
Age
30
XP
97
Country
Brazil
I have this switch v1 Unpatched for repair, it works normally in the original mode without starting the unlock, but whenever I try to start with the hekate of the different colors on the screen both in cfw and in emunand, in addition to having these scratches on the letters, I have already tested another sd card slot and another Nand but the problem persists


Would a GPU rebaling fix it?
 

Attachments

  • 20230409_220912.jpg
    20230409_220912.jpg
    1 MB · Views: 67
  • 20230407_233459~2.jpg
    20230407_233459~2.jpg
    653.9 KB · Views: 55
Well the problem here is either your eMMC, or the SD card as it won't write the NAND backup to the SD card.
I don't think so, because I already tested it with another emmc module and the image failure problem is the same, I also used another sd connector so I'm thinking that it could be a gpu problem
other than that the system starts normally without activating the rcm
 
I don't think so, because I already tested it with another emmc module and the image failure problem is the same, I also used another sd connector so I'm thinking that it could be a gpu problem
other than that the system starts normally without activating the rcm

Reason I said it is one of those two is because based on your provided it point toward the eMMC and SD card.
 
  • Like
Reactions: Bl_BR
Did you check the connector that the emmc module connects to? I've seen some water damaged switches where there was corrosion on the emmc module but it usually results in 'slow mode' as Hayato213 has mentioned. It might be worth checking the connections on the connector and the traces to the cpu.
 
  • Like
Reactions: Bl_BR
Did you check the connector that the emmc module connects to? I've seen some water damaged switches where there was corrosion on the emmc module but it usually results in 'slow mode' as Hayato213 has mentioned. It might be worth checking the connections on the connector and the traces to the cpu.
ok i will do a check on the board
 
ok i will do a check on the board
While you're at it, might as well check the connector on the emmc module, the emmc module itself and the sd card reader module (connector on the mainboard and sd card module and the module itself). Just need to beep out the traces (DMM on continuity) to ensure they are intact.
 
While you're at it, might as well check the connector on the emmc module, the emmc module itself and the sd card reader module (connector on the mainboard and sd card module and the module itself). Just need to beep out the traces (DMM on continuity) to ensure they are intact.
no problem, I'll get back to you
Post automatically merged:

While you're at it, might as well check the connector on the emmc module, the emmc module itself and the sd card reader module (connector on the mainboard and sd card module and the module itself). Just need to beep out the traces (DMM on continuity) to ensure they are intact.
I did the test on the eMMc and Cpu connector tracks, they are normal, I tested the SD card connector and it is normal too. I turned it on in RCM mode through Tegra without using the sd card And the image failure continues, so I'm already ruling out that it is the sd connector, probably some track or the eMMc communication with the CPU
 

Attachments

  • 20230413_144913.jpg
    20230413_144913.jpg
    1.6 MB · Views: 45
Last edited by Bl_BR,

Site & Scene News

Popular threads in this forum