pixel 3a - copy files to a usb flash drive - Google Pixel 3a Themes, Apps, and Mods

hello
i bought a small usb flash drive that has also usb type c connector, so i connected it to the phone
i installed the "files by google" app: https://play.google.com/store/apps/details?id=com.google.android.apps.nbu.files&hl=en_US
but when when i select files and click the 3 dots, there is no "copy to" feature so i can copy it to the usb flash drive.
i tried also es file manager & mix file explorer, but still i cannot copy to the usb flash drive.
i guess the phone is blocking \ not allowing files to be copy to a usb flash drive?
is there some fix for that or i am missing something?

Did you try an usual USB stick with the USB-Adapter that was included by the 3a for transfer from an old phone? Does this work? The adapter is not a simple USB-A-to-C but an USB-OTG adapter and works. Perhaps your flash drive doesn't work directly without an USB-OTG adapter between.

yaron86 said:
hello
i bought a small usb flash drive that has also usb type c connector, so i connected it to the phone
i installed the "files by google" app: https://play.google.com/store/apps/details?id=com.google.android.apps.nbu.files&hl=en_US
but when when i select files and click the 3 dots, there is no "copy to" feature so i can copy it to the usb flash drive.
i tried also es file manager & mix file explorer, but still i cannot copy to the usb flash drive.
i guess the phone is blocking \ not allowing files to be copy to a usb flash drive?
is there some fix for that or i am missing something?
Click to expand...
Click to collapse
You need an OTG drive (or use the adapter that comes with the phone). On an OTG drive, pin 4 and pin 5 are connected that allows the drive to function as a host. On a regular usb-c drive, pin 4 is not connected. Then you also need a file copy/transfer app that supports OTG (X-plore is one).

I have tried with a usb drive and the adapter to usb-c that comes with the phone. Files copied with solid explorer with no issues.
Enviat des del meu Pixel 3a usant Tapatalk

yaron86 said:
hello
i bought a small usb flash drive that has also usb type c connector, so i connected it to the phone
i installed the "files by google" app: https://play.google.com/store/apps/details?id=com.google.android.apps.nbu.files&hl=en_US
but when when i select files and click the 3 dots, there is no "copy to" feature so i can copy it to the usb flash drive.
i tried also es file manager & mix file explorer, but still i cannot copy to the usb flash drive.
i guess the phone is blocking \ not allowing files to be copy to a usb flash drive?
is there some fix for that or i am missing something?
Click to expand...
Click to collapse
Pixels will only automatically mount FAT32 drives so it's possible your new flash drive is exFAT or something and you might need to format it. The built-in Files app will show the drive in the side bar if your phone mounted it. This app does have a copy to feature.

I have got an Sandisk USB-A and USB-C Stick and it worked straight out of the box. Used Total Commander to copy files.

Yep, I formatted mine in fat 32 on my PC and instead of 128 gb it gave me 133 gb and the phone picks it up like an extra drive and you can even do straight to it.

Related

Newbie with the Nexus

I am having issues, probably missing something silly.
I connect my phone via usb, there is nio option to mount card.
I installed the new drivers following the info provided here as below:
Getting Nexus One ADB/USB Mount working (Driver)
--------------------------------------------------------------------------------
hit Windows Key + r
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.
---------------Notes-------------
Be sure to enable debugging on your phone via Settings>Applications>Devlopment>USB debugging.
Phone shows in my device manager as Android composite Adb interface.
In My computer it shows as Removable drive (N)
not sure where I am going wrong, when i pull down the screen from notificatio area all i get is "Turn Off USB Storage" & USB Debugging Connected.
Any help greatly appreciated
i didnt need to install anything. i just connected my nexus to my work laptop, it recognized a mass storage device, i pull down the shade and press "cclick to copy files". thats it.
I have installed via wifi Astro file manager, but it does not find any *.apk files i drag over to the memory card, so I can not install the apps I have currently sitting on my pc. I have no idea what folder I should drag them to, tried the root of removable drive(N) as well as the temp folder.

Chromecast won't root

