this morning, i was using adb with my phone and then i decided to update from haykuroHr3 to Hr4. after that, i cant get adb to detect my phone. every time i try "adb remount" i get "error: device not found"
i have tried doing a few wipes and reinstalling the update but no luck. when i plug in my phone, i just shows up as a usb mass storage device. debugging is enabled and i have no clue what i wrong with it.
can anyone help me out? thanks.
You need to update your drivers. You probably did the SPL update didn't you? See Haykuro's blog.
thanks for the response.
i didnt have the new spl installed so i decided to try it and installed the spl and the new driver on my computer and after restarting both of them, i get the same problem.
Related
I just got a new mytouch because i lost my old one :/
last time i did the rooting through the gold card method, now i tried the one click method and it went horribly wrong, i belive i got root, i tried to boot up with a new image but i just stays stuck on the mytouch logo, i can go into fastboot, but when i try to go through fastboot through my computer, the computer doesn't recognize my phone(it doesnt show the serial number) should i install the drives all over again? right now i have i connected to my computer through usb, and it says "fastboot usb".
i have looked though the forums but i didnt find a specific answer, so please if im going to get bombed, all im asking is for a little help.
thanks in advance
ok so..
ok so i fixed my drivers and it detects my phone, but now when i am trying to fastboot it it doesnt let me
you are sure you installed the drivers correctly? can you make it to the recovery screen?
if u try adb devices in cmd using adb from sdk does it give you something like HT9623465? cos that should be fine, also if you're using the sdk try uninstall the driver and then copy the 'usb driver' folder contents from the sdk into the 'tools' folder so everythings in the same place and then refer to that directory for driver installation (windows detects it as android 1.0 device when in fastboot and the drivers are different from normal mode). forgive me if im wrong
So let me start by saying I have been researching these forums for the last 8 hours trying to following instructions on getting my phone to connect to my computer and with no luck, hoping someone out there can please help me step by step in correcting my problem.
1)I flashed DC's Rom, then flashed the most current radio, then flashed the most current Wimax.
2)I noticed that when I connect my phone to the computer, it says device is not recognizable. The phone charges but does cannot be seen by the computer as a disk drive (I'm trying to RUU to stock but the comp. will not see my phone and I've already tried running RUU but it also is having probs seeing the phone).
3)I've read Calculin's instructions in fixing the SD Card and USB as close as possible but also no luck. I've downloaded Android-SDK Tools and ran CMD with the Instructions saying type in "fastboot oem boot", from there, thats where I get stuck, it just says "waiting on device". Not sure where I go from there, I'm in Reboot mode where it has Fastboot on my evo screen.
Any help would be much appreciated, I'm just so frustrated and I'm trying to get back to square one.
Unplug your phone and restart it, then plug it back in. I had to do this 3 times before it started working again. Other than that, you might just need to download the new drivers.
And you posted in the wrong section.
Sorry about posting in the wrong section, what drivers should I install, are you talking about the new HTC Sync Files or something else? Can you point in the direction to get these files?
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
faquedado said:
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
Click to expand...
Click to collapse
You should be able to get the proper drivers from either Sprint or HTC's web site. There are links on both sites. Also, when you install / reinstall the sync drivers make sure anti-virus is disabled. If the situation continues and you've tried everything else other folks suggested look at program permissions in your anti-virus program. I was having something similar and CA anti-virus was not letting the program start-up. I had to toggle it to "allow".
Good Luck.
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Does usb debugging is on?
Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?
If You use asus drivers it worth to try universal naked driver.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.
Hmm... How windows show tablet when You connect it to PC?
Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.
Try first remove all drivers and software for tablet. Then install universal naked driver.
Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.
Guys, i need some help.
I was able to install the Viper ROM without any problems. But when i did a factory reset, i'm now stuck on the HTC ONE screen. I can still get to the recovery without issue. But i can't reflash it because i don't have anything in my sdcard to flash.
I found somebody had this issue too:
http://forum.xda-developers.com/show...2518736&page=3
I'm trying to push the rom into my sd card but i can't get my computer to recognize my phone! It's having the HTC MCP device driver issue (code 10). Tried installing HTC sync and that didn't help. Tried uninstalling the driver, but it won't allow me to install driver after i uninstall. Tried to update the driver but Windows is saying driver is up to date and won't let me update. Without getting my phone to be recognized by my computer, i can't push anything into my phone.
I posted in the Viper forum and i was told that maybe i need to reflash the boot.img since I'm on S-On. Which i think is the case.
The thing is i can't flash boot.img because of this MTP issue. I tried different cables with different USB ports. Nothing's working. When i plug in with HTC One, it recognizes fine. But when i plug in with One S, it's back to that MTP issue.
Anybody has any suggestions?
Thanks!
kc73837 said:
Guys, i need some help.
I was able to install the Viper ROM without any problems. But when i did a factory reset, i'm now stuck on the HTC ONE screen. I can still get to the recovery without issue. But i can't reflash it because i don't have anything in my sdcard to flash.
I found somebody had this issue too:
http://forum.xda-developers.com/show...2518736&page=3
I'm trying to push the rom into my sd card but i can't get my computer to recognize my phone! It's having the HTC MCP device driver issue (code 10). Tried installing HTC sync and that didn't help. Tried uninstalling the driver, but it won't allow me to install driver after i uninstall. Tried to update the driver but Windows is saying driver is up to date and won't let me update. Without getting my phone to be recognized by my computer, i can't push anything into my phone.
I posted in the Viper forum and i was told that maybe i need to reflash the boot.img since I'm on S-On. Which i think is the case.
The thing is i can't flash boot.img because of this MTP issue. I tried different cables with different USB ports. Nothing's working. When i plug in with HTC One, it recognizes fine. But when i plug in with One S, it's back to that MTP issue.
Anybody has any suggestions?
Thanks!
Click to expand...
Click to collapse
same problem ....sm1 please help
hassam_2010 said:
same problem ....sm1 please help
Click to expand...
Click to collapse
Fixed it!! i used CWM sideload. Go into recovery, then go into sideload. Connect your usb, then open adb. type "adb devices" just to make sure you're connected.
Now, you want to flash the ROM again. Download the zip file and put it into the same folder as adb. then type this command: adb sideload <filename of update.zip> and you're good to go!
Let me know if you have any questions!!
Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error