Database Info

Coby Kyros MID7015 Utimate Guide - Rooting, Android Market, ClockworkMod Recovery

This guide is written for new users who have NO experience with the Android OS or this device. I do not take credit for the patches/fixes. I am just documenting the process to make it easier for new Kyros tablet users.
Intro Steps
1. Put your device in USB Debugging mode.
From the main menu, press Settings, Applications, make sure Unknown sources is checked.
Press Development,and make sure that USB Debugging is enabled.
2. Turn on your WIFI by going to Settings, Wireless & Networks, check WIFI,and then Wi-Fi settings.
Select your Wi-Fi access point.
3. Open AppsLib,press the search hour glass icon,and type File Manager and press Search. I like the File Manager by mmaapp. Install it. Close AppsLib
Rooting your Tablet
By rooting, what they mean is that you will have full control over all of the files and folders on your tablet. This is a good and a bad thing. It is good because we can add programs. It is also bad because you can delete files that you shouldn’t…meaning you could kill your tablet if you mess around.
1.
From your PC, download z4Root and copy it to your micro SD card. Z4Root can be found here:
http://forum.xda-developers.com/showthread.php?t=833953
2. Put the sd card in your Kyros, and open File Manager.
3. In File Manager, Press SD card, then press z4root.x.x.x.apk (x indicates the version number), and press install.
4. Press Open
5. Z4Root will open. Press Permanent Root. Once it is done rooting, it will reboot your Kyros.
Installing the Windows software and ADB drivers
1. Download and install The Java Development Kit 6here (you will need to register on their site first):
https://cds.sun.com/is-bin/[email protected]_Developer
2. Download and unzip the android-sdk-r07-windows.zip file to the C: drive on your computer.
http://developer.android.com/sdk/index.html
3. Go to the android-sdk-windows folder that you unzipped
4. Launch SDKManager.exe
5. Under choose which package to install, click accept all. As a part of what it is downloading, it will download the Android USB drivers. This part will probably take like 30 minutes or more to complete.
6. Once the download is done, close the SDK Manager.
7. You should now see a folder called usb_driver. Open that folder.
8. You will see a file called android_winusb.inf. Open that file in notepad.
--- Alternatively you can just download an android_winusb.inf file with all of the modifications already done here:
http://rapidshare.com/files/435451166/android_winusb.inf
--- You would then just copy over the original android_winusb.inf file in your \android-sdk-windows\usb_driver folder.
--- Once the file is over written, skip to step 12
9. Right underneath the section labeled [Google.NTx86] paste in the following:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
; Android Eclair
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
10. Right underneath the section labeled [Google.NTamd64] paste in the following:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
---- Note --- Thanks goes to phygman for the code here to get the ADB driver working in XP!
11. Save the changes in the android_winusb.inf file
12. Plug in your Kyros device. Windows will still not find the driver for the device, but go into the Device manager, and select AndroidEclair, and update driver, browse my computer, let me pick from a list of device drivers on my computer.
13. Click "Have Disk" and browse to the c:\android-sdk-windows\usb_driver folder. Double click on android_winusb.inf.
14. Select Android ADB Interface.
15. It will then come up with some messages about this is unsigned or something, are you sure you want to do this, click yes or continue.
Then it will install the driver and detect the kyros.
Installing ClockworkMod Recovery to back up your Kyros.
1. On your pc, download recovery.img and place it on the root folder of your sd card (\)
Recovery.img can be found here: sendspace.com vkv6yz
2. Put the sd card back into the tablet and then plug the usb cable into the tablet, and then your pc. Make sure your tablet is powered on.
3. Open the Command Prompt in windows (cmd.exe)
4. Go to the android-sdk-windows\tools folder. Since I placed the android-sdk-windows folder on the root of my c drive, I typed cd\android-sdk-windows\tools and pressed enter.
5. Type adb shell and press enter.
6. Type su and press enter.
7. Type flash_image recovery /sdcard/recovery.img and press enter.
8. Press and hold the CTRL button, then press C.
9. Type adb reboot recovery and press enter.
10. Your Kyros tablet will reboot. Clockwork Mod Recovery will then load.
When Navigating through ClockworkMod Recovery, here are the keys:
Home is down
Menu is select
Back is back
11. Press the Home button until backup and restore is highlighted and press Menu.
12. Backup should already be selected. Press Menu.
13. It will now do a complete system backup. This is ESSENTIAL as it is VERY easy to play around and break your Kyros to the point that it is useless.
14. It will say “Backup complete” once the backup is done.
15. Reboot system now should be highlighted. Press Menu to reboot.
Installing Google Marketplace
1. Remove your sd card and put it back in your pc. Download the file gapps-passion-EPE54B-signed.zip and place it on the root of your sd card (\).
The file can be downloaded here: mediafire.com mjmmfmm0jez
2. Connect the usb cable to the Kyros and the pc.
3. Put the sd card back into the tablet and then plug the usb cable into the tablet, and then your pc. Make sure your tablet is powered on.
4. Open the Command Prompt in windows (cmd.exe)
5. Go to the android-sdk-windows\tools folder. Since I placed the android-sdk-windows folder on the root of my c drive, I typed cd\android-sdk-windows\tools and pressed enter.
6. Type adb reboot recovery and press enter.
7. It will boot into the ClockworkMod Recovery menu.
8. Press Home until install zip from sd card is selected and press menu.
9. Press Home until choose zip from sd card is selected and press menu.
10. Press Home until gapps-passion-EPE54B-signed.zip is selected and press Menu.
11. Press Home until Yes – Install gapps-passion-EPE54B-signed.zip is selected and press Menu.
12. It will then install the Google Market.
13. Once the install is done, it will say Install from sd card complete.
14. Press the back button
15. Reboot system now should be highlighted. Press Menu.
16. It will reboot the Kyros. You will see a Wizard appear. Go through the Wizard
17. You now have the Android Marketplace installed on your Kyros.
I would also recommend installing the AppBrain app from the Google Market. It gives you the ability to install more apps then just the Google Market alone.
Enjoy!
Jason Andreas

