Hacking Switch Lite no battery information and no boot to firmware after hekate usb tools crash.

[C9H9N]

So i installed a Picofly chip into my switch lite, and everything seemed to be working fine Battery percentage and all information was showing and it just worked as expected. I havent tried booting into any firmware yet and did all the necessary backups. As i was setting up EmuMMC and was putting the nintendo folder back onto my sd card via usb tools my windows explorer completely froze. Evereything crashed even the desktop. On my switch i also couldnt abroad the connection, so regardless of the warning i have unplugged the cable, without ejecting the console first as this was not possible. Immediatley after unplugging the cable my windows came back to life, but my switch was still frozen. I tried establishing the connection again but it did not work, so i shut the switch down by holding the power button. After the switch had turned on again I resumed using the usb tools and got ready to the point of launching EmuMMC, as i was setting up everything i noticed that all the battery information was gone and showing errrors. I just assumed the battery had run dry but it was plugged in so i didnt care that mouch as all the backups were on my pc already. OFW and EmuMMC are just booting into a black screen now without any errors. I tried unplugging the battery holding the power button and leaving it unplugged for a few days, but that didn not work. I also meassured the battery and it got 4.0V without being plugged into a charger and 4.2V when charging. I meassure 14.9V on my usb connector wehen charging. Dumping the battery information gives me a empty file. I have of course checkt the board for any shorts but i have found none, and the board (apparently) was working completely fine before the crash. If you need further information i will be ready to provide it. Thanks for any help!

 

[CMDreamer]

Sounds like a microSD card fault.

Test it for corruption and if possible use a new one.

 

[C9H9N]

Sounds like a microSD card fault.

Test it for corruption and if possible use a new one.

I have not thaught of that! I just have tried a different one, same issue persists...

 

[thesjaakspoiler]

If Hekate boots, then your modchip is fine.
If you never once were able to boot into CFW, then you likely have some other (software) issue.
If you can boot into OFW, then the partitions on the emmc that are needed to boot the CFW are fine.
If OFW also doesn't boot, then you do have an issue with the emmc or your OFW is out of sync with the fuses (downgrade protection).

Hekate boots before everything else and only needs some files from the SD card.
Sometimes it's just an outdated version of Atmosphere or extra things like overlays and sys modules that break everything.
A plain install of Hekate/Atmosphere/sigpatches should work.

Your battery information is retrieved from the charger chip in your Switch.
It communicates with the APU via 2 datalines.
These datalines have a pull up resistor.
When that resistor is broken or missing, you end up with no battery information.
Also if one of the datalines is broken, then you also get nothing.

On the old Switch, those datalines and resistors were close the the APU shield, so sometimes they got damaged when removing the shield.
I don't know about this model but just search the forum.

 

[C9H9N]

If Hekate boots, then your modchip is fine.
If you never once were able to boot into CFW, then you likely have some other (software) issue.
If you can boot into OFW, then the partitions on the emmc that are needed to boot the CFW are fine.
If OFW also doesn't boot, then you do have an issue with the emmc or your OFW is out of sync with the fuses (downgrade protection).

Hekate boots before everything else and only needs some files from the SD card.
Sometimes it's just an outdated version of Atmosphere or extra things like overlays and sys modules that break everything.
A plain install of Hekate/Atmosphere/sigpatches should work.

Your battery information is retrieved from the charger chip in your Switch.
It communicates with the APU via 2 datalines.
These datalines have a pull up resistor.
When that resistor is broken or missing, you end up with no battery information.
Also if one of the datalines is broken, then you also get nothing.

On the old Switch, those datalines and resistors were close the the APU shield, so sometimes they got damaged when removing the shield.
I don't know about this model but just search the forum.

Thanks for the answer, I've searched everywhere and was not able to find anything that works. So OFW is not booting, it was before the chip was installed with the wiring and the flex cable in place. Then Hekate bootet with the battery info working and everything, so I startet backing up everything and was setting up emu MMC. I have not booted into OFW since the chip was installed. Then the USB tools crashed and nothing except Hekate boots any longer, and the battery readings look like in the picture. I also just measured the resistors around the chips with the error messages and got no shorts. I also have tried different versions of Hekate but it doesn't change anything really. It seems like USB tools froze the I2C bus somehow but I'm really no expert. Just wanted to try a fun little soldering project which succeeded for the most part... I really don't know what to try anymore.

 

[Hayato213]

Are you able to boot into OFW?

 

[C9H9N]

Are you able to boot into OFW?

No it just black screens after Hekate logo.

 

[Hayato213]

No it just black screens after Hekate logo.

For other modchip like instinct NX it need to boot into OFW to get battery info so not sure if that applies to picofly.

 

[C9H9N]

For other modchip like instinct NX it need to boot into OFW to get battery info so not sure if that applies to picofly.

It had battery information working before USB tools crashed. Now it won't boot into OFW...