I dont really know, if i should post this here, or in an ubuntu forum; but anyway:
I "installed" Lite'ning Rom v3.6 XWLPG with LitePro kernel v3.2.
In windows i can connect to the sd card(s) when using the usb debugging modus, but when in ubuntu, i cant.
Both sd cards are mounted (although they are not in fdisk -l or mount -l, but in nautilus) and i can see the "root" directorys in every one of them, but i cant write data on them.
When trying to copy something, the phone pops up a short notice of "MTP application" but then in ubuntu/nautilus i get an error:
"While copyping a file to gphoto2://[usb:001,006]/store_00010001 an error occured."/ "Error while writing the file: -108: Unknown file or folder" (translated from german)
Anyone got an idea?
BastianF said:
I dont really know, if i should post this here, or in an ubuntu forum; but anyway:
I "installed" Lite'ning Rom v3.6 XWLPG with LitePro kernel v3.2.
In windows i can connect to the sd card(s) when using the usb debugging modus, but when in ubuntu, i cant.
Both sd cards are mounted (although they are not in fdisk -l or mount -l, but in nautilus) and i can see the "root" directorys in every one of them, but i cant write data on them.
When trying to copy something, the phone pops up a short notice of "MTP application" but then in ubuntu/nautilus i get an error:
"While copyping a file to gphoto2://[usb:001,006]/store_00010001 an error occured."/ "Error while writing the file: -108: Unknown file or folder" (translated from german)
Anyone got an idea?
Click to expand...
Click to collapse
Could it be file system issue? i.e. FAT vs ext?
Probably you have USB issues? Download/Install Linux USB driver for your phone.
I dont think, that there is an issue with the filesystem.
It did work with the original kernel etc. (should have mentioned that...)
And ubuntu recognizes the phone: Bus 001 Device 006: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Ubuntu 12.04 usb mtp fix
just found this and it worked for me. i'm running carbon rom 4.3 on my galaxy s2 hercules and it was detected by ubuntu 12.04 with this fix.
http://www.webupd8.org/2013/01/upgrade-to-gvfs-with-mtp-support-in.html
:good:
Related
So, I tried to get jmtpfs to work with my Galaxy S III (the international version, although I suppose the situation would be identical with the US version as well). It doesn't. I tried to use jmtpfs 0.4 with both libmtp 1.1.3 and a git version of libmtp, the result is the same, that is:
Code:
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
what(): Can't open device
Aborted
Very nice indeed. Has anyone managed to get this working, and if so, how? FWIW I'm running 64-bit version of Arch.
(On a somewhat related note, why on earth don't manufacturers support plain old USB mass storage mode? It works pretty much anywhere and with anything)
I've been desperately trying to find a solution to the same problems as well. I'm also running Arch x64. My phone is a rooted international S3 with stock kernel and firmware.
As it seems other phone models don't have this problem.
A workaround is: http://forum.xda-developers.com/showthread.php?t=1711009
However, you'll only be able to access the external SD card this way.
Has anyone been succesful in using/mounting their S3 with any linux distro?
Same case. I can't connect my GS3 to Kubuntu. There is no USB mass storage protocol in the SGS3.
To transfert files between PC and GS3 it's possible to use OTA USB cable and a usb stick.
Or use application in google play : airdroid with wifi..
There is no USB mass storage protocol in the SGS3.
Click to expand...
Click to collapse
Actually there is. It's just not available in the menu.
Use the 'Easy UMS' APK here in XDA (requires root) and you're good to go.
As dieteric already said: only works for external SD though since internal one is virtual.
I am using Neo V official build 4.1.B.0.431 (ICS 4.0.4), rooted, unlocked bootloader (doesn't seem to matter)
I've downloaded the kernel source code, compiled the `usb-storage.ko` module, and placed it on `/system/lib/modules/drivers/usb/storage/`.
I've also changed `/system/etc/vold.fstab`, added this line:
Code:
dev_mount usb /mnt/usbstor auto /devices/platform/msm_hsusb_host.0
Then I restarted the phone.
After that, I typed the commands (using root) in shell:
Code:
mount -o remount,rw /
insmod /system/lib/modules/drivers/usb/storage/usb-storage.ko
cd /mnt
mkdir usbstor
Then I plugged in the OTG cable with a USB Flash Drive.
The storage is successfully mounted (by vold, I think), as I can verify in Root Explorer. I don't have photos so can't verify whether media scanner can detect it.
But in Settings->Storage it didn't appear. Seems that the Settings app don't support. I cannot unmount it using GUI, so when I remove the storage it warns me about that.
Are there any ways to get the Settings app to show my USB storage so that I can unmount via GUI?
Also how to automatically `insmod` and create `/mnt/usbstor` when startup? I won't bother editing ramdisk, but anything under `/system` is fine. I saw a few shell scripts under `/system`, are they fine to use?
Download USB otg from market. It's for both, arc s & neo/ neo v.
Use it with caution it may burn your motherboard....
Sent from my MT11i using xda app-developers app
Fine. I didn't use any piece of compiled binary anywhere else, but I've done the following:
1. insmod and create mountpoint using `/system/etc/pre_hw_config.sh`
2. edited `res/xml/storage_list.xml` in `framework-res.apk`.
Now the USB storage shows up in system storage settings. The name showed "USB storage" though it still shows "mount USB". I can normally use it now.
It seems to be better than using 3rd-party applications.
alvinhochun said:
I am using Neo V official build 4.1.B.0.431 (ICS 4.0.4), rooted, unlocked bootloader (doesn't seem to matter)
I've downloaded the kernel source code, compiled the `usb-storage.ko` module, and placed it on `/system/lib/modules/drivers/usb/storage/`.
I've also changed `/system/etc/vold.fstab`, added this line:
Code:
dev_mount usb /mnt/usbstor auto /devices/platform/msm_hsusb_host.0
Then I restarted the phone.
After that, I typed the commands (using root) in shell:
Code:
mount -o remount,rw /
insmod /system/lib/modules/drivers/usb/storage/usb-storage.ko
cd /mnt
mkdir usbstor
Then I plugged in the OTG cable with a USB Flash Drive.
The storage is successfully mounted (by vold, I think), as I can verify in Root Explorer. I don't have photos so can't verify whether media scanner can detect it.
But in Settings->Storage it didn't appear. Seems that the Settings app don't support. I cannot unmount it using GUI, so when I remove the storage it warns me about that.
Are there any ways to get the Settings app to show my USB storage so that I can unmount via GUI?
Also how to automatically `insmod` and create `/mnt/usbstor` when startup? I won't bother editing ramdisk, but anything under `/system` is fine. I saw a few shell scripts under `/system`, are they fine to use?
Click to expand...
Click to collapse
Hi Alvin,
I´m having big issues with enabling USB Host mode as well (phone does not find any usb devices such as usb mouse or a pendrive), so I would greatly appreciate your help in finding the root of this problem. Here are the details and what I tried so far:
1. Im running on a rooted GT-i8530, leaked 4.1.2 rom with busybox installed
2. android.hardware.usb.host.xml permissions xml file exists in etc/permissions and just mentiones the apache license
3. Running USB host diagnostics I got:
Android API
Claims support yes
classes found yes
device detected no
Rooted API
Claims support N/A
Device detected N/A
Kernel
Claims support Yes
Device detected No
Verdict OS support No
3rd party apps No
4. I tried 3 different USB cables (original samsung one with female to female connector), another original micro usb to female plug, and a no name one,
5. No mouse nor usb sticks (fat32) seem to be recognized (below 200 ma)
6. Had a look into the storage folder and I can see a folder for external sd, sdcard and UsbA-UsbF. These Usb folders have no permissions set ( like rwx). Looking into the mnt folder I can see the same but in there the Usb folders have rwx permissions set.
7. I was thinking to manually mount the pendrive but when type into terminal as su: ls /dev/block there are no devices (like sda, sdb, sdc) or partitions ( sda1...) mentioned. So I didnt even try commands such as mount -t vfat /dev/block/sda1 /mnt/sdcard/usb...Only mmccblk, loop, dm, ram, vold, param is mentioned on dev/block
8. In vold.fstab all usb(a-f) folders including paths are visible
Now I read your post regarding the usb-storage.ko module and I guess thats whats missing for the phone in order to recognize any usb devices. Reason why I think that is because once I connect a usb device I cant even see any sda´s or sda1´s...In system/lib/modules the folder driver is non existent but I found in sys/module/usb_storage/drivers a usb-storage file but its not a .ko What do you think? I would appreciate your thoughts on that one..
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Heathie89 said:
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Click to expand...
Click to collapse
Okay! Step one, you need to make a bootable CWM card.
Get yourself a microSD card, format it, and copy the files from HERE (download, unzip to your SD card).
Power your NT completely down, plug in the card, and then plug in the USB cable.
You should boot to a "cardboard" box screen.
After that, its going to boot into CWM recovery. Now you're not going to have alot of tools on the card at this point, but you may see some errors about stuff not being able to be mounted, etc.
Once you've got that done, post back here, and also include any errors you see!
From there, we can try to figure out exactly what's gone wrong, and the best approach to fix it.
--Also! Include the information about your NT, Is it rooted? What firmware or Rom? Other than powering up, what had you done (If anything) previously before the error!
^ Thanks for your quick reply!
As I wrote in my first post I'm a complete noob when it comes to rooting or hacking any devices. I have not once tried rooting my NT. What I did do though in order to have android as an option on my tablet is buy one of those Nook2Android cards. Now I think I may have accidentally pressed Format SD card or something like that when trying to do something else. That's all that I can think of that I may have done to cause the error.
I'm going to try and make the bootable CWM card right now. I'll make sure to report back!
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Heathie89 said:
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Click to expand...
Click to collapse
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
lag0matic said:
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
Click to expand...
Click to collapse
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Heathie89 said:
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Click to expand...
Click to collapse
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
maxxcool7421 said:
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
Click to expand...
Click to collapse
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
couple different things to try
#1
adb kill-server
adb start-server
adb devices
try this a couple times. my nook did not get hooked until i did this 2,3 times
#2 with the unit booted from cwm recovery *on the sd card*, reboot windows while leaving the device plugged in.
once back in windows try the adb devices command again.
failing that you are where i was. but at least you can get into cwm, mine ceased booting from sd entirely. heres a thought and a test. can you make the bootable-apla SD card and still use the nook via sd card only? or does it freeze up... ?
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
i have had that happen a few times and the problem was that my drivers were not installing correctly. sure it appeared as android adb composite device, but it most likely installed the wrong driver for the wrong device.
this is where things get a bit complicated because you need to look for the product and vendor id's for the nook tablet and modify them correspondingly in the android_winusb.inf.
also make sure you execute the runmefirst.bat
that creates a .android folder in your user folder. that was the step i kept missing when i had your problem with the drivers... ironic right? "runmefirst" and i run it last haha...
I am new to this,I am running Touchpad toolbox,and did a complete reset then Install Android the touchpad folder opens on the PC i then copied over the following 3 .zip files
recovery-clockwork-6.0.4.7-tenderloin.zip
gapps-kk-20140105.zip
cm-11-20140609-UNOFFICIAL-tenderloin.zip
then eject touchpad from pc and unmount.
I just keep getting the error NO RECOVERY FILE FOUND, ABORTING
Could someone help please,I don't know what to do.
Thanks...
Touchpad Toolbox Install Android, error "No supported recovery file found. Aborting."
coleraine said:
I am new to this,I am running Touchpad toolbox,and did a complete reset then Install Android the touchpad folder opens on the PC i then copied over the following 3 .zip files
recovery-clockwork-6.0.4.7-tenderloin.zip
gapps-kk-20140105.zip
cm-11-20140609-UNOFFICIAL-tenderloin.zip
then eject touchpad from pc and unmount.
I just keep getting the error NO RECOVERY FILE FOUND, ABORTING
Could someone help please,I don't know what to do.
Thanks...
Click to expand...
Click to collapse
TouchPad 32GB using TouchPad Toolbox v40 2014-05-18
similar error with this Syntax:
No supported recovery file found. Aborting.
** It turns out, this is the same message after the Unmount Media Volume step, even if I don't copy any files to HP Touchpad/ttinstall
** Not sure what is causing this, and at this point I don't know what I should do to load KitKat or get a bootable Android
THIS WAS A BAD USB CABLE - It appeared to work fine for TPToolbox load, but that is deceptive,
the zip files copied are never valid!! Once I switch to new mini-usb it was fine....
SOLVED BY THREAD http://forum.xda-developers.com/showthread.php?t=2774779&page=2
which was excellent effort in the debugging process ...Where do these other cables come from?
Stop after "Detecting Android-x86" (was: How to install on USB stick on Linux)
Hi
How do I install the 2.0.102 beta 32bit version on a USB stick, so that I can boot it? I'm on Linux.
I tried the easy way with the following command, but the system won't boot from the stick:
Code:
sudo dd if="Remix OS for PC Beta 32-bit.iso" of=/dev/sdi
(/dev/sdi was the correct device - verified by checking the dmesg output.)
I see that there's some "Remix OS Installation Tool.exe" program, but that's just for Windows.
Thanks,
Alexander
alexs77 said:
Hi
How do I install the 2.0.102 beta 32bit version on a USB stick, so that I can boot it? I'm on Linux.
I tried the easy way with the following command, but the system won't boot from the stick:
Code:
sudo dd if="Remix OS for PC Beta 32-bit.iso" of=/dev/sdi
(/dev/sdi was the correct device - verified by checking the dmesg output.)
I see that there's some "Remix OS Installation Tool.exe" program, but that's just for Windows.
Thanks,
Alexander
Click to expand...
Click to collapse
If you're on Ubuntu , follow this thread. Works great!
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
Yes, I'm on Ubuntu, but I don't want a dual boot and I'd need RemixOS on a USB stick, so that I can use it on a different PC.
Isn't there an easy way to get RemixOS on a USB stick? dd would be easy
alexs77 said:
Hi
How do I install the 2.0.102 beta 32bit version on a USB stick, so that I can boot it? I'm on Linux.
I tried the easy way with the following command, but the system won't boot from the stick:
Code:
sudo dd if="Remix OS for PC Beta 32-bit.iso" of=/dev/sdi
(/dev/sdi was the correct device - verified by checking the dmesg output.)
I see that there's some "Remix OS Installation Tool.exe" program, but that's just for Windows.
Thanks,
Alexander
Click to expand...
Click to collapse
Make sure you type the underscores in the "if" and "or" commands for the file names. The code you posted will not work without the actual correct file name. Perhaps you left them out in your code example. Hope this helps.
Don
Unetboot works the same as the Official RemixOS installer.
Stop after "Detecting Android-x86..... found"
As it turned out, the "installation" on the USB stick worked - it's just, that RemixOS doesn't work and halts during boot. I took some photos (attached) and also a short video, please see my "RemixOS vs. HP Thin Client" Google Photos album for that.
It stops after "Detecting Android-x86..... found". The "Remix OS for PC" Google Groups has a lot of reports regarding that. But until now, no solution, it seems.
u guys tried booting with DEBUG=1?
freelancer81 said:
u guys tried booting with DEBUG=1?
Click to expand...
Click to collapse
Yes, I tried booting with DEBUG=1. Doesn't help. The last message I see is "Detecting Android-x86..... found" and then the screen turns black.
whats the specs of your computer?
After having added "nomodeset vga=31b" to the boot command line in Grub, it boots.
But, boy, is that slow
The system is a HP T5740 HSTNC 006 TC thin client system. Piece of crap, to be honest
Intel Atom N280 1.66 GHz
System Memory: 2GB
Graphics: Intel GL40
Worked on my old Macbook pro 1,1 ssd
Its very slow... but its booting now...