RCA Viking II, RCT6603W47M7 Factory Blocked ADB Usage
The RCA Viking II, RCT6603W47M7, came to me crippled by default. User cannot connect the device via USB.
I found an interesting item in the device's 'build.prop' -
"# USB Charge only function
ro.sys.usb.charging.only=yes".
Of course, I couldn't edit it because the device isn't rooted. It also has android 6.0, which makes it very difficult to root with a root app.
I tried everything I could possibly think of to no avail. I then installed "wifi file transfer pro" (Google Play), designed to allow file transfers between android and pc via a web browser. It works fine!
I then tried adb via wifi. Heres what occured:
1. Without the app
adb connect 192.168.1.39:5555
adb connect cannot connect to <ip>: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)
2. With the app
First command/result:
adb connect 192.168.1.39:1234
connected to 192.168.1.39:1234
Second command/result:
adb shell
error: no devices/emulators found
Conclusion: ADB works partially. Catch 22: PC still needs usb connection, even temporarily.
If The Canucks at RCA can get away with blocking ADB, we are dead in the water!
What's next? Any answers/suggestions?
The RCA Viking II, RCT6603W47M7, came to me crippled by default. User cannot connect the device via USB.
I found an interesting item in the device's 'build.prop' -
"# USB Charge only function
ro.sys.usb.charging.only=yes".
Of course, I couldn't edit it because the device isn't rooted. It also has android 6.0, which makes it very difficult to root with a root app.
I tried everything I could possibly think of to no avail. I then installed "wifi file transfer pro" (Google Play), designed to allow file transfers between android and pc via a web browser. It works fine!
I then tried adb via wifi. Heres what occured:
1. Without the app
adb connect 192.168.1.39:5555
adb connect cannot connect to <ip>: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060)
2. With the app
First command/result:
adb connect 192.168.1.39:1234
connected to 192.168.1.39:1234
Second command/result:
adb shell
error: no devices/emulators found
Conclusion: ADB works partially. Catch 22: PC still needs usb connection, even temporarily.
If The Canucks at RCA can get away with blocking ADB, we are dead in the water!
What's next? Any answers/suggestions?
Facebook
Twitter
Instagram