Related
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
4nic8 said:
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
Click to expand...
Click to collapse
WORKS FOR EPIC 4G!!!!!
This worked for my BH2 but it may need some tweaking on the rules file to make it work, but I will double check it when I get home.
After downloading the SDK, I moved the adb to the (in my pc is like this) ~/android/tools/ folder and ran the chmod a+rwx adb command.
After this, I took the rules file (attached) and I moved it to the /etc/udev/rules.d/ folder (logged as root). After doing this, I ran the following commands:
su [then placed the password]
chmod a+x 51-android.rules
chown root:root 51-android.rules
Once done, I restarted the PC and its working 100%, I ran the lsusb command to confirm the connection of the device and then a ./adb devices an I got positive return!
Note: Attachment updated!
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I will tune the Rules file and test and let you know. Most of the time, when it doesn't work, its the rules file who has the problem.
4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
megabiteg said:
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
Click to expand...
Click to collapse
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
4nic8 said:
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
Click to expand...
Click to collapse
mmmm..
I've tested this with several other friends that use Ubuntu 10.10 and it works fine for them. Are you following step by step on my OP?
Also are you on a desktop or laptop? Please note that while you have USB Debugging on the option to mount your SD card will not be prompted.
If your using a Desktop, please refrain of using front side USB ports. If you need additional help, let me know, I'll be glad to help you getting it working.
send me what the lsusb command dumps if you can, that can help me tweak the rules file for you.
Thanks! after some trial and error..the zip file in the first post worked for me!
FYI, you can just run this command instead of restarting your computer:
Code:
sudo udevadm control –reload-rules; sudo reload udev; adb kill-server; adb devices
Same problem
Hello, I have the same problem, adb don't detect my tablet. I do it from my laptop and this is the lsusb exit:
[email protected]:~$ lsusb
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 007: ID 18d1:0001 Google Inc.
Bus 001 Device 002: ID 174f:a311 Syntek 1.3MPixel Web Cam - Asus A3A, A6J, A6K, A6M, A6R, A6T, A6V, A7T, A7sv, A7U
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
Click to expand...
Click to collapse
Is it possible that the integrated webcam generates the conflict? how can I disable it on Ubuntu 10.10?
Thanks
One thing I've noticed is that my phone will come right up (with debugging turned on) on certain usb ports but won't on others. Might be worth trying different USB ports just to see if it makes a difference.
Was this way on both my desktop and my netbook (both running Ubuntu 10.10).
Thanks flatspin, I have tried all my 4 usb ports without luck.
Solved, I forgot to put the tablet on adb mode at boot time.
The xoom can mount just fine on Linux but it is an MTP not a Mass Storage device.
Disclaimer: I am not responsible for any damage to your device, computer, relationship, etc.... The following is meant as a guideline and worked for me but as always use your head.
I did this on my Kubuntu Maverick laptop, but it should apply to most *buntus plus debian. Other flavors should be similar, post a request and I will help if I can. I am familiar with Suse and RHEL/Centos as well but beyond those it will be guess work.
The first thing I would recommend doing is making the device read/write to normal users.
Code:
sudo touch /etc/udev/rules.d/51-android.rules
echo "SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"22b8\", MODE=\"0666\"" |sudo tee -a /etc/udev/rules.d/51-android.rules
sudo /etc/init.d/udev restart
NOTE: This also "fixes" adb so it is useable with the xoom as a normal user. If that is all you want you can stop here.
NOTE 2: You could also set an OWNER rather than changing MODE but I chose the most common route for this example/
Now install either mtp-tools or mtpfs for mounting using FUSE. Since I went the fuse route that is what I will conver here. (I installed the mtp-tools package but beyond using it to debug getting mtpfs to work I have never used it before.)
Assuming you already have fuse configured, for (k|x)ubuntu or debian :
Code:
sudo apt-get install mtpfs
If you do not have fuse already configured then do that first. Look it up online if you have any questions. If you get stuck I will try and help but this post is not about how to configure FUSE.
After that it is simple. Plugin your xoom and from the command line type:
Code:
mtpfs mountpoint
and to dismount it
Code:
fusermount -u mountpoint
so in my case I mount it in a subdirectory under home called xoom
Code:
mtpfs /home/janetpanic/xoom
fusermount -u /home/janetpanic/xoom
I have confirmed moving files to and from the actual directories but not from the meta "playlists" directory. I hope that helps...
EDIT: Fixed Typo... had "(idVendor)" instead of the correct "{idVendor}"
Thanks for sharing your workaround. Unfortunately, it's no joy here. After following the procedure described, the terminal returned no error, but on trying to open the Xoom directory via Nautilus, I received the following message:
Code:
Error: Error stating file '/home/sog/Xoom': Transport endpoint is not connected
Please select another viewer and try again.
Unmounting proceeds without error.
Distribution: Ubuntu Lucid x64
Did you connect your xoom before or after you mounted? The most likely problem is the undeveloped configuration .
Change the line in 51-android.rules to
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", SYMLINK+="libmtp-%k", MODE="0666"
[\code]
Restart udev and then do a "ls -lah /dev/libmtp*" with the device attached and list the output. I need to figure out if the problem is the udev rule or elsewhere.
If the ls does not show any files then send the result of "lsusb |grep Motorola" which better list a line or there is something weird going on.
Sent from my Xoom using XDA App
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Wait, you aren't able to get the Xoom to mount as a mass storage device?
ed. The leaked Xoom manual suggests it support mass storage. Phew. You were scaring me there a bit.
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
sogrady said:
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
Click to expand...
Click to collapse
Which stack, Linux or Honeycomb's? Where is it confirmed?
Non-working mass storage is a potential deal breaker.
honeycomb's. see here or here for details.
Thanks for the links.
This is a real WTF.
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
Relevant code snippet for those interested:
Code:
StorageManager s = (StorageManager)getSystemService(Context.STORAGE_SERVICE);
Class c = s.getClass();
Method m = null;
try
{
m = c.getMethod("enableUsbMassStorage", (Class[]) null);
m.invoke(s);
}
catch(Exception e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
ydaraishy said:
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
Click to expand...
Click to collapse
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
sogrady said:
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Click to expand...
Click to collapse
Well that is interesting . You have read write privileges on the xoom. Sounds like it is a fuse configuration issue. Do you have any other fuse file systems you run?
Sent from my Xoom using XDA App
bigrushdog said:
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
Click to expand...
Click to collapse
Damn it. Looks like I actually need a device to get it working, and the AOSP drop. It's so moronic why they disabled mass storage.
Hmm. Can someone run, from adb shell, the output from "mount", and "ls /sys/devices/platform" for me?
Never mind. Mass storage has been defined out of the stingray (Xoom) kernel. It's not even in the default kernel.
To get mass storage support, be prepared to build your own kernel and reflash the device (once that's done, the am command above or the enabler app will work properly).
I've founded a working(ish) solution. This Xoom forum post details an approach that permits transfer of video/music/etc to the Xoom via Linux.
Couple of caveats:
1. The gnomad2 application is very unstable. Crashes frequently.
2. It appears to be write-only: I have not been able to delete files from the Xoom using this interface.
Thanks for the instructions to connect to a xoom tablet via Linux! However, I'm using Opensuse 11.3 and 11.4 on two different systems. I did install the mtp-tools with no issues, however, there is NO file by the name of mtpfs. A search on the net does not reveal it either. Where do I get this, or what package is it part of? Thanks again. If I can't get this tablet to connect to my linux box, I will have to take it back, since I do NOT use winbloze or Mac. Pretty short sited of Motorola IMHO.
Personally, I've given up on MTP + Linux Combo. I just use a straigt FTP transfer over wifi ( FTP Server on tablet ). It's about the same speeds.
any headway on this...
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
stlsaint said:
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
Click to expand...
Click to collapse
try following the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=981774
They are basically a superset of what I posted. If you still have trouble after that post in either thread (this one or that one) and I will try and help as best I can.
followed the thread up unto the fstab part as i dont wan to edit my fstab without confirmation that it will work. But i get the exact same error with the endpoint text. I am trying this on Crunchbang linux which is based off debain the same way ubuntu is. I am probably going wrong with FUSE somehow but i have never messed with it so i dont know how to troubleshoot it.
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
thats awesome thanks!
good to know thanks
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Yes, but some of us don't feel like paying...or just prefer command line. :]
smaskell said:
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Click to expand...
Click to collapse
What is included in the sdk on the xoom? I know that you can build apps from the command line on windows and linux. I think that this function would really be what I need to buy a tablet (again). Or you might be able to borrow things from the linux sdk.
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
diablo2224 said:
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
Click to expand...
Click to collapse
search "adb wireless"，you can get this awesome free app, it has a widget built-in.
and born at a bit long ago.
ftgg99 said:
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
Click to expand...
Click to collapse
So I checked out the field utils...
Apparently the Xoom has a WCDMA component? That's HSPA+ if I'm right...further supported in the iFixIt teardown.
Turned off the GSM functionality (on by default), hoping it'll save battery...not that I can complain. Battery life on this thing kicks ass.
Here's my question: Does it have an IMEI? As in can I put an AT&T SIM in there and it'll work? I'll try testing it out later. Might be time to pull out the ole' faraday cage...
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
RinTinTigger said:
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
Click to expand...
Click to collapse
Gscript should be able to do it.
AT&T on cdma? Lolwut?
It has an MEID that looks one hell of a lot like an imei, but I can't see an imei anywhere in the tablet. I don't know if the sim slot is active or not. (3g version.)
Sent from my Xoom using Tapatalk
I know this is an older thread but I need some direction in how to get adb in xoom to recognize my NS4G device when plugged in via usbOTG. Is it possible?
Daniel Smith1953
Jewremy said:
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
Click to expand...
Click to collapse
thanks for the info but, I can't get adb on my pc! says it doesn't exist! No idea of where to go for that. Any suggestions?
Dan [email protected]
Thank you for these commands.
I have troubles with developer mode on my phone.
Enable usb debug option is checked, but adb (running under gentoo linux, ubuntu, windows 7) doesn't show any devices.
But when recovery (CWM) is loaded, everything works well.
When I'm trying to start adbd with
Code:
#adbd start
I get message "cannot bind tcp:5037"
I thought it appears because adbd is already running but
Code:
ps aux | grep adb
gives nothing
Any ideas what to do? Does anyone have problems with adb even if Usb debug is turned on?
I use Debian and my command is adb start-server.
Give it a try.
Fr0zen1977 said:
I use Debian and my command is adb start-server.
Give it a try.
Click to expand...
Click to collapse
It doesn't help
Shtsh said:
...But when recovery (CWM) is loaded, everything works well...
Click to expand...
Click to collapse
Looks like ROM problem. Did you tried another one??
Yes. I'm tried several stock ROMs (2.3.6, 2.3.5), cranium, broodROM. Factory reset doesn't help.
Hi Folks
heimdall.7z - 334.63 KB
I thought I'd continue in the same vein as my previous post and add to the Pi's arsenal of android related tools , So here is the Open Source Samsung Flashing utility Heimdall.
There's nothing special about this build, I just cloned the git sources and compiled them on Rapbian. Easy as, well , Pi I suppose
you'll have to install either libusb-1.0-0 or libusb-1.0-0-dev using apt-get.
[ EDIT: ] Do It yourself!
Just for completeness here's the steps if you want to build it yourself using Raspbian
Open a terminal window
Code:
sudo apt-get install git-core libusb-1.0-0-dev
cd ~/
git clone git://github.com/Benjamin-Dobell/Heimdall.git
cd Heimdall/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
cd ~/
rm -rf Heimdall
The configure -> make -> make install workflow is used by a large number of linux tools this make compiling most things for the Pi on the Pi as simple as the steps above. Sometimes finding where the official source code is for a package is the hardest step.
trevd said:
Hi Folks
[ heimdall.7z ]
I thought I'd continue in the same vein as my previous post and add to the Pi's arsenal of android related tools , So here is the Open Source Samsung Flashing utility Heimdall.
There's nothing special about this build, I just cloned the git sources and compiled them on Rapbian. Easy as, well , Pi I suppose
you'll have to install either libusb-1.0-0 or libusb-1.0-0-dev using apt-get.
I've not got a samsung device to hand at the minute but I'm going to give it a test later on
Click to expand...
Click to collapse
Awesome work! Having both ADB and now Heimdall working definitely opens up some really interesting possibilities for the RPi.
Sent from my SCH-I535 using xda premium
I love you trevd!
Sent from my GT-S5830 using Tapatalk 2
did you try it on any phones?
Hi,
I'm glad to see someone else considering using a Pi for this. Did you try using it on any phones?
I don't have a linux or windows machine handy, just a mac (which has some problems with heimdall), so I thought I'd try the Pi for rooting an old Epic 4G (a Galaxy S phone), in order to upgrade to CM10. Unfortunately I ran into two problems:
1) When I plug the phone in (not just the USB cable), the Pi would sometimes completely restart. This didn't happen every time. I think this may be due to power issues (perhaps it was trying to charge, and the Pi couldn't produce the right current), I didn't try a powered hub (I don't have one). But it also could be a software bug crashing the system. Debugging crashes like this is a little beyond my expertise, though if I get some time and can reproduce it I might try some more.
2) I was only able to get heimdall to detect the phone once. Other times it said "no device detected". When it was detected, I flashed clockwork recovery mod (or at least I typed the commands to do so), and it seemed to work (as far as I could tell), but when I started in recovery mode it was a stock recovery. Perhaps it didn't finish? I'm not sure what happened, since heimdall treated it as a success and the phone restarted.
Anyway, I thought I'd give my experience in case anyone else saw either of these problems too (or knew the answers). And I'd be interested to hear if someone had no problems.
Steve
sdeneefe said:
Hi,
I'm glad to see someone else considering using a Pi for this. Did you try using it on any phones?
I don't have a linux or windows machine handy, just a mac (which has some problems with heimdall), so I thought I'd try the Pi for rooting an old Epic 4G (a Galaxy S phone), in order to upgrade to CM10. Unfortunately I ran into two problems:
1) When I plug the phone in (not just the USB cable), the Pi would sometimes completely restart. This didn't happen every time. I think this may be due to power issues (perhaps it was trying to charge, and the Pi couldn't produce the right current), I didn't try a powered hub (I don't have one). But it also could be a software bug crashing the system. Debugging crashes like this is a little beyond my expertise, though if I get some time and can reproduce it I might try some more.
2) I was only able to get heimdall to detect the phone once. Other times it said "no device detected". When it was detected, I flashed clockwork recovery mod (or at least I typed the commands to do so), and it seemed to work (as far as I could tell), but when I started in recovery mode it was a stock recovery. Perhaps it didn't finish? I'm not sure what happened, since heimdall treated it as a success and the phone restarted.
Anyway, I thought I'd give my experience in case anyone else saw either of these problems too (or knew the answers). And I'd be interested to hear if someone had no problems.
Steve
Click to expand...
Click to collapse
I haven't tried this tool at all as I use my pi as a htpc, but i can tell you from experience setting that up that power can be a major issue. I didn't have reboots, but rather all my usb devices would quit working, even powered ones(and the only thing drawing power was a keyboard dongle) and my power supply is supposed to be rated for 2A.
I picked up a 20$ 7 port hub that works almost flawlessly (the 7th port doesn't agree with it). I would recommend picking one up.
Just my 2 cents
Also you don't mention what os you are running but try checking /var/log if it happens again. This is where logs generally get generated
Sent from my DROID3 using xda premium
sdeneefe said:
I'm glad to see someone else considering using a Pi for this. Did you try using it on any phones?
I don't have a linux or windows machine handy, just a mac (which has some problems with heimdall), so I thought I'd try the Pi for rooting an old Epic 4G (a Galaxy S phone), in order to upgrade to CM10. Unfortunately I ran into two problems:
Click to expand...
Click to collapse
Hi sdeneefe,
I never did get round to have a go myself .....but it's top of my new years resolutions list I've got a galaxy S lying around the place to have a go with so I'll let you know my results.
sdeneefe said:
1) When I plug the phone in (not just the USB cable), the Pi would sometimes completely restart. This didn't happen every time. I think this may be due to power issues (perhaps it was trying to charge, and the Pi couldn't produce the right current), I didn't try a powered hub (I don't have one). But it also could be a software bug crashing the system. Debugging crashes like this is a little beyond my expertise, though if I get some time and can reproduce it I might try some more.
2) I was only able to get heimdall to detect the phone once. Other times it said "no device detected". When it was detected, I flashed clockwork recovery mod (or at least I typed the commands to do so), and it seemed to work (as far as I could tell), but when I started in recovery mode it was a stock recovery. Perhaps it didn't finish? I'm not sure what happened, since heimdall treated it as a success and the phone restarted.
Anyway, I thought I'd give my experience in case anyone else saw either of these problems too (or knew the answers). And I'd be interested to hear if someone had no problems.
Click to expand...
Click to collapse
Endoroid said:
I haven't tried this tool at all as I use my pi as a htpc, but i can tell you from experience setting that up that power can be a major issue. I didn't have reboots, but rather all my usb devices would quit working, even powered ones(and the only thing drawing power was a keyboard dongle) and my power supply is supposed to be rated for 2A.
Click to expand...
Click to collapse
Thanks for sharing sdeneefe, I'm no electronics expert, but a educated stab in the dark and given the fun I had myself finding a stable setup combination I'd be tempted to agree with Endoroid, power does seem to be in the hands of the gods. Personally I could not find a charging plug the would supply enough power to keep the HDMI output stable on my monitor.....every other display I've tried works fine apart from the intended main one, partly to do with the monitor I think because it also has trouble with MHL connections. I eventually solved my power woe's by using my computer's USB as the power source.
EDIT: Initial Tests seems OK although I had to run with sudo because I've not configured udev but device is detected and I've pulled and printed the pit. This is both through a powered hub and jacked straight into the device I'll try flash a rom in a bit...... because doesn't everyone spend NYE flashing roms and posting on xda,
wanted to drop this Linux 64 Heimdall 1.4 RC1 built from today's source debian package somewhere
http://d-h.st/2Vj
trevd said:
Hi Folks
heimdall.7z - 334.63 KB
I thought I'd continue in the same vein as my previous post and add to the Pi's arsenal of android related tools , So here is the Open Source Samsung Flashing utility Heimdall.
There's nothing special about this build, I just cloned the git sources and compiled them on Rapbian. Easy as, well , Pi I suppose
you'll have to install either libusb-1.0-0 or libusb-1.0-0-dev using apt-get.
[ EDIT: ] Do It yourself!
Just for completeness here's the steps if you want to build it yourself using Raspbian
Open a terminal window
Code:
sudo apt-get install git-core libusb-1.0-0-dev
cd ~/
git clone git://github.com/Benjamin-Dobell/Heimdall.git
cd Heimdall/libpit
./configure
make
cd ../heimdall
./configure
make
sudo make install
cd ~/
rm -rf Heimdall
The configure -> make -> make install workflow is used by a large number of linux tools this make compiling most things for the Pi on the Pi as simple as the steps above. Sometimes finding where the official source code is for a package is the hardest step.
Click to expand...
Click to collapse
packaged in deb format.... Please let me know if this works.. i had to guess the arch code.
If this doesn't work, it's the arch, and I can repackage properly. I'm working on getting CASUAL support up on the Raspi.
AdamOutler said:
packaged in deb format.... Please let me know if this works.. i had to guess the arch code.
If this doesn't work, it's the arch, and I can repackage properly. I'm working on getting CASUAL support up on the Raspi.
Click to expand...
Click to collapse
No Dice on the arch, My Real Pi was doing not playing nice... but the emulators fails with this
Code:
package architecture (armv6l) does not match system (armhf)
trevd said:
No Dice on the arch, My Real Pi was doing not playing nice... but the emulators fails with this
Code:
package architecture (armv6l) does not match system (armhf)
Click to expand...
Click to collapse
I kinda figured... do this:
Code:
dpkg -i --force-architecture /path/to/heimdal.deb
I will fix the arch later tonight.
AdamOutler said:
I kinda figured... do this:
Code:
dpkg -i --force-architecture /path/to/heimdal.deb
I will fix the arch later tonight.
Click to expand...
Click to collapse
Code:
heimdall depends on libc6 (>= 2.4).
heimdall depends on libgcc1 (>= 1:4.1.1).
heimdall depends on libstdc++6 (>= 4.1.1).
heimdall depends on libusb-1.0-0 (>= 2:1.0.8).
Got some dependency version issues, Is that something you want to/can deal with automatically? or just tell the user to upgrade! I'm not overly familiar with what debs and dpkg etc are fully capable of.... I tend to let apt and aptitude do all the heavy lifting
Could always build a static one I suppose. :good:
I just placed this version of Heimdall into my CASUAL repository. Here is a proper arch Heimdall deb file packaged with the binary from the OP.
https://android-casual.googlecode.com/svn/trunk/GUI/src/CASUAL/resources/heimdall/heimdall_armv6.deb
Code:
dpkg -i heimdall_armv6.deb
This will always be up-to-date with CASUAL's capabilities because this is my source repository, so it's a good link. Let me know if there's any problems.
Hello, this stopped being usable time ago i think. I'm also having big problems compiling heimdall on current 3.12.35+/3.18.3+|4+ kernel Raspbian on rasPi B+, seems to be a libc dependancy problem. Could you please provide a new link instead of android-casual googlecode site? Thank you very much
anyone succeeded in flashing a Pi4 with "Heimdall", the flashing-software ?