Has anybody got a Sony Tablet S being recognised by adb?
It seems to be blocked :-(
And yes, I have done all the usual enable USB debugging etc...
I can not use it for development :-(
---------- Post added at 12:56 PM ---------- Previous post was at 12:06 PM ----------
Managed to sort it myself
you need to cd to your .android folder (on a mac, this is ~/.android) and then type
echo 0x054c > adb_usb.ini
Where 0x054c is the vendor id for Sony (I got that by looking at the attached evices in the 'About this mac' preferences)
Now adb sees the device - woohoo
would this apply if i just wanted to use it to transfer music and such? I am not incredibly savy with coding but i tried to enable debugging and all that. I am justnot sure whats the problem.
No, the Android File Transfer program still works without this
Good to know it can be used to dev on. Anyone have any information on how to send data out using the IR blaster, I dont think there is support for it in the native android libraries from what I can see?
The following procedure has confirmed that ubuntu 11.04.
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Kaz Taguchi said:
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Click to expand...
Click to collapse
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Found a way on Windows!
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Bojanglez said:
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Click to expand...
Click to collapse
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file.
Works lime a charm now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
CaptainJack87 said:
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Click to expand...
Click to collapse
Done loading packages.
Preparing to install archives
Downloading Google USB Driver package, revision 4
File not found: C:\Program Files (x86)\Android\android-sdk\temp\usb_driver_r04-windows.zip (Access is denied)
Done. Nothing was installed.
I tried downloading and installing
(Can't post links)Download: Android USB Drivers - Original (Firmware 1.0)
But when I try to install the drivers for the tablet through device manager it says:
The folder you specified doesn't contain compatible software... ...Windows for x64-based systems.
Apparently this driver is only for x86. But after googling "download Google USB Driver Package" that's all I can find.
Got it...
At least I was able to "enable it" through the USB port,
thanks to this exercise in frustration.
Alas no root screen cap still didn't work.
It flashes wildly and does nothing.
Anyone happen to know the proper command line in system variables for win 7 for adb should be?
I haven't used adb in forever, and I think alot of peoples issues with adb is in the fact they cannot use it outside of the android/android-sdk/platform-tools directory. As in you can just type adb shell, adb start-server, adb kill-server from the root dir. I had it set up before, but with a new comp now, and I forgot what it was before.
whats going wrong
i cant seem to get the device driver on my adb at all. no matter what i do i cant get the usb driver sorted. this is where i get stuck"
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
home directory???? every time i try this from home directory i get nothing.
this is my problem.... i dont have this file or entry. what is the entry?????? o notpad doc??,
adb_usb.ini file was missing the 0x54c entry! <<< what is this. a screen shot goes a loooong way.
Adb was simple with my x10 and sgs2 but man this is giving me the ****s.
can someone please post a few simple screenshots of what directory is supposed to be where please?
---------- Post added at 08:39 AM ---------- Previous post was at 08:21 AM ----------
what does this mean?
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file
?????????
I've created an automated ADB driver installer for the Sony tablets.
No more messy, time-consuming SDK install.
http://forum.xda-developers.com/showthread.php?t=1488822
Official Sony instructions
Looks like Sony has posted official instructions for setting up ADB with the Tablet S:
esupport.sony.com/US/perl/support-info.pl?info_id=878
After following their instructions I still had to go to Device Manager, choose to Update the driver for my tablet, and point it to the SDK/usb_driver folder. After that it works great.
debug
Hey guys i have installed the android sdk and the sony s drivers from the official site as dreadengineer posted. but after run the adb devices command i was unable to saw my device.
After that i tried the automated installations that BluechipJ posted, but the result was the same i cannot see the devices neither on eclipse or adb devices command.
i want to debug my application on this device but i could not access it. Can someone help me.
I have a windows 7 x64 OS. i'm able to debug on htc phone and also on the super slower emulator
This guide is for getting your tablet rooted from Linux. It is similar to the guides made by Indirect and t-r-i-c-k for Windows and OS X respectively.
Get ADB working
If you are running a 64 bit system then you will need to have the 32 bit ncurses library installed.
For Arch Linux:
Code:
sudo pacman -S lib32-ncurses
For Ubuntu (can someone check this?):
Code:
sudo apt-get install lib32ncurses5
Now you will need the Android SDK. you can get it from http://developer.android.com/sdk/index.html
Extract the downloaded SDK to a location of your choice. This will give you an android-sdk-linux directory.
Now we need to install the platform tools. Run the android-sdk-linux/tools/android program and install at least the "Android SDK Platform-tools"
Optionally, you can install the Nook Tablet/Color SDKs.
Choose Tools->Manage Addon Sites
Click the "New..." button and add http://su.barnesandnoble.com/nook/sdk/addon.xml
Also add http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Now install the Nook Color and/or Nook Tablet SDKs.
You will have to manually edit or create the ~/.android/adb_usb.ini file. Make sure it contains the following line:
Code:
0x2080
Now we need to set up the udev rules for your Nook. These instructions work for Arch Linux, let me know if they don't work for your distribution.
create an /etc/udev/rules.d/51-android.rules file and populate it with:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_fastboot"
run the following commands:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
$ sudo udevadm control --reload-rules
reference:
https://wiki.archlinux.org/index.php/Android
Enable USB debugging on your Nook
Open up your web browser on your Nook and go to http://comptonsoft.com/test and Download AppMenu.
reference: http://forum.xda-developers.com/showpost.php?p=19421107&postcount=18
After the download completes, open the AppMenu.apk from the notification area (tap on the lower left corner of the nook screen where the three down arrows are)
Choose "Package Installer", when it says "Install blocked" choose "Settings"
Check off "Unknown Sources" and then choose "Development"
Check off both "USB debugging" options and uncheck "Auto Mount"
Bring up the notification window and tap on the AppMenu.apk and install with package installer. This time it should work.
If you ever need to get back to the appmenu you can now access it from the search screen (make sure to show all results). Sometimes the thing likes to reset it's debugging abilities.
Perform a temporary root
Now the fun begins. Let's get the rootkit. Download the zergrush binary from http://forum.xda-developers.com/showthread.php?t=1296916
Extract the zergRush file from the zip and remember where you put it. I put mine in ~/Downloads
Adjust the following instructions according to your location:
Plug in your nook, you should get a beetle icon in the notification area.
Open up a terminal on your computer and change to the android-sdk-linux/platform-tools directory, and do the following commands:
Code:
$ cd ~/android-sdk-linux/platform-tools
$ ./adb kill-server
$ ./adb start-server
$ ./adb push ~/Downloads/zergRush /data/local/
$ ./adb shell
We are now in the nook.
Code:
$ chmod 755 /data/local/zergRush
$ /data/local/zergRush
zerg does it's thing and if all goes well, says it's restarting as root and kicks us out of adb
Code:
$ ./adb remount
It should say "remount succeeded" if the root worked.
Install su to make the root permanent
In order for the root to persist after a reboot we need to install superuser. Get it from http://androidsu.com/superuser/
Make sure to get the gingerbread version. Extract the contents of the zip somewhere, say ~/Downloads/superuser/ and do the following:
Code:
$ ./adb push ~/Downloads/superuser/system/bin/su /system/bin
$ ./adb push ~/Downloads/superuser/system/app/Superuser.apk /system/app
$ ./adb shell
# chmod 6755 /system/bin/su
# ln -s /system/bin/su /system/xbin/su
# chmod 644 /system/app/Superuser.apk
# exit
Install google apps
Of course we are gonna want to get access to the market and what not.
Get google apps from http://goo-inside.me/gapps
Extract somewhere, say ~/Downloads/gapps and do the following:
Code:
$ rm ~/Downloads/gapps/system/app/SetupWizard.apk
$ ./adb push ~/Downloads/gapps/system /system
$ ./adb shell
# chmod 644 /system/app/*
# chmod 644 /system/lib/libvoicesearch.so
# chmod 644 /system/etc/permissions/*
# chmod 644 /system/framework/*
# exit
$ ./adb remount
$ ./adb reboot
When the nook comes up again, choose search, tap the g in the upper left, choose apps, type in market. Choose to add an account, create/sign in.
I had to back out of the market in go back in again a couple times to get the "agree to license screen". If the market just sits there loading for a while, try that.
You can run any apps you install any time by searching for them.
Some tips for getting the most out of your tablet:
I suggest installing a launcher from the market. I use zeam. I think launcher pro and adw launcher are both popular choices also. These will allow you launch apps directly, instead of searching for them.
The Homecatcher app seems to be getting a good reception I haven't had a chance to try it yet, but i plan on it. It allows you to use a different launcher than barnes and noble's by default
Install busybox from here. You'll need to have an sd-card in your tablet for the install to work, but don't need it afterwords (just throw the one from your phone in or something if you don't have one).
To get adbd running as root (to do things like remount or push to system folder) you can run zergRush again as in the temporary root step. I had to su, and then run zergRush, and adb seems a little flakey and kicked me out from time to time when i did it, but it worked. ADB root goes away every time you reboot still.
Happy trails.
Worked great
I'm a noob to both linux and android and your directions worked like a charm, Thanks so much.
flawless
absolutely flawless instructions. thank you!
Works good but now I can't "adb remount" because I get an "operation not permitted", and thus I can't "adb push".
Is this normal behavior after this root?
The only reason I noticed was from attempting to install the newer talk app which is probably possible by other means but I haven't found the right answer out of about a billion search results.
Also the part about installing the color sdk stuff or adding the adb_usb.ini line isn't accurate I don't think. I had to run "android update adb" and then the file was updated, which is the same as editing the file but I think it gets autocreated or updated from something else possibly.
firephoto said:
Works good but now I can't "adb remount" because I get an "operation not permitted", and thus I can't "adb push".
Is this normal behavior after this root?
Click to expand...
Click to collapse
Yeah... :-(
You'll have to su and remount by hand. The following should work:
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# exit
$ exit
$ adb push teh_files
Sadly after you reboot the adb deamon doesn't have superuser permissions anymore and can't do things like remounting filesystems.
I'm not sure why this is tbh. maybe because the SUID bit isn't set, or the version of adb in the tablet is gutted?
I'm sure people would be grateful if someone figured it out (hint hint), it's gonna cause all kinds of annoyances like this in the future no doubt :-/
firephoto said:
Also the part about installing the color sdk stuff or adding the adb_usb.ini line isn't accurate I don't think. I had to run "android update adb" and then the file was updated, which is the same as editing the file but I think it gets autocreated or updated from something else possibly.
Click to expand...
Click to collapse
Weird. It definitely wasn't on my system after installing tablet sdk and before installing the color sdk and definitely was after installing the color sdk. i'll change the original post to get rid of that part, since it's kind of unnecessary anyhow.
There's something that seems more locked down (while allowing root) so maybe it's intentional to maintain some security in certain situations. (guessing).
I did mount the filesystem rw but that still doesn't allow the push. Seem like the standard adb shell user doesn't have the permissions to do the normal things and then the root user doesn't have the commands even though the $PATH is correct.
So some permission bit set strange somewhere I guess but I haven't found it yet.
Oh wow, you are right. And it gets even better...
You can push to the /mnt/media/ directory...
And now for the good news...no cp command, and mv doesn't work to move files apparently.
As a temporary work around you can use cat >< I feel so dirty saying this:
Code:
$ adb push teh_file /mnt/media
$ adb shell
$ su
# cat /mnt/media/teh_file > /system/teh_file
Things are getting really hackey now :-/ maybe i will have to look into the adbd issues after all. Not tonight though.
I'll update the guide tomorrow to get busybox installed so we have a cp command. The market app didn't work for me, but I don't have an sd card in mine atm, and i think it wants to download there.
Anyone with an sd card able to just install the (stericson) busybox market app?
I did some research on adbd. Apparently by default it runs as a "shell" user, not root.
This is pretty standard for stock roms apparently. There are a few ways around this.
For more information, see this thread
Honestly, I forgot the step to remove zergRush from /data/local, so the easiest thing in my opinion would be to just run zergRush whenever you need adb running as root.
Also, busybox from the market installs just fine with an sd-card, doesn't have to be a good one or anything, it just needs a place to park the busybox binary that it is copying over
Great work. Was thinking about writing one once I got an NT but knew someone would beat me to it. FYI you can follow link in my signature to install adb in Ubuntu. Will try this as soon as I get my hand on one (next week). Thank you
Sent from my NookColor using xda premium
I used the first half of these instructions to get sideloading working on my non-rooted NT 1.4.1. Windows messed everything up by installing the "correct" drivers automatically and adb wouldn't recognize the NT so had to flip to Linux. Thanks!
Sent from my BNTV250 using Tapatalk
I get the following error after it begins installing the SDK Platform-tools: Stopping ADB server failed (code -1). Is this normal?
This is a clean install of the Android SDK.
Thanks!
Code:
Fetching https://dl-ssl.google.com/android/repository/addons_list-1.xml
Validate XML
Parse XML
Fetched Add-ons List successfully
Fetching URL: https://dl-ssl.google.com/android/repository/repository-5.xml
Validate XML: https://dl-ssl.google.com/android/repository/repository-5.xml
Parse XML: https://dl-ssl.google.com/android/repository/repository-5.xml
Found SDK Platform Android 1.1, API 2, revision 1 (Obsolete)
Found SDK Platform Android 1.5, API 3, revision 4
Found SDK Platform Android 1.6, API 4, revision 3
Found SDK Platform Android 2.0, API 5, revision 1 (Obsolete)
Found SDK Platform Android 2.0.1, API 6, revision 1 (Obsolete)
Found SDK Platform Android 2.1, API 7, revision 3
Found SDK Platform Android 2.2, API 8, revision 3
Found SDK Platform Android 2.3.1, API 9, revision 2 (Obsolete)
Found SDK Platform Android 2.3.3, API 10, revision 2
Found SDK Platform Android 3.0, API 11, revision 2
Found SDK Platform Android 3.1, API 12, revision 3
Found SDK Platform Android 3.2, API 13, revision 1
Found SDK Platform Android 4.0, API 14, revision 3
Found SDK Platform Android 4.0.3, API 15, revision 1
Found ARM EABI v7a System Image, Android API 14, revision 2
Found ARM EABI v7a System Image, Android API 15, revision 1
Found Samples for SDK API 7, revision 1
Found Samples for SDK API 8, revision 1
Found Samples for SDK API 9, revision 1 (Obsolete)
Found Samples for SDK API 10, revision 1
Found Samples for SDK API 11, revision 1
Found Samples for SDK API 12, revision 1
Found Samples for SDK API 13, revision 1
Found Samples for SDK API 14, revision 2
Found Samples for SDK API 15, revision 1
Found Android SDK Platform-tools, revision 10
Found Android SDK Tools, revision 16
Found Documentation for Android SDK, API 15, revision 1
Found Sources for Android SDK, API 14, revision 1
Found Sources for Android SDK, API 15, revision 1
Found Android Support package, revision 6
Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
Parse XML: https://dl-ssl.google.com/android/repository/addon.xml
Found Google APIs by Google Inc., Android API 3, revision 3
Found Google APIs by Google Inc., Android API 4, revision 2
Found Google APIs by Google Inc., Android API 5, revision 1 (Obsolete)
Found Google APIs by Google Inc., Android API 6, revision 1 (Obsolete)
Found Google APIs by Google Inc., Android API 7, revision 1
Found Google APIs by Google Inc., Android API 8, revision 2
Found Google APIs by Google Inc., Android API 9, revision 2 (Obsolete)
Found Google APIs by Google Inc., Android API 10, revision 2
Found Google APIs by Google Inc., Android API 11, revision 1
Found Google APIs by Google Inc., Android API 12, revision 1
Found Google APIs by Google Inc., Android API 13, revision 1
Found Google APIs by Google Inc., Android API 14, revision 2
Found Google TV Addon by Google Inc., Android API 12, revision 2
Found Google APIs by Google Inc., Android API 15, revision 1
Found Google Market Licensing package, revision 1
Found Google USB Driver package, revision 4
Found Google Market Billing package, revision 1
Found Google Admob Ads Sdk package, revision 4
Found Google Analytics Sdk package, revision 2
Found Google Webdriver package, revision 2
Fetching URL: http://www.echobykyocera.com/download/echo_repository.xml
Validate XML: http://www.echobykyocera.com/download/echo_repository.xml
Parse XML: http://www.echobykyocera.com/download/echo_repository.xml
Found Dual Screen APIs by KYOCERA Corporation, Android API 8, revision 1
Found Dual Screen APIs by KYOCERA Corporation, Android API 10, revision 1
Fetching URL: http://developer.lgmobile.com/sdk/android/repository.xml
Validate XML: http://developer.lgmobile.com/sdk/android/repository.xml
Parse XML: http://developer.lgmobile.com/sdk/android/repository.xml
Found Real3D by LGE, Android API 10, revision 1
Found Real3D by LGE, Android API 8, revision 1
Fetching URL: http://innovator.samsungmobile.com/android/repository/repository.xml
Validate XML: http://innovator.samsungmobile.com/android/repository/repository.xml
Parse XML: http://innovator.samsungmobile.com/android/repository/repository.xml
Found GALAXY Tab by Samsung Electronics., Android API 8, revision 1
Fetching URL: http://developer.sonyericsson.com/edk/android/repository.xml
Validate XML: http://developer.sonyericsson.com/edk/android/repository.xml
Parse XML: http://developer.sonyericsson.com/edk/android/repository.xml
Found EDK 1.2 by Sony Ericsson Mobile Communications AB, Android API 10, revision 1
Fetching URL: http://su.barnesandnoble.com/nook/sdk/addon.xml
Validate XML: http://su.barnesandnoble.com/nook/sdk/addon.xml
Parse XML: http://su.barnesandnoble.com/nook/sdk/addon.xml
Found NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Fetching URL: http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Validate XML: http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Parse XML: http://su.barnesandnoble.com/nook/sdk/Nook_Tablet_addon.xml
Found NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Done loading packages.
Preparing to install archives
Downloading Android SDK Platform-tools, revision 10
Installing Android SDK Platform-tools, revision 10
Stopping ADB server failed (code -1).
Installed Android SDK Platform-tools, revision 10
Downloading SDK Platform Android 2.3.3, API 10, revision 2
Installing SDK Platform Android 2.3.3, API 10, revision 2
Installed SDK Platform Android 2.3.3, API 10, revision 2
Downloading SDK Platform Android 2.2, API 8, revision 3
Installing SDK Platform Android 2.2, API 8, revision 3
Installed SDK Platform Android 2.2, API 8, revision 3
Downloading Samples for SDK API 10, revision 1
Installing Samples for SDK API 10, revision 1
Installed Samples for SDK API 10, revision 1
Downloading Samples for SDK API 8, revision 1
Installing Samples for SDK API 8, revision 1
Installed Samples for SDK API 8, revision 1
Downloading Android Support package, revision 6
Installing Android Support package, revision 6
Installed Android Support package, revision 6
Downloading NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Installing NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Installed NOOK Tablet by Barnes and Noble, Inc., Android API 10, revision 1
Downloading Google APIs by Google Inc., Android API 10, revision 2
Installing Google APIs by Google Inc., Android API 10, revision 2
Installed Google APIs by Google Inc., Android API 10, revision 2
Downloading NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Installing NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Installed NOOKcolor by Barnes and Noble, Inc., Android API 8, revision 1
Downloading Google APIs by Google Inc., Android API 8, revision 2
Installing Google APIs by Google Inc., Android API 8, revision 2
Installed Google APIs by Google Inc., Android API 8, revision 2
Updated ADB to support the USB devices declared in the SDK add-ons.
Stopping ADB server succeeded.
Starting ADB server succeeded.
Done. 10 packages installed.
Done loading packages.
Did it work? Can adb see the NT? Can you root? The error may not be normal, but it doesn't really matter unless something doesn't work...
Sent from my Desire HD using Tapatalk
winsettr said:
Did it work? Can adb see the NT? Can you root? The error may not be normal, but it doesn't really matter unless something doesn't work...
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Running openSUSE 12.1
I've tried different USB ports but something isn't right:
Code:
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb kill-server
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb push zergRush /data/local
error: insufficient permissions for device
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb devicesList of devices attached
???????????? no permissions
*******@arena:~/programs/android-sdk-linux/platform-tools> ./adb shell
error: insufficient permissions for device
*******@arena:~/programs/android-sdk-linux/platform-tools>
*******@arena:~/programs/android-sdk-linux/platform-tools> ls -l /etc/udev/51-android.rules
-rw-r--r-- 1 root root 234 Jan 2 18:12 /etc/udev/51-android.rules
*******@arena:~/programs/android-sdk-linux/platform-tools>
I have even tried running this with SUDO and as ROOT but then I'm am presented with an empty "List of devices attached" after running "./adb devices" command. I have also rebooted my Linux system and the Nook Tablet but no change.
You shouldn't need special permission to push ZergRush (how else could you get it on the NT to root) so that's a problem. When you stop then start the adb daemon, then list devices (before trying to push ZergRush), is the NT listed?
Sent from my Desire HD using Tapatalk
RegLinUsr said:
...
I have even tried running this with SUDO and as ROOT but then I'm am presented with an empty "List of devices attached" after running "./adb devices" command. I have also rebooted my Linux system and the Nook Tablet but no change.
Click to expand...
Click to collapse
winsettr said:
You shouldn't need special permission to push ZergRush (how else could you get it on the NT to root) so that's a problem. When you stop then start the adb daemon, then list devices (before trying to push ZergRush), is the NT listed?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Your question is easily answered with the information from the end of my post...
Fully reading a post before replying is quite the useful trait. It helps to notice that this is not my first time rooting something as well so the obvious isn't the issue here, the problem is something else that is a bit off of the beaten path. Might be something openSUSE specific; missing driver or program but I'm not sure at this point.
Stil remount will not work for me?
ylixir said:
Yeah... :-(
You'll have to su and remount by hand. The following should work:
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
# exit
$ exit
$ adb push teh_files
Here's my commands:
$ su
su
reloc_library[1311]: 2959 cannot locate '_ZNK7android6Parcel15setDataPositionEj
'...
CANNOT LINK EXECUTABLE
$ su
mount -o rw,remount /dev/block/platform/mmci-omap-hs.1/by-name/system /system
mount: Operation not permitted
Click to expand...
Click to collapse
Works!
Thank you! tried on the mac and had issues with device not being found. This worked perfect, thanks again for the guide!
Ren
I don't see any option to "Manage add-on sites" in the ADK Manager (the "android" app). Where are you getting this from?
Nevermind, I understand it now.
Has anyone managed to connect their S2 using MTP when running Ubuntu? Obviously I know that it's a very simple tast to just connect via mass storage instead, but I'm interested to know.
I think that Samsung have some weird implementation of MTP because I was able to connect and copy files when I was running CM9 but not on stock ICS. I always get the error message:
Unable to mount SAMSUNG_Android
Error initialising camera: -60: Could not lock the device
Though it does mount and I can see the root of both SDCards, all the folders are empty and I can't copy any files to the cards from the computer as I get a error message reading:
There was an error copying the file into gphoto2://[usb:001,010]/store_00020002.
The same happens whether I try to use MTP or PTP.
I think the problem lies in that libmtp-1.1.3 contains fixes for the S2 but that version isn't included with 11.10 or 12.04
hint
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
alpike said:
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
Click to expand...
Click to collapse
That's connecting via USB mass storage, not mtp. But thanks for trying.
Sent from my GT-I9100 using XDA
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
what I have found out that mtpfs is unable to preserve timestamps of the files at least on my install.
gphoto2 backend worked fine on CM9 now wile testing CM10 its a bit buggy, I can get the list of files but I am unable to read or rename them.
Most likelly it will improve as development of CM10 progresses rapidly.
Mounting my Galaxy S3 when connected via USB to my Ubuntu computer
D4rKn3sSyS said:
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
Click to expand...
Click to collapse
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
slubkin said:
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
Click to expand...
Click to collapse
Ubuntu 13.04 is a drastic improvement for MTP support. I have not got around to trying my S II but I successfully managed a family friends Galaxy TAB 2 with MTP with zero manual modifications to Ubuntu. Everything worked perfect plug and play out of the box.
I have also tried old versions to know how bad they were compared to 13.04.
No luck with S2 and Ubuntu 13.04
I'm on Android 4.1.2 and trying to connect via USB to Ubuntu 13.04. Error I get is that my device is not an MTP device, which it's not as its using USB
Issue is that I don't see the mounted android partitions. To make this worse, it works every now and then. Following is the syslog and the outpu of lsusb
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aug 26 23:04:00 ml kernel: [134718.425536] usb 1-5: new high-speed USB device number 11 using ehci-pci
Aug 26 23:04:00 ml kernel: [134718.558636] usb 1-5: New USB device found, idVendor=04e8, idProduct=685b
Aug 26 23:04:00 ml kernel: [134718.558647] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 26 23:04:00 ml kernel: [134718.558655] usb 1-5: Product: SAMSUNG_Android
Aug 26 23:04:00 ml kernel: [134718.558661] usb 1-5: Manufacturer: SAMSUNG
Aug 26 23:04:00 ml kernel: [134718.558666] usb 1-5: SerialNumber: 001964815b817e
Aug 26 23:04:05 ml kernel: [134723.546077] usb 1-5: can't set config #1, error -110
Aug 26 23:04:05 ml mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5"
Aug 26 23:04:05 ml mtp-probe: bus: 1, device: 11 was not an MTP device
[email protected]:~$ lsusb
Bus 001 Device 011: ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (mass storage mode)
Bus 003 Device 002: ID 046d:c52e Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The Android device in question is a Micromax A87(a relatively unknown brand in global market but I hope that should'nt matter).
In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running
adb, adb start-server as root. But
Code:
adb devices
shows no devices at all.
However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.
Now the interesting part.
If I go back to Ubuntu without disconnecting the cable and do
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[B]1234567890ABCDEF[/B] device
The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!
But the moment I disconnect the USB cable, its gone.
So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.
What could be a way to get this to work? (Besides developing on Windows :silly: )
Btw the
Code:
/data/property/persist.service.adb.enable
is 1 too.
What is your computer setup? Are you using a Windows machine, with Ubuntu in a vm? Dual-boot? Other?
My setup:
Dual boot.
Ubuntu 12.04 and Windows 7.
Ok, how about if you plug in the USB with the computer's power off, then boot into Ubuntu?
i have the clone of this phone. mine is Mito A78.
lsusb command shows it as 1c9e:9e08
so idVendor =1c9e and idProduct = 9e08
for now, what you say (plugin to windows and reboot to ubuntu without unplug the phone) is the solution.
i will see if lsusb output still the same.
okay, have checked on windows pc, it should be switched to idVendor =1c9e and idProduct = 9e18
anyway, what you say is a clue that the solution may be around usb_modeswitch and modem manager
further search on usb_modeswitch 1c9e 9e08 found the solution here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1351
have tried, but not yet switched to idVendor =1c9e and idProduct = 9e18
have to find the correct rules on /etc/usb_modeswitch.d/1c9e:9e08
Code:
########################################################
# Mito A78
DefaultVendor=0x1c9e
DefaultProduct=0x9e08
TargetVendor=0x1c9e
TargetProduct=0x9e18
SierraMode=1
CheckSuccess=20
NoDriverLoading=1
found it.
after writing the rules, insert
Code:
# Mito A78
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
to /lib/udev/rules.d/40-usb_modeswitch.rules
i than have to run
Code:
sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W
and then the phone switched to idVendor =1c9e and idProduct = 9e18 and adb can access the phone.
:good: :good: :good:
I-mobile IQ 5.1 has same issue, but adb still can't see device
The usb_modeswitch is exactly the same for this phone (same usb vid/pid). However adb still doesn't find the phone under Windows and Ubuntu. lsusb shows the product id switch did work and it all looks right.
Under windows it spins up a cdrom device from the phone so you can install the windows drivers (this lives as an *.iso file under /system); after the driver install, you get the adb device in device manager and two com ports,with all devices having a pid of 9e18 (original 9e08). However adb does not see the device!
I recon there is something wrong on the phone side. This is a very new phone (only release about 5 days ago), so I suspect this is one of the early release bugs...
Since I don't even have a custom recovery for it (CWM, etc) I can even backup my phone and try and do a factory reset.
Looks like a low level USB issue
Switched on tracing on adbd on the phone side. Looks like a phone/usb low level issue:
Code:
--- adb starting (pid 14270) ---
system/core/adb/adb.c::main():Handling main()
system/core/adb/adb.c::adb_main():Local port disabled
system/core/adb/usb_linux_client.c::usb_init():failed to open /dev/android_adb_enable
system/core/adb/usb_linux_client.c::usb_init():[ usb_init - starting thread ]
system/core/adb/adb.c::adb_main():adb_main(): pre init_jdwp()
system/core/adb/jdwp_service.c::jdwp_control_init():jdwp control socket started (5)
system/core/adb/adb.c::adb_main():adb_main(): post init_jdwp()
system/core/adb/adb.c::adb_main():Event loop starting
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - opening device ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ opening device succeeded ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - registering device ]
system/core/adb/transport.c::register_usb_transport():transport: 0x11364a0 init'ing for usb_handle 0x1136410 (sn='')
system/core/adb/transport_usb.c::init_usb_transport():transport: usb
system/core/adb/transport.c::register_transport():transport: (null) registered
system/core/adb/transport.c::transport_registration_func():transport: (null) (10,11) starting
system/core/adb/transport.c::output_thread():(null): starting transport output thread on fd 11, SYNC online (2)
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::transport_socket_events():transport_socket_events(fd=10, events=0001,...)
system/core/adb/transport.c::dump_packet():fd=10: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/adb.c::handle_packet():handle_packet() SYNC
system/core/adb/transport.c::dump_packet():fd=10: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::output_thread():(null): data pump started
system/core/adb/usb_linux_client.c::usb_read():about to read (fd=9, len=24)
system/core/adb/transport.c::input_thread():(null): starting transport input thread, reading from fd 11
system/core/adb/transport.c::dump_packet():fd=11: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::input_thread():(null): transport SYNC online
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11279 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11325 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11818 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13994 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13951 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13913 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13856 to jdwp process list
system/core/adb/usb_linux_client.c::usb_read():ERROR: fd = 9, n = -1, errno = 5 (I/O error)
system/core/adb/transport_usb.c::remote_read():remote usb: read terminated (message)
system/core/adb/transport.c::output_thread():(null): remote read failed for transport
system/core/adb/transport.c::output_thread():(null): SYNC offline for transport
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=0 arg1=0 (len=0)
system/core/adb/transport.c::output_thread():(null): transport output thread is exiting
system/core/adb/usb_linux_client.c::usb_kick():usb_kick
---------- Post added at 04:31 AM ---------- Previous post was at 04:27 AM ----------
I also tried the Chainfire adbd insecure and its exactly the same in the debugging.
Now working on win7 64!
Followed this link and managed to get it working. The PID value was set to 9e18. In essence the andriod usb driver was missing (install via the andriod.bat andriod package manager).
Also works in virtualbox winxp vm on Linux (ubuntu 12.10; actually Mint 14). Just mapped in my win7 64 partition to get access to the andriod sdk/usb driver.
Now that I know its not a handset issue, can return to trying to get the Linux side working.
Now working under Linux!
You need the vendor id in adb_usb.ini:
Code:
cat ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1c9e
If you will run adb as root, make sure you also create the file for root too.
Tip: You will be logged into the phone as the 'shell' user. Try and 'su -' to get root access, and then click on your su dialog on the phone to grant access.
Final issue is that plugging in the device should do the switch automatically; I will update you on that when I have that fixed.
udev sorted on ubuntu
Ok, we are rocking on udev on ubuntu 12.10. Seems like udev doesn't like ATTR keywords, although ATTRS makes everything burst into life (man page says ATTR is useable). Steps that worked for me:
Code:
# cp /lib/udev/rules.d/40-usb_modeswitch.rules /etc/udev/rules.d/usb_modeswitch.rules
# vi /etc/udev/rules.d/usb_modeswitch.rules
Add the following entry near the bottom under the last entry:
Code:
# I-Mobile IQ5.1
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
Create /etc/usb_modeswitch.d/1c9e:9e08 as described earlier by jurban.
Unplug the phone. Plug it in. Do an lsusb. Firstly shows up as dev 1c9e:9e08. Enter lsusb again. Shows up as 1c9e:9e18. Now adb will show the device as jurban shows above. All good to go!