Hwfly snowball disaster

This was about my 10th hwfly install and my first time running into a major issue. I’m honestly not sure at all what happened, but here’s the order of what I witnessed today.

  • Switch OLED, modded and working last week with hwfly v6 kit using the under-chip DAT0 adapter. Everything worked great. Even had emummc loaded up and played a test game from cartridge.
  • Powered it on today and got a sideways red-text error saying it couldn’t boot, press a button to go back to hekate
  • Hekate tools showed “failed to init” for emmc and also “Your eMMC is initialized in slower mode”
  • SD card passed everything I could throw at it and I also reformatted and re-loaded it with the bootloader - same error

So, I removed the hwfly parts and put it back to stock and then it boots to a purple screen. ONCE .

After that, black screen, no signs of life. Pulled the board to check for shorts and they’re all over and on both sides. It looked like MAX77812 was causing shorts, so I removed it and I still have shorts on both sides. I’m really not sure on this one - I’ve never had an experience like this with hwfly installs. Did it cook my APU? I’ve got some pics below from both sides where some of the bigger groupings of shorts are. Any help or recommendations are greatly appreciated!



These lines have all low impedance. If you check diode mode or resistance you will see that those lines are not shorted.

The purple screen and emmc related messages are point towards the emmc or the lines to it.

Thanks, @Calvin. I’ve got a replacement MAX77812 on the way and I also replaced the CMD resistor as the value was incorrect and it sounds like that could have been the cause of the purple screen. Is there anything you’d recommend checking around the emmc? I did carefully reflow the emmc as well.

If the CMD resistor had a false value or is damaged, it is very possible that you found your issue.

I replaced the MAX77812 and the shorts are still there. I get 15.3V and 0.13A on usb connected with or without the battery plugged into the board. I’m out of ideas and really not sure what to check next. The right side of the MAX chip all beep for continuity to ground now that the chip is in.

These are the new shorts around the other side of the board surrounding MAX77620H

These are the new shorts around MAX77812:

I removed and reinstalled the MAX77812 and…great success. I’m going to button it back up and move on without modding this one. My nerves are shot from this. I’m not sure if I got a bad picofly or what, but now that it’s back in a working state I’d hate to go full circle after reinstalling the chip. ¯_(ツ)_/¯

From your discription it sounds like the Vsys was shorted after the first replacement of the max77812. Your shown shorted caps around the max77620h are touching/smoothing Vsys.

Hey @Calvin, sorry for not saying it sooner, but thank you very much for your help. I greatly appreciate it!