I have a noname chinese made Rockchip 2918 based tablet PC that I am trying to root so I can use some tools to increase performance/etc.
I have ADB and the Android SDK installed.
I have the most recent Rockchip drivers installed.
I have Development Mode turned on on the tablet.
When I plug the device into USB, nothing happens other then the windows notification sound to let me know something was plugged in. No "searching for drivers" nothing. When I go to ADB and do a "ADB Shell" command, it says device not found.
If I boot the tablet into Recovery mode, connect USB, and repeat the above procedure, I get the same result.
Is there a seperate USB Recovery mode I need to get into? I read about this on other RK2918 based tablets and I have tried all the methods to no avail. Volume up and Power is the only combination that does something, and that just takes me into normal recovery mode.
Just a side note, If I connect my HTC Evo 4G LTE and try the shell command, it finds it instantly.
Any ideas on what I am missing here?
Goanna said:
I have a noname chinese made Rockchip 2918 based tablet PC that I am trying to root so I can use some tools to increase performance/etc.
I have ADB and the Android SDK installed.
I have the most recent Rockchip drivers installed.
I have Development Mode turned on on the tablet.
When I plug the device into USB, nothing happens other then the windows notification sound to let me know something was plugged in. No "searching for drivers" nothing. When I go to ADB and do a "ADB Shell" command, it says device not found.
If I boot the tablet into Recovery mode, connect USB, and repeat the above procedure, I get the same result.
Is there a seperate USB Recovery mode I need to get into? I read about this on other RK2918 based tablets and I have tried all the methods to no avail. Volume up and Power is the only combination that does something, and that just takes me into normal recovery mode.
Just a side note, If I connect my HTC Evo 4G LTE and try the shell command, it finds it instantly.
Any ideas on what I am missing here?
Click to expand...
Click to collapse
Go to my post http://forum.xda-developers.com/showthread.php?t=2362844 use this tool to root the device then use adb wifi. Is the only method to have adb on those rockchip devices without disassambling them. Do not worry the CWM is for all RK2918 devices.
Related
Hello People!
I have a serious problem with my brothers phone. It doesn't start and also doesn't show the Android with the red triangle or let itself turn into the recovery mode. When I attach the phone to my computer with the USB Cable, the PC only detects an "Unknown Device". When I try to install the drivers from the Android SDK it only says that the latest drivers for "Unknown Device" are installed.
I am not sure if it's a hardware problem or a software problem. But I think that my 12 year old brother has installed a virus, because he had problems with various standard apps before.
I also tried to go to platform-tools and type adb recover mode, or fastboot devices (which doesn't show a single line).
Any help appreciated
mfg Kafioin
bump
bump
You could try the ZTE Update tool. But if you can't pull your device up using adb I'm not sure it'll work. Sorry
I have had my new Visture V97HD Retina display tablet for a week now and I am having few problems understanding what is happening with drivers/adb/fastboot and recovery. I managed to install the Win 8 RK3188 rockchip driver, but had to do it with USB debugging/disabled and driver signing disabled. Then I installed the rockchip update.Then I installed PDAnet 64bit and run a RK3188 root script and all seemed to have worked OK. Rootchecker now tells me the device is rooted. The trouble is I don't have any recovery. When I try to boot into recovery I get the little Android with red exclamation mark. Also when I run ADB cmds the device is not recognized. When USB debugging is enabled and I attach the device. I get message from the device to connect via USB, then another question asking me to press here for USB storage. When I accept and connect I can see the device in explorer but still not recognized in ADB. What is happening and what can I do to fix this?
Confused
Mossey said:
I have had my new Visture V97HD Retina display tablet for a week now and I am having few problems understanding what is happening with drivers/adb/fastboot and recovery. I managed to install the Win 8 RK3188 rockchip driver, but had to do it with USB debugging/disabled and driver signing disabled. Then I installed the rockchip update.Then I installed PDAnet 64bit and run a RK3188 root script and all seemed to have worked OK. Rootchecker now tells me the device is rooted. The trouble is I don't have any recovery. When I try to boot into recovery I get the little Android with red exclamation mark. Also when I run ADB cmds the device is not recognized. When USB debugging is enabled and I attach the device. I get message from the device to connect via USB, then another question asking me to press here for USB storage. When I accept and connect I can see the device in explorer but still not recognized in ADB. What is happening and what can I do to fix this?
Confused
Click to expand...
Click to collapse
I still really could use some help!
Mossey said:
I still really could use some help!
Click to expand...
Click to collapse
I've successfully rooted v97hd using how2 on vondroid.com. it worked for original FW and also for the latest from 05/05/13. But I need to get some image to flash. what did you want to flash ? I have the same issue with the bootloader...
As the title suggests, bootloader unlocked no problem, tablet was connecting to ADB at the time, tried to flash recovery which as far as I can tell was not successful (I can't boot to recovery, get the injured Android icon), now I can't connect to ADB (get the "List of devices attached" result). So I'm completely stuck, can't move forward, can't go back to stock, what do I do?
Edit: Apparently it's an issue with my PC, my wife's PC worked fine, why it worked to unlock the bootloader and then stopped I have no idea. Can anyone link me to a solution to get ADB working on my PC again? I tried removing/re-installing drivers, rebooting, you name it, no luck.
With your device booted into recovery or the system do you get anything in device manager? If you get a device with a yellow exclamation mark, right click it. Go to where it allows you to choose a driver from a list on your computer. Select adb android composite (or something like that)
Sent from my Nexus 5 using XDA Free mobile app
Thanks for replying.
So before unlocking the bootloader, with USB debugging enabled I could get the tablet to connect using the ADB driver and could access it with ADB but could not access storage for file transfer, with USB debugging disabled and switching the driver manually to the MTP driver I could access storage but not ADB. I have had other device drivers installed on this PC for my Galaxy phones, I had issues initially with the tablet connecting but showing a yellow exclamation mark, then I removed all of the Android USB devices using USBDeview and installed the 15 second ADB tool to get it working, I'm on Windows 8.1 BTW.
After unlocking the bootloader, with USB debugging enabled I cannot get the tablet to connect using the ADB driver and but it does show as an ADB device with no yellow exclamation mark, I just get the "List of devices attached" result and anything that tries to access the device via ADB hangs or fails. I can still switch the driver to MTP and access the storage just fine.
My wife's PC is a Win7 box and has never had android drivers or ADB installed, I used the 15 Second ADB installer on her PC and the tablet works for ADB and storage access with USB debugging turned on, so there's something I'm missing that needs to be wiped out or reset on my box.
Hello, I own a RCA Viking Pro 10 tablet with Android 6.0 installed (RCT6303W87M7). I am having a lot of trouble rooting it for two key reasons.
1. It seems to be incompatible with most "One-Click" root applications.
2. It requires a special type of A-A USB cord, so it can not be connected to any computers.
I have looked through many root methods, but none of them seem to work. Any suggestions would be appreciated.
I have the exact same tablet and came upon those same two problems. I have, however, purchased a USB A-to-A cable and tried connecting it to a PC. I noticed that if the tablet is on when you connect it, the PC wont recognize it, but, if the tablet is turned off, the PC sort of recognizes it and begins to download and install drivers. The problem is is that once the drivers and installed, I can't find the tablet in my device manager.
One-click APKs don't work. I've tried, King Root, Kingoroot, One-Click Root, Towel Root, iRoot and virtually any and every one-click root that I come upon in the wild. I've also tried the PC root method with the USB A-to-A cable. I've used iRoot, King Root and Kingoroot. These obviously don't work because of the PC connectivity issue mentioned above.
It's a real nice tablet to dabble with, just a damn shame that there is virtually no information on it out there. If you do a google search, you will more than likely end up at this thread: https://forum.xda-developers.com/an...e-rca-viking-pro-rct6303w87dk-t3325158/page52 . Unfortunately, this thread is dedicated to an older model of this tablet running Lollipop. The only thing to do would be to keep searching and re-searching until we find something on it. Hope this helps.
so i'm still trying to root the RCT6303W87M7. i'm not really trying to install custom roms on it, i just want root access. so to update, i finally got my pc to recognize the device; but i dont beleive that it's recognizing it properly. here's what i did, making sure that USB debugging & OEM unlocking are both enabled in the developer options, i did this:
1. hold the 'power'+'volumeUP' buttons until you get into recovery mode
2. once in recovery mode, go to and select 'Reboot to bootloader'
3. when the 'Fastboot mode' message appears at the bottom of the screen, plug in the USB-A male to male cable to the PC
4. if you have your device manager open, you will notice that it is recognized as 'Android Phone'/'Android Sooner Single ADB Interface"
i tried rooting with three different 'one-click root' pc applications: iRoot(v1.8.8), Kingoroot(v1.5.0), and King Root(v3.5)
these are the results i got:
-iRoot: it connects but the message reads 'Not support mode'
-Kingroot: it detects the device and trys to connect but gets stuck in a loop trying to connect
-Kingoroot: this detects the device as 'HTC Device'. i click the 'Root' button and it trys to root, but it only gets to 19% and then it fails
i'm theorizing that maybe if i get some different drivers for the pc or maybe making sure that the 'one-click root' applications are the latest versions might help. i dont know, we'll see.
again this is for the RCA RCT6303W87M7 running Android 6.0.
if anyone tries this and has more success, please let me know.
I am trying to root my old phone Samsung Galaxy core prime G360h so that I can gain some confidence to change the stock rom of my main device. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letti g me to post imaves
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
On MediaTek devices you need Preloader VCom Driver so your PC would detect your phone on fastboot but on Qualcomm ( which is your phone chipset ) i don't know what driver is required ...