[USB OTG] can't write on usb stick - Nexus 5 Q&A, Help & Troubleshooting

usb otg helper crashes when trying to mount ntfs drives and doesn't even notice when a fat32 one is insered...stickmount works perfect in reading but i can't get it to write on disks, usb sticks neither hard disks...i thought the cause was the stick formatted in ntfs, so i formatted it in fat32 but still i can't modify anything...i got this error:
https://www.dropbox.com/s/tr3vs6h9o2528vf/Screenshot_2014-02-05-19-57-13.png

really no one has a solution?

Not seen it before but can tell that it hasn't mounted correctly anyway from the screenshot. Looks like incorrect permissions. What kernel is it? What is the output of the "mount" command in terminal emulator?

thanks for your reply, i'm on franco kernel r32...i gave the mount command (without su, am i wrong?) and this is the output...
https://www.dropbox.com/s/gll2yuemglu9t0l/Screenshot_2014-02-07-15-59-04.png

Is teh USB stick definitely plugged in? cant see it there at all?
You could test with other kernels too, maybe elementalx, chaos if you're on a cm rom (actually neither of those need stickmount - just check /storage for the drive.)

i'm on stock rom...anyway i tried with another usb stick, and i was able to modify/delete folders...it worked! so it means that i have to bear the annoying fact that some usb sticks are not compatible for unknown reasons??

Related

Accessing Usb thumb drive.

I have been working my way thru several posts tonight but still can not access my thumb drive.
Wifi xoom running tiamat rom. Official Motorola camera connection cable. Sandisk cruzer USB thumb drive formatted to fat32.
I have a folder labeled usbotg on the xoom (not on the sdcard) but nothing shows. Whati step am I missing?
can you show us the outcome of "df" on your xoom?
rkboid said:
I have been working my way thru several posts tonight but still can not access my thumb drive.
Wifi xoom running tiamat rom. Official Motorola camera connection cable. Sandisk cruzer USB thumb drive formatted to fat32.
I have a folder labeled usbotg on the xoom (not on the sdcard) but nothing shows. Whati step am I missing?
Click to expand...
Click to collapse
Did you download the latest version of the USB Mass Storage Watcher app from the market? Also, I have found that when I insert a usb drive, I usually have to reboot to see it in the /usbOTG folder.
qwerp - "df" ? Is that an adb command? if so I assume I need run it after I have inserted the USB?
okantomi - Yes I installed it, but it does not see that I have plugged in a thumb drive.
A little more info - my USB mouse works without a problem - The light on USB/USBs flash and then does become solid.
rkboid said:
qwerp - "df" ? Is that an adb command? if so I assume I need run it after I have inserted the USB?
okantomi - Yes I installed it, but it does not see that I have plugged in a thumb drive.
A little more info - my USB mouse works without a problem - The light on USB/USBs flash and then does become solid.
Click to expand...
Click to collapse
df is the command you run in the terminal to see devices mounted on your drive.
if you are running the latest tiamat kernel, you do not need the USB watcher.
you see something like
/mnt/usbOTG 1G 1G xxxxxxx
also, can you do a "ls" under /dev/block/ ?
rkboid said:
qwerp - "df" ? Is that an adb command? if so I assume I need run it after I have inserted the USB?
okantomi - Yes I installed it, but it does not see that I have plugged in a thumb drive.
A little more info - my USB mouse works without a problem - The light on USB/USBs flash and then does become solid.
Click to expand...
Click to collapse
I'm not sure if its a power problem or the unusual way the built-in Sandisk software mounts the drive (it mounts as a "cd drive" in Windows); but Sandisks are problematic.
If you can, please try another thumb drive just to be sure. Preferably, one with no lights (to minimize power requirements) and not a Sandisk or Kingston, which both use proprietary built-in software upon insertion into PC usb ports.
Try downloading an app call USB Mass Storage. Its not in market but I found the thread. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1068999
Try flashing the kernel in that thread through recovery. Make sure you flash the correct images first.
When I run "df" in terminal i get/data/media/extrenal and /mnt/sdcard.
I am going to flash the tiamet kernal seperate from the rom and see if that fixes things.
Might be obvious to everyone else but when I first plugged a drive in I noticed two folders called usbOTG, one in the root and one in /mnt/usbOTG. The one in the root is always empty and the one in /mnt is the one I need to access. Again, not sure if relevant but just thought I'd share
burden010 said:
Might be obvious to everyone else but when I first plugged a drive in I noticed two folders called usbOTG, one in the root and one in /mnt/usbOTG. The one in the root is always empty and the one in /mnt is the one I need to access. Again, not sure if relevant but just thought I'd share
Click to expand...
Click to collapse
I just looked at my Xoom's file system again, and actually, the relevant usbOTG folder is on the root. It's on the same directory level as the internal sdcard that contains all of your apps. There is also a mnt/ folder that contains the external sdcard as well as another usbOTG folder (among other things), but that one is empty.
I apologize for having given a wrong location for the usbOTG in the past. I was being lazy.
Edit: I don't know, it's possible that your file system may show usbOTG at a different location, but I just checked again, and mine is on the root. Also can completely hot-swap, no reboot needed. (That's for fat32.)

[Q] External USB drive not mounted, TF101G, Katkit 4.3 019

[PARTIALLY SOLVED]
Description of the issue: when I insert an USB drive at any of the USB dock ports, the drive is not mounted.
Conditions of the tests:
Asus Transformer TF101G
ROM: Katkit 4.3_0.19.zip
Kernel: Katkernel_106b_JB4.3_Lidpatch.zip
Gapps version: gapps_4.2.2_TF101_20130323b.zip
- I followed the exact procedure listed for flashing.
- Issue reproduced right after flashing and before restoring anything.
- I have not found any specific reference at the known issues.
- I have used a 256MB, 1GB & 16GB USB drives (all FAT32) and the drives have been tested on other devices to be sure they are working properly.
- Additionally I have observed the following: (when the USB drive is plugged in)
I selected: Settings --> storage --> external devices
It shows the option "USB device 1" --> "Activate SD Card" activated, however nothing happens; the USB drive is not mounted even after clicking on it.
I am not sure if I have missed anything, if so, please let me know it.
Any idea/suggestion about what can be the problem?
Kind regards,
PD. My external Mini SD Card (32GB) when inserted in the SD Card slot is working fine.
--------------------------------------
Attached files: (in one .zip file)
Dmesg, top, lc : obtained before connecting the USB drive.
Dmesg1, top1 y lc1: obtained after connecting the USB drive.
Dmesg2, top2 y lc2: obtained after click at "Activate SD Card".
What was on your TF101 prior to flashing KatKiss 4.3/19? Did you do a full wipe if coming from a different ROM? Did you wipe system if coming from an older KatKiss?
I have tried multiple USB (even with all slots filled: 2 USB, 1 SD Card, 1 MicroSD) and they have mounted on my TF101 with KKbuild19 and 20.
mak8tack said:
What was on your TF101 prior to flashing KatKiss 4.3/19? Did you do a full wipe if coming from a different ROM? Did you wipe system if coming from an older KatKiss?
I have tried multiple USB (even with all slots filled: 2 USB, 1 SD Card, 1 MicroSD) and they have mounted on my TF101 with KKbuild19 and 20.
Click to expand...
Click to collapse
Sorry, I forgot to add such information. Thanks for your help.
Before 4.3/19 I had 4.3/16 which was giving also the same problem. I did a Format /system as indicated in the instrutions (no full wipe / factory reset).
I flashed gapps again and wiped as indicated.
Micro SD is not problem at all. It is just USB drive inserted in any of the USB slots of the dock or in the tablet with the Asus USB adaptor.
Try just flashing the ROM and not the 106b kernel. The kernel included with build 019 is a rurally 106e. The extra letter does not show in settings. See if that works better.
frederuco said:
Try just flashing the ROM and not the 106b kernel. The kernel included with build 019 is a rurally 106e. The extra letter does not show in settings. See if that works better.
Click to expand...
Click to collapse
First of all, thanks for your reply.
Please, forgive me if my comments sound silly.
When I flashed the build 019 I did NOT flashed the kernel.
I flashed the kernel when I flashed build 016. I though that flashing the ROM only was not overwriting the kernel.
I understand from you reply that flashing the ROM will overwrite the kernel.
If that is the case, then my current kernel is the one included with build 019.
I wonder if it is possible to confirm it?
Regards,
-----------------------------
ASUS Transformer TF101G, 3G, with Keyboard Doc -
Katkiss 4.3 build 019
fjherna said:
First of all, thanks for your reply.
Please, forgive me if my comments sound silly.
When I flashed the build 019 I did NOT flashed the kernel.
I flashed the kernel when I flashed build 016. I though that flashing the ROM only was not overwriting the kernel.
I understand from you reply that flashing the ROM will overwrite the kernel.
If that is the case, then my current kernel is the one included with build 019.
I wonder if it is possible to confirm it?
Regards,
-----------------------------
ASUS Transformer TF101G, 3G, with Keyboard Doc -
Katkiss 4.3 build 019
Click to expand...
Click to collapse
You can always wipe the system partition. This will ensure the old kernel is gone. Then flash the ROM and GAPPS.
pexecum Tèim
frederuco said:
You can always wipe the system partition. This will ensure the old kernel is gone. Then flash the ROM and GAPPS.
Click to expand...
Click to collapse
:crying:
I did a full re-install of the ROM. I followed this steps:
- Backup everything
- Go to recovery
- Make a full wipe / factory reset
- Format /system
- Flash the ROM (4.3 #019)
- Flash the gapps
- Wipe cache / dalvik
- Reboot
After Reboot I ONLY set up my WIFI and my google account.
I tried inserting USB drives (1GB, 2GB FAT32) but none of them was mount.
I inserted a Mini SD Card and it was mount without problem.
I'm attaching the LOG files (lc1, dmesg1, top1) just in case anyone could see anything related with the problem.
Apparently the USB device is recognize but it is not mounted for any reason. (See dmesg1)
I am running out of ideas what can be the problem.
Regards,
At this point, it seems you've done all you can to get the OS to a known baseline. Since it's not working, you might be forced to try a external USB mount application as per Timduru's tip's page:
http://public.timduru.org/Android/tf101/KatKiss/4.3/#tips
Code:
- Certain NTFS disk won't automount: might be dependant on the formatting and/or partitionning ?
=> workaround: try a 3rd party app to mount it: USB OTG Helper, paragon ntfs or the K.A.T app.
Despite his mentioning it mostly for NTFS formatted devices, this might still apply to you.
[partially solved]
mak8tack said:
At this point, it seems you've done all you can to get the OS to a known baseline. Since it's not working, you might be forced to try a external USB mount application as per Timduru's tip's page:
http://public.timduru.org/Android/tf101/KatKiss/4.3/#tips
Code:
- Certain NTFS disk won't automount: might be dependant on the formatting and/or partitionning ?
=> workaround: try a 3rd party app to mount it: USB OTG Helper, paragon ntfs or the K.A.T app.
Despite his mentioning it mostly for NTFS formatted devices, this might still apply to you.
Click to expand...
Click to collapse
-------------------------------
:cyclops:
I have partially found a way to mount the USB external drives.
I installed USB OTG Helper (Free version). I plan to test the paid version for obtaining some debugging info.
I was able to mount ONE USB drive (If one USB drive was mounted I could not mount a second USB drive at the other USB port).
It worked with 256MB, 2GB, 8GB USB drives, however it did not worked for 16GB USB drive.
The mounting point was:
/storage/Usb0tgDrives/drive_1
It did not worked with K.A.T. and I have not tried with paragon ntfs yet.
Rgds,
fjherna said:
-------------------------------
:cyclops:
I have partially found a way to mount the USB external drives.
I installed USB OTG Helper (Free version). I plan to test the paid version for obtaining some debugging info.
I was able to mount ONE USB drive (If one USB drive was mounted I could not mount a second USB drive at the other USB port).
It worked with 256MB, 2GB, 8GB USB drives, however it did not worked for 16GB USB drive.
The mounting point was:
/storage/Usb0tgDrives/drive_1
It did not worked with K.A.T. and I have not tried with paragon ntfs yet.
Click to expand...
Click to collapse
Additional info:
I have tried "StickMount" and it worked really fine. :good:
It made possible to mount two USB drives (one at each USB port) without problem.
Mounting point:
/data/media/0/usbStorage/sda
/data/media/0/usbStorage/sdb
I will report if I test anything else.
:laugh:

NTFS formatted pendrives doesn't work with PA 4.4

Hi, I'm using PA 4.4 RC1 with ElementalX kernel, and I can't get to work my two USB 3.0 pendrives with NTFS filesystem (exFAT doesn't work too). FAT natively works fine, so this isn't cable or pendrives fault. StickMount gives me an error "The service is busy - try again in a few seconds", when clicking Mount or Unmount. Paragon exFAT, NTFS & HFS+ and USB OTG Helper doesn't works too
Logs of StickMount: pastebin. com/z1kuD8nD
Logs of Paragon: pastebin. com/acdgaiFy
For USB OTG Helper I can't find any logs, and Debug info gives an error "Debug data collection failed".
So is there possibility to get it working, preferably without any additional apps?
Note; I'm using builtin SuperUser, which comes with PA, and I would like to not change it.
And sorry for my bad English :laugh:
Even I'm using ElementalX and all the three file systems which you've mentioned work fine here. However, I've seen many people who have a problem of their NTFS formatted drives not getting detected. I guess it's just the way it is!
Ntfs is spotty on a devices that use otg. I had no issue getting my 1tb external attached to my phone and nexus 7 without issue.
Sent from my Nexus 5 using Tapatalk
pshela94 said:
Hi, I'm using PA 4.4 RC1 with ElementalX kernel, and I can't get to work my two USB 3.0 pendrives with NTFS filesystem (exFAT doesn't work too). FAT natively works fine, so this isn't cable or pendrives fault. StickMount gives me an error "The service is busy - try again in a few seconds", when clicking Mount or Unmount. Paragon exFAT, NTFS & HFS+ and USB OTG Helper doesn't works too
Logs of StickMount: pastebin. com/z1kuD8nD
Logs of Paragon: pastebin. com/acdgaiFy
For USB OTG Helper I can't find any logs, and Debug info gives an error "Debug data collection failed".
So is there possibility to get it working, preferably without any additional apps?
Note; I'm using builtin SuperUser, which comes with PA, and I would like to not change it.
And sorry for my bad English :laugh:
Click to expand...
Click to collapse
cm11 suports ntfs read and write out of the box, it also supports exfat. I managed to implememt this feature to my aosp rom. You can try to do the same with paranoid android. I can help you with the rom building. Contact me via e-mail if you are intrested: [email protected]
Tapatalk-kal küldve az én Nexus 5-el

[Q] Wiped storage, now USB OTG not being mounted by TWRP v2.8.0.1

Hi,
I'm in deepsh*t right now !! ... I was about to install new ROM for my Moto G XT1033, so I wiped clean everything, and while doing the same way, USB OTG was inserted, went back to mount option to mount the USB OTG, but it doesn't mount it, basically I click on it and it doesn't work, is there any other way or I will have to throw away my phone now ??
Is there a way to manually move ROM data to the root directory or under any directory there using just a cable and adt-bundle ??
Nevermind
TWRP wasn't detecting it due to some FS related issue of the pendrive, i just formatted the pen drive from TWRP, though it wasn't mounting I just wanted to check the wipe option for USB OTG, and it formatted into its recognizable FS, i think it would still be NTFS, but anyway, working now !! ... Almost had a heartattack ...
But anyway, if anyone knows, if similar happens, how to move files directly under root access using some tool or commands, connecting the phone with USB and laptop please give an update
devlamania said:
TWRP wasn't detecting it due to some FS related issue of the pendrive, i just formatted the pen drive from TWRP, though it wasn't mounting I just wanted to check the wipe option for USB OTG, and it formatted into its recognizable FS, i think it would still be NTFS, but anyway, working now !! ... Almost had a heartattack ...
But anyway, if anyone knows, if similar happens, how to move files directly under root access using some tool or commands, connecting the phone with USB and laptop please give an update
Click to expand...
Click to collapse
Use adb sideload
Agree with post above. Just use either ADB to push a file to your phone or use ADB to sideload a ROM to install.
Try this!
devlamania said:
Hi,
I'm in deepsh*t right now !! ... I was about to install new ROM for my Moto G XT1033, so I wiped clean everything, and while doing the same way, USB OTG was inserted, went back to mount option to mount the USB OTG, but it doesn't mount it, basically I click on it and it doesn't work, is there any other way or I will have to throw away my phone now ??
Is there a way to manually move ROM data to the root directory or under any directory there using just a cable and adt-bundle ??
Click to expand...
Click to collapse
Goto Fastboot Mode and Install philz_touch_6.57.9-falcon.img and try using OTG cable. Make sure the pendrive you use is in FAT 32 format.
exactly
CedricAndroidlover said:
Goto Fastboot Mode and Install philz_touch_6.57.9-falcon.img and try using OTG cable. Make sure the pendrive you use is in FAT 32 format.
Click to expand...
Click to collapse
Im not too sure, but i think i have used ntfs before, but as you mentioned fat32 works

USB OTG not working in TWRP

I have a problem/question : I want to use USB dongle to flash Q beta, pendrive connected via USB dongle is visible if in the system, but when I reboot to recovery, then it is not. In Install menu I s go to Select storage then USB OTG shows 0 MB and I cannot access it and if I go to Mount menu, USB OTG is not ticketed, but I cannot tick it/mount it (when I press it, it dyas unticketed). Any solutions to that? I tried it on stock kernel and also on Blu spark.
make sure your drive is the correct format. likely the problem
knives of ice said:
make sure your drive is the correct format. likely the problem
Click to expand...
Click to collapse
Well it is FAT32, so I think it is ok? Besides as I said - when system is running, files manager sees pendrive and all the files, only in TWRP it cannot be seen...
spawnn617 said:
Well it is FAT32, so I think it is ok? Besides as I said - when system is running, files manager sees pendrive and all the files, only in TWRP it cannot be seen...
Click to expand...
Click to collapse
If it's a usb-c drive try flipping it over.
Even on q betas I've never had an issue with the drive not mounting.
Usually it automounts once you select it as storage. It will show 0mb till you click it
spawnn617 said:
Well it is FAT32, so I think it is ok? Besides as I said - when system is running, files manager sees pendrive and all the files, only in TWRP it cannot be seen...
Click to expand...
Click to collapse
Did you mount it in twrp?
twinnfamous said:
If it's a usb-c drive try flipping it over.
Even on q betas I've never had an issue with the drive not mounting.
Usually it automounts once you select it as storage. It will show 0mb till you click it
Click to expand...
Click to collapse
Yeah I know, but clicking it does nothing unfortunately - doesn't open it nor change 0 MB.
lollyjay said:
Did you mount it in twrp?
Click to expand...
Click to collapse
I tried as I described in first post "if I go to Mount menu, USB OTG is not ticketed, but I cannot tick it/mount it (when I press it, it dyas unticketed)" - is there any other way to mount it?
twinnfamous said:
If it's a usb-c drive try flipping it over.
Even on q betas I've never had an issue with the drive not mounting.
Usually it automounts once you select it as storage. It will show 0mb till you click it
Click to expand...
Click to collapse
Flipping it over sever times also didn't help...
Maybe I should somehow activate USB OTG in the Rom/kernel so it can be used in recovery? Any ideas?
Solved maybe somehow? I have the same.
Did anyone find a fix for this?
Hi, same thing happend to me. The USB drive can't be mount and it's not seen in TWRP. I tried with the drives, intending to do a backup, but with no success.
its probably a slow usb 2.0 drive or the adapter making it mount really slow or when twrp boots goto reboot recovery and reboot it sometimes twrp cant decrypt put on pc and transfer to phone in recovery
ecompton59 said:
its probably a slow usb 2.0 drive or the adapter making it mount really slow or when twrp boots goto reboot recovery and reboot it sometimes twrp cant decrypt put on pc and transfer to phone in recovery
Click to expand...
Click to collapse
It is a 2.0 drive but it works fine once the phone is booted. I will try a 3.0 or a USB C drive later.
Sent from my GM1917 using Tapatalk
If on 10 twrp is weird i use USB 2.0 one has changed its format to raw lol used dispart on PC to fix the writing speed is too slow my Samsung 64gb Evo works great and the OnePlus otg adapter works best eBay 3.95
twrp error 2 usb-otg
Between a twrp, I get this error, when repairing: /sbin/fsck.fat -y process ended with error:2 unable to repair usb-otg.
unable to repair usb-otg
formatting usb-otg using mkfs.fat...
mkfs.fat process ended with error: 1
unable to wipe usb-org.
error changing file system.
updating partition datails...
...done
wipe
partition options for: usb-otg
mount point: /usb-otg
file system: vfat
present: no removable: yes
size: 0MB used: 0MB
free: 0MB backup size: 0MB
Any one solved this?
I have also 0b and can't backup to type C drive, in Android 10 it works ok.
mikek753 said:
Any one solved this?
I have also 0b and can't backup to type C drive, in Android 10 it works ok.
Click to expand...
Click to collapse
I just bought a newer 128Gb USB-C thumb drive and everything works fine.
Had the same issue. Turns out I had plug in my usb before booting into recovery for it to shown up as usbotg in TWRP.
ntfs drive canoot red by all twrp but fat32 can be read all twrp , but how we fix?
I've noticed that if I tried connecting a USB drive by way of my USB otg cable, it wouldn't pick it up.
However, when I used my drive that has a type C connector at the end and plugged it in, it would work.
This is the drive that has both the USB and the type C connector, one on each end. The USB side with otg adapter would not work in twrp
I know this is a really really old post....but....I have a OP 3 with olny Pitch Black recovery on it. I have (at least to this point) never walked away from something like this, but shortly this phone is going in the creek behind my apartment if I can not fix it.
adb - nope doesnt recognise
otg - nope
rebooted and shut down and restarted with usb plugged in - nope
msm - 10 different tools -nope
I'm just a duffer, and I dont even know if this is possble, but could I write/modify files in terminal to get/force to recognise otg/adb/msm?
I've been at this about 3 months, continuing to believe, perhaps erroneously, that I will be able to use the damn again. Any help/suggestions/cults I can join, phone gods to pray to to move the ball forward - appreciated more than there are descripitives in the mother-tongue to quantify.
but, please tell me change usb ports, cables, computers, any of that stuff..been there, done that about 100 times
I know that all these tools are installed correctly
Thank you for you time and energy considering my plea (more accurately, my prayer)
btw, phone is not encrypted, according to PB - wiped and formated from recovery mucho times

Categories

Resources