Open sysadminpower2019 opened 1 week ago
So I was able to work around the touchscreen issue and managed to install LOS however the touch screen is still not working on LOS but more interestingly it is asking me for a password. To start android enter your password. Any idea what the password is? Do you think this device can accept a mouse?
Also here are the steps I took to work around this touchscreen issue.
First make sure the LK installer has installed fastboot by running the LK installer script on windows.
Then I switched to Linux There were some issues with the script and a black screen
After that the phone will restart in fastboot mode even if the screen is black. Pressing the volume up and power will cause the device to vibrate.
After you can use fastboot devices to see that the device is actually there.
here is where the interesting part happens. You can unpack the TWRP.img using an android image kitchen.
edit ramdisk/default.prop
and change the following lines
ro.secure=0
ro.adb.secure=0
ro.debuggable=1
this will allow ADB to work later on.
Save the edited image and then use
fastboot flash recovery twrp.img
then
fastboot boot twrp.img
now on the twrp screen type
adb shell
to connect to the phone via CLI on Linux
Next run the following commands some of them may fail
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data
twrp sideload
adb sideload ....name of the lineageos zip.
then you can do
adb reboot
this will start the phone.
It's strange that it asks for a password on first boot already. Technically you could pair a bluetooth mouse if you know how to add pairings over ADB, but that will not work until you enter the decryption password either. USB mice won't work, as there is no OTG support on the hardware level.
With an unsupported touch panel, you can't really do anything on Android.
Hello,
Unfortunately, it seem this phone has an unofficial touchscreen as TWRP boots fine but the touch screen does not work. Also since TWRP wants you to slide to confirm the write mode on the phone it makes it impossible to continue. Is there any work around?