Doov r17 pro

[yohanboniface]

Hi!

I'm trying to use mtkclient to install dumberOS/Dumbdroid) on a Doov R17 pro (cf https://dumbermini.com/blogs/news/how-to-install-dumbdroid-on-a-compatible-device).

I'm trying to do the backup with:

mtk rl --skip userdata path/to/empty/folder

(Using mtkclient from git)

The command just loops with "DeviceClass - [LIB]: Couldn't detect the device. Is it connected ?" or "DeviceClass - [LIB]: Couldn't get device configuration."

Given that this device has no volume buttons, I'm unsure about the process to enter BROM mode, so that may be the trick.

lsusb gives:

Bus 001 Device 099: ID 0e8d:20ff MediaTek Inc. r77

dmesg:

[45494.586394] usb 1-1: new high-speed USB device number 93 using xhci_hcd
[45494.700263] usb 1-1: device descriptor read/64, error -32
[45494.925189] usb 1-1: New USB device found, idVendor=0e8d, idProduct=20ff, bcdDevice= 2.23
[45494.925194] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[45494.925196] usb 1-1: Product: r77
[45494.925198] usb 1-1: Manufacturer: alps
[45494.925199] usb 1-1: SerialNumber: MTK0002601142209060
[45494.928509] hid-generic 0003:0E8D:20FF.001F: hidraw1: USB HID v1.01 Device [alps r77] on usb-0000:00:14.0-1/input0

The chip is supposed to be Mediatek MT6762.

Any suggestion ? Thanks!

[R0rt1z2]

Sounds like you haven't properly set up the udev rules (step 3 of README-INSTALL.md)?

[yohanboniface]

Thanks! I've received another answer, (seen in my emails but that that never appeared on the site, no idea why), saying:

You could try running mtkclient and also using the adb command in parallel
adb reboot edl
The phone will probably go into brom/preloader

And this worked. I'll check the udev rule next time I've to install on this phone. Thanks!