Wow! Thanks so much. Can't figure out how to give you a +rep...
Question: is it possible to do without an sd card? The stock model only comes with internal memory...

The Kyros MID7015 should have (mine does) an port on the side for a MicroSD card. You MUST have an sd card to do these steps. I don't see any other way to acheive some of the steps (particularly with ClockworkMod recovery) without having the MicroSD card installed. My understanding is that it will support a max of a 16GB sd card. I have a 16gb installed and it works great
Plus with a card that big you can put movies on it and watch them with the tablet. The movie player on this is really phenominal!

It looks like XDA stripped out some of my download links. I also posted this how to guide on another website. All of the links are in tact on their site.
http://tipstir.the-talk.net/rooted-...ackup-and-then-install-google-market-t689.htm

Is it possible to get this done through Windoze XP or Linux? I have the files needed and rooted kyros and a terminal on the device...anyway to bypass a pc completely? I just don't have windoze 7.

I came up with the ADB fix myself. I tried both Windows 7 and XP. Even though they are both 32 x86 operating systems, I just can't get XP to recognise the ADB driver. Without this driver, you can not run the ADB commands in Windows. I have heard that there are some programs that will let you type in the commands right on the Kyros, but I have not used them. You will need to find the file on your pc, and it will need to be in the .apk file format. Then copy to the sd card. Put the sd card in to the kyros and launch File Manager. You should be able to install the .apk file, then run the commands on the Kyros.
Again all of that is theory since I have not tried it.
As far as linux is concerned, I have NO idea. I'm pretty linux savy, but getting devices to recognize can be tricky to say the least.
This adb driver in reality would probably work in Vista as well. Surely you know someone who has Vista or Windows 7 that would let you run through the commands?

To make the Windows 7 or XP, x86 or x64 make these changes to your android_winusb.inf.
under the [Google.NTx86] section add :
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
under the [Google.NTamd64] section add :
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
I know these changes work on both windows XP and Windows 7
Phygman

