Just like it says in the thread title, I was wondering if anybody -- in particular, any linux users -- had tried using heimdall yet? I'm too new to both the Galaxy family of phones and odin/heimdall to try it myself yet.
thanks.
This is just a repeat of what I said in the official heimdall thread:
I just tried using it with the SGS2. Nothing radical, since I have zero experience with heimdall and Galaxy phones.
1) I put the phone into download mode, following instructions I got here.
2) I connected the phone to my fedora 11 install (yes, I'm way behind the times!)
3) I ran lsusb and got:
Bus 001 Device 002: ID 04e8:685d Samsung Electronics Co., Ltd
It doesn't mention the words "mobile phone" as I think it does for the S1, but I may be wrong about that.
4) I ran:
heimdall close-pc-screen --verbose
according to instructions earlier in this thread (page 26).
5) I got:
Failed to detect compatible device
Anything new on that?
Would be great for us Linux-Only-Nerdys
Thanks
Ali
aliander said:
Anything new on that?
Would be great for us Linux-Only-Nerdys
Thanks
Ali
Click to expand...
Click to collapse
Sorry guys I don't have a Galaxy S II to develop with so I haven't been able to make the necessary changes to support the Galaxy S II. If anyone has one they want to donate that would be fantastic, but that's probably not all that likely
Benjamin Dobell said:
Sorry guys I don't have a Galaxy S II to develop with so I haven't been able to make the necessary changes to support the Galaxy S II. If anyone has one they want to donate that would be fantastic, but that's probably not all that likely
Click to expand...
Click to collapse
I just tested heimdall a bit with the SGSII.
At least, kernel flash works.
Modifications needed:
BridgeManager.h: device ID is 685D not 6601 (maybe add a switch for sgs2)
main.cpp: getUnknown is 131072, not 0 (again, maybe switch)
and it'll work.
I'd also suggest a switch for "--no-reboot" ;-)
Let me know if you would prefer a diff or w/e like that..
Disclaimer: I did NOT test this thoroughly, this is AT YOUR OWN RISK - flashing CAN destroy your device.
Kernel flashing does work tho
ps: I'd have prefered giving you a GT-I9100 but that's a little over my budget right now
bad stuff:
x64 linux binary http://www.multiupload.com/A1R7SDUFZM
more bad stuff:
ive put it in a diff cause i'm not so lazy today:
https://github.com/kangsterizer/Heimdall/commit/86e9b66d4ec5b415b3a8d2d310f9ce7633679a16
bilboa1 said:
I just tested heimdall a bit with the SGSII.
At least, kernel flash works.
Modifications needed:
BridgeManager.h: device ID is 685D not 6601 (maybe add a switch for sgs2)
main.cpp: getUnknown is 131072, not 0 (again, maybe switch)
and it'll work.
I'd also suggest a switch for "--no-reboot" ;-)
Let me know if you would prefer a diff or w/e like that..
Disclaimer: I did NOT test this thoroughly, this is AT YOUR OWN RISK - flashing CAN destroy your device.
Kernel flashing does work tho
ps: I'd have prefered giving you a GT-I9100 but that's a little over my budget right now
bad stuff:
x64 linux binary http://www.multiupload.com/A1R7SDUFZM
more bad stuff:
ive put it in a diff cause i'm not so lazy today:
https://github.com/kangsterizer/Heimdall/commit/86e9b66d4ec5b415b3a8d2d310f9ce7633679a16
Click to expand...
Click to collapse
I have tried compiling this on two different machines -- one Fedora 11 and one Fedora 14. Both result in the same error, and sadly, I'm not experienced enough to figure it out
Here's the badness:
depbase=`echo source/BridgeManager.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
g++ -DHAVE_CONFIG_H -I. -I/usr/include/libusb-1.0 -g -O2 -MT source/BridgeManager.o -MD -MP -MF $depbase.Tpo -c -o source/BridgeManager.o source/BridgeManager.cpp &&\
mv -f $depbase.Tpo $depbase.Po
source/BridgeManager.cpp:57:47: error: ‘kPidGalaxySDownloadMode’ is not a member of ‘Heimdall::BridgeManager’
make[1]: *** [source/BridgeManager.o] Error 1
I'd be grateful for any suggestions, although I fully understand that you all have lives elsewhere!
I think you need to look more up to find the cause, you are surely missing some devel packages
godutch said:
I think you need to look more up to find the cause, you are surely missing some devel packages
Click to expand...
Click to collapse
I'm sure it's something stupid. On both laptops I have run:
yum groupinstall "Development Tools"
yum install rpmdevtools
I also installed the kernel source rpm.
try installing the libusb-devel packages
Got it there is an error in the patch. I can't make a diff for you but it's easy to change in heimdall/source/BridgeManager.h change the enum section around line 67 like this:
enum
{
kPidGalaxyS2DownloadMode = 0x685D,
kPidGalaxySDownloadMode = 0x6601,
kPidGalaxySInternational = 0x681C,
kPidGalaxySNewInternational = 0x681D,
kPidVibrantCanadaBell = 0x6877
};
Thanks a lot, godutch! That worked and got me as far as the next error:
Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused
Luckily Dr. Hotdog seems to have a fix for that here. Thanks all
It seemed to install all right, but when I run:
heimdall close-pc-screen
I get:
Failed to detect compatible device
Is this to be expected? I.e. does that functionality work with the SGS2 or do I have more problems I need to investigate?
What's the output of lsusb with the sgs connected?
Bus 005 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 04e8:685d Samsung Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
anybody tried installing this kernel:
http://forum.xda-developers.com/showthread.php?t=1060673
with this pre-compiled heimdall?
I just didn't want to break my shiny new toy
And I do not have windows, of course!
elban said:
anybody tried installing this kernel:
http://forum.xda-developers.com/showthread.php?t=1060673
with this pre-compiled heimdall?
I just didn't want to break my shiny new toy
And I do not have windows, of course!
Click to expand...
Click to collapse
yeah i did, it works - but of course i can't give any warranty if something goes wrong
bilboa1 said:
I just tested heimdall a bit with the SGSII.
At least, kernel flash works.
Modifications needed:
BridgeManager.h: device ID is 685D not 6601 (maybe add a switch for sgs2)
main.cpp: getUnknown is 131072, not 0 (again, maybe switch)
and it'll work.
I'd also suggest a switch for "--no-reboot" ;-)
Let me know if you would prefer a diff or w/e like that..
Disclaimer: I did NOT test this thoroughly, this is AT YOUR OWN RISK - flashing CAN destroy your device.
Kernel flashing does work tho
ps: I'd have prefered giving you a GT-I9100 but that's a little over my budget right now
bad stuff:
x64 linux binary http://www.multiupload.com/A1R7SDUFZM
more bad stuff:
ive put it in a diff cause i'm not so lazy today:
https://github.com/kangsterizer/Heimdall/commit/86e9b66d4ec5b415b3a8d2d310f9ce7633679a16
Click to expand...
Click to collapse
hello
when I try to flash a kernel, I get:
Failed to detect compatible device
lsusb gives:
Bus 001 Device 007: ID 04e8:685e Samsung Electronics Co., Ltd
maybe the problem is the different usb ID?
elban said:
hello
when I try to flash a kernel, I get:
Failed to detect compatible device
lsusb gives:
Bus 001 Device 007: ID 04e8:685e Samsung Electronics Co., Ltd
maybe the problem is the different usb ID?
Click to expand...
Click to collapse
sorry guys, me stupid, I wasn't in download mode!
flashed supercurio kernel succesfully, now I'm rooted and with cifs, all without needing to run windows!
thanks very much!
just wanted to let you know that with this heimdall I've successfully flashed CFROOT in this thread:
http://forum.xda-developers.com/showthread.php?t=1103399
very very nice!
https://github.com/kangsterizer/Heimdall/
Please correct:
- heimdall/source/BridgeManager.cpp
56:
Code:
const DeviceIdentifier BridgeManager::supportedDevices[BridgeManager::kSupportedDeviceCount] = {
DeviceIdentifier(BridgeManager::kVidSamsung, BridgeManager::kPidGalaxySDownloadMode)
to:
56:
Code:
const DeviceIdentifier BridgeManager::supportedDevices[BridgeManager::kSupportedDeviceCount] = {
DeviceIdentifier(BridgeManager::kVidSamsung, BridgeManager::kPidGalaxyS2DownloadMode)
OR:
- heimdall/source/BridgeManager.h
69:
Code:
kPidGalaxyS2DownloadMode = 0x685D
to:
69:
Code:
kPidGalaxySDownloadMode = 0x685D
Related
Not really a development question, but I still think this section of the forum suites best.
My device (Acer A500 tab) is not recognized by Eclipse when I plug it in via USB (USB debugging is set, ofc). It is, however, recognized by OS as a valid USB device - I can see it with lsusb.
Any suggestions?
Thanks in advance.
P.S. I never had such a problem on Windows. I can't beleive Linux cannot be use for development.
Sorry, my bad. The device couldn't connect via USB because it was already connected over Wi-Fi, and I forgot about it
Please close the topis.
Connecting via USB to Linux (Ubuntu)
I could not get my Ubuntu machines to recognize the tablet when I plugged in the USB cable. Bummer.
Digging around I found a similar issue experienced by Xoom owners. The original article describing the fix is here. The steps listed there are for the Xoom, not the Acer, although the fix is almost the same.
I am posting the slightly modified instructions again here for clarity and brevity.
I did this fix on both Ubuntu 10.10 (Maverick) and 11.04 (Natty). Your mileage may vary.
1. Get the mtpfs package installed on your machine.
Code:
sudo apt-get install mtpfs
2. In the tablet, go to Settings->Applications->Development and turn USB Debugging on (check the box). For me, this was required for file transfers to work.
3. Plug your USB cable into the tablet and your Ubuntu machine.
4. Open your Terminal app on the Ubuntu machine.
5. Use the lsusb command to get the vendor id. Type "lsusb" in Terminal.
6. The output should look something like this:
Code:
[email protected]:~$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 006: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 003 Device 005: ID 05af:0802 Jing-Mold Enterprise Co., Ltd
Bus 003 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0502:3325 Acer, Inc.
Bus 001 Device 003: ID 04f2:b16b Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The line with "Acer, Inc." in it tells you the VendorID. In the example above, it's 0502.
** Disconnect the USB cable at this point **
7. Create a UDEV rule file. Use your editor of choice, mine is nano.
Code:
sudo nano /etc/udev/rules.d/51-android.rules
The file should contain this line when you are finished:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
8. Create a mount point and make yourself the owner.
Code:
sudo mkdir /media/a500
sudo chown user:user /media/a500
IMPORTANT: Replace user:user with your user name and default group on your Ubuntu machine. For most people it will be your login name. If your login is "bob", then replace user:user with bob:bob, capice?
9. Add the mount point to fstab.
Code:
sudo nano /etc/fstab
At the bottom of the file, type this stuff:
Code:
# mount point for Acer A500
mtpfs /media/a500 fuse user,noauto,allow_other 0 0
10. Modify fuse.conf. Uncomment user_allow_other.
Code:
sudo nano /etc/fuse.conf
Look for #user_allow_other and remove the #.
11. Add yourself to the fuse group.
Code:
sudo nano /etc/group
Look for the line starting with "fuse" and put your login at the end of that line (if it's not already there).
12. Reboot.
You should see your mount point in Nautilus when you open it. After plugging in the USB cable, you can click the a500 entry under Places to mount the tablet.
I have spent many hours traulling the net, scanning through forums across multiple websites and found no information on how to make my device which in its current software incarnation currently seems to only allow MTP as the option for transferring data via the USB cable to and from my Mac running OSX 1.7.3.
Please note, that that google app for file transfers DOES NOT WORK (for me). I cannot get it to work no matter which god I've prayed to or what kinda dance I did. So I looked for alternatives.
ADB worked, but I got tired of ADB to push files across (which is effective, but not what I would call fun). I came across MacPort, giving us ports of Linux/Unix stuff in the world of OSX. YAY!
Found that the various libraries for MTP and MTP-FS was ported! YAY!
After installing the hell out of macport (found: www macports org) and runing the updates.
Drop to the command line and then run these commands once:
Code:
sudo port install libmtp
sudo port install mtpfs
Every time you load your device:
Code:
sudo mtpfs
Awesome! Progress, plug in the device and run mtpfs. But then I get this:
Code:
bergenmacbook:Applications bergenlarsen$ sudo mtpfs
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 250, dev 6
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): Operation timed out
outep: usb_get_endpoint_status(): Operation timed out
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device -208647360
I'm running MIUI v4 (2.4.13) with Siyah Kernel (currently 3.1RC5).
Help?
BergenLarsen said:
I have spent many hours traulling the net, scanning through forums across multiple websites and found no information on how to make my device which in its current software incarnation currently seems to only allow MTP as the option for transferring data via the USB cable to and from my Mac running OSX 1.7.3.
Please note, that that google app for file transfers DOES NOT WORK (for me). I cannot get it to work no matter which god I've prayed to or what kinda dance I did. So I looked for alternatives.
ADB worked, but I got tired of ADB to push files across (which is effective, but not what I would call fun). I came across MacPort, giving us ports of Linux/Unix stuff in the world of OSX. YAY!
Found that the various libraries for MTP and MTP-FS was ported! YAY!
After installing the hell out of macport (found: www macports org) and runing the updates.
Drop to the command line and then run these commands once:
Code:
sudo port install libmtp
sudo port install mtpfs
Every time you load your device:
Code:
sudo mtpfs
Awesome! Progress, plug in the device and run mtpfs. But then I get this:
Code:
bergenmacbook:Applications bergenlarsen$ sudo mtpfs
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 250, dev 6
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): Operation timed out
outep: usb_get_endpoint_status(): Operation timed out
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device -208647360
I'm running MIUI v4 (2.4.13) with Siyah Kernel (currently 3.1RC5).
Help?
Click to expand...
Click to collapse
Tried installing gvfs-gphoto2 and nautilus?
Read more here:
How To: Fix Samsung Galaxy Nexus MTP File Transfer for Ubuntu GNU/Linux 11.10
Hello, dear.
I have installed the CM 10 rom from FXP, and I have found some bugs.
I don't know what should I do, so I am creating this thread. If I am wrong, please, excuse me and tell me.
So, in FPX 151, I don't have access to my SDCard while I connect my telphone in my notebook, that is OpenSuSE Linux. Before this version, my SDCard was connecting correctly.
Ps.: In Windows operating system I can open my SD.
Ps².: Maybe is a OS unrecognizing, but I already do the udev rules correctly.
/etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666", GROUP="users"
Click to expand...
Click to collapse
My lsusb while telephone connected in MTP:
[email protected]:~> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
Bus 006 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse
Bus 002 Device 021: ID 0fce:0167 Sony Ericsson Mobile Communications AB
[email protected]:~>
Click to expand...
Click to collapse
The other bug I found occur just in my ST15 and it's occuring in all releases after FX152. I haven't tested the FX152, but all releases until the FX207, my telephone doesn't start the WiFi.
When I try to start my WiFi, I get the message that is starting, but still ever there. Maybe it's a kernel bug.
Can someone help me?
Regards,
Rudah Ximenes.
RudahXimenes said:
Hello, dear.
I have installed the CM 10 rom from FXP, and I have found some bugs.
I don't know what should I do, so I am creating this thread. If I am wrong, please, excuse me and tell me.
So, in FPX 151, I don't have access to my SDCard while I connect my telphone in my notebook, that is OpenSuSE Linux. Before this version, my SDCard was connecting correctly.
Ps.: In Windows operating system I can open my SD.
Ps².: Maybe is a OS unrecognizing, but I already do the udev rules correctly.
/etc/udev/rules.d/51-android.rules
My lsusb while telephone connected in MTP:
The other bug I found occur just in my ST15 and it's occuring in all releases after FX152. I haven't tested the FX152, but all releases until the FX207, my telephone doesn't start the WiFi.
When I try to start my WiFi, I get the message that is starting, but still ever there. Maybe it's a kernel bug.
Can someone help me?
Regards,
Rudah Ximenes.
Click to expand...
Click to collapse
Hi
I can't help you with the linux stuff, but I can help you with the wifi!
[INDEX] ROMs, KERNELS, FTFs, TOOLKITS and GUIDES - http://forum.xda-developers.com/showthread.php?t=2148684
Check out this list of all the kernels,
find the kernel you use,
go to thread , find modules,
flash modules in [cwm, twrp], ??????, click thanks after rebooting the phone:fingers-crossed:
Hi
I have installed Arch Linux but cannot find suitable material on setting up drivers and utilities for flashing rom on Linux specifically arch linux.
I can setup arch even if instructions are available for other distro Linux Mint and Ubuntu so any link can come in handy.
I was using flashtool in windows but after shifting to Arch, I am not sure whats the right procedure to do it.
I have unlocked bootloader and rooted rom (FXP kernel + MIUI) installed as of now which I want to change asap.
Please help.
Regards
Hello,
You don't need any drivers,just install android-udev and android-sdk-platform-tools for adb and fastboot (both from aur).
Download latest flastool and run it from the terminal just like you do in windows (it requires jre and libusbx from official repos ).
Ok I have reinstalled fatsboot, android-sdk-platform-tools and openjre
Now I still cannot use fastboot devices , its list nothing.
Also since I should have adb available (from sdk-platform) when I run adb it says no command ?
Code:
[[email protected] fastboot]$ fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo adb
sudo: adb: command not found
[[email protected] fastboot]$ adb
bash: adb: command not found
I have also installed udev-android , previous I created 51-android.rules manually but still doesnt work.
fastboot won't list the devices nor it works.
Code:
[sha[email protected] fastboot]$ lsusb
Bus 002 Device 005: ID 413c:2107 Dell Computer Corp.
Bus 002 Device 003: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0fce:5146 Sony Ericsson Mobile Communications AB
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
First of all make sure you have enabled usb debugging on your phone.Adb and fastboot should be under /opt/android-sdk/platform-tools/ and also 51-android.rules file in /usr/lib/udev/rules.d/ (with -rw-r--r-- permissions).
With these things i have everything in my sytem to flash roms etc,maybe you're missing something with your installation.
Also for more information check wiki from archlinux wiki.archlinux.org/index.php/android
Hi all,
I have a Dell server,
plugged in my rooted Galaxy S2,
installed Ubuntu 12.04 LTS,
Ran the following:
apt-get install openjdk-6-jdk
apt-get install ia32-libs-multiarch
downloaded adt-bundle-linux-x86_64-20140321.zip and extracted it, found adb.
I can see my phone:
# adb devices
List of devices attached
4fad0260 device
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0624:0248 Avocent Corp.
Bus 002 Device 006: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Bus 002 Device 004: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 005: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
I can reboot it and do other basic tasks but I can't send an sms from the shell
#adb shell am start –a android.intent.action.SENDTO –d sms:014166666666 --es sms_body "Hello World" --ez exit_on_sent true
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] pkg=–a }
Error: Activity not started, unable to resolve Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=–a }
I read posts about 'changing your manifest file' but again, it's purely a standalone purpose and I'm not writing an application.
Any ideas?
Thank you
gingivitor said:
Hi all,
I have a Dell server,
plugged in my rooted Galaxy S2,
installed Ubuntu 12.04 LTS,
Ran the following:
apt-get install openjdk-6-jdk
apt-get install ia32-libs-multiarch
downloaded adt-bundle-linux-x86_64-20140321.zip and extracted it, found adb.
I can see my phone:
# adb devices
List of devices attached
4fad0260 device
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0624:0248 Avocent Corp.
Bus 002 Device 006: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Bus 002 Device 004: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 005: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
I can reboot it and do other basic tasks but I can't send an sms from the shell
#adb shell am start –a android.intent.action.SENDTO –d sms:014166666666 --es sms_body "Hello World" --ez exit_on_sent true
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] pkg=–a }
Error: Activity not started, unable to resolve Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=–a }
I read posts about 'changing your manifest file' but again, it's purely a standalone purpose and I'm not writing an application.
Any ideas?
Thank you
Click to expand...
Click to collapse
Are you trying to send via adb shell for a specific purpose or you just want to be able to send SMS via your computer in general? If just general, then check out AirDroid. Nice web based interface and works pretty well. It also allows you to transfer files (limited amount for free), see what's on storage, your pics, etc.
es0tericcha0s said:
Are you trying to send via adb shell for a specific purpose or you just want to be able to send SMS via your computer in general? If just general, then check out AirDroid. Nice web based interface and works pretty well. It also allows you to transfer files (limited amount for free), see what's on storage, your pics, etc.
Click to expand...
Click to collapse
Thanks for the tip!
Yes I want to build an internal webpage to send out sms txt's via paid cell phone and usb cable.
I was going to have the webpage (via php) ssh in and run adb shell to send out the sms text programmatically.
gingivitor said:
Thanks for the tip!
Yes I want to build an internal webpage to send out sms txt's via paid cell phone and usb cable.
I was going to have the webpage (via php) ssh in and run adb shell to send out the sms text programmatically.
Click to expand...
Click to collapse
Maybe this would be helpful then? http://ubuntuforums.org/showthread.php?t=2140370
es0tericcha0s said:
Maybe this would be helpful then?
Click to expand...
Click to collapse
That worked great! Thank you!
Is this a new thing with android? I'm curious why I have to buy an app to do something that I was able to do before (without intent errors)
Thanks again
gingivitor said:
That worked great! Thank you!
Is this a new thing with android? I'm curious why I have to buy an app to do something that I was able to do before (without intent errors)
Thanks again
Click to expand...
Click to collapse
I've no clue. It's not something I've ever bothered looking in to. Just thought I would be helpful and I like to learn new things. Glad that was what you were looking for though!