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.
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...
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.
I have an old multipad PMP3384B with seriously old and slow Android 2.3. I tried to update it following the process below and using a rooted image.
What you need:
-get Rockchip Batch Tool from HERE (contains USB drivers)
-get a firmware:
a) PMP3384BRU_20111206_V1.1.9_root -prerooted image, no other changes
b) PMP3384BRU_20111206_V1.1.9_root_607Mb_free - 607 MB for /data, prerooted, Golauncher, Gokeyboard, Adobe Reader, CoolReader, Dolphin browser HD, ButtonSaviour- only for RockChip Batch Tool flashing
How to flash:
1. fully charge your MultiPad
2. backup internal flash- it will be erased
3. unpack Rockchip Batch Tool and launch it as admin
4. press and hold Reset (on the back), plug USB cable, release Reset
5. there should be a popup asking for drivers- they are placed in Rockchip_Batch_Tool_v1.4\drivers\[windows version]. If there is no popup go to Device Manager and install drivers
6. load firmware .img file to Rockchip Batch Tool and click Update button
After I completed this process rockchip batch confirmed that the update was successful with no errors but I can no longer power up the tablet. I have tried the reset button but no joy. I also tried following the process again as the tablet is still being detected by Rockchip batch tool when plugged into my pc via usb. I'm downloading the original firmware from the prestigio site now so once that is done I will try restoring it.
Any other ideas would be much appreciated
EDIT : Problem resolved, reinstall of firmware from prestigio site worked.
find my post on this topic http://forum.xda-developers.com/showthread.php?t=1403956 hope it will help you !
I have been using mtkclient from my PC to unlock bootloaders and flash images onto mt8163 tablets (hat-tip to Bjoern Kerler for developing this amazing tool).
In my current situation, it would be very helpful to be able to setup one of these tablets to flash other tablets of the same make (mt8163 chipset) using termux. I was able to successfully setup the mtkclient environment on termux. However, when the CLI asks to connect the device, it won't detect it in BROM mode.
I'm able to connect via OTG for file transfers and the like, so the device is OTG compatible. However, as stated above, the CLI just doesn't detect anything being connected when I try BROM mode.
On the PC, I have to install mediatek vcom drivers to get the device to connect in BROM. Obviously there is no equivalent for this going from android to android.
I was hoping someone could shed some light on the challenge I'm facing. Such as whether this is a hardware limitation, or something I could potentially overcome with some software manipulation.
Thanks!