Open BlueAction opened 1 year ago
If you connected the device to a PC and used fastboot devices
instead, what would the output look like?
I suppose it will be just the first eight characters because the rest keeps changing. Looks like a missing null terminator of the serial number string. I'll try to find where the problem is.
Without alternatives for debugging via fastboot / adb
I only use the smartphone device. As a substitute for termux, I run the bugjagear application whose output is correct.
But I prefer to use your tool because it has adb
support, which I have difficulties with in bugjaeger.
Thanks for the report again, I will look into it.
Hello, I am using a Huawei device to connect via OTG to another smartphone which has an unlocked bootloader status. In order to display the output of
termux-fastboot devices
~ $ termux-fastboot devices && termux-fastboot devices && termux-fastboot devices && termux-fastboot devices && termux-fastboot devices d3d59b1b/|�� v}�0�E� �y�0�E�<��� d3d59b1b�l� �m�0�� mj�0��� d3d59b1b_�B ��0��� -�0������ d3d59b1bߤ�g &��0�d� ���0�d�L7�� d3d59b1b�0� 2�0��� �.�0����� ~ $
Output![230228-183737](https://user-images.githubusercontent.com/46908543/221919074-17550598-a325-4c89-81e1-320356d67810.png)
fc-list
output for displaying the installed fontsI'll also add architecture and kernel![Screenshot_20230228_184532](https://user-images.githubusercontent.com/46908543/221921498-588687f1-90ba-409d-9db0-b60da6381177.jpg)