HWFLY chips will brick your OLED. Here is how to avoid it

First things first, I should start by saying that if you have an OLED-specific clone chip you're fine.

Anyways, all HWFLY Lite chips come with Spacecraft v1. For those that don't know, Spacecraft v1 sets certain pins to 5V that shouldn't be set to that on an OLED.

You can find more info in the readme of my application here: https://github.com/Pheeeeenom/payloadchecker

All this application does is check the payload that's currently written and checks it to verified hashes stored in the program.

Steps to follow are:

Boot hekate
Dump BOOT0
Check it on application

If you have a genuine modchip, update it to the latest Spacecraft v2 before you install it into an OLED.

The OLED-specific modchip also comes with broken USB debugging, if you want to fix this issue you will need to write this repaired firmware binary.
 
I would update it purely out of pre-caution. SX Payload is even older than spacecraft. Surely they wouldn't know in advance when a new revision is coming out let alone how the board will be laid out. I would update.
 
  • Like
Reactions: Donnie-Burger
I double checked to be extra sure, but yeah, I am good xD
It's a good thing I am using a genuine SX Lite in my OLED :P

1641680198242.png
 
  • Like
Reactions: Donnie-Burger
So I ordered off Taobao a 3rd generation hwfly lite the other day - fuck me.

Does anyone if this "3rd generation" has the same issues?
 

Attachments

  • 04B2B8B0-ABEB-4973-AAF0-7D154117DFC1.jpeg
    04B2B8B0-ABEB-4973-AAF0-7D154117DFC1.jpeg
    98.8 KB · Views: 166
  • 1691BD56-5E63-497A-8920-1FF5D863A8CC.jpeg
    1691BD56-5E63-497A-8920-1FF5D863A8CC.jpeg
    122.8 KB · Views: 158
  • Like
Reactions: Donnie-Burger
You may direct your thanks to the Chinese who clone a product without respecting any form of licensing and maime it to the point where built-in firmware update functionality that could remedy this is taken away.
It's even worse than that, they kept the code that optimizes timings per console but made the storage that stores the timing configuration read only, so it can't use per console optimal timings and instead relies on the factory built in ones (which somehow works most of the time). ie. They are idiots who can't even clone stuff correctly and don't understand how what it is that they are cloning even works.
 
I mean if its not flashed at all and is already inside the oled
If it's not updated, you need to update it before using it in an OLED, if it's in your OLED and your OLED still function properly, please do update it before using it further or you will risk damaging your OLED console.
 
It uses the same or equivalent power configuration to Spacecraft-NX version 0.1.0 I would not advice using it on OLED consoles.
The worst part of this is the fact it's a ticking timebomb. Most consoles will work just fine... obviously for however long that chip that gets the 5V can handle it. I've seen issues already about either dead on first power-up (seen it twice now). There was one user that had issues with his joycon/fan circuit which is apparently the 5V rail. Not sure if they're related at all but he also had a HWFly Lite chip. I don't know the OLED layout to know where it goes but @doom95 is working on delayering the board.
 
Last edited by Mena,
The worst part of this is the fact it's a ticking timebomb. Most consoles will work just fine... obviously for however long that chip that gets the 5V can handle it. I've seen issues already about either dead on first power-up (seen it twice now). There was one user that had issues with his joycon/fan circuit which is apparently the 5V rail. Not sure if they're related at all but he also had a HWFly Lite chip. I don't know the OLED layout to know where it goes but @doom95 is working delayering the board.
Realistically, all those dead on install consoles may as well be installation issues, the OLED install isn't a walk in the park, most people will not know how to install those properly, points on the board are tiny as well, all it takes is bridging the wrong pins.

That said, it's not a good idea to supply wrong voltages to begin with and we do not know how far tolerance extend, for all we know it's well within spec but it might not be, either way you risk damaging your console, especially long term if you do not apply proper voltages, as such I would not recommend running a firmware that's not designed for Aula in mind on an OLED console.
 
Realistically, all those dead on install consoles may as well be installation issues, the OLED install isn't a walk in the park, most people will not know how to install those properly, points on the board are tiny as well, all it takes is bridging the wrong pins.

