Hello!
I have an HTC m7, and am using Windows 7 to interface with it. Long story short, I have twrp on it, but no working operating system. For a moment yesterday, it appeared successfully in the results of /adb devices, though when I tried to push a new rom to the internal storage on the phone using adb sideload, it failed (made it to 100% but then said failed, and when I tried to install the created .zip file, it failed as well). Since that attempt, I have been unable to see my phone as an ADB device again - I've reinstalled HTC drivers, tried various usb cables, and gone through many iterations of /adb devices (blank) /adb kill-server. After failing to find a solution elsewhere on these forums or elsewhere, I come to you.
I'd love to know if there's anything that could cause the phone to disappear after it had been previously connected, and if there's some further steps I could take to get it to work!
Thanks for your help,
Devin
Hi there!
I suggest you try returning to stock, since you're having troubles with adb. Tho, it must be a driver issue, or cable, or USB port. Usually it ends up being the cable in cases similar to yours.
Anyway, if you have no luck, try returning to stock....here's a great guide,
>*HTC One*>*One General*>*[GUIDE] How to Return to 100% Stock
Of course you will need to install recovery and root again after.
Any questions on this can be asked in the guide thread.
Good luck!!
Related
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
i've had a few issues with this on my Droid Pro. with windows connection a connection assistant came up with some options that I was able to get it to work as a drive.
Getting it to work with adb is another issue alone. The phone needs to be in "debug" mode. I would search for a tutorial on this because you need to edit files on the computer.
for example on my windows I needed to edit one set of files, while on my linux I had to edit another set of things.
I leave my phone in debug mode because i use it for my android app dev on both computers. try that and see if it shows up on your mac.
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
Hi all,
I've had to root my HTC One S for school recently (yes, really), but now I can't install the update that's been released.
When I start the update my phone reboots and enters Clockwork..
I've been trying to unroot my phone, but there's a lot of (different) information out there, and I can't seem to put my finger on it.
For starters, I have no idea what RUU is and I have no idea which stock img I need, since their are more than 20 of them out there..
Can somebody please guide me through?
Thanks!
Tom
Edit: I can't seem to get a Android 1.0 USB driver working.. If I type adb devices it lists no devices.. I've tried like 5 different drivers but none are working.
Edit: My normal USB driver is working. ADB devices returns my device, but when I try to flash the recovery in normal mode, it just says 'waiting for device'.
First time poster, long time lurker. I downloaded TWRP and installed the recovery image but soft bricked my phone. Silly me remembered I had a backup made in CWM but not in TWRP. This is when you say to run boot.img but unfortunately I can not get the drivers to install properly on my Windows 7 x64 machine, due to not having them on here to begin with. So I have no One X drivers on the computer, I have MIUI and CM10 downloaded but can not get them to load due to not flashing properly, and TWRP with no backup. I have followed all the forums to delete drivers, re-install HTC Sync, manually point to the drivers but no dice. So.....what should I do :fingers-crossed:
Mode please close, I have resolved the issue.
Please post your solution for the benefit of others. That is how this forum works, its basically a database of issues and solutions that everyone can use.
I also think you are/were confused. The phone doesn't need to be working to get the drivers on your PC. You can download them from a variety of places. If you have HTC Sync properly installed, the drivers needed to connect your phone (USB mount, adb, fastboot, etc.) are installed. But if you have connection problems, updating these drivers or re-installing them will sometimes resolve the issue.
It seems that all you needed to do is get the drivers properly installed, then mount USB and put the ROM on the phone's SD, and flash boot.img using fastboot.
You're absolutely right. The solution was that I kept looking for fastboot to identify the device, and in my head that mean I couldn't push or flash to it. So I ended up just flashing TWRP recovery again, then it booted to CM10. Now im dealing with a whole new issue, but I'm going to work through it before I post again. Thanks.
I'm trying to root my Verizon LG G3 on 5.0.1 VS98524B, but now ADB wont recognize my device. Yesterday I was trying to root it using a one click root tool but it would fail (it would say successful, but would not achieve root). today I decided to use the LG flash tool to restore my phone and try again. then I saw that the tool (which claims to support all g3 models on all firmwares above kitkat) did not support VS98524B, but there is another that does, but surprise surprise, adb no longer finds my phone.
I have tried; restoring my phone again, installing and reinstalling the drivers, use different computers (2 win 7, one win 10), use different cables, on different ports, change between ptp and mtp, toggling and untoggling usb debugging, restarting my computer, etc.
adb doesn't find the phone while running a root tool, or just doing the adb devices command in cmd....
looked at many threads, and not many (if any) seem to have this problem, and all who did were able to solve using one of the steps I mentioned above....\\
any help?
Coltonbyu said:
I'm trying to root my Verizon LG G3 on 5.0.1 VS98524B, but now ADB wont recognize my device. Yesterday I was trying to root it using a one click root tool but it would fail (it would say successful, but would not achieve root). today I decided to use the LG flash tool to restore my phone and try again. then I saw that the tool (which claims to support all g3 models on all firmwares above kitkat) did not support VS98524B, but there is another that does, but surprise surprise, adb no longer finds my phone.
I have tried; restoring my phone again, installing and reinstalling the drivers, use different computers (2 win 7, one win 10), use different cables, on different ports, change between ptp and mtp, toggling and untoggling usb debugging, restarting my computer, etc.
adb doesn't find the phone while running a root tool, or just doing the adb devices command in cmd....
looked at many threads, and not many (if any) seem to have this problem, and all who did were able to solve using one of the steps I mentioned above....\\
any help?
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist but fortunately there is an XDA area dedicated to the Verizon LG G3 at http://forum.xda-developers.com/verizon-lg-g3 which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/verizon-lg-g3/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.