V2 Switch. Black screen after Launching from Hekate.

  • Thread starter Thread starter Modzvilleusa
  • Start date Start date
  • Views Views 13,734
  • Replies Replies 8
  • Likes Likes 2

Modzvilleusa

Well-Known Member
Newcomer
Joined
Apr 17, 2019
Messages
86
Reaction score
142
Trophies
0
Age
57
Website
youtube.com
XP
780
Country
United States
Greetings,
I'm trying to troubleshoot a botched v2 install at the moment. There was no noticeable damage.
Installed a core flashed with hwfly-nx 0.7.2. emmc is samsung.
Trained and booted to hekateipl screen no problem. Pressed vol+ and vol-
Black screen.
Launching cfw sys or stock from hekate results in the same thing, no errors just launches to a black screen.
Dumped emmc, keys, boot0 boot1 no errors.
I attempted a system restore using this method

No change.
I have a replacement emmc ordered. I figure it has to be some sort of emmc issue since hekate works totally fine.
No issues detecting or benchmarking emmc in hekate
Has anyone ever seen anything like this?
Any insight would be appreciated, I'm stumped on this one.
 
Based on the information provided, it's possible that the issue could be related to the installation of the v2 or a problem with the emmc. It's good to hear that hekate works fine and the emmc is detected without any issues, but it's worth checking if the emmc is fully functional.

One possibility could be that the emmc is corrupted, resulting in a black screen when launching cfw sys or stock from hekate. If the replacement emmc arrives, it's worth trying to install it and see if it resolves the issue.

Another thing to consider is that the installation of the v2 could have caused some unforeseen issue that is not immediately apparent. Checking for any loose connections or inspecting the installation process may help identify the root cause of the issue.

Lastly, reaching out to the manufacturer or support forums could provide additional insight and help resolve the issue. They may have encountered similar issues or have more experience in troubleshooting the v2 installation process.
 
There are person fix this problem by replace power ic max77621and he finally fix it. And one person change mmc chip nand and also fix it.coz your console try to boot mmc field. ((erorr during lzma decompression...!!!!))
 

Attachments

  • -208657398482382229.jpg
    -208657398482382229.jpg
    577 KB · Views: 139
  • -1396576434-1690268612.jpg
    -1396576434-1690268612.jpg
    353.3 KB · Views: 152
Last edited by Danook28,
Did you ever find a solution to this? You're the second person I've found so far with this problem and its always HWFly, only difference is I CAN boot Stock from hekate but I cant reboot > ofw
 
Did you ever find a solution to this? You're the second person I've found so far with this problem and its always HWFly, only difference is I CAN boot Stock from hekate but I cant reboot > ofw
Sorry for leaving you guys hanging here. Totally thought I responded.
It was a goober oversight on my part. I got pigeon holed into thinking it was a software issue.
Eventually I removed the cpu flex and realized that multiple caps between sp1 and sp2 were bridged / shorted out.
Since it was out of the range of anywhere that needs to be soldered to I managed to overlook it.
Still don't know how or why the person bridged those caps. Since it was booting hekate it didn't dawn on me to check for shorts way out in lalala land.

TLDR - check for random shorts on the APU caps
 
Sorry for leaving you guys hanging here. Totally thought I responded.
It was a goober oversight on my part. I got pigeon holed into thinking it was a software issue.
Eventually I removed the cpu flex and realized that multiple caps between sp1 and sp2 were bridged / shorted out.
Since it was out of the range of anywhere that needs to be soldered to I managed to overlook it.
Still don't know how or why the person bridged those caps. Since it was booting hekate it didn't dawn on me to check for shorts way out in lalala land.

TLDR - check for random shorts on the APU caps
your solution saved my day. Thank you very much for sharing!
 
your solution saved my day. Thank you very much for
Sorry for leaving you guys hanging here. Totally thought I responded.
It was a goober oversight on my part. I got pigeon holed into thinking it was a software issue.
Eventually I removed the cpu flex and realized that multiple caps between sp1 and sp2 were bridged / shorted out.
Since it was out of the range of anywhere that needs to be soldered to I managed to overlook it.
Still don't know how or why the person bridged those caps. Since it was booting hekate it didn't dawn on me to check for shorts way out in lalala land.

TLDR - check for random shorts on the APU caps
This also fixed my issue... I had tried everything in software and I thought I was going crazy!!!!!
 
  • Like
Reactions: Danook28

Site & Scene News

Popular threads in this forum