Skip to content
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

Open
Talkless opened this issue May 17, 2024 · 11 comments
Open

Not available via adb after reset button #12

Talkless opened this issue May 17, 2024 · 11 comments

Comments

@Talkless
Copy link

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":

May 17 15:16:47 kernel: usb 1-7: USB disconnect, device number 50
May 17 15:16:55 kernel: usb 1-7: new high-speed USB device number 51 using xhci_hcd
May 17 15:16:55 kernel: usb 1-7: New USB device found, idVendor=2207, idProduct=310c, bcdDevice= 1.00
May 17 15:16:55 kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
$ lsusb | fgrep Rockchip
Bus 001 Device 051: ID 2207:310c Fuzhou Rockchip Electronics Company RK3126/RK3128 in Mask ROM mode

But adb on Debian 11 does not see it as a android device...

$ adb devices -l
List of devices attached

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!

@user0-07161
Copy link
Contributor

Hi, thank you for getting in touch. Please give me a minute to take a look at your issue.

@user0-07161
Copy link
Contributor

It could be possible that they patched it.

@user0-07161
Copy link
Contributor

Kindly, upgrade the Box to the latest firmware (I know, this sounds weird)

@muellerlukas
Copy link

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.

@user0-07161
Copy link
Contributor

oh hi i didnt see your comment -
this is honestly weird. maybe the manufacturer added something to protect the recovery from adb?

@user0-07161
Copy link
Contributor

anyways i've bought a tigerbox touch plus now - gonna try to get access on it

@user0-07161
Copy link
Contributor

also @Talkless, could you tell me if the usb cable was connected while pressing the key combo?

@user0-07161
Copy link
Contributor

you just have to get it into the android recovery mode

@user0-07161
Copy link
Contributor

then connect it, and modify it

@user0-07161
Copy link
Contributor

ah yea i see now,
i assume the screen is black during that stage?
if so, disconnect the cable, get it into recovery and try again...

@Talkless
Copy link
Author

i assume the screen is black during that stage?

Sorry, I do not recall, and I haven't time to try that again. Maybe some time in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants