Related
So I just installed Ubuntu 10.10 on my PC and I'm really digging it. But when I try to mount my sdcard from the phone, it doesn't show up under my places menu. I'm running GSB 1.8.1. I don't have a problem mounting it under windows XP, and also have no problem using the wired tether function. Is there anything I can change on the phone or in Ubuntu to fix this?
I am running Ubuntu 10.04 LTS - inside a Virtual Machine - and I can mount the drive from inside the VM. (Believe me, that's even trickier than what you are trying).
But, 10.10 might have had some changes, and I wouldn't be surprised if your result depended on which desktop you are running; so maybe you need to mount the thing manually.
Try this:
With the phone unplugged, type
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Cancel the "tail" command (Ctrl-C) and do a
# mount | grep sdb1
( note device name "sdb1" ; use whatever you saw previously )
This will show you if the device is already mounted somewhere.
If the device has not been mounted, you can manually mount it, as in:
# mkdir -p /mnt/Eris_SD
# mount -o rw /dev/sdb1 /mnt/Eris_SD
( Again, note device name "sdb1" - use whatever you saw previously. If it doesn't recognize the file system, use "mount -o rw -t vfat /dev/sdb1 /mnt/Eris_SD" )
Hopefully that will do it. Don't forget to "umount /mnt/Eris_SD" when you are done.
If the device never shows up in the /var/log/messages file, then you have some other problems.
If you don't see anything in the log file indicating USB activity, well - you ought to investigate what is going on at the USB port.
Right now my phone is booted into Amon_RA; if I issue the "lsusb" command, I see:
Code:
Bus 001 Device 031: ID 0bb4:0c98 High Tech Computer Corp.
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Another thing that you might try to make things more automatic is the instructions in "Step #5" of this XDA post. This is meant for allowing an unprivileged user on your Ubuntu box to use ADB or fastboot without needing to "sudo" to root. I did this on my VM - I don't think that's the reason that the phone automounts into the SD drive, but perhaps it is related - the same "Vendor_ID" is in use when the phone is in "Composite ADB mode".
When you get to the part in these instructions about restarting the "udev" subsystem, unplug your USB cable first - and then see what you get when you plug it in and fire up the SD export from the phone.
hope that helps.
bftb0 said:
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Click to expand...
Click to collapse
I noticed this on my desktop with a full install of Ubuntu. I knew it was connected because the charge led was lit, but I would have to unplug the usb and plug it back in almost every time just to get it to mount or connect to the internet with wired tether. I never messed with it BUT it did seem to fix itself once I started doing the system updates on Ubuntu.
bftb0 said:
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Click to expand...
Click to collapse
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
In case this helps, GSB mounts the SD card through USB just fine with Windows. Don't take my comment as a Windows versus Ubuntu, thing, however. Just for whatever it's worth.
prsguitaruser said:
I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Glad to here you got this fixed
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Great news! I don't know how I missed your edit since I quoted it in my last response. I must've had this thread open in my browser from before, and went to respond to it after your edit.
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
prsguitaruser said:
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
Click to expand...
Click to collapse
Are you using the tethering abilities built into CM7 (for wired you have to use the Tether Widget from the market, but that's it), or are you using the "for root" apps? IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
roirraW "edor" ehT said:
IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
Click to expand...
Click to collapse
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
wildstang83 said:
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
Click to expand...
Click to collapse
Just curious, did you have the opportunity to try the native tethering under Froyo/CM6 as well, or did you only try it under CM7? I haven't needed the tethering since before I started to try CM7, so I actually don't know from personal experience if Cyanogen has made the tethering work correctly under it yet. I didn't have any trouble with it under CM6, besides the usual occasional semi-random tethering failures.
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
adaneshade said:
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Thanks, I'll keep them both in mind. I tried PDANet a long time ago and it didn't keep the tethering from failing, but maybe they improved it.
Didnt want to further muck up the CM9 development thread. CM9 .04 doesnt want to boot for me, and potentially others with an 8gb NT. I'd love to get help and potentially help others but Fattire has requested logs in order to help figure out the problem. Problem is I'm very new to this and could use some help generating whatever log files I can. I'm on a windows machine, no knowledge of Linux. CM9 reboots right after the Cyanoboot screen(can still use cyanoboot to access recovery etc). If its too much of a hassle to help me figure this out, no worries, I can stick to stock for now.
http://forum.xda-developers.com/showthread.php?t=1474956
To output logcat to a txt file:
adb logcat > logcat.txt
First confirm you have ADB working. Then try the above command just after you turn the NT on. It will log everything up until the NT reboots itself.
lost101 said:
http://forum.xda-developers.com/showthread.php?t=1474956
To output logcat to a txt file:
adb logcat > logcat.txt
First confirm you have ADB working. Then try the above command just after you turn the NT on. It will log everything up until the NT reboots itself.
Click to expand...
Click to collapse
I got the NT to appear as Android Composite ADB Interface in the device manager(it also appears as Usb Mass storage), however I cant get it to appear when when I check adb devices in cmd. Tried uninstalling and re-installing the drivers still no luck. In Cm9 I verified that Usb Debugging is enabled but it still doesn't want to appear.
Try rebooting; or perhaps: http://forum.xda-developers.com/showthread.php?t=1550603
Maybe the 'Usb Mass Storage' entry should actually be installed as Android Composite ADB.
lost101 said:
Try rebooting; or perhaps: http://forum.xda-developers.com/showthread.php?t=1550603
Maybe the 'Usb Mass Storage' entry should actually be installed as Android Composite ADB.
Click to expand...
Click to collapse
Ok, I got it to output a log file from within .03, and it shows up under adb devices. I tried installing .04 and starting the log just as i start up, but all I seem to get is CMD saying -waiting for device-. The NT appears to be resetting before windows notices the device. It creates the logfile but its empty. I miss something?
Hello,
My vibrant got recently run over by a car and the screen doesn't work anymore However, I know that it still can function because I can see the 4 capacitive keys on the bottom light up when I touch them. Is there anyway for me to be able to view the Vibrant's harddrive on my computer without having to switch to USB mode (since my screen doesn't work)?
if you have adb installed and know some basic linux commands you can use ADB to view the contents of your vibrants storage via command prompt and should be able to copy most of your data over. As far as a graphical solution i think there was something being developed called screen cast at some point but i dont think that will be much use to you as i believe it has been abandoned
I am familiar with adb but I can't see my device for some reason when I connect my phone to my computer and run 'adb devices'. I've used adb in the past to push / pull files but I remember having to mount the device from the dropdown menu before it would be recognized. Is there any way to force the phone to be connected? Thank you for your help!
isyiwang said:
I am familiar with adb but I can't see my device for some reason when I connect my phone to my computer and run 'adb devices'. I've used adb in the past to push / pull files but I remember having to mount the device from the dropdown menu before it would be recognized. Is there any way to force the phone to be connected? Thank you for your help!
Click to expand...
Click to collapse
are you on a stock rom? ever since i started using custom roms ive always had ADB debugging enabled, unfortunately you may be SOL if you need to enable ADB debugging as both the adb method and screen cast require ADB to work,the other option is to take apart your vibrant and have the internal memory chip read that way tho your stand a good risk of damaging the internal memory chip
I have been trying for a few days not to get my NT to connect to ADB in CWM. I am having no luck.
I am able to connect and browse the 1 gb partition and the sd card in windows but cannot connect to adb even when the tablet is running.
It has been a while since i have messes with my NT but i currently running nightly CM and have CWM 6.0.0.0 installed as well.
I am sure i am just missing someting simple to accomplish this task but my searches are leading me know where.
I have also tried both in linux and windows to connect to ADB.
I feel one of my problems may be that i do not have debugging turned on in my ROM but i cant seem to find that either.
Any guidance or a link would be greatly apreciated.
Thanks in advance.
"ADB Debug" setting is under Settings->Developer's Options.
If you're trying to use ADB over USB, see also http://forum.xda-developers.com/showthread.php?p=35971559#post35971559.
Hey Guys,
Been lurking for a while. I want to get into some Android development. I bought a cheap Galaxy Tab s SM-T800 from ebay. It was a retail unit, so came with the usual retail protection, but that was no issue, I've reflashed it and rooted it, it is now running 6.0.1 with build number MMb29K.T800XXU1CRJ1.
The issue is, there are a bunch of apps and files that appear to be left over from the retail demo mode, and I can't remove them. The apps won't uninstall, it just says "uninstall unsuccessful", and the files, when I try to delete them, it just says "failed to delete".
Even after freshly restoring the new firmware, the storage on this device is pretty much zero, a lot of the space being taken up with the files and apps that I can't remove.
There was just about enough space remaining to install System App Remover, but that couldn't delete the files and apps either.
How are these files being write protected? How do I go about removing the write protection? I'm wondering if this device, because it was a retail demo unit, was configured with some kind of write protected partition, which is why the storage is so low, and why I can't delete the apps?
Any thoughts, this is driving me nuts.
Thanks
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
jwoegerbauer said:
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
Click to expand...
Click to collapse
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
DotNetDude said:
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
Click to expand...
Click to collapse
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
jwoegerbauer said:
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
Click to expand...
Click to collapse
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
DotNetDude said:
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
Click to expand...
Click to collapse
I realise I am responding to my own message!
Now that I am running with adb insecure, I have realisd that the USB debugging mode from developer settings is working in reverse. That is, if I enable it, the tab detaches form the PC. If I disable it, the tab reconnects to the pc. However with that setting disabled, and the pc connected, when I then run the command adb devices, it says there are no devices connected (even though I can browse to the tablet through windows explorer)
From within the adb insecure app on the tablet, when I enable the app, I can see it displays a message that says USB debugging is disabled.
I have no idea what is going on here...
Any help much appreciated?
Thanks
@DotNetDude
May be reading this helps.
jwoegerbauer said:
@DotNetDude
May be reading this helps.
Click to expand...
Click to collapse
Thanks for this. Actually, adbd insecure was just causing more problems. In the end I have resolved this by extracting the PIT file and re-partitioning. Firmware then restored correctly and all the problems are now gone, and there is plenty of free space remaining.