Hello
I need help, I'm trying to root my Chromecast but when I plug in my flash drive and connect to power I press the button on the Chromecast and the screen sets to black with a little line with colors an the flash drive starts to blink as if it's being reed but the Chromecast never reboots so I don't know what to do next I've already try with 2 different otg cables and 2 Chromecast so it definitely is something I'm doing wrong and the bin was flashed correctly (I think) I'll appreciate any help
Patched
Hell.Knight said:
Hello
I need help, I'm trying to root my Chromecast but when I plug in my flash drive and connect to power I press the button on the Chromecast and the screen sets to black with a little line with colors an the flash drive starts to blink as if it's being reed but the Chromecast never reboots so I don't know what to do next I've already try with 2 different otg cables and 2 Chromecast so it definitely is something I'm doing wrong and the bin was flashed correctly (I think) I'll appreciate any help
Click to expand...
Click to collapse
Sounds like your bootloader is locked. Even new retail devices (bought one yesterday) already have the exploit patched.
the momentary access of the thumbdrive followed by the sliver of colored pixels and then a blank screen indicates you cannot exploit the bootloader on that chromecast (this root method has been closed tight like the sphincter of a young human)
Bild 12072
BusterChestnut said:
Sounds like your bootloader is locked. Even new retail devices (bought one yesterday) already have the exploit patched.
the momentary access of the thumbdrive followed by the sliver of colored pixels and then a blank screen indicates you cannot exploit the bootloader on that chromecast (this root method has been closed tight like the sphincter of a young human)
Click to expand...
Click to collapse
I Appreciate your reply but the thing is that I double check the build version and well one is all ready on the 12940 build which updated today but the other one is still on the older build 12072 which I thinkit can still be rooted doesn't it?
Hell.Knight said:
I Appreciate your reply but the thing is that I double check the build version and well one is all ready on the 12940 build which updated today but the other one is still on the older build 12072 which I thinkit can still be rooted doesn't it?
Click to expand...
Click to collapse
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
I use Win32DiskImager as well. The file shows up on the USB drive. When I connect the OTG/USB cable to the CC while holding the reset button, I get the same black screen with a few colored dots. My build is 12072.
How long does reset need to be held?
We are supposed to be using the .bin file in Win32Diskimager, and not the .zip, correct? Win32DiskImager by default asks for files of type .img, .IMG. and you must change this, correct?
What kind of file system must the USB drive be formatted in before using Win32DiskImager?
The unpacked .bin file is 125MB on the computer, but after being flashed to the USB it is only 68.8MB. Is this correct?
Donteventrii said:
I use Win32DiskImager as well. The file shows up on the USB drive. When I connect the OTG/USB cable to the CC while holding the reset button, I get the same black screen with a few colored dots. My build is 12072.
How long does reset need to be held?
We are supposed to be using the .bin file in Win32Diskimager, and not the .zip, correct? Win32DiskImager by default asks for files of type .img, .IMG. and you must change this, correct?
What kind of file system must the USB drive be formatted in before using Win32DiskImager?
The unpacked .bin file is 125MB on the computer, but after being flashed to the USB it is only 68.8MB. Is this correct?
Click to expand...
Click to collapse
I used the .bin file without renaming it.
When Win32DiskImager is done, Windows Explorer shows it as being a 128gb drive. It actually is a 256gb drive, but apparently the . bin file repartitions it to be 128gb. I don't think it matters how the USB drive is formatted, because the WI 32DiskImager will repartition and reformat it. With windows Explorer I can see files on the flash drive.
Then I connect the chromecast to the USB stick, then connect the chromecast to the TV, then hold the reset button, then plug in the ac power supply for the chromecast. I'm not sure exactly how long I kept pressing the reset button after providing power to the chromecast, but my guess is about 30 seconds.
HowardZ said:
I used the .bin file without renaming it.
When Win32DiskImager is done, Windows Explorer shows it as being a 128gb drive. It actually is a 256gb drive, but apparently the . bin file repartitions it to be 128gb. I don't think it matters how the USB drive is formatted, because the WI 32DiskImager will repartition and reformat it. With windows Explorer I can see files on the flash drive.
Then I connect the chromecast to the USB stick, then connect the chromecast to the TV, then hold the reset button, then plug in the ac power supply for the chromecast. I'm not sure exactly how long I kept pressing the reset button after providing power to the chromecast, but my guess is about 30 seconds.
Click to expand...
Click to collapse
What did you see when you it booted up? The black screen with the few colored dots?
How big is the bin file on the the disk?
Donteventrii said:
What did you see when you it booted up? The black screen with the few colored dots?
How big is the bin file on the the disk?
Click to expand...
Click to collapse
You live in Baltimore.
I am about one hour drive away.
If you are having so much difficulty, you can come over and I can do it for you.
Howard
HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
I used another program and got the exact same lines and loops. I used Win32DiskImager.exe with the same bin, cable and USB stick.....All I was asked when everything was done was to set up my chromecast
Rooted
HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
Thank you man! In fact after using dd my pc would tell me that my usb had no format and I thought it was normal but with win32diskimager.exe it was faster to write to the usb stick and the Chromecast was rooted in no time.
I really appreciate you're help, thanks a lot.

