Blank screen but bluetooth available after flashing

[RWrightWells]

I thought I had a brick as the screen was blank but I could still see connect via bluetooth,

1. created Xiaomi account and added device to Xiaomi app
2. used https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor to obtain BLE key and Token.
3. downloaded Stock_fw_2.1.1_0159, ATC_Expliot and ATC_Thermometer.
4. Connected with bluetooth Xiamoi named device
5. Added BLE Key , Token etc and Loggin in successfully
6. Flashed with ATC_Exploit.
7. Power cycled device , blank screen
8. Connected with ATC bluetooth id
9. Flashed Stock_fw_2.1.1_0159
10. Screen working
11. added device again to Xiaomi app
12. used extractor to obtain BLE key and Token.
13. Connected with bluetooth Xiamoi named device
14. Added BLE Key , Token etc and Loggin in successfully
15. Flashed with ATC_Exploit.
16. Flashed with ATC_Thermometer.
17. Power cycled device , blank screen.

Is there an issue with the new devices being shipped ot have I done something wrong?

[Chanabra]

[surprised] Brandon Norman reacted to your message:

…

________________________________ From: RWrightWells ***@***.***> Sent: Sunday, March 30, 2025 4:58:18 PM To: atc1441/ATC_MiThermometer ***@***.***> Cc: Subscribed ***@***.***> Subject: [atc1441/ATC_MiThermometer] Blank screen but bluetooth available after flashing (Issue #350) I thought I had a brick as the screen was blank but I could still see connect via bluetooth, 1. created Xiaomi account and added device to Xiaomi app 2. used https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor to obtain BLE key and Token. 3. downloaded Stock_fw_2.1.1_0159, ATC_Expliot and ATC_Thermometer. 4. Connected with bluetooth Xiamoi named device 5. Added BLE Key , Token etc and Loggin in successfully 6. Flashed with ATC_Exploit. 7. Power cycled device , blank screen 8. Connected with ATC bluetooth id 9. Flashed Stock_fw_2.1.1_0159 10. Screen working 11. added device again to Xiaomi app 12. used extractor to obtain BLE key and Token. 13. Connected with bluetooth Xiamoi named device 14. Added BLE Key , Token etc and Loggin in successfully 15. Flashed with ATC_Exploit. 16. Flashed with ATC_Thermometer. 17. Power cycled device , blank screen. Is there an issue with the new devices being shipped ot have I done something wrong? — Reply to this email directly, view it on GitHub<#350>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACQ42B6ULDY6X6P3IEWJAFD2XAPCVAVCNFSM6AAAAAB2CWRBFCVHI2DSMVQWIX3LMV43ASLTON2WKOZSHE2TQOJXHE3TONA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [RWrightWells]RWrightWells created an issue (atc1441/ATC_MiThermometer#350)<#350> I thought I had a brick as the screen was blank but I could still see connect via bluetooth, 1. created Xiaomi account and added device to Xiaomi app 2. used https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor to obtain BLE key and Token. 3. downloaded Stock_fw_2.1.1_0159, ATC_Expliot and ATC_Thermometer. 4. Connected with bluetooth Xiamoi named device 5. Added BLE Key , Token etc and Loggin in successfully 6. Flashed with ATC_Exploit. 7. Power cycled device , blank screen 8. Connected with ATC bluetooth id 9. Flashed Stock_fw_2.1.1_0159 10. Screen working 11. added device again to Xiaomi app 12. used extractor to obtain BLE key and Token. 13. Connected with bluetooth Xiamoi named device 14. Added BLE Key , Token etc and Loggin in successfully 15. Flashed with ATC_Exploit. 16. Flashed with ATC_Thermometer. 17. Power cycled device , blank screen. Is there an issue with the new devices being shipped ot have I done something wrong? — Reply to this email directly, view it on GitHub<#350>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACQ42B6ULDY6X6P3IEWJAFD2XAPCVAVCNFSM6AAAAAB2CWRBFCVHI2DSMVQWIX3LMV43ASLTON2WKOZSHE2TQOJXHE3TONA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[atc1441]

Hey @RWrightWells there are some PCB versions which doe result in this. They use a different LCD Controller.
It is advised to the Victors version of the ATC_MiThermometer as it is more advanced, I stopped implementing further hardware revisions as it would be just the work done twice that victor already thankfully did
https://github.com/pvvx/ATC_MiThermometer

[RWrightWells]

Great thanks, just saw a youtube comment you had made saying the same thing so I'm currently down that rabbit hole :)

[RonandoDeLaVega]

Hello @RWrightWells, by any chance, did you get this issue solved ?
Thanks !

[smstuff]

Looks like there is another ticket (#346) for the same issue.

[Server4hassio]

pvvx#664 (comment)

this firmware display is working.

@atc1441 Can you combine the display driver (the working display part) from test_B16_new_04_clk20kHz.bin into exploit.bin?

[pvvx]

@atc1441 - UART LCD controller in old HW versions: B1.5/1.6 after receiving new display buffer "AAxxxxxx55" responds with byte 0xAA in RX on GPIO_PB7.
In the SPI version of the LCD, GPIO_PB7 is the SPI data.
If you enable the GPIO_PB7 pull-up to zero, then there will be "0" on the new version with SPI. And on the UART version = "1", since this is the TX UART output of the display controller...
It can also be distinguished by the received response from the RX port "0xAA" from the controller on the UART.