Mostly agree with your post, but sadly I have first hand experience. Had an OLED install fully prepared, i.e. wires solders to all the points on the switch. HWFLY chip jist needed wiring up. Before I did so I verified the switch still worked. Then I soldered the few wire ends to the HWFLY. It glitched indefinitely and the console never booted again.

First two attached pics are taken 2 seconds apart. Last one is post mortem. I verified correct wiring endlessly. Diode mode readings fully as expected. I couldn't find any flaw in the installation. This was my 6th OLED I believe, the earlier ones were successful. I'm not saying I couldn't have made an error, but I've been very diligent and couldn't find any traces of mistakes, and yet the outcome speaks for itself.
 

Attachments

  • 20211229_150634.jpg
    20211229_150634.jpg
    1.9 MB · Views: 163
  • 20211229_150636.jpg
    20211229_150636.jpg
    2.1 MB · Views: 141
  • 20211229_160120.jpg
    20211229_160120.jpg
    1.6 MB · Views: 166
Would it be possible to
1. Upgrade an OG Chip
2. Read the program off that (hex?)
3. Get a brand new chip (I believe some clones have data etched onto the chip) and flash the program that way.

It'd require removing and replacing a chip a chip... but a possible solution. (I'm just a hobbyist and just throwing out ideas).
I still have an OG sx core still on sxos but I'd be curious if itd work.
 
Would it be possible to
1. Upgrade an OG Chip
2. Read the program off that (hex?)
3. Get a brand new chip (I believe some clones have data etched onto the chip) and flash the program that way.

It'd require removing and replacing a chip a chip... but a possible solution. (I'm just a hobbyist and just throwing out ideas).
I still have an OG sx core still on sxos but I'd be curious if itd work.
 
Sthetix has do it.
Here's hoping he documents what he has done so we can look, are the issues with these chips i.e. the timing section read only, inability to flash etc... coming from them messing around with SpaceCraft NX and the boot loader? Or is it physical i.e. using cloned chips or similar leading to them being write once (although Sthetix seems to have defied that).

I was wondering whether it would be possible to basically flash one of the HWFly chips back to the original SX bootloader and firmware, then update the firmware to Spacecraft NX maybe? I was going to try soldering a programmer to it to see what I could do, but I assumed greater hackers than me had already ruled that out.
 
  • Like
Reactions: Mat3 and tyiphius
So I ordered off Taobao a 3rd generation hwfly lite the other day - fuck me.

Does anyone if this "3rd generation" has the same issues?
The one I did we where told it was the v3/g3 and it still has spacecraft 0.1.0
 
  • Like
Reactions: yee
yeah you're good.


I should change my wording honestly, I can't say it *will* kill your oled but it most certainly can cause damage. Hell, even the creator of Spacecraft said this but it didn't really gain any traction. Now that people are actively doing this mod I've seen issues come up.View attachment 292755

I am honored to have my Twitter post quoted :) (that's me intelliaim)

My HWFLY Lite has SpaceCraft 1.0 in my OLED and I'm going to remove it. Thankfully I have an extra SX Core genuine modchip that I can install into it. I didn't put the SX Core in my OLED initially because of the size....the Lite just fit so darn well. Well, now that there are many more Core installs I can see how people fit it in and I'll get it in there with SpaceCraft 2.0.

Also, my "3rd gen" HWFLY Lite has SpaceCraft 1.0 on it.
 
So I ordered off Taobao a 3rd generation hwfly lite the other day - fuck me.

Does anyone if this "3rd generation" has the same issues?
they are coming from the factory with 0.1.0 it seems :/
 

Attachments

  • Screenshot_3.jpg
    Screenshot_3.jpg
    187.5 KB · Views: 166
  • Like
Reactions: yee
The spacecraft firmware comes with a factory encryption program, don't try to decipher it, it will cause problems with your console and chip.
We guarantee that all hwfly chips are compatible with the latest consoles and there are no issues.
The firmware release is also more than 2 months old and there is no evidence that it will break the console, this is a mature product.
Is this account even legit?
It's so sad you'll defend a batch of dangerous products just because you want to sell them.
Instead, accept the fact you need to allow flashing and start using the new version of spacecraft asap, or no one will be buying from you at all ever again.
 
  • Like
Reactions: doom95

Site & Scene News

Popular threads in this forum