Switch OLED teardown V1/V2

  • Thread starter Thread starter grubgrub
  • Start date Start date
  • Views Views 260,925
  • Replies Replies 1,138
  • Likes Likes 10
What about the serial over USB connection on the modchip?
Iirc you could putty into it and press "r" to reset it - did they remove this feature?
No idea, I don't own a HWFLY myself so I can't test it, from what I have heard though going through USB does not seem to work, at least for updating, I would presume the reset command wouldn't work either, but feel free to test it should you acquire one.
 
  • Like
Reactions: peteruk and FR0ZN
They are both using a variation of v1 it uses different APIs so it's not updatable even on V3 hwfly, it's also buggy because they made the storage that stores timing configurations to be read only, so it can never update timings per console and instead relies on the factory set timing.

That said all spacecraft-nx v2 allows is to use the OLED panel to display the NO SD screen, so you can make do with the status LED. Then again a legit SX Lite modchip is preferable assuming you can secure one.

What about the serial over USB connection on the modchip?
Iirc you could putty into it and press "r" to reset it - did they remove this feature?

No idea, I don't own a HWFLY myself so I can't test it, from what I have heard though going through USB does not seem to work, at least for updating, I would presume the reset command wouldn't work either, but feel free to test it should you acquire one.
I have some HWFLY laying around here and would LOVE to test this :)
@FR0ZN, any guidelines on how to do this?

@mathieulh, you're right! USB does nothing on HWFLYs. You can only use it once: when the chip is "blank" on the first write. After that the PC doesn't recognize them anymore.
 
  • Like
Reactions: lufeig
Seeing that the mentioned "clone" as well, I guess it should be possible to reset HWFLY modchips.
Even if you do reset the HWFLY, there is nothing to reset from, given how timings aren't being saved to begin with, it will always use the factory built in values no matter what. That's assuming the reset command even works.
 
Even if you do reset the HWFLY, there is nothing to reset from, given how timings aren't being saved to begin with, it will always use the factory built in values no matter what. That's assuming the reset command even works.
honestly speaking, I'm, actually, more interested in knowing whether it's possible to update a HWFLY to Spacecraft-NX 0.2.0 than to update the timings.
I know we can flash it once so I don't know the chip is write locked after the initial programming.
 
Just sharing in case anyone is wondering about the HWFLY chips and the OLED. I heard that they boot slowly and the connector that you solder to the capcitors on the CPU sucks and doesn't solder well.

Well...both of those were untrue for me.

I had no issues soldering the connector to the capacitors on the CPU. Fluxed and heated up the points, and solder stuck to it just fine, no issues.

As for booting, the HWFLY Lite in my OLED boots to hekate in 1 or 2 seconds. Only 1 or max 2 flashes of the blue/purple light then I get the green light, every time!!! Whereas the SX Core in my OG V1 Switch takes anywhere from 3-7 seconds to get the green light...

Anyways, I'm finally enjoying my OLED and playing games, hope you all can get to this point of bliss as well :) :D
 
Last edited by sean222,
Hi everyone I try to install a sx core on my oled and I try to boot the light show light blue then red and the red light will stay there for while and The screen will show purple light anyone here know what the issue ?
 

Attachments

  • A70D094B-A634-4CB9-921A-219C9CC82D35.jpeg
    A70D094B-A634-4CB9-921A-219C9CC82D35.jpeg
    808.8 KB · Views: 108
  • Like
Reactions: mvmiranda
Hi everyone I try to install a sx core on my oled and I try to boot the light show light blue then red and the red light will stay there for while and The screen will show purple light anyone here know what the issue ?
https://switchbrew.org/wiki/Panic_codes
Purple screen could mean a bootloader issue. Let's just hope your NAND code is not corrupted already.

Red light could mean short or bad communication to the NAND.
If it's instant red light on the chip then the issue is a short on top of the CPU.
If it's after the chip blinked some times purple/blue (your case) then it's, most likely, a bad DAT0 connection. You're either touching the wrong DAT line (or shorting two DAT lines) or an unsatisfactory connection (the DAT pin is not making good connection to your wire or adaptor).

Good luck on resolving your issue!
 
Last edited by mvmiranda,
Hello! I need help to identify the missing capacitor near emmc. Switch Oled. Would somebody be so kind to measure the capacitor from their own switch if possible.
 

Attachments

  • IMG_20211205_193519.jpg
    IMG_20211205_193519.jpg
    653.2 KB · Views: 142
https://switchbrew.org/wiki/Panic_codes
Red light could mean short or bad communication to the NAND.
If it's instant red light on the chip then the issue is a short on top of the CPU.
Can you clarify the difference between these two red lights? Mine boots straight to a solid red light. Does that mean there is a short on the ribbon connected to the CPU ( the flat thing with v1 v2 written on it)? Or is it the nand?
 
  • Like
Reactions: mvmiranda
Can you clarify the difference between these two red lights? Mine boots straight to a solid red light. Does that mean there is a short on the ribbon connected to the CPU ( the flat thing with v1 v2 written on it)? Or is it the nand?
I just mentioned... :)

Yes! Instant red light means a short, most likely in your CPU flat cable!
in case of a short under the eMMC IC (NAND chip) the SX/HWFLY chip would work fine BUT would fail to get "access" to the NAND and would, depending on the short, RED or WHITE light.

This is not a "science" and I can be wrong. But this is the knowledge I got based on my experiences.

Good luck, bud!
 
  • Like
Reactions: lufeig and BigOnYa
Just sharing in case anyone is wondering about the HWFLY chips and the OLED. I heard that they boot slowly and the connector that you solder to the capcitors on the CPU sucks and doesn't solder well.

Well...both of those were untrue for me.

I had no issues soldering the connector to the capacitors on the CPU. Fluxed and heated up the points, and solder stuck to it just fine, no issues.

As for booting, the HWFLY Lite in my OLED boots to hekate in 1 or 2 seconds. Only 1 or max 2 flashes of the blue/purple light then I get the green light, every time!!! Whereas the SX Core in my OG V1 Switch takes anywhere from 3-7 seconds to get the green light...

Anyways, I'm finally enjoying my OLED and playing games, hope you all can get to this point of bliss as well :) :D
yes like I said if it installed correctly it boots with no errors everytime also fasther then sxcore
 
  • Like
Reactions: sean222
Hi all,
I'm looking for an errorcode list and shema.

do the HWFLY chip show errorcode via led (blinking or via error report file to the micro sd card)?

Long storry short, when HWFLY is not booting is there any chance to see errorcodes from the booting process, which may indicate the issue?
 
Last edited by gregor4711,
I just mentioned... :)

Yes! Instant red light means a short, most likely in your CPU flat cable!
in case of a short under the eMMC IC (NAND chip) the SX/HWFLY chip would work fine BUT would fail to get "access" to the NAND and would, depending on the short, RED or WHITE light.

This is not a "science" and I can be wrong. But this is the knowledge I got based on my experiences.

Good luck, bud!
My switch still boots up normally as if nothing was installed though. Wouldn’t a short on the cpu cable prevent that?
 
My Switch is blinking 15 times (blue and a litle bit red at same time(wondering)) than 1 sec full red and switch off (screen black)
any idea ?
 

Site & Scene News

Popular threads in this forum