Unfortunately I broke the screen of my beloved 6P today and have spent the last 8 hours trying to figure out how to recover everything from it. It's still working as I can hear notifications and phone calls but the screen is blank.
After searching everywhere (xda, stackoverflow etc.), I'm a bit stuck and was wondering if anyone can help. Here's my plan/what I know:
1) I want to emulate the phone screen on my PC via USB using Android Control
2) I need USB debugging mode to access the phone via ADB
3) I need the correct (Google) USB drivers installed on my PC to access ADB
I have downloaded several tools/drivers and this is how far I got:
1) Windows sees/recognizes the phone under Devices and in Device Manager (as It does normally) - I am unable to access the phone because it's not in file transfer mode
2) When I run adb devices, the list is empty
3) I tried to update the driver to the latest Google USB driver but Windows 10 won't let me (windows has determined the best drivers etc. etc.)
I can't be sure what is blocking access via ADB. I'm sure I enabled USB debugging when I first got the phone but it was a long time ago. I read that I might need to disable Windows Driver Signing to install the latest Google driver but I haven't tried it yet.
My question is, how can I tell if it's USB debugging or the Driver? Any help would be greatly appreciated!
If you have your bootloader open, then this should be easy. You can install (if not already installed) TWRP recovery with "fastboot flash recovery file.img". When you then boot blindly into the recovery (its always the same amount of button presses in bootloader) then you can access the storage of your phone.
Other cheap solution: Get a phone with bootloop issue and use that screen from it. Then you have again a fully working phone.
Related
After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Roland
Rolandh said:
After trying to Sideload the 4.4 Update onto my Wifi Nexus 7 (2012) I'm unable to connect to my Computer in MTP Mode & can only connect in PTP Mode which is far more limited than MTP Mode. I did a Factory Reset & updated to 4.4 OTA, but I'm now still unable to connect in MTP Mode, when I use MTP Mode I get a Google Nexus 7 ADB Interface in Device Manager with Manufacturer ID of ClockworkMod has anyone got any clues how to get MTP Mode working?
P.S. I'm unrooted and have no idea how the ClockworkMod ADB Driver got installed and haven't got a clue how to permanently remove it.
Click to expand...
Click to collapse
Look in your PC's Control Panel - do you see Portable Devices (it's most likely missing or not showing up)
Folks over at Nexus 5 (I owned both devices) are running into similar problems - long story short, it's corrupted and/or missing usb devices drivers. Simplistic solution, use the computer (assuming you are running Windows 7 or Vista and not Linux) SYSTEM RESTORE feature & roll back to last few days, it should be a successful effort & then reboot. Reconnect your device, let it sit & recognize the device, install drivers, etc. - do this with USB debugging OFF first, and when it is done - enable USB debugging, let it finish.
Now, reboot PC again to be sure, and connect. usb cable again - give it 3 to 5 seconds, your Auto Play should be popping up with prompt to open folders/files, etc.
Check your CP again, you should now see Portable Devices part of the hardware, and Google Nexus 4 (yes, that's what is on mine)
Let me know if this solution works for you - the alternative is to uninstall all usb drivers, reboot, install, etc. etc. Please post your results if you choose to follow this dummy's approach, thanks.
Hi everyone,
I have a big issue after having flashed my XT320 : when it starts, I have a setup wizard failure (com.android.setupwizard) asking me to force closing it... and it does it again without ending (error message, close, error message, close..). The consequence is that I can't use my phone anymore (the weird thing is I see the incoming sms, but that's all).
The problem is that my phone is not detected by RSDlite anymore (and even by Motorola device manager). ADB isn't working when I try to connect when the phone is in USB mass storage mode (device not found), which could be normal as I can't enable USB debugging mode. The only thing I can do is power on the phone in recovery mode, then plug it to the PC, then use the terminal to make fastboot recovery (I used a custom recovery.img taken from xda). Thus, I might be able to reflash the phone with another ROM, but I am not sure... I figured I also could enable USB debugging mode with ADB, but I can't use ADB
Anyway, this is what I've done before I was stucked :
- enable fastboot (it wasn't)
- root my phone (ok)
- install CWM
- backup my data
- install CyanogenMod 7.2.zip and corresponding google apps on my SD card
- restart in recovery
- wipe data & cache
- choose install from sdcard option
- run cyanogenmod 7.2 and google apps
- reboot
If you have a genious idea, please tell me, I will be REALLY grateful !
Thanks
EDIT:
I have also installed Motorola Device Manager (and I am under windows 8). I was wondering if there was an issue with the drivers, but I tried to reinstall, reboot, with no changes... I also tried to force windows using the drivers in Motorola folder, but windows says the device won't work properly. I am quite sure there is a driver issue too (I've just tried to use Android root software, but the phone is not detected).
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix). I do not consider my phone to be "bricked", just it has the display broken.
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ), maybe it's related to not having activated before the screen damage the debugging mode.
If I start the phone normally I can hear it when connecting it to computer and also it is shown in device manager, under "Portable device".
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
Hi all,
I am having a slight dilemma with my UK Note 4 N910F. I broke my screen while trying to replace my rear camera (long story). Now I have a phone that still works apart from the screen is dead.
My next problem is my phone is stock, USB debugging not enabled and has a password/fingerprint lock on it. The fingerprint lock won’t work due it being the first time the phone gets turned on after a restart it doesn’t work. I have looked into “recovering the data from it” for quite a few days now, and am at a dead end.
I first downloaded Android Control & Droid Screen and finally got them to work after having a windows 10/java nightmare.*
Downloaded and installed SDK platform tools and ADB drivers and to no avail it still would recognise my phone in “adb devices” so I thought this must be because USB debugging isn’t enabled.
I then installed Samsung Odin 3 and flashed Clockworkmod recovery which I believe has worked fine.
Still “ADB devices” nothing listed.
I then downloaded Dr.Fone (trial version) and started the data recovery and pulled my phone half way through. Which leaves it in recovery mode. Closed Dr.Fone reconnect my phone and I can get adb devices to show a “serial number recovery” listed.Droid screen detects my device but says its offline, and I can power on/off reboot etc my phone through android control.
If I reboot my phone then I lose recovery and droid screen/adb/android control wont work anymore.
Is this because it is resetting USB debugging enabled option?
Is there anyway when im in recovery mode I can enable USB debugging and keeping that setting if my phone is reset?
Any advice would be great.
Regards Jim