Could someone please post a Factory ROM backup from their Coby Kyros-4G please?
Before there were these backup instructions above I messed up my WiFi trying to get the tablet to see an ad-hoc network. I have tried everything I can think of to try to fix it, with no luck.
So, if someone could post a backup of the ROM out of the box I would really appreciate it. That should solve my problem.
Thanks.

Effect of Rooting 2.1 on Future 2.2 Upgrade
I am new to Android. The Kyros is my first device, which I got while waiting for the Archos 101. My question(s):
If I root 2.1, what effect will this have on a future 2.2 upgrade.
1. will I have to restore to a baseline 2.1 system before upgrading?
2. will the 2.2 upgrade remove any customizations and downloaded apps?

just followed your tutorial and all went great!
Question: Now that I have finished this, what is required to update to the new firmware file recently posted on coby's website because I hear there are fixes to the touchscreen and wifi?

phygman said:
To make the Windows 7 or XP, x86 or x64 make these changes to your android_winusb.inf.
under the [Google.NTx86] section add :
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
under the [Google.NTamd64] section add :
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_DEED&MI_01
I know these changes work on both windows XP and Windows 7
Phygman
Click to expand...
Click to collapse
Ha! I replied earlier and looks like it didn't post.
Phygman...many thanks it seemed to work. However, I have a problem, for a minute I thought I bricked by tablet. I got to the point where I ran the command to reboot into recovery; however, it did not do anything and I did not have any clockwork options. I copied the image from the zip file into the root of sdcard. What do I do with all the other files? Was I supposed to just copy the entire zip instead of just one file? Does the whole archive get unziped, not unzipped? Or just a single file on the SD card? Also, prior to me trying this I upgraded the firmware of the device. Coby just posted it yesterday, so I'm not sure if that has anything to do with it because everything else like rooting went well.

Also, prior to me trying this I upgraded the firmware of the device. Coby just posted it yesterday, so I'm not sure if that has anything to do with it because everything else like rooting went well
Click to expand...
Click to collapse
I'm also wondering if updating prior to following these instructions will affect the outcome

Deenybird said:
I'm also wondering if updating prior to following these instructions will affect the outcome
Click to expand...
Click to collapse
It will not affect your outcome. In fact, if you try to do the update after these steps, you will have to redo each of them. Also, clockwork will not install the update without modification.

adamdietrick said:
It will not affect your outcome. In fact, if you try to do the update after these steps, you will have to redo each of them. Also, clockwork will not install the update without modification.
Click to expand...
Click to collapse
I agree with you but I can't figure out what went wrong with Clockwork.
Anyone added clockwork that can tell me what to do with the zip file? I tried extracting all contents of the zip on the root of sdcard and I still don't get anything. Can anyone give me a pointer or two?

moon303 said:
I agree with you but I can't figure out what went wrong with Clockwork.
Anyone added clockwork that can tell me what to do with the zip file? I tried extracting all contents of the zip on the root of sdcard and I still don't get anything. Can anyone give me a pointer or two?
Click to expand...
Click to collapse
ok, I figured it out. I completely bypassed using a pc and did it all within the tablet using a terminal. Finally got to the recovery menu.

anyone know if there are any 2.2 modded roms for this device? google search yields nothing.

Thanks OP. You're procedure worked like a charm!
Now, a procedure for Froyo

Market Place bloat
Does anyone know of a way to either modify the market place zip install or remove the bloat that comes with it ? I installed according to all the instructions and it worked great, but some of the apps don't work like voice search so I'd like to get rid of that, and also the amazon mp3 app and some other apps that came with it that are just bloatware for me.
Any help or hints appreciated greatly.

flashed 3 now
I have done this with 3 Coby tablets now, I will be glad when there is a custom kernel to do some over clocking, since Coby thought it was a good idea to throttle back to 725mhz. I personally went ahead and did the Coby firmware update before I did any other flashing. This is a GREAT thread mega props! These are certainly not the best tablets in the world but for the price they aren't bad...

