-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not available via adb after reset button #12
Comments
Hi, thank you for getting in touch. Please give me a minute to take a look at your issue. |
It could be possible that they patched it. |
Kindly, upgrade the Box to the latest firmware (I know, this sounds weird) |
Hmm, upgraded to the current OS version. But no ADB in Recovery sadly. Same port and cable get's a working ADB on my android phone, so port, cable, drivers, etc are working. |
oh hi i didnt see your comment - |
anyways i've bought a tigerbox touch plus now - gonna try to get access on it |
also @Talkless, could you tell me if the usb cable was connected while pressing the key combo? |
you just have to get it into the android recovery mode |
then connect it, and modify it |
ah yea i see now, |
Sorry, I do not recall, and I haven't time to try that again. Maybe some time in the future. |
Hi,
I've been asked to try to open Tigerbox 1203...
Holding reset and power button made to enter some sort of "Mask ROM mode":
But
adb
on Debian 11 does not see it as a android device...Do I need udev rules of some sort, or this "Mask ROM mode" is not the required Android Recovery mode that "via USB Android Recovery without opening" documentation section suggests, but something else?
Thanks!
The text was updated successfully, but these errors were encountered: