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.)
Related
I am on a stock wifi xoom and bought a motorola camera connection kit. I put a several thumb drives in the cord and cannot seem to find the thumb drive using astro viewer. Where do the files show up? I have look in all the directories but I cannot find anything that looks like the files on the thumb drive.
For now, to use thumb drive, you need to be rooted on the xoom also you need to manually mount it into a folder.
But if you are on Tiamat's kernel, you can find it at /usbOTG
jiwengang said:
For now, to use thumb drive, you need to be rooted on the xoom also you need to manually mount it into a folder.
But if you are on Tiamat's kernel, you can find it at /usbOTG
Click to expand...
Click to collapse
I was under the impression that on 3.1 it would work.
yup. i was given the same impression too. thought with 3.1 i can just plug the usb and it will automatically detects the usb.
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??
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
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
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
I use https://play.google.com/store/apps/details?id=com.alphainventor.filemanager
It mounts my usb stick fine.
Anyway i think Google File Manager should BE able to do the Same.
Skuddle said:
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
Click to expand...
Click to collapse
Android can't read NTFS
Skuddle said:
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
Click to expand...
Click to collapse
Enable OTG.
If it doesn't help, it means the Pixel cannot read NTFS formatted file system.
Use one of these to read NTFS formatted systems:
1. ZUGate
2. exFAT/ NTFS for USB by Paragon
elong7681 said:
Android can't read NTFS it needs to be FAT32
Click to expand...
Click to collapse
OnePlus devices CAN.
elong7681 said:
Android can't read NTFS it needs to be FAT32
Click to expand...
Click to collapse
Not true. It was true about 6 or 7yrs ago
Maybe it can't read NTFS, I'm not sure. But USB connectivity on Pixel devices is read only, and not r/w. exFAT has been supported for years now
elong7681 said:
Android can't read NTFS
Click to expand...
Click to collapse
It can.
JohnTheFarm3r said:
It can.
Click to expand...
Click to collapse
I stand corrected. Just tried it myself and it can read it.
Some people have had success with writing to USB flash drives, through third-party apps like Total Commander and others. You might need additional plugins for such apps though.
Edit: Mixplorer also works well for writing to USB flash drives. If needed, the custom USB OTG driver can be enabled from Mixplorer settings.
Skuddle said:
A few days ago I read that one can connect a flash drive to a Pixel 7 and upload files from the Pixel 7 to the flash drive. So I connected a flash drive that has one file on it and that is formatted as NTFS. However I don't know what to do next because I can't find anything on the P7P that refers to that flash drive. Could someone please point me in the right direction?
Click to expand...
Click to collapse
xunholyx said:
Not true. It was true about 6 or 7yrs ago
Maybe it can't read NTFS, I'm not sure. But USB connectivity on Pixel devices is read only, and not r/w. exFAT has been supported for years now
Click to expand...
Click to collapse
I'm confused where there is any trip-up; I apologize if it's simply going over my head.
I use the Kingston DataTraveler MAX (256 GB) USB-C flash drive directly plugged into the P7P, formatted to exFAT, and that's all there is to it to do my monthly backup (that I do before I manually update the security Full Factory image) -- both using Swift Backup, SMS Backup&Restore, and manually moving non-data folders from the internal SD!
It pops up in the stock Files app (in "Storage devices" section under "internal storage"; I can't recall what exactly it comes up as off the top of my head), and it definitely can do r/w. No plugins needed, no third-party app needed, no OTG setting required to be ticked (at least with the stock Files app).
It's very straightforward; I'm afraid I'm missing something. Is the comments only speaking on running it with NTFS format?
Again, sorry if I'm missing something obvious...
@simplepinoi177
Google Files app is buggy, and often does not even show the USB flash drive as one of the destinations to choose from, after selecting the copy file operation, even though it otherwise shows the USB flash drive.
When it does work, it does not copy over the original timestamps of the files to the USB flash drive.
The timestamp issue is also present while copying with the good old Documents UI.
halfbytecode said:
@simplepinoi177
Google Files app is buggy, and often does not even show the USB flash drive as one of the destinations to choose from, after selecting the copy file operation, even though it otherwise shows the USB flash drive.
When it does work, it does not copy over the original timestamps of the files to the USB flash drive.
The timestamp issue is also present while copying with the good old Documents UI.
Click to expand...
Click to collapse
Thank you for explaining. I wasn't aware of those issues with it.
My personal experience is never having any issues with it (both the flash drive nor the Files app); and I use it on my two P7Ps every month since getting it release day. And all I do is do the copy file operation as I only use that drive for backing my data up.
I've never took notice of the timestamps, but it's not a priority for me, but it's good to be aware of; so thank you for informing me.
simplepinoi177 said:
formatted to exFAT
Click to expand...
Click to collapse
Yours is formatted in exFAT (which is an improved version of FAT32) which is kind of universal. Works on Windows, Android , Linux and macOS too.
simplepinoi177 said:
Is the comments only speaking on running it with NTFS format?
Click to expand...
Click to collapse
Yes. NTFS is Microsoft's file system that works as read-only in macOS and doesn't work in many Android devices (OnePlus is a known exception).
TheMystic said:
Yours is formatted in exFAT, which is kind of universal. Works on Windows, Android , Linux and macOS too.
Yes. NTFS is Microsoft's file system that works as read-only in macOS and doesn't work in many Android devices (OnePlus is a known exception).
Click to expand...
Click to collapse
And Samsung (read-only).
JohnTheFarm3r said:
And Samsung (read-only).
Click to expand...
Click to collapse
Since when? As far as I can remember, I had to install a 3rd party app to make it work. It's been quite a while since I connected a NTFS formatted drive.
When I plug a USB stick (that has been formatted the long way as ExFAT) into my P7P and get to USB Preferences, tapping "This device" results in "Couldn't switch". And I'm using whatever File app came with my (as of April 2023) new unit. And it's using Android 13, and the unit tells me that all apps have been updated (as of May 8 when I performed the Update operation).
I see that there is no consensus on how to format the USB stick. Some say ExFAT, some say FAT32, some say that the P7P can read NTFS and others say that it can't... What's a guy to believe??? In any event, I've tried all formats and my P7P is not able to read any of them.
Skuddle said:
When I plug a USB stick (that has been formatted the long way as ExFAT) into my P7P and get to USB Preferences, tapping "This device" results in "Couldn't switch". And I'm using whatever File app came with my (as of April 2023) new unit. And it's using Android 13, and the unit tells me that all apps have been updated (as of May 8 when I performed the Update operation).
I see that there is no consensus on how to format the USB stick. Some say ExFAT, some say FAT32, some say that the P7P can read NTFS and others say that it can't... What's a guy to believe??? In any event, I've tried all formats and my P7P is not able to read any of them.
Click to expand...
Click to collapse
Use exFAT. It is universal and is supported by most operating systems.
Are sure your USB stick isn't corrupt?
Skuddle said:
When I plug a USB stick (that has been formatted the long way as ExFAT) into my P7P and get to USB Preferences, tapping "This device" results in "Couldn't switch". And I'm using whatever File app came with my (as of April 2023) new unit. And it's using Android 13, and the unit tells me that all apps have been updated (as of May 8 when I performed the Update operation).
I see that there is no consensus on how to format the USB stick. Some say ExFAT, some say FAT32, some say that the P7P can read NTFS and others say that it can't... What's a guy to believe??? In any event, I've tried all formats and my P7P is not able to read any of them.
Click to expand...
Click to collapse
I don't see where you're getting USB Preferences...it's never anything I need to do/choose "tapping 'this device'", it merely shows up under internal storage (as I've mentioned before) -- as DataTraveler MAX. This is using the stock Files app as well. I'm also updated to May update.
If anything, the only thing I found that I do that I didn't need to before is there is an "eject" option in the notifications to choose to safely remove it. Other than that, there isn't/wasn't anything particular to get it all working for me; to detect, read, write, delete, etc.
I did a bit of research on what to format USB-C flash drives for Pixel 7's and it said to do ExFAT; and ExFAT is the only format that can be read by both Microsoft and MacOS -- so I figured that kind of compatibility is also the reason why it's best for Android/Pixels....
It's curious how you're having so much issues when it's so simple (at least to me in my experience).
Like @TheMystic said, it makes me think it might be a corrupted drive if you're having that much inconsistencies and issues....
simplepinoi177 said:
I don't see where you're getting USB Preferences.
Click to expand...
Click to collapse
It shows up in the notification area when you connect a USB. You can choose how you want to control the connection: using the phone itself or using the computer that the phone is connected to.
You'll basically see 2 notifications every time you connect a USB device.
simplepinoi177 said:
If anything, the only thing I found that I do that I didn't need to before is there is an "eject" option in the notifications to choose to safely remove it.
Click to expand...
Click to collapse
It has always been there, unless you turn OFF Android System notifications. Not sure about custom ROMs though.
TheMystic said:
It shows up in the notification area when you connect a USB. You can choose how you want to control the connection: using the phone itself or using the computer that the phone is connected to.
You'll basically see 2 notifications every time you connect a USB device.
It has always been there, unless you turn OFF Android System notifications. Not sure about custom ROMs though.
Click to expand...
Click to collapse
I'm familiar with the 2 choices on choosing how to control the connection -- but why would that apply with a USB Flash (HD/SD) Drive; as opposed to a computer? It would neither gain power from a flash drive nor need to make the "distinguishment" to transfer via MTP or PTP, or need any device "control" -- it's a flash drive, it would only be for file transferring/storing.
At the very least, when I connect mine, there is no such options in my notification (nor is it needed/necessary)...I only get the two options to "Explore" or "eject"; not like the multiple I get when connecting to the computer...