Related
"USB Device Not Recognized"
I have searched for so long trying to figure out what's wrong. I'm out of idea's on how to fix it, nothing will recognize my Evo.
Tried on 4 different computers, two of them running 7, one running xp, and last running vista, all say the same thing, computers not the problem.
Downloaded htc sync, disabled/enabled usb debugging, restarted the phone many times, restarted computers, and even changed the default usb connection to HDD and HTC sync.
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
b1indsided said:
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just tried that and still not recognizing it.
Which HTC Sync did you try? I think the latest is 2.0.40
http://www.htc.com/us/support/evo-sprint/downloads/
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
http://kenshinjeff.18jan.us/2009/06/12/adb-error-device-not-found-android-phone/
or here
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
stratman71 said:
Which HTC Sync did you try? I think the latest is 2.0.40
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
Click to expand...
Click to collapse
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
guesswhatimevan said:
"USB Device Not Recognized"
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Click to expand...
Click to collapse
Did you do the 3 click method?
guesswhatimevan said:
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
Click to expand...
Click to collapse
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Philosuffer said:
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Click to expand...
Click to collapse
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Sorry but bump, i relly need help with this.
It still says unknown device when i try to connect my phone in recovery mode.
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Mast3rpyr0 said:
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Click to expand...
Click to collapse
Just tried that and it's a no go, still the same problem, Also tried another cable today and that didn't help either.
I have light leakeage at the bottom of my phone, so i think i'm going to take it in for that and just get a replacement.
guesswhatimevan said:
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Click to expand...
Click to collapse
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Philosuffer said:
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Click to expand...
Click to collapse
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
guesswhatimevan said:
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
Click to expand...
Click to collapse
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Philosuffer said:
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Click to expand...
Click to collapse
It shows up in usb controllers instead of other devices as he shows in the guide. If i try to update the driver it just tells me it's already up to date.
>Sorry yea it does say unknown device in device manager.
Gotta bump, would really love to just fix this instead of driving 30 mins to a sprint store.
So i followed the guide for installing apb drivers, but even in recovery mode my phone still shows up as unknown device in device manager.
Ok, well I just ran into this myself on my secondary computer. Have you tried a different USB port on your PC?
My front ones were giving me unknown device, but as soon as I plugged it into one of the ports on the back of the mobo ADB showed right up in device manager.
Factory reset it and get it exchanged.I belief is the SD card failure issue.
Sent from my PC36100 using XDA App
I have the same problem and posted this question on 3 forums including the HTC support forum and nobody has been able to find the correct solution.
I know the cable and the port is good because I can connect my Samsung Moment to it and it works perfectly. On the Evo, I've downloaded the latest HTC Sync from the official HTC site, tried the one on the microsd card, checked and un-checked USB debugging, and still it doesn't connect.
The Evo won't connect to my Win 7 computer at home, Win XP at work, but it will connect to my daughters computer which is running Win XP also (all 32 bit).
I bought this Evo from Best Buy exactly 28 days ago today. Do they give you 30 days to return it, or is that only the Sprint store?
They do give u 30 day trial.go get it exchanged or...........
Sent from my PC36100 using XDA App
I installed COTR (Cannibal Open Touch Recovery), and tried to install a KitKat ROM. It didn't work, and my android installation was removed.
I had backed up the system using TWRP, but now it has been replaced with COTR, and I don't have a working zip on my kindle to flash.
I tried to connect using adb, but I'm not sure how (I'm on a mac), and trying to mount the sd card using COTR doesn't seem to work either.
I'd really like to fix this because it's my main device and I rely on it
jji7skyline said:
I installed COTR (Cannibal Open Touch Recovery), and tried to install a KitKat ROM. It didn't work, and my android installation was removed.
I had backed up the system using TWRP, but now it has been replaced with COTR, and I don't have a working zip on my kindle to flash.
I tried to connect using adb, but I'm not sure how (I'm on a mac), and trying to mount the sd card using COTR doesn't seem to work either.
I'd really like to fix this because it's my main device and I rely on it
Click to expand...
Click to collapse
The quick and painless fix here would be soupkit. If you follow the instructions it's quite simple. If you can't use soupkit for whatever reason look for a tutorial on adb with Mac. I don't own a Mac myself so I can't be much help in that department.
When I connect my kindle to my Mac it doesn't appear at all, even when I mount as USB mass storage using recovery, and adb/fastboot doesn't detect it either, so I suspect that my usb connection may only work for charging, and not for data. I've had problems with the usb port before as well, and I wasn't able to mount my kindle before the brick either (though I presumed it was a jelly bean bug).
Therefore I think my kindle is a hard brick with no solution.
Ok I pronounce my kindle dead. It was a good run, didn't expect it to end so abruptly
I might sell it for parts or something later.
Sad... Kikat does not work with cotr
I was using cotr
Twrp 2.6.0.0 was not able to make a backup, now that thing is fixed, so I came back to twrp for kitkat
Sent from my air powered ceiling fan
jji7skyline said:
When I connect my kindle to my Mac it doesn't appear at all, even when I mount as USB mass storage using recovery, and adb/fastboot doesn't detect it either, so I suspect that my usb connection may only work for charging, and not for data. I've had problems with the usb port before as well, and I wasn't able to mount my kindle before the brick either (though I presumed it was a jelly bean bug).
Therefore I think my kindle is a hard brick with no solution.
Click to expand...
Click to collapse
You could use the USB shorting trick coupled with the advice I already posted and you'd very likely fix your Kindle. The USB trick skips all the driver BS and listens directly to the USB before the OS or boot even has a chance to do anything.
Keep in mind it can take many, many tries to actually do the USB trick right. The first time I did the USB trick it took 20 tries or more, others have had the same problem. Some people say a strong piece of copper wire works best, but I didn't have one on hand.
Firekit is built in with Soupkit (which I already posted).
http://forum.xda-developers.com/showthread.php?t=1405052
8) Short the point shown here to the metal frame around the CPU area using your paperclip or whatever. While keeping it shorted, plug in the USB cable. This will power up the Fire with the CPU in USB boot mode.
I'm 99% sure you can fix your Kindle like that. Ask if you need anything clarified.
So just get Soupkit set up, get it into Firekit and order "usb_fix_parts_and_install_fff_twrp". It will say <waiting for device>, at this point you do the USB trick again and again until it works. It absolutely should work, keep trying.
The problem is that i think the usb is broken and only works for charging - no data.
Ill give it a go anyway though. Thanks.
Sent from Google Glass
So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.
Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.
Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?
So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?
One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...
This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.
My rooted+bootloader unlocked LG Nexus 5x was not recognised by adb or fastboot in either Arch Linux or Windows (the latter with the proper drivers installed and the former with udev rules properly established). The device will also not show up in Windows' device manager or lsusb and the like in Arch. This was not too much of a problem until I accidentally deleted my SystemUI app from a new ROM.
The moment I realised what I had done I tried to reinstall from TitaniumBackup's restore function. That failed. I placed another copy of the apk within a folder in priv-app, assuming that I'd have no problems. I was very wrong.
On the next boot my SystemUI began crashing. My attempt to boot into TWRP required a password, which has never been the case before. I cancelled and tried to allow TWRP write access to /system. I then wiped data, cache, and dalvik during a factory reset. No luck.
Now it does not appear that my internal storage or system partitions are mounting properly, and I can't access the backup files on the sdcard. I can't sideload anything or adb push.
On a scale from one to screwed, how bad is my situation?
Not. If you have tried EVERYTHING else, download WugFresh tool kit, get into bootloader connect the USB and click the box under "unroot and return to stock" that states "device in bootloop" ,click on "unroot and return to stock" and follow the instructions. Make sure you manually select which device you are using first tho.
Edit: the tool kit has the option to install the ADB drivers, do that first (just in case). shouldnt have a problem pushing to ADB if you only messed with system files.
Boot up a live version of Linux Mint. You don't have to fart around with udev rules and adb and fastboot are packaged up and in the repos. You will have a functioning system in no time.
Sent from my SM-G930V using Tapatalk
Hehe, I was using a third party cable. Jiggled it around a bit and "adb devices" eventually returned the device's information. I just had to hold down the cable and I was able to start flashing. I'll buy a good cable soon (or wait and buy a laptop with Type C as I've been planning so that I can use the cable that came with the device).
PiArc said:
Hehe, I was using a third party cable. Jiggled it around a bit and "adb devices" eventually returned the device's information. I just had to hold down the cable and I was able to start flashing. I'll buy a good cable soon (or wait and buy a laptop with Type C as I've been planning so that I can use the cable that came with the device).
Click to expand...
Click to collapse
Glad you got it working. Test each side of the cables. Mine work better on one side than the other. The one side needs to be held in like you described but simply flipping the cable around it has a sold connection.
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.
tnsmani said:
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.
Click to expand...
Click to collapse
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,
manto02 said:
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,
Click to expand...
Click to collapse
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.
tnsmani said:
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.
Click to expand...
Click to collapse
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.
manto02 said:
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.
Click to expand...
Click to collapse
Just now, I switched off USB debugging in my OP3 and connected it to the Laptop. While the command 'adb devices' does not find the phone, as soon as it is connected, it shows up as a storage device and I can open it and copy data. I think that for this to work, you should have enabled MTP option for file transfer.
Check this on your phone.
EDIT: Check THIS as there seems to be a way though I am not sure that it works on current Android versions since the file locations may be different. Read till the end.
My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?
manto02 said:
My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?
Click to expand...
Click to collapse
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.
tnsmani said:
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.
Click to expand...
Click to collapse
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself
manto02 said:
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself
Click to expand...
Click to collapse
Have you tried fastboot flash twrp recovery and then fastboot reboot to recovery
You can try usb c to hdmi adapter , connect to a monitor or tv.
I am not sure but worth trying!!!
manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
From what i can remember, the recovery mode, accessible from the fastboot menu, has a usb access mode.
If worst comes to worst though, i personally have replaced the screen on my OP3, and its not as difficult as it seems or is made out to be. Took me max 4 hrs.