Thank you for the walk-thru! Made the process very easy.
Anyone have any luck getting Latitude (google maps) working on this? I can't find where to enter my google credentials so when I click "Join Latitude" all I get is logon failed.

[Q] CMW (internal storage) no ROM (on SD) on TF101 b80

hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "

im on recovery and when i run adb devices it just blank. any walk through is much appreciated!

Do yo have USB debugging on?

I dont know because i was about to flash a new rom so i did a full wipe already

Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.

i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe

i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.

I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!

Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!

If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.

thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...

still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.

yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz

monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.

[Q] Windows will not install drivers for tf101

I have a B90 TF101 and I am able to get into recovery mode. I have no ROM on my internal SD card and have wiped and formatted everything. I have read that it is possible to push a file using ADB while in recovery.
However I am not able to see my device when I use the adb devices command. I noticed that the drivers for the transformer are not installed. So I tried to install them and it tells me that windows can't install. I am pointing the installer to the MTP devices driver folder.
How do I get the drivers to work so I can use ADB or can I set up ADB in Linux and not have to worry about the drivers?
edit: I forgot to mention I am running windows vista.

Hi! Search in transformer's support page, you can find the drivers there

Are you saying that the drivers in the MTP folder are not the right ones? I got them right from Asus' website. Which drivers should I be using?

Ageesaman, did you ever get the drivers working? I had the exact same problem (got adb working as far as listing devices, but then it returned with a blank line after "adb devices" in cmd window). I downloaded the ASUS site's USB drivers download as well as every other utility from that site; I also tried external sources; finally, I tried manually updating by pointing to the unzipped MTP folder - nothing worked. I used both 64 and 32 bit Windows 7 machines. I am stuck in the cwm recovery loop so I can't do much troubleshooting. I tried searching dozens of sites for several hours but came up short.
Thanks in advance for any help offered.

Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.

Ageesaman,
Unfortunately I know nothing about Linux, but what finally got it working for me was starting the installation of PDANet for Android. I saw it look for and install the driver, then I got a ADB confirmation. I then canceled the PDANet install. If you decide to go this route and get error messages in the cmd window, retry "adb devices" up to 3 times. In the meantime, I hope you get your Linux answer. Good luck.

I will give that a try. Is PDAnet something from Asus? I will do a search and see if I can find it.

ageesaman said:
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Click to expand...
Click to collapse
Yes, I can confirm the TF101 works with ADB without drivers on Ubuntu linux [I am on 11.04]. The current [stable, with 12.04 betas] Ubuntu version is 11.10, and you can download it to a live CD and run it off the CD without installing it.
I just got my tf101 the other day and I tried using adb [and older version], and it did not show up. Then I downloaded the tf101 root.zip file, and tried the adb within that folder, and it worked.
I've uploaded it to mediafire:
adb-1.0.29 http://www.mediafire.com/?hqwxbljs2gbpfxe
md5 64c4afbab6d2f769ddbb229f0247cf8a
update: newest adb is 1.0.31 http://www.mediafire.com/download.php?vcvc4dxkdd57695
md5 ed5c8f9a221cae0cb24d6cdc8b76d396
download, and run
chmod +x ./adb-1.0.29
to make it executable

That worked! I can now connect to my device with ADB. Thanks for that pdanet advice.
Now I just need to figure out how to push the file. Can't seem to get it to work. Here is what I am typing in the cmd line.
adb push rom.zip /sdcard
The rom I am trying to push is in the Platform tools folder that I am using to access adb. Does anybody know what I am doing wrong? Any help would be awesome.

is the rom.zip in the same directory as you are in (cd <path>)?
What does it say when you try to transfer it?
You can also try to push it to the full path (/mnt/sdcard/)

The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.

ageesaman said:
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
Click to expand...
Click to collapse
It's probably because /sdcard is a soft link to /mnt/sdcard/
if you did /sdcard/, I think it should probably work.

You sir are the man! Thanks for your time.

