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...
Related
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
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 a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
IvanSantosPT said:
I have a ICOO D70PROII tablet, with a Rockchip 3066. After installing the Chainfire 3D driver, the tablet stucks at ICOO boot screen, even before the Android animation. I've started the tablet in recovery mode (appears the Android guy with the open bonnet and a red exclamation point).
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
The only way I can see to fix this is doing the job in ADB command line, but the only way that I know to uninstall the Chainfire 3D driver is in Shell. Could anyone help me in this problem?
I made a small and simple recording showing the driver, RKBatchTool error and ADB errors. (please copy the following link to the browser's URL bar, I can't post direct links)
youtube.com/watch?v=4iQi5SkKGe4
Best regards and thank you in advance,
Ivan Santos.
Click to expand...
Click to collapse
Did you make a backup B4 installing Chainfire?
ken.okech.94 said:
Did you make a backup B4 installing Chainfire?
Click to expand...
Click to collapse
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Use ADB
IvanSantosPT said:
I didn't. But even I've made a backup, I can't connect the tablet to the computer with RKBatchTool and I can't install the Rockchip 3066 driver, only the ADB Android driver (which i can connect via adb).
Click to expand...
Click to collapse
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
ken.okech.94 said:
Google a pre-made adb backup specifically for your tablet and restore it via adb. Or you can just use fastboot to flash a new ROM.
Click to expand...
Click to collapse
Did you read what I said?
I have the ADB drivers installed, i can access to almost everything in the ADB tool, except the "adb shell" command, even pushing up the mksh file to /system/bin.
The fastboot doesn't work, because the tablet turns off the screen, but appears in Device Manager an unknown driver, that I can't find the driver for it.
The RKBatchTool 1.3 and 1.5 doesn't recognize the tablet.
Click to expand...
Click to collapse
IvanSantosPT said:
Did you read what I said?
Click to expand...
Click to collapse
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
https://mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
ken.okech.94 said:
I think adb shell doesnt work because your tablet has not yet booted and will not be booted as long as it is in the current state.
Your only hope is RK Batch tool. Uninstall all current versions and the drivers you have in your computer and try reinstalling this and the drivers.
mega.co.nz/#!TIFwFCob!YniP23RpZH6hRj1Q-WSYvgQ4v28FUjU2qJ8b_4xLJXg
Your only hope!
Click to expand...
Click to collapse
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Y u so Ungrateful?
IvanSantosPT said:
Thank you, I reinstalled the driver and it worked. I installed the CWM 6.0.2.7 and all was working fine. Then I installed the CyanogenMod for RK3066 (cm3066.com) and the device doesn't boot, doesn't even shows the battery charger indicator and I can't mount or format anything in the CWM. I've lose the SD card, but I will borrow someone and try to reinstall the CWM, because I can't go to the RKBatchTool option.
Click to expand...
Click to collapse
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
ken.okech.94 said:
<<<<<<<<<<<<<<<<<<<<Hit thanks button if I helped , dude.
Click to expand...
Click to collapse
No problema. But now I can't even reflash the CWM or the ROM, the tablet is soft bricked.
UPDATE: To access to the Downloading Mode, I had to click Vol+ plus Vol- when I connect the device to USB port. I am trying to flash with official firmware.
UPDATE 2: I've noticed that the ROM that I installed damaged the kernel, and now I need someone's boot partition dump.
UPDATE 3: I downloaded the oficial ROM from soft.aoicoo.com/soft/show.asp?id=285 and flashed the device. Then the device started! I installed the CWM 6.0.2.7 and then installed DarkwaterV2 CM ROM (not required). The tablet is working better than never with 10279 points scored in AnTuTu Benchmark v3.3! Thank you all!
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
install kies if you have it installed already then uninstall it then install again
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
Since you're already looking in the right place, consider installing a custom recovery (such as philz) with odin and then flash the zip.
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
1337Dev said:
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
Click to expand...
Click to collapse
Take another shot by booting into a custom recovery, most give you adb access while in recovery.
If the phone is locked with usb debugging disabled you won't be able to get adb access.
Is there a way to root my phone without a pc?
When i connect my phone to my pc it will charge but it isn't recognized by the PC.
thanks
borgami said:
Is there a way to root my phone without a pc?
When i connect my phone to my pc it will charge but it isn't recognized by the PC.
thanks
Click to expand...
Click to collapse
No. You should install the drivers then your phone should be recognised, follow the root guide in this forum.
Sent from my Elephone P9000 using XDA Labs
Jonny said:
No. You should install the drivers then your phone should be recognised, follow the root guide in this forum.
Sent from my Elephone P9000 using XDA Labs
Click to expand...
Click to collapse
I installed the drivers but i couldn't see it in device driver.
borgami said:
I installed the drivers but i couldn't see it in device driver.
Click to expand...
Click to collapse
tbh the drivers are very temperamental, as I have windows 10 I had to restart the Pc disabling the driver enforcement. I had the same issue as yourself but I uninstalled and reinstalled and fiddled around a bit to get the drivers to work.
Now they are installed with no issues.
I actually used the "SP_Driver_v2.0" .. found HERE
I have also noted that another driver (Driver_Auto_Installer_v1.1236.00.zip) is HERE but I think I had issues with that driver (dont know why)
The SP_Driver_v2.0 worked for me .. hope you get it sorted, i know how frustrating it is ;0)
Technically you can perfectly root without PC. But you need to have a custom recovery on your phone. To get the custom recovery, you need to flash it, using a PC.
But once you have the recovery, rooting does not require a PC, just the su binary.
If windows isn't recognizing your device at all, it might be a bad USB cable? I had issues with windows - ended up using linux.
i used SP_Driver_v.2.0 but doesn't work for me for preload, i connect my device and in device managment it is with triangle and it disconnects after 2~3 seconds and goes in offline charging. is there any preload driver for win 10 64 bit that actually works?
Same problem with my P9000.
Unable to get SPFT to see my device.
Tried hours, disabling driver signature, secure boot, many different drivers and SPFT versions.
It's frustrating. Can't update OTA to 20160810 version, FOTA installed firmware from july and tells me it's up to date.
Can i install newest firmware without PC and no custom recovery from device storage?