OK, so here's the issue. I have an HTC Desire C. It's my girlfriends so I don't know the OS version. I replaced the Touch Digitizer because it was shattered (it did respond to touches though). Now that its replaced it seems to respond to touches but not correctly. I can't get it to swipe the lock screen out of the way. It's as if it is not calibrated correctly. So I'm stuck on the lock screen.
I want to run ADB so I can figure out if its registering touch events correctly, and also try and send them over ADB. But, being my girlfriends phone, she never enabled "USB Debugging". When I hook the phone to the computer, I don't see it showing up as a unknown device in windows Device manager (VISTA). I know it works, cause I tried it with my Nexus S and that shows up. I know the steps are first find it in device manager then manually select the driver as the ADB interface, I've had this working on my Nexus S. But the issue is that it doesn't show up at all in Device manager, and I assume its because USB debugging is off. I tried turning off USB debugging on my Nexus S, hooked it to my computer, and it doesn't show up either. So it seems like that is the issue.
I tried to boot into recovery (power button + volume down), then went into fastboot, connected the phone to the comp again, but it still does not show up.
Below are some of the other things I have tried, but they still brought me no luck:
I have tried installing HTC sync so I get the HTC drivers on my computer, but it doesn't even show up in HTC's software (In fact, it does not show up as a storage device either, I assume cause you have to accept the notification on the phone, but I can't use the phones UI at all). I tried moving the HTC drivers into c:\windows\system32 and it still does not show up. I then tried rebooting the phone and my computer. Still does not show up. It seems like windows isn't even reading the phone as a USB device. Tried swapping USB cables (both work with my nexus s), and still nothing. Is there something I am missing?
Any help would be much appreciated, this is driving me crazy.
Also, after replacing the digitizer, if I first boot into the phone and then hit the power button, I don't get the content window that allows you to choose "reboot", "shutdown", etc. The only thing I can do is hold it for 15 seconds and the thing turns off. I'm hoping this is because I never passed the lock screen for the first time. I'm hoping this is not an indicator that I screwed something up when I opened the phone. I've had my Nexus S open plenty of times.
Another guy had same issue. here
Try that.
life!
Yea let us know if it works
Lifehacker7 said:
Another guy had same issue. here
Try that.
life!
Click to expand...
Click to collapse
I can't get the phone to show up when I type "fastboot devices" or "adb devices". I have tried this from the lock screen, from the bootloader, from the bootloader and in fastboot mode. That is my critical problem now. Cable is actual data cable, and I'm using USB port on back of a desktop computer. Is there anything else that could be causing the phone to not be recognized?
Related
I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
Hello!
Today both the screen as the touch panel of my Galaxy Nexus broke. I wanted to run screencast or some other apps to control my phone via pc BUT after searching for "adb devices" I got my devices number and the word "offline".
I looked up on what I guess the issue was and what I found out was, that I have to verify my pc with this RSA-fingerprint in order to control my device, which I have not done yet on my latest rom, as I just flashed it a few days ago.
Now: can you think of any way, either bypassing the fingerprint or letting me control the device via pc to prompt the fingerprint-request?!
As mentioned, I THINK that is the problem.
Things I have tried:
different USB-port
different USB-cable
updating platform-tools
HDMI-output via MHL-adapter (no signal)
I really am hopeless and happy about all the ways, you could think of showing my phones screen on my pc. I would prefer to keep my current ROM data, as I do not want to wipe arrived messages before viewing them (WhatsApp).
some information:
device: Galaxy Nexus (GSM)
rom: latest AOKP Milestone (4.2.2)
root access of course
device definetly turned on (LED blinking)
-Jakob
Resolved!
I had a similar problem and after hours of research and trial/error, I was able to get this working. Here's how:
1. Download & install the Galaxy Nexus Toolkit and MyPhoneExplorer to your PC
2. Goto the Google Play Store on your PC and remote install MyPhoneExplorer and AF Rescue 2 apps to your phone. Wait 10 minutes or more so that this step has time to complete before continuing (longer is better)
3. Next you have to boot your phone into Recovery mode... pull the battery and usb cable out (so you can be sure your device is off). Put the battery back in, plug in the usb cable (I do this now so I can hear when the device is connected and later so you can hear that the command/reboots are working). hold down both vol up and vol down AND then hold down the power button... I do this for about 10 seconds. After releasing the buttons, your phone should be in bootloader mode, but I give it a minute just in case. now hit the vol up button 2 times then the power button. You will hear the usb connection go on and off several times and when it's done, your device will be in Recovery mode.
4. Launch the Toolkit, answer "no" to the initial question about checking for updates, then choose your device from the list
5. on the next screen (main menu) you should see your device ID listed under ADB mode list with the word "recovery" after it. If so, you have done everything correct so far. (if not, close the toolkit window, go back to step 3 and try again).
6. Next choose option 2 for Backup/Restore. Then select option 3 for "Backup your Internal Storage"
7. This is crucial. On the next screen choose option 2 "manually answer the question". Then when it asks if you are using a custom rom or recovery image, ANSWER "NO" (even if you are). This is the most important step in the whole process because it will then boot your phone into fastboot for you and install an insecure recovery image bypassing the 4.2.2 security!
8. When it tells you that the backup will take a long time and are you sure you want to continue, I recommend doing so. It will take hours (I left mine to run overnight.) Either way, when you get back to the main menu DO NOT REBOOT YOUR PHONE. YOU NEED IT IN THIS STATE.
9. Now if all has worked properly, you can launch MyPhoneExplorer on your PC and choose setup your connection via wifi. Cross your fingers, but if all worked as it did for me, your phone will appear on the screen (if it is all black, just hit the power button on your phone to wake it up). Use your mouse to enter your lock pattern or pin number if you have those set. At this point you should be using your phone through your PC. Just remember that as soon as you reboot the phone, it will revert back to it's secure state and you will have to go through this process again. I hope this helps you and others (and saves everyone the hours of frustration and research I went through).
jakbold said:
Hello!
Today both the screen as the touch panel of my Galaxy Nexus broke. I wanted to run screencast or some other apps to control my phone via pc BUT after searching for "adb devices" I got my devices number and the word "offline".
I looked up on what I guess the issue was and what I found out was, that I have to verify my pc with this RSA-fingerprint in order to control my device, which I have not done yet on my latest rom, as I just flashed it a few days ago.
Now: can you think of any way, either bypassing the fingerprint or letting me control the device via pc to prompt the fingerprint-request?!
As mentioned, I THINK that is the problem.
Things I have tried:
different USB-port
different USB-cable
updating platform-tools
HDMI-output via MHL-adapter (no signal)
I really am hopeless and happy about all the ways, you could think of showing my phones screen on my pc. I would prefer to keep my current ROM data, as I do not want to wipe arrived messages before viewing them (WhatsApp).
some information:
device: Galaxy Nexus (GSM)
rom: latest AOKP Milestone (4.2.2)
root access of course
device definetly turned on (LED blinking)
-Jakob
Click to expand...
Click to collapse
themadczar said:
I had a similar problem and after hours of research and trial/error, I was able to get this working. Here's how:...
Click to expand...
Click to collapse
Thank you very much for your time and effort, I will try this soon!
Sadly I am in the same position as the OP. My screen is cracked and I need to access the phone via adb, unfortunately, it is appearing as offline. Does anyone know a way to bypass this RSA-fingerprint issue?
Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.
momostarz said:
Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please direct your question here for further assistance:
http://forum.xda-developers.com/google-nexus-5/help/help-thread-nexus-5-question-t2496506
Good luck!
Hello, there.
I bought my nexus 5 the day it was launched. Worked great for 2 yeas+.
Now is dead. It's a long story.
One day simply died. I pluged it to charge it and turn on and off constantly (boot loop). I watched some videos on youtube where people constrantly press the power button and after a moment, it worked. But eventualy stop working again and it never boot again.
I can't access fastboot, nothing. I researched again and found that the power button could be damaged. So I removed it and install a new one and SURPRISE. The loop was gone, it charges, but the power button doesn't seem to be working...or could be another thing!!!
When I plug it to the USB, the PC recognize it, but as "other device". However, it call it "Android". Can't understand.
If I search for adb devices on the command line, it founds nothing.
If adb devices could find it, maybe i'll be able to boot it from the command line, right?
Any help would be appreciated.
Thanks
Adb commands won't work unless the phone is booted into the rom. If you can get into the bootloader, fastboot commands should work if the drivers are loaded.
So, something very weird started happening to my phone. Out of nowhere, about 7 hours ago, it would stop charging whenever it was on, charging only when it was off and connected to my laptop. However, I thought it was just something wrong in the dev options, and I went to change whatever was the USB option to "charge phone". With this, I did accidentally forgot to activate the OEM option, and had to reboot not long after. You can probably see where this is going now.
Now I have a phone that bootloops on the FAP Lock message, and whenever I go to download mode to fix it, my PC just doesn't recognize the Phone. I've tried different USB cables, all of them are only recognized when the phone is shut down. So it isn't a hardware problem, because the Phone actually charges when it's shut down, and it isn't a problem with my USB ports or cables, as anything else I use with it works fine. And the worst part is, I need this phone today for a serious bank matter, and I can't afford to lose any data on it either, there's some very personal important stuff from yesterday that wasn't backed up yet. And keep in mind that paying for it to be fixed is the last option for me, as I can't afford it (besides, I fear they might end up getting the phone in factory reset mode, and I can't lose that data as I said).
Any kind of suggestions on how to get either the PC to recognize the phone, or flashing in a different way that doesn't need the PC to recognize the device? Thanks in advance.
Edit: Whenever I try to connect the phone via USB, it doesn't even make the Windows "USB connected" sound, it's just like it isn't there at all. One time, I got it to show, but it was as a "unrecognized usb device", and I haven't been able to replicate it yet.