Broken screen, want to retrieve files via USB.

Hello, my captivate screen broke (zero display) and I'd like to retrieve some the files mostly vids and pics from the phone memory.
I have downloaded the mini abd on my PC. The phones two drive paths are shown on my PC via USB cable, but says "insert disk". So how can I use abd to mount the phone as external storage so I can browse and copy files? I know "enable USB debugging" was already checked. Phone is rooted with CM10.1
This is my first attempt with adb....so I'll need the dummy explanation.
I hope that makes sense, thank you for reading!
Hope this helps. Check the links below.
http://www.xda-developers.com/android/beginners-guide-to-the-android-debug-bridge/
http://forum.xda-developers.com/showthread.php?t=2266638

MTP file transfer trouble in Redmi-4A

I have rooted Redmi-4A. I have supersu 2.79. My MIUI version is MIUI Global 8.2 | Stable 8.2.1.0 (MCCMIDL).
My USB debugging option is enabled.
I tried the following android applications but failed to get access to the MTP file transfer mode through my phone to PC.
1. MTP enabler Release 3.3
https://forum.xda-developers.com/android/apps-games/app-mtp-enbaler-t3263467
2. QCustomShortcut application
3. MIUI Usb settings
I can select the MTP mode easily in the phone using the default method and the 3rd party apps that I listed above but my PC does not detect my phone. The ADB drivers are installed on my PC. However, my PC detects insertion of USB device and shows a notification upon insertion and taking out of USB cable connected to the phone.
I tried using MI PC suite and it also is not detecting my phone.
Have you tried installing the USB drivers? USB driver is NOT the same as the ADB driver. Google "Redmi 4A driver" and install the USB drivers.
Fobos531 said:
Have you tried installing the USB drivers? USB driver is NOT the same as the ADB driver. Google "Redmi 4A driver" and install the USB drivers.
Click to expand...
Click to collapse
I've installed them as well. They came along with the MiFlash tool. I forgot to mention it earlier
Sent from my Redmi 4A using Tapatalk
archz2 said:
I've installed them as well. They came along with the MiFlash tool. I forgot to mention it earlier
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
Have you tried with USB debugging disabled? Also, does changing the USB mode to PTP help?
Fobos531 said:
Have you tried with USB debugging disabled? Also, does changing the USB mode to PTP help?
Click to expand...
Click to collapse
Yes, I tried with both of these options but failed.
Hmm, that leads me to think that something's wrong on the PC's side. Can you boot up a Linux distro and see if you can transfer files there?
Fobos531 said:
Hmm, that leads me to think that something's wrong on the PC's side. Can you boot up a Linux distro and see if you can transfer files there?
Click to expand...
Click to collapse
I have Windows 10 on my PC. I DON'T have Linux.
archz2 said:
I have Windows 10 on my PC. I DON'T have Linux.
Click to expand...
Click to collapse
You can easily create a bootable Ubuntu USB and test the phone in the live session (i.e. without installing it).
I am currently getting that error with my phone. Not sure but it could happen because of the computer. I have two os in my computer. Win10 and Linux mint. Win10 can detect my phone without an issue but mint not. With usb debugging on I can use adb in linux but still no file sharing.
dokuz said:
I am currently getting that error with my phone. Not sure but it could happen because of the computer. I have two os in my computer. Win10 and Linux mint. Win10 can detect my phone without an issue but mint not. With usb debugging on I can use adb in linux but still no file sharing.
Click to expand...
Click to collapse
Do you have a rooted phone?
archz2 said:
Do you have a rooted phone?
Click to expand...
Click to collapse
Yes and no I mean both. Got same issue in different times with different phones. When the time I use crunchbang I would able to fix it. (by installing things on crunchbang not on the phone). But this time, I did not try to fix actually. I am connecting my not rooted phone only for android studio. It detects it. I can install my apps and can test them. But I cant see my phone in file manager. Thats the story.
the same thing is happening to my wife's rooted 4a and her sisters unrooted one
the same for my not rooted one, I've seen my phone one day in windows 10 explorer (this day it makes 10 seconds to see and when reconnected I could see it one time over 2), but the next day nothing more, I spent hours to try fixing it and have a few computers (all with windows 10), I think it's a miui problem not letting windows acces to the storage.
I have a part of a solution, have ejected my sandisk 64GB SD card, found it was formatted in exFat, empty it in windows, put it back in redmi, after redmi search errors I clicked on the notification and saw a few remaining folders and files, so I went to storage to format the sd card, after this the sd card (and only it) was visible in Windows explorer, but only in MTP (without usb debugging), but the copy from the PC is a kind of erratic (drag and drop 1 folder full of subfolders and files is ok but selection of 10GB gb folders and files to copy stops after the first file copied...), I don't understand how one day I manage to see correctly internal storage and sd card...
edit: today I can see the sd card as empty in windows explorer despite of properties shows it is not, and impossible to copy anything...
So i use now a turnaround, I tried airdroid but device folders were shown as sd card(?), but tried another app "gestionnaire de fichiers" flashlight + clock which can activate ftp service (edit: I have seen after that file explorer from miui could, but it hangs before I found the soulution)
so I type on chrome ftp://192.168.0.45:1234 (1234 is the port number you can choose) with the phone on my box with wifi and all (device ssytem androïd too) is accessible (but to copy to the sd card I would have to use a ftp client).
EDIT: Eureka! I uncheck the fictive sd card optimisation (optimisation de la carte sd fictive in french) option in developper's options and all is ok.
---------- Post added at 05:38 PM ---------- Previous post was at 05:22 PM ----------
So for me to access both sd card and internal device memory in USB in Windows 10 for my not rooted xiaomi 4A miui global miui 9 global 8.1.11 beta android 7.1.2N2G47H
I had to:
-activate developper's mode (7 taps on Miui version)
to activate debugging usb (seems better)
-unactivate fictive sd card optimisation (windows and airdroid do not understand internal memory like a sd)
-format the sd card in the phone (in stockage menu, delete the sd card)
using the MPT mode seems the better option (in "selectionner la configuration usb" in french in developper's mode options) or with the notification when usb is connected.
For me Adb drivers were ok.
And there was a problem with file explorer that hangs when "fictive sd card optimisation" was activated, so even redmi can't access to sd card when this option is on...

Question File transfer to PC

Impossible for me now to transfer files from PC to P7. Whenever the content loads, the explorer windows shuts down. Very annoying.
Any fix ?
StressFull said:
Impossible for me now to transfer files from PC to P7. Whenever the content loads, the explorer windows shuts down. Very annoying.
Any fix ?
Click to expand...
Click to collapse
What happens when you use the pull command?
Android Debug Bridge (adb) | Android Studio | Android Developers
Find out about the Android Debug Bridge, a versatile command-line tool that lets you communicate with a device.
developer.android.com
I had to use usb 3.0 port because 2.0 was giving me the exact same problem as you're facing.
Alternatively you can copy the files you want onto a usb stick and then connect it to your phone using the provided usb c adapter. I've done it few times and it works well.
innit said:
I had to use usb 3.0 port because 2.0 was giving me the exact same problem as you're facing.
Alternatively you can copy the files you want onto a usb stick and then connect it to your phone using the provided usb c adapter. I've done it few times and it works well.
Click to expand...
Click to collapse
Worked, thank you. Very strange.
Can you totally deny it is frozen because the transfer is taking time (ongoing) ?
I could imagine that it just waits for the task to be finished before accepting further commands.
I had this happen as well, I would select the MTP mode (file transfer/android auto or something) and it would disconnect from the computer. Switching to another USB-C cable fixed the issue

Categories

Resources