Timeline for Data recover with broken screen
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2020 at 7:18 | comment | added | jack_the_beast | turns out otg doesn't even work... I guess that's really the end :( | |
| Jun 26, 2020 at 15:24 | comment | added | jack_the_beast | @alecxs will try | |
| Jun 26, 2020 at 11:48 | comment | added | alecxs | you need second device to figure out key sequence. first test on working device. then you can do it blind android.stackexchange.com/q/159551 | |
| Jun 26, 2020 at 10:21 | comment | added | jack_the_beast | @alecxs unfortunately I can't see anything anymore | |
| Jun 26, 2020 at 9:53 | comment | added | alecxs | if you still can see something try to enable usb-debugging with OTG Keyboard. once you authorized adb you can use scrcpy to get full control | |
| Jun 26, 2020 at 9:22 | comment | added | Robert | If your device is protected by a PIN/password, then the USB OTG keyboard is the way to go. After authentication via PIN adb should be usable again. Additionally you can check out or broken-screen tag wiki. | |
| Jun 26, 2020 at 9:21 | history | edited | Robert |
tag added
|
|
| Jun 26, 2020 at 9:05 | review | First posts | |||
| Jul 10, 2020 at 9:06 | |||||
| Jun 26, 2020 at 9:00 | history | asked | jack_the_beast | CC BY-SA 4.0 |