To get the process all in the same place for anyone else who may need this here you go. Just to make it clear.... This is what I did on my device and it worked. It may or may not work for you but maybe it's worth a try.
1. Downloaded SDK and Java JDK.
2. Used PDAnet to force windows to install the correct ADB device drivers.
3. When the drivers where installed and ADB was working I used this command to push the .zip file to the internal sd card.
adb push rom.zip /sdcard/
Just a few notes for this.
ADB was not working well at first because I had Asus sync running in the background. Make sure this is off.
Also make sure you put the file you are trying to push in the same directory you are using for ADB. For instance I used C:/android-sdk/platform-tools/ to access ADB so the file had to be in that folder in windows explorer.
To make it easier to type (I had to do this a lot while troubleshooting) I changed the name of the rom I was trying to push to rom.zip. This made typos less of an issue.
Make sure that you put the file extension (.zip in my case) in the ADB command even if it doesn't say it when you look at the file in windows explorer.
I think that is it in a nutshell. I hope this helps anyone else who needs to push a rom.
Good Luck

This method in this post didn't work for me, but this one did: http://forum.xda-developers.com/showthread.php?t=1689193

I set Windows to look for driver in c:. After a while one was installed and worked.

What I did on windows 7
Go to Device manager
Find transformer , right click on faulty marked unit.
Select properties
go to tab driver
update driver
Select browse
select path to the subfolder ANDROID ( containing usb drivers from asus )
include subfolders
Windows will find to alternatives , choose xxxx ADB
Windows will complain, ignore
done
/Claes R
W

[Q]Problem with MTP (and help with a workaround)

Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys

I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.

m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php

I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media

m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html

Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...

[Q] Installing USB Drivers for ADB in Recovery

It's been bugging me for a while that I can't use ADB while in recovery. It's a matter of getting the drivers installed correctly, I think, I just don't know exactly how to do it. When the phone is booted I can use ADB and MTP just fine. Odin sees my phone in download mode as well. The only problem is in recovery. I'm using TWRP 2.3.3.0, but I've had the problem on previous version of TWRP and CWM. I have the Samsung USB drivers installed, and when the phone is booted Device Manager (in Windows 7) says the drivers being used are from Samsung. However, when in recovery Device Manager shows SAMSUNG_Android_SCH-I535 with the yellow '!' and says no drivers are installed. I can try to choose the drivers to install manually, but if I point to the Samsung USB Drivers folder, Windows can't find the right drivers automatically and there are 25 subfolders with somewhat cryptic names, so I don't know which to choose.
Does anyone know how to get ADB working in recovery?
EDIT: Got it working. I don't know anything about how drivers work, but I dug around a little and it turns out the device shows different Hardware IDs when booted versus when in recovery. The drivers .inf has to contain one of the Hardware IDs given by the device so after finding the driver being used by Windows (by searching for the Class GUID given in the driver details when the phone was booted and searching through all the .infs in the Samsung drivers folder for the matching string) I just added a line with one of the Hardware IDs given in recovery so Windows would install the driver. I tested with adb devices, adb shell and adb pull default.prop and each worked fine.
For anyone interested the driver being used is in 25_escape. In the file ssudadb.inf just add the line
Code:
%CompositeAdbInterface% = ssud.Install, <Hardware ID>
under [Google.NTx86] and [Google.NTamd64], where <Hardware ID> is one of the Hardware IDs given by your phone when in recovery. In Windows, go to the Device Manger > right click your phone > Properties > Details tab > Hardware IDs in the drop down. Mine was
Code:
%CompositeAdbInterface% = ssud.Install, USB\VID_18D1&PID_D001
Then update the driver, browse for drivers, pick the 25_escape folder, and you're good to go. The driver will fail a security check because you've modified it, I ignored it.
I imagine this could cause a problem if some other device uses the same Hardware ID (e.g. if it's some sort of generic or default one that's given in recovery) but I'll cross the bridge if I come to it. There may be some safer way to force driver installation.
EDIT: After doing this you'll get a warning when you plug your phone while it's booted. It will say something to the effect of Hardware ID missing or not being able to identify the device plugged in. This isn't a problem though, ADB and MTP still work fine and the device is identified properly in Device Manager.