The display of my Xperia z3 is non-functioning(i.e. all I can see is a black screen) after an accidental damage due to water-insertion. But all other parts are working fine. The screen responses to touch, I can hear the touch sounds and I can click photographs as well with the camera key.
After connecting the phone with USB cable to my ubuntu laptop, I can browse through the internal storage files on the phone and locate the newly created image files as I click new photographs and take screen-shots. But I can't open any files(images/audio/videos) with errors like "couldn't load image" and "couldn't determine type of stream". However, I'm able to copy new files to the internal storage.
I want to install some screencasting application like vysor on my phone so that I can access it using my laptop. I know this can be done using adb commands but the problem here is that USB debugging is not enabled on my phone and hence I can't find it on the list of adb devices.
Is there any workaround for such situation?
Is your phone rooted?
do you have a custom recovery?
able to use fastboot?
Related
OK, a friend of mine's girlfriend's daughter (insert Spaceballs joke) broke the screen on her One S. She wants him to get the data off her phone (likely pictures and whatever else). Does anyone know of a way to do this? The bootloader isn't unlocked, which apparently makes a difference. I've never touched a HTC device before, so I don't know if there are any quirks, but there seem to be.
Few windows programs( Android Manager, Android Commander) will let you access the sd card, and adb commands will do it too if you have usb debugging enable. Look like you are on stock recovery. Is been so long time since I use stock recovery that I do not remember if you can have the "usb mount" in there. When you plug the phone into computer, can you access the sd card?
liesnomore said:
Few windows programs( Android Manager, Android Commander) will let you access the sd card, and adb commands will do it too if you have usb debugging enable. Look like you are on stock recovery. Is been so long time since I use stock recovery that I do not remember if you can have the "usb mount" in there. When you plug the phone into computer, can you access the sd card?
Click to expand...
Click to collapse
No, hence the question. No offense, but if it was that easy, I wouldn't have posted this question...
It may not be booting up correctly or something, but without a working screen he can't tell. Or she may have a security code or pattern, which would prevent you from accessing the SD until it's unlocked. But either way, if the phone is booted up, you can't see the SD. And even if the stock recovery has a Mount USB option...well, the screen is busted, so he can't see that option or select it.
The only possibility I can see is if it can be booted into the bootloader, and do an ADB pull for whatever files she wants. But apparently to do an ADB pull (or for ADB to even recognize the device, according to him), the bootloader has to be unlocked first?
Android Manager will let you bypass the security as long as usb debugging is enable. Hard to tell. I had that problem with my friend phone, but he had the usb debugging enable. I wish that I could help you more - I know "that pain" of busted screen. Try that Android Manager. Is free - nothing to loose but time searching for it on xda. I forgot the link.
Hello everybody.
I need to know how to disable the multi user interface in my note 10.1 rooted with pacman rom in jelly bean 4.3.
It is always duplicating the files that I put in it.
For example, if I put the NFS most wanted data files in the android/data folder it gets repeated three or four times in other folders.
If I put it in the emulated/0 folder it gets duplicated and it is present in storage and media and some other folder.
Hence the approx 1 GB file becomes 3-4 GB.
I'm guessing this is due to the multi user interface.
Also I have another problem
The USB connection isn't working.
If I plug it into the pc it doesn't show upon my computer but it charges.
If I out it in USB debugging mode the PC makes the connected sound but I still can't access the folders.
I need help.
The USB connection isn't working.
If I plug it into the pc it doesn't show upon my computer but it charges.
If I out it in USB debugging mode the PC makes the connected sound but I still can't access the folders.
Have you installed the Samsung USB drivers ???
JJEgan said:
The USB connection isn't working.
If I plug it into the pc it doesn't show upon my computer but it charges.
If I out it in USB debugging mode the PC makes the connected sound but I still can't access the folders.
Have you installed the Samsung USB drivers ???
Click to expand...
Click to collapse
Yes I have installed the USB drivers
Its not even working on another computer.
Any idea about the multi user?
:victory:I got both of them to work.
I disabled multi user by tying
fw.max_users 0
in terminal emulator, and made it permanent by typing fw.max_users=0 in the ending of build.prop.
i got the usb to work when i removed pacman and installed official cyanogenmod.
:victory:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.
ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.
By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!
I'm trying to access the data on a Galaxy S4 on which the screen is not working at all(no backlight and doesn't respond to touch). the data I mainly require is the contacts.db file. what I have tried sofar: NOTE: USB Debugging is disabled .
1. tried to access the data via USB but cant access the content due to the lock on the phone.
2. tried to access the data with KIES but once again failed to do so due to the lock on the phone.
3. Downloaded the ADB shell and installed the required USB drivers but cant access the phone, when running the command "adb devices" it says no devices found which I think is because the USB Debugging setting on the phone is not enabled.
4. Also tried to sync with the Google account but unfortunately it was not setup to sync contacts with the Google account.
5. Tried to make use of apps such as MoboRobo and Droid Explorer but it does not work due to the USB Debugging that is disabled
Some other suggestions were to get another S4 and connect its screen to the one in question which I'm sure will work but is there no other way to access the data or to somehow remove the pattern lock from the phone? maybe using another platform to gain full access to the phone or anything?
Just got the 6 today. Connected it to my Win10 pc to transfer files and notice that the internal storage/phone is not showing in windows explorer. Spent the next few minutes installing OnePlus drivers, changing cables, etc. all to no avail. I am unable to get the phone to show in windows explorer with USB Debugging checked along when using MTP. However, if I deselect USB Debugging, the phone now shows in windows explorer along with all files and folders. I have done a hard reset - which actually put me in a bootloop for an hour or so - thanks to OnePlus Support. Upon resolving the bootloop, my phone was completely wiped and set it up again. I still have the same issue. The only item that shows in windows explorer when USB Debugging is connected is the drivers folder for OnePlus - see image 1. I also have an error in device manager for MTP - see image 2.
I currently have the 5T and have no issues viewing it in windows explorer with USB Debugging selected. Also, if I select PTP (pictures) rather than MTP, it shows in windows explorer albeit with only two folders DCIM / Pictures.
Any suggestions are certainly appreciated as I am sure when I call OnePlus Support back in the AM they will be clueless and tell me to ship the phone back.
Thanks, in advance!
azsl1326 said:
Just got the 6 today. Connected it to my Win10 pc to transfer files and notice that the internal storage/phone is not showing in windows explorer. Spent the next few minutes installing OnePlus drivers, changing cables, etc. all to no avail. I am unable to get the phone to show in windows explorer with USB Debugging checked along when using MTP. However, if I deselect USB Debugging, the phone now shows in windows explorer along with all files and folders. I have done a hard reset - which actually put me in a bootloop for an hour or so - thanks to OnePlus Support. Upon resolving the bootloop, my phone was completely wiped and set it up again. I still have the same issue. The only item that shows in windows explorer when USB Debugging is connected is the drivers folder for OnePlus - see image 1. I also have an error in device manager for MTP - see image 2.
I currently have the 5T and have no issues viewing it in windows explorer with USB Debugging selected. Also, if I select PTP (pictures) rather than MTP, it shows in windows explorer albeit with only two folders DCIM / Pictures.
Any suggestions are certainly appreciated as I am sure when I call OnePlus Support back in the AM they will be clueless and tell me to ship the phone back.
Thanks, in advance!
Click to expand...
Click to collapse
Mine works like this.
Plug up the phone to the computer pull down your notification bar and select PTP
It will show only the DCIM folder
Now pull the notification bar down again and switch to transfer files and there you go
but how to turn on mtp while you are in bootloader ?
tried different drivers and window 10 does not show me phone storage.
x111 said:
but how to turn on mtp while you are in bootloader ?
tried different drivers and window 10 does not show me phone storage.
Click to expand...
Click to collapse
Apparently you can not enable mtp in bootloader or TWRP yet on this phone.
azsl1326 said:
Apparently you can not enable mtp in bootloader or TWRP yet on this phone.
Click to expand...
Click to collapse
I was able to get mtp in twrp. Once you're in twrp, unplug the cable then plug it back in
surface13 said:
I was able to get mtp in twrp. Once you're in twrp, unplug the cable then plug it back in
Click to expand...
Click to collapse
Per TWRP's site, "MTP is disabled because it causes a kernel panic sometimes with the stock kernel."
Haven't actually tried your suggestion, but I will next time.
azsl1326 said:
Per TWRP's site, "MTP is disabled because it causes a kernel panic sometimes with the stock kernel."
Haven't actually tried your suggestion, but I will next time.
Click to expand...
Click to collapse
Why not instead of risking panic, just use an OTG drive?
adb push should work fine