Hey there, I am trying to install either Lineage or DivestOS on a HTC One m8, I am able to install adb and fastboot, enable USB Debugging, unlock the bootloader, install recovery and then enter recovery. I am also able to wipe data but when trying to sideload I get an "adb: sideload connection failed: no devices/emulators found" error. I have no idea of what is causing this issue, but I am out of ideas. I have now tried doing this on 3 different computers, 2 of them with win7 and 1 with win10. What am I doing wrong? I have no idea what the issue might be since the only abnormal thing I have noticed is the fact that the "MTP" driver fails at installing (or loading idk) with code 10. Could that be the issue? I need to install some OS asap since my main phone just died and stock m8 is unusable because of how slow it is rn, so I would really appreciate any help.
kpinal said:
Hey there, I am trying to install either Lineage or DivestOS on a HTC One m8, I am able to install adb and fastboot, enable USB Debugging, unlock the bootloader, install recovery and then enter recovery. I am also able to wipe data but when trying to sideload I get an "adb: sideload connection failed: no devices/emulators found" error. I have no idea of what is causing this issue, but I am out of ideas. I have now tried doing this on 3 different computers, 2 of them with win7 and 1 with win10. What am I doing wrong? I have no idea what the issue might be since the only abnormal thing I have noticed is the fact that the "MTP" driver fails at installing (or loading idk) with code 10. Could that be the issue? I need to install some OS asap since my main phone just died and stock m8 is unusable because of how slow it is rn, so I would really appreciate any help.
Click to expand...
Click to collapse
Yes, get the MTP driver correctly installed.
@kpinal
In your case ADB makes use of a HTC One M8 suitable Android USB Driver ( ADB & Fastboot ), not of any MTP-driver.
Look inside here:
Download HTC USB Driver for Windows (Latest Driver)
Download the latest and original HTC USB Driver to connect any HTC Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
On my Windows 10 PC I couldn't get the fastboot command to work with my HTC, now with the driver you've provided I can actually use it but it still gives me the same error when getting to the adb sideloading step. On both of my Win7 PCs the sideload error remains and MTP driver still fails to install. I finally gave up and used TWRP loading the zip from storage, but If someone has any other suggestion for the sideload issue, I'd appreciate it, since I might just need to repeat this process again at some point and I like that method the most.
Become familiar what ADB Sideload method is to be used for:
How to Use ADB Sideload to Install ROMs, Updates, Restore on Android
There are various smartphones available out there. Android powers most of these smartphones. Some of the android devices often showContinue Reading
www.theworldsbestandworst.com
kpinal said:
Hey there, I am trying to install either Lineage or DivestOS on a HTC One m8, I am able to install adb and fastboot, enable USB Debugging, unlock the bootloader, install recovery and then enter recovery. I am also able to wipe data but when trying to sideload I get an "adb: sideload connection failed: no devices/emulators found" error. I have no idea of what is causing this issue, but I am out of ideas. I have now tried doing this on 3 different computers, 2 of them with win7 and 1 with win10. What am I doing wrong? I have no idea what the issue might be since the only abnormal thing I have noticed is the fact that the "MTP" driver fails at installing (or loading idk) with code 10. Could that be the issue? I need to install some OS asap since my main phone just died and stock m8 is unusable because of how slow it is rn, so I would really appreciate any help.
Click to expand...
Click to collapse
I ran into this problem. For future reference, the issue is that when it reboots into recovery, the driver on your pc changes. You have to go into device manager and manually change (update driver -> let me pick) it to "ADB Interface". Should be able to see it in command prompt after that.
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
I have a NS i9020T which was running the latest MIUI ROM until I tried to update it to MIUI ICS. I had noticed, while running pre-ICS, that my computer wouldn't mount USB storage. As a working around (rather that trying to fix the issue) I just FTPed files. When I tried to install MIUI ICS something went wrong (probably corrupt ROM image) and now my NS won't boot.
If I go through Clockwork Recovery to mount USB mass storage, nothing happens. I'm running OS X, but I've tried mounting in Ubuntu 11 and Win7 -- Windows recognizes that there is a device there but the drivers won't recognize it (I think).
Finally, I've tried flashing a new recovery using fastboot but I get "<waiting for device>" in Terminal.
My best guess is that the USB connection is shot, which would probably require me ripping the NS open and tinkering around (which I have zero experience doing).
Does anyone have any ideas for fixing what is likely a permanent brick? I can boot into Win7, OS X, or Linux to troubleshoot. Also I'm on the XDA IRC as "threepape" right now trying to solve this issue.
Thanks in advance!
I was working with threepape on IRC trying to narrow down the issue.
Basically he's had his phone rooted, tried flashing a rom and now it's stuck at the boot screen. He went to connect to his computer and it gave him an error. and wouldn't let him connect his phone to the os. This is a problem.
So he then downloaded kies to see if it would install drivers automatically, downloaded odin and then tried to see if odin would recognize the phone. It did not and his computer gave him the error "unknown USB device, error code 43"
So we reviewed what we could control: trying different cords, checking drivers, etc.
Now we are going to try booting into an osx platform, installing heimdall and seeing if "heimdall detect" prompt will detect the phone. If that doesn't work we're going to either need more help or rule it out as a hardware issue.
<threepape>
Failed to detect compatible download-mode device.
[8:55pm] <ddrt>
so you typed out heimdall, then heimdall detect and it came back with that?
[8:55pm] <ddrt>
and you are 100% it was in download mode?
[8:55pm] <threepape>
yep
[8:56pm] <threepape>
it does ay on my phonee "USB Control Init USB Control Init End"
Click to expand...
Click to collapse
edit: device is not being detected on multiple os using different programs, device will not wipe fully when doing a factory restore through CWM. I am at a loss.
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Click to expand...
Click to collapse
Are you using windows?
Did you try this?
Transformer Toolkit v2.0.1
Root your device with motochopper: http://forum.xda-developers.com/showthread.php?t=2230763
and from the playstore download and install goomanager and from goomanager install TWRP.
Then from TWRP flash CROMi-X
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
Click to expand...
Click to collapse
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
berndblb said:
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
Click to expand...
Click to collapse
Well I had tried motochopper around 20x before (and sadly, I am not exaggerating there) without it working once, but I felt that I should at least give it one more shot before saying I couldn't use it and of course now that I had asked for help it does work. lol; the IT curse strikes again. Thanks for that, monecani.
The drivers, on the other hand, are not working. :/ Windows is letting me try to install them now at least (before it was telling me there was "no compatible drivers" when I was literally having it select the ASUS specific ADB USB drivers, or just telling me that it had determined that my usb drivers that were in no way functioning were completely up to date), but then it fails install and says "This device cannot start. (Code 10)". I was able to install the drivers you gave me when the device was in launcher, but they didn't help me in fastboot, and actually interfered with my device being recognized properly by anything. I had to roll back the drivers to run motochopper.
I kinda agree with you on fastboot being something I don't strictly need, but would still be a good idea for me to have access to. Plus, I'm that special kind of person who cannot let something just be broken. It drives me crazy to know that something's wrong, even if I almost never use it, or even never use it.
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!!
I'm trying to install the 4.4.1 update but my device isn't being detected in recovery mode and thus adb sideload is not working. Would really appreciate some help. I've tried almost every solution that I've googled and nothing seems to be working.
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Sent from my Nexus 5 using xda app-developers app
jkimbro said:
I had a similar issue. Found the naked drivers and they seemed to work after uninstalling the other drivers and rebooting my PC.
Click to expand...
Click to collapse
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
You just need the Google drivers from their website:
http://developer.android.com/sdk/win-usb.html
I had to force the installation of the drivers for the "AOSP on Hammerhead" device in the device manager.
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
I used USB ADB Composite Interface or something like that by pointing the device manager's Update Driver dialog to the USB drivers from the SDK that EddyOS pointed at.
Windows 7 x64
Yep, had issues with my work PC (Win 7 Pro x64) - had to manually point Device Manager to the android_winusb.inf so it would find the drivers. Bit of a ballache but all working after that!
greenkabbage said:
I couldn't even get the device to show until I pressed VolUp in recovery and selected the ADB option in the recovery.
Click to expand...
Click to collapse
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
a hammerhead wrote this.
beekay201 said:
ADB isn't enabled on stock recovery, and sideload is not the same thing. From Google's POV, ADB access on recovery would be a heavy security risk, since you can still access recovery even with your bootloader locked. That's why they created sideloading.
Click to expand...
Click to collapse
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
jt3 said:
Any chance you could post those drivers? Mine works fine, but it would certainly help others if you could post them, or at least post a link to where you found them.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2513339
jt3 said:
ADB Server may not be enabled, but ADB obviously is, otherwise you wouldn't be able to connect in order to Sideload, which you can certainly do with stock recovery (even with a locked bootloader). Also, if ADB wasn't available on the device, it wouldn't show up with the "ADB Devices" command.
Now, maybe you mean it's not available once you boot into recovery until you select "apply update from ADB." That may be true (not sure), but that's not what I got from your statement.
Click to expand...
Click to collapse
Try it. Select "apply update from ADB", and then try to get a ADB prompt like you would normally, you know, ls /sdcard/, something.