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.

 

[james194zt2]

Fucking legend here! Saving us all from these garbage sellers with old stock chips. The hero we needed!

Can't watch the video, I was going to try connecting the ST Link programmer as usual and lifting pin 44 and applying 3.3V to it instead of ground, this should in theory change the boot order and not run the onboard code leaving SWD open so then in theory you can unlock the chip and program whatever you want.

The highlighted pin below

Not had chance to try though due to year end at work and late nights

 

[Vladjaye]

So, is the bin file from the first post is flashable through USB of the new OLED chip? Or it has to be done through hardware programmer first before anything else may be flashed?

 

[Mena]

Can't watch the video, I was going to try connecting the ST Link programmer as usual and lifting pin 44 and applying 3.3V to it instead of ground, this should in theory change the boot order and not run the onboard code leaving SWD open so then in theory you can unlock the chip and program whatever you want.

The highlighted pin below

View attachment 293315
Not had chance to try though due to year end at work and late nights

supposedly @doom95 has already tried this and it did not work for him. my method does involve changing boot order with boot0 pin but it uses another interface

 

[james194zt2]

supposedly @doom95 has already tried this and it did not work for him. my method does involve changing boot order with boot0 pin but it uses another interface

woohoo I was half right lol!! Do I assume once you have done this the USB interface is back open and the chip can be flashed normally in the future as you have uncrippled the stupid sh*t the HWFly guys did to this in the first place by using the regular firmware?

Also hoping debug works on it as well!!

 

[Mena]

woohoo I was half right lol!! Do I assume once you have done this the USB interface is back open and the chip can be flashed normally in the future as you have uncrippled the stupid sh*t the HWFly guys did to this in the first place by using the regular firmware?

Also hoping debug works on it as well!!

it requires fixing of option bytes. @doom95 can likely get it sorted or some other community member. I'm simply releasing the method and people can tweak and adapt it from there

 

[james194zt2]

it requires fixing of option bytes. @doom95 can likely get it sorted or some other community member. I'm simply releasing the method and people can tweak and adapt it from there

Make sense, so have you flashed the 0.2 dump from earlier on in this thread then? Or was it the official firmware. Looking forward to being able to do this as I am trying to debug a power issue on my HW Core in a Mariko at the moment and being unable to load firmware on it or simply debug is a nightmare!

 

[Mena]

Make sense, so have you flashed the 0.2 dump from earlier on in this thread then? Or was it the official firmware. Looking forward to being able to do this as I am trying to debug a power issue on my HW Core in a Mariko at the moment and being unable to load firmware on it or simply debug is a nightmare!

official firmware

 

[kylum]

soon

You sir are amazing!!! I would like to donate a cup of coffee or a Red Bull, what ever it is you like!

 

[linuxares]

soon

"What's created by man, can be cracked by man. It's all a matter of time."

 

[HellsBoyz]

@Mena this question is out of topic subject but if I want to create emunand (partition based) only 10GB or more for Aula device, I know it is doable but is it recommend or safe to do it? Or my emunand must be 59GB (~64GB)?

 

[Tembokbesi]

soon

Holy... you are the savior

 

[Bonovox40]

Advice: To avoid damage (due to OPs info) on an original SX lite being installed in an OLED... What's my best course of action if the installer does NOT want to load hekate/homebrew files on an SD card, as part of the install/test process? (To avoid the gray aspect of the scene)

I'm not sure he'd be willing to usb flash spacecraft 2.0 on the chip before handing it back to me. Obviously it would need to be tested post solder install to even know that everything works though. He has installed SX chips on lites and V2, and usually boots it up with a blank SD card to get the little spaceship no SD message, but isn't that possibly dangerous if it's still on outdated SX chip fw? I guess that's the conundrum.

 

[HermitDash]

Advice: To avoid damage (due to OPs info) on an original SX lite being installed in an OLED... What's my best course of action if the installer does NOT want to load hekate/homebrew files on an SD card, as part of the install/test process? (To avoid the gray aspect of the scene)

I'm not sure he'd be willing to usb flash spacecraft 2.0 on the chip before handing it back to me. Obviously it would need to be tested post solder install to even know that everything works though. He has installed SX chips on lites and V2, and usually boots it up with a blank SD card to get the little spaceship no SD message, but isn't that possibly dangerous if it's still on outdated SX chip fw? I guess that's the conundrum.

Pretty sure this whole thread is based around just clone chips. SX Lite chips can be updated to v2

hwfly clone chips are locked down for normal methods of updating. (But there's also a tutorial now to sorta get past it and flash the new firmware)

 

[Stryd]

so I don't have to worry anymore as long as it work normally after trying to boot without an sdcard to get no sd message..

I'm pretty sure you should avoid to boot without an SD card instead. If you do, then the 5v code will be executed

 

[Tembokbesi]

I'm pretty sure you should avoid to boot without an SD card instead. If you do, then the 5v code will be executed

maybe one incident is not enough to kill my oled or I'm a little lucky it doesn't kill my oled... now i will never do it again.

 

[Stryd]

maybe one incident is not enough to kill my oled or I'm a little lucky it doesn't kill my oled... now i will never do it again.

Definitely it won't be enough, but from now on, be extra careful

 

[Cajacava]

Hi all, I need your support, ai install the hwfly chip y my oled switch (is nos my fisrt time), but when I test it, the led finish not in green but in otange and then turns off. I uninstall the chip and now, the oled do not turn on.
Smeone knows what can I do? There's a way to unbrick it?
Thanks in advance

 

[Stryd]

Hi all, I need your support, ai install the hwfly chip y my oled switch (is nos my fisrt time), but when I test it, the led finish not in green but in otange and then turns off. I uninstall the chip and now, the oled do not turn on.
Smeone knows what can I do? There's a way to unbrick it?
Thanks in advance

There probably is, however i would assume this is not the right place where to ask! You could try make another thread and post some pics so who has the knowledge can help

 

[xdMatthewbx]

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.

How do we flash this?

 

[izy]

Hi all, I need your support, ai install the hwfly chip y my oled switch (is nos my fisrt time), but when I test it, the led finish not in green but in otange and then turns off. I uninstall the chip and now, the oled do not turn on.
Smeone knows what can I do? There's a way to unbrick it?
Thanks in advance

you did something wrong in install