ADB is unable to see my HAM2L03. It just keep waiting for devices or list of devices bring up nothing. The command is "adb devices." Where can I find drivers for my phone? I looked at this, but it doesn't look safe at all. Their website doesn't have the drivers either. What should I do?
I have tried:
-Restart the daemon
-Changing USB ports [USB2.0 & USB 3.0]
-Restarting the phone
-Restarting the computer
Stock 5.1
Windows 10
lowao said:
ADB is unable to see my HAM2L03. It just keep waiting for devices or list of devices bring up nothing. The command is "adb devices." Where can I find drivers for my phone? I looked at this, but it doesn't look safe at all. Their website doesn't have the drivers either. What should I do?
I have tried:
-Restart the daemon
-Changing USB ports [USB2.0 & USB 3.0]
-Restarting the phone
-Restarting the computer
Stock 5.1
Windows 10
Click to expand...
Click to collapse
Install HiSuite Google it
Sent from my Ascend Mate 2 using Tapatalk
---------- Post added at 01:28 PM ---------- Previous post was at 01:27 PM ----------
lowao said:
ADB is unable to see my HAM2L03. It just keep waiting for devices or list of devices bring up nothing. The command is "adb devices." Where can I find drivers for my phone? I looked at this, but it doesn't look safe at all. Their website doesn't have the drivers either. What should I do?
I have tried:
-Restart the daemon
-Changing USB ports [USB2.0 & USB 3.0]
-Restarting the phone
-Restarting the computer
Stock 5.1
Windows 10
Click to expand...
Click to collapse
You don't need the app but the drivers
That's why you need to install it. Along with adb
Sent from my Ascend Mate 2 using Tapatalk
superbass311 said:
Install HiSuite Google it
Sent from my Ascend Mate 2 using Tapatalk
---------- Post added at 01:28 PM ---------- Previous post was at 01:27 PM ----------
You don't need the app but the drivers
That's why you need to install it. Along with adb
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Thanks, that's the information I needed. And thank you for your TWRP how to video. It's been a while since I have messed around with my HAM2 and that video helped refresh my memory.
No problem anything just ask
Sent from my Ascend Mate 2 using Tapatalk
superbass311 said:
No problem anything just ask
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Actually, do I have to manually update myself to B322? I am currently at MT2-L03C00B309 and I have no available updates for my phone. And I know CM requires you to be on B3222 to even flash it.
Also, which nightly or snapshot are you using on your ham and how is it? Is it your daily driver?
lowao said:
Actually, do I have to manually update myself to B322? I am currently at MT2-L03C00B309 and I have no available updates for my phone. And I know CM requires you to be on B3222 to even flash it.
Also, which nightly or snapshot are you using on your ham and how is it? Is it your daily driver?
Click to expand...
Click to collapse
Yes update to b322. It's actually easy download from Huawei site. Unzip and place unzipped folder on root of sd card and then turn off the phone and press all 3 buttons at once then let go over power or something
Sent from my Ascend Mate 2 using Tapatalk
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You have the choice of CM, carbon or PAC. I can't choose for you.. I think CM is updated fastest. PAC is coolest and Carbon has all Devs but I don't like carbon for silly lil bug reasons.
Sent from my Ascend Mate 2 using Tapatalk
superbass311 said:
Yes update to b322. It's actually easy download from Huawei site. Unzip and place unzipped folder on root of sd card and then turn off the phone and press all 3 buttons at once then let go over power or something
Sent from my Ascend Mate 2 using Tapatalk
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You have the choice of CM, carbon or PAC. I can't choose for you.. I think CM is updated fastest. PAC is coolest and Carbon has all Devs but I don't like carbon for silly lil bug reasons.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Thanks for the fast reply.
No OTA? Do you have a Consumer Cellular or what?
Also, just for anyone else reading this, sometimes trying a different cable will help your phone to be identified. (You did good updating drivers, trying a different port, etc. I just wanted to get this idea out there, too.)
kimtyson said:
No OTA? Do you have a Consumer Cellular or what?
Also, just for anyone else reading this, sometimes trying a different cable will help your phone to be identified. (You did good updating drivers, trying a different port, etc. I just wanted to get this idea out there, too.)
Click to expand...
Click to collapse
Actually, it's straight from Huawei, themselves, well Amazon that is. But yea, no OTA. Weird, right? I am going to do the B322 update tonight and then try CM.
When I installed HiSuite v2.3.55.1, fastboot devices shows nothing while adb devices outputs:
C:\adb>adb devices
List of devices attached
68a0f6ad32d4 device
Are there other drivers that I am missing? Yes, my bootloader is unlocked.
sakui23 said:
When I installed HiSuite v2.3.55.1, fastboot devices shows nothing while adb devices outputs:
C:\adb>adb devices
List of devices attached
68a0f6ad32d4 device
Are there other drivers that I am missing? Yes, my bootloader is unlocked.
Click to expand...
Click to collapse
I think usually fastboot should work when adb works. One thing i can think of is maybe try run the DOS prompt with admin rights? Btw, when you under fastboot, what the phone is showing in the screen? Just want to make sure you are in the correct mode.
xordos said:
I think usually fastboot should work when adb works. One thing i can think of is maybe try run the DOS prompt with admin rights? Btw, when you under fastboot, what the phone is showing in the screen? Just want to make sure you are in the correct mode.
Click to expand...
Click to collapse
I guess there is a fastboot mode now. I had these phones in the closet for a while. The provider had a bad singal before we went to sprint. I am digging the new b322 version of an Android. I'm tempted to replace the Note 4 for the HAM2 but I love the S-Pen. The HAM2 are all unlocked and rooted and I have 3 of them.
Sakui
Related
I've been working at this problem for 6 hours about now...Everytime I plug in the device to put the ViperDNA rom onto it, it keeps coming up with with an MTP, or MTP USB Device driver error failed...I cannot figure out how to fix it...any suggestions?
Do you have usb debugging enabled in settings?
Also you can get the adb drivers doing a google search
cmos8088 said:
Do you have usb debugging enabled in settings?
Also you can get the adb drivers doing a google search
Click to expand...
Click to collapse
Well, the problem is once i turn on the device, it goes into SoD, and I dont believe usb debuggin was on..so what do i do?
What about using "AirDroid" from the market and copy the ROM over WiFi ?
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
Thats how I do it so I never have to plug it on or download the ROM directly on the phone.
zone23 said:
What about using "AirDroid" from the market and copy the ROM over WiFi ?
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
Thats how I do it so I never have to plug it on or download the ROM directly on the phone.
Click to expand...
Click to collapse
I can't even boot the phone...I can only get into recovery and fastboot. and those dont even connect right.
Well since your getting a SoD... you most likely have to reflash your rom. If you don't have it on your phone you will have to to a sideload install. I've never played with sideload but I am sure others will be able to help you.
Do you have the android sdk installed? Sounds like you don't have the right drivers installed. Get the sdk, open the sdk manager, update the usb driver, reboot the pc. You should be able to push the rom to the phone with Adb.
You need to be bootloader unlocked and have a recovery installed like twrp or cwm as well.
Sent from my HTC One X using xda app-developers app
c5satellite2 said:
Do you have the android sdk installed? Sounds like you don't have the right drivers installed. Get the sdk, open the sdk manager, update the usb driver, reboot the pc. You should be able to push the rom to the phone with Adb.
You need to be bootloader unlocked and have a recovery installed like twrp or cwm as well.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
alright, i got really close, i got adb working and i cud see the device, but then it said "protocol failure" when i pushed the rom to the phone. what now?
BTW did you happen to make a backup before flashing? If you did restore it
cmos8088 said:
BTW did you happen to make a backup before flashing? If you did restore it
Click to expand...
Click to collapse
I did, and tried to do that...but it says no files found...which makes no sense, i did backup during 1.0 viper
did you update cwm I have heard others not being able to find it once they did. Also did you get that SoD from updating to a new rom? if so it is most likely corrupt or the install didn't complete.
cmos8088 said:
did you update cwm I have heard others not being able to find it once they did. Also did you get that SoD from updating to a new rom? if so it is most likely corrupt or the install didn't complete.
Click to expand...
Click to collapse
Alright i got it to work, somehow (lol), shud i do rosie or desense? which one ismore stable? And no not from the rom, i used a dpi changer(density) to 480 dpi...and i restarted and just never would fully boot. But i think i got it now.
NSammut said:
Alright i got it to work, somehow (lol), shud i do rosie or desense? which one ismore stable? And no not from the rom, i used a dpi changer(density) to 480 dpi...and i restarted and just never would fully boot. But i think i got it now.
Click to expand...
Click to collapse
It is a matter of preference I personally like HTC sense others hate it. You can always reflash and change it...
I'm glad you got it working
cmos8088 said:
It is a matter of preference I personally like it others don't hate it. You can always reflash and change it...
I'm glad you got it working
Click to expand...
Click to collapse
Yup, thanks for your help...I honestly don't know how i got it working, but i hope it stays that way haha.
Glad to hear you are back up and running. Rosie and sense run great on the DNA. But if you are messing with the dpi you might be better off desensing.
Sent from my HTC One X using xda app-developers app
Today I woke up to my phone saying Please insert Sim card, it was inserted. I restarted, no dice, reinstalled cm 10.2, no dice, wiped factory settings, cache, dalvik cache, then installed Paranoid android, still not working. It won't let me get past the activation screen even if I let it time out and hit skip it literally will just go back to the welcome screen and try to activate again.
I searched around and found that RUU-ing back to stock, locking the bootloader and all that would fix it so I locked the bootloader and am trying to use Ruu but half way through Ruu-ing it takes me to a black screen with a silver HTC logo on it and freezes, then Windows 8 tells me that it is not reconized and Ruu says error 171 which is a USB error. I checked under Device manager and it said unknown device so I'm obviously missing the driver so I go to install htc sync to get the driver and no dice, even if I uninstalled HTC sync and kept the driver it still didn't work. My question is which driver am I suppose to be using?
Phone: Droid DNA
Rom: Was running CM10.2 at the time then installed Paranoid Android to see if it would help
OS: Windows 8
iximoronixi said:
Today I woke up to my phone saying Please insert Sim card, it was inserted. I restarted, no dice, reinstalled cm 10.2, no dice, wiped factory settings, cache, dalvik cache, then installed Paranoid android, still not working. It won't let me get past the activation screen even if I let it time out and hit skip it literally will just go back to the welcome screen and try to activate again.
I searched around and found that RUU-ing back to stock, locking the bootloader and all that would fix it so I locked the bootloader and am trying to use Ruu but half way through Ruu-ing it takes me to a black screen with a silver HTC logo on it and freezes, then Windows 8 tells me that it is not reconized and Ruu says error 171 which is a USB error. I checked under Device manager and it said unknown device so I'm obviously missing the driver so I go to install htc sync to get the driver and no dice, even if I uninstalled HTC sync and kept the driver it still didn't work. My question is which driver am I suppose to be using?
Phone: Droid DNA
Rom: Was running CM10.2 at the time then installed Paranoid Android to see if it would help
OS: Windows 8
Click to expand...
Click to collapse
Try change USB port to 2.00, usb v3.00 is causing known issues . Update ADB drivers. also under windows devices manager unknown devices try to updates driver unknown device. Try it on Windows 7 pc.
http://forum.xda-developers.com/showthread.php?t=2293919
finanandroid said:
Try change USB port to 2.00, usb v3.00 is causing known issues . Update ADB drivers. also under windows devices manager unknown devices try to updates driver unknown device. Try it on Windows 7 pc.
http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Done all of those things except trying on a windows 7 computer, let me see if I can sneak onto my mother's work laptop hah. I also read that installing PDAnet would help me, each time during install it would BSOD me
Edit
Same thing on windows 7
Second edit
O man it is working even though adb devices showed nothing I booted to the welcome screen and started ruu there! Its always windows 8s problem isn't it?
Seriously thank you
iximoronixi said:
Done all of those things except trying on a windows 7 computer, let me see if I can sneak onto my mother's work laptop hah. I also read that installing PDAnet would help me, each time during install it would BSOD me
UPDATE
Same thing on windows 7
Click to expand...
Click to collapse
Did you FLASH THE STOCK HBOOT 1.15 so it matched RUU, when you ran RUU?
---------- Post added at 02:23 AM ---------- Previous post was at 02:05 AM ----------
iximoronixi said:
Done all of those things except trying on a windows 7 computer, let me see if I can sneak onto my mother's work laptop hah. I also read that installing PDAnet would help me, each time during install it would BSOD me
Edit
Same thing on windows 7
Second edit
O man it is working even though adb devices showed nothing I booted to the welcome screen and started ruu there! Its always windows 8s problem isn't it?
Seriously thank you
Click to expand...
Click to collapse
yes I read something about Windows 8 troubles working with adb. Hopes you back in business, but asap RUU finish and you boot in to
out the box Stock, do a Factory or phone reset from Stock Recovery*
finanandroid said:
Did you FLASH THE STOCK HBOOT 1.15 so it matched RUU, when you ran RUU?
---------- Post added at 02:23 AM ---------- Previous post was at 02:05 AM ----------
yes I read something about Windows 8 troubles working with adb. Hopes you back in business, but asap RUU finish and you boot in to
out the box Stock, do a Factory or phone reset from Stock Recovery*
Click to expand...
Click to collapse
I am back on stock but still roaming sadly. Any ideas?
iximoronixi said:
I am back on stock but still roaming sadly. Any ideas?
Click to expand...
Click to collapse
Did you Reset the phone after RUU? are u on VZW, you should receive the OTA 2.04 then 2.06
sometimes that happen, (the roaming s) if you still roaming get it to VZW to exchange SIM Card and be resetting.
finanandroid said:
Did you Reset the phone after RUU? are u on VZW, you should receive the OTA 2.04 then 2.06
sometimes that happen, (the roaming s) if you still roaming get it to VZW to exchange SIM Card and be resetting.
Click to expand...
Click to collapse
Evidently resetting it via recovery was the wrong way to do it. I tried it through fastboot and it worked!!! Thank you for all your help!
I'm on my second dna, about a month in total two phones. First one rooted, s-off from stock rom flashed the latest build of cm10.1. Upon boot up the first screen where it says activating it just sat there after about 5 minutes said it couldn't activate. Odd. On my past nexus devices Samsung gs2 and gs3 it would fly past that screen. I restored my back up same thing it said I had no service. Data worked but couldn't make a call or send a text.. Didn't know what to do and luckily Verizon didn't seem to care and swapped it out. So now I'm re-rooted on this phone but to afraid to flash anything cause of what happened. Seems like the same thing that happened to you happened to me.. I don't know how to do the ruu thing and I guess u can reset the phone from boot loader?? What fixed your issue.? I really want to rock stock android but to scared to flash anything. Let's say something happens again do I just get in boot loader and reset that's it nothing else needed?
Sent from my HTC6435LVW using Tapatalk 2
finanandroid said:
Did you FLASH THE STOCK HBOOT 1.15 so it matched RUU, when you ran RUU?
---------- Post added at 02:23 AM ---------- Previous post was at 02:05 AM ----------
yes I read something about Windows 8 troubles working with adb. Hopes you back in business, but asap RUU finish and you boot in to
out the box Stock, do a Factory or phone reset from Stock Recovery*
Click to expand...
Click to collapse
I can confirm not a windows 8 problem. I've done it several times on 8 pro 64 bit. Must have been something else.
Sent from my HTC6435LVW using xda app-developers app
iximoronixi said:
Evidently resetting it via recovery was the wrong way to do it. I tried it through fastboot and it worked!!! Thank you for all your help!
Click to expand...
Click to collapse
You welcome!
after RUU >Stock Factory Reset, can be done from the phone... Setting>Back up & Reset> Reset Phone ( is exactly the same process when you go to Bootloader, fastboot and apply /Factory Reset. my bad if you misunderstand my concept , I called Stock Recovery to the Factory image and setting of the phone as it came out of the box to differentiate from Custom Stock Recovery like CWR/TWRP. Glad that u figured it out and have your phone back. Next time i will more specific.
cstrife999 said:
I can confirm not a windows 8 problem. I've done it several times on 8 pro 64 bit. Must have been something else.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Maybe I shouldve mentioned I am on Windows 8.1 (Which is leaps and bounds above 8) but that could have had something to do with it
iximoronixi said:
Maybe I shouldve mentioned I am on Windows 8.1 (Which is leaps and bounds above 8) but that could have had something to do with it
Click to expand...
Click to collapse
yeap it need extra work around windows drivers.
iximoronixi said:
Maybe I shouldve mentioned I am on Windows 8.1 (Which is leaps and bounds above 8) but that could have had something to do with it
Click to expand...
Click to collapse
I actually had to downgrade from 8.1 because it was impossible for me to get adb and fastboot working, because of the drivers. I spent the better part of a whole day trying to, its simply broken because of driver signing.
jake.corey.jacobs said:
I actually had to downgrade from 8.1 because it was impossible for me to get adb and fastboot working, because of the drivers. I spent the better part of a whole day trying to, its simply broken because of driver signing.
Click to expand...
Click to collapse
Yeah it was just easier for me to use my mother's work laptop which has windows 7 on it but now moonshine won't work so there goes my day
Use Ubuntu live CD bro
Sent from my HTC6435LVW using Tapatalk 4
jake.corey.jacobs said:
Use Ubuntu live CD bro
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
I was trying to avoid that because I have had issues with ubuntu in the past and I also have gotten s-off before without it but I honestly don't remember what way I used but I guess I'll give ubuntu a shot
There's nothing to mess up. Its a live CD and changes nothing on your HD. And nothing to install outside of Moonshine itself.
Sent from my HTC6435LVW using Tapatalk 4
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
So wait. Are you still s-off?
Sent from my HTC6435LVW using Tapatalk 4
jake.corey.jacobs said:
There's nothing to mess up. Its a live CD and changes nothing on your HD. And nothing to install outside of Moonshine itself.
Sent from my HTC6435LVW using Tapatalk 4
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
So wait. Are you still s-off?
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
ah ok sweet thanks and no I am now s-on, tampered, and getting kind of frustrated hah
Edit:
I am still getting the don't drink and shine error on Ubuntu live as I was getting on windows
iximoronixi said:
ah ok sweet thanks and no I am now s-on, tampered, and getting kind of frustrated hah
Edit:
I am still getting the don't drink and shine error on Ubuntu live as I was getting on windows
Click to expand...
Click to collapse
So you went back to s-on?
if so you can try this http://forum.xda-developers.com/showpost.php?p=44796097&postcount=5
jake.corey.jacobs said:
So you went back to s-on?
if so you can try this http://forum.xda-developers.com/showpost.php?p=44796097&postcount=5
Click to expand...
Click to collapse
You are amazing! This worked! thank you so much!
improvements in touch, performance and stability of the system, detecting the sim, htc share
88 Mb.
Enviado desde mi HTC One max mediante Tapatalk
wow, could you post the OTA file for us here please?
Where is the OTA?
Enviado desde mi HTC One max mediante Tapatalk
This is for what model/variant is this for? Verizon Sprint International?
International
axpion
OTA Link
Here it is:
https://drive.google.com/file/d/0B27MEA0Eavx1aUt4UVdFcWFLTEk/edit?usp=sharing
shenye said:
Here it is:
https://drive.google.com/file/d/0B27MEA0Eavx1aUt4UVdFcWFLTEk/edit?usp=sharing
Click to expand...
Click to collapse
Thanks for posting
Sent from my HTC One max using XDA Premium 4 mobile app
---------- Post added at 12:12 PM ---------- Previous post was at 11:18 AM ----------
shenye said:
Here it is:
https://drive.google.com/file/d/0B27MEA0Eavx1aUt4UVdFcWFLTEk/edit?usp=sharing
Click to expand...
Click to collapse
Do you know which version of the software was there on your phone prior to this ?
Hello there,
I have also received this update but can't apply it. I am on stock rom but with rom manager clockworkMod recovery,rooted, s-off and relocked the bootloader. CID is J_15
I am little bit confused with this, appreciate your kindly advise. Thanks.
Ota only in recovery stock, no?
axpion
axpion said:
Ota only in recovery stock, no?
axpion
Click to expand...
Click to collapse
I do have the full backup files. do i need to unroot unlock and lock the bootloader via htcdev ? and restore the recovery.img from backup ? Thanks a lot
maximum not know two days ago that I have not
axpion
ahmedalmandhari said:
I do have the full backup files. do i need to unroot unlock and lock the bootloader via htcdev ? and restore the recovery.img from backup ? Thanks a lot
Click to expand...
Click to collapse
Do you mean that I should unroot and remove the custom recovery and put back the stock recovery which I back it up earlier.
pradeepvizz said:
Thanks for posting
Sent from my HTC One max using XDA Premium 4 mobile app
---------- Post added at 12:12 PM ---------- Previous post was at 11:18 AM ----------
Do you know which version of the software was there on your phone prior to this ?
Click to expand...
Click to collapse
Well this is the file name
Code:
OTA_T6_UL_JB43_SENSE55_HTC_Europe_1.54.401.1-1.19.401.2_release_341451bchda87kitj44eh9.zip
Which clearly shows which version it is targeted at.
shenye said:
Well this is the file name
Code:
OTA_T6_UL_JB43_SENSE55_HTC_Europe_1.54.401.1-1.19.401.2_release_341451bchda87kitj44eh9.zip
Which clearly shows which version it is targeted at.
Click to expand...
Click to collapse
So silly of me, thanks
Any noticeable improvements?
Sent from my HTC One max using XDA Premium 4 mobile app
---------- Post added at 06:40 PM ---------- Previous post was at 06:09 PM ----------
shenye said:
Well this is the file name
Code:
OTA_T6_UL_JB43_SENSE55_HTC_Europe_1.54.401.1-1.19.401.2_release_341451bchda87kitj44eh9.zip
Which clearly shows which version it is targeted at.
Click to expand...
Click to collapse
Oh God, This is Shen! did not realize it until now lol
Good to see you at the MAX forums
Issues with Update and Fastboot
I'm also having issues with the update... Got stock rom, cwm recovery and backups. Glad to have it back after screwing up my partition... ? Atm I'm not able to get my One connected in fastboot. As usbdisk it does, though... I de- and reinstalled all adb's and other necessary drivers several times... And I thought about flashing the recovery img of the update zip to get the whole update installed; do you think this is possible (provided I get my device connected in fastboot) ?
lol I just saw the stock recovery in an other thread, nevermind, I'll give it a shot...
MasterMace said:
I'm also having issues with the update... Got stock rom, cwm recovery and backups. Glad to have it back after screwing up my partition... �� Atm I'm not able to get my One connected in fastboot. As usbdisk it does, though... I de- and reinstalled all adb's and other necessary drivers several times... And I thought about flashing the recovery img of the update zip to get the whole update installed; do you think this is possible (provided I get my device connected in fastboot) ��
lol I just saw the stock recovery in an other thread, nevermind, I'll give it a shot...
Click to expand...
Click to collapse
And? Problems?
Still problems with adb
RayHeath said:
And? Problems?
Click to expand...
Click to collapse
I'm still strugglin' gettting my device connected in adb/fastboot
This is what I get when I plug in my One and reboot-bootloader and then it doesn't recognize the device....
Uninstall every driver you see connected to it in windows device manager. Restart pc and install htc sync manager. After it installs connect phone once without usb debugging and then unplug and connect again with usb debugging. You can then uninstall only htc sync manager if you want. Leave the driver package it installs. Then try...
MasterMace said:
I'm still strugglin' gettting my device connected in adb/fastboot
This is what I get when I plug in my One and reboot-bootloader and then it doesn't recognize the device....
Click to expand...
Click to collapse
Your OS seems pretty old there. Which country are you from? My OS is 1.25.111.2, I also agree with Jiggity Janx. Reinstall HTC Sync, and follow his instructions.
Jiggity Janx said:
Uninstall every driver you see connected to it in windows device manager. Restart pc and install htc sync manager. After it installs connect phone once without usb debugging and then unplug and connect again with usb debugging. You can then uninstall only htc sync manager if you want. Leave the driver package it installs. Then try...
Click to expand...
Click to collapse
Oh oh
RayHeath said:
Your OS seems pretty old there. Which country are you from? My OS is 1.25.111.2, I also agree with Jiggity Janx. Reinstall HTC Sync, and follow his instructions.
Click to expand...
Click to collapse
So, thanx for your advices. I already tried to de- and reinstall all drivers I'm Swiss FYI... I guess it doesn't mean something good when I look the attached shot...
Requesting you to help me as i had flashed SuperluminalDad Rom 2 days back on my friend's Micromax A116 HD.
Everything was working fine gained superuser access after updating binary and also was able to run root applications, just 2 days later i tried to connect my device to my laptop running Windows 8.1, it shows:
"The last USB device you connected malfunctioned and windows cannot recognize it", so i restarted the phone but superuser access was lost as SU binary couldnt be installed.
Troubleshooting Already Done:
1- Restarted phone and Laptop
2- Re-installed drivers on laptop still couldn't recognize and also tried re-installing SU bin and superuser from CWM after disabling the superuser apk on-board.
3- Flashed the complete Rom once again from CWM but still laptop couldn't recognize neither root access gained.
AmythP said:
Requesting you to help me as i had flashed SuperluminalDad Rom 2 days back on my friend's Micromax A116 HD.
Everything was working fine gained superuser access after updating binary and also was able to run root applications, just 2 days later i tried to connect my device to my laptop running Windows 8.1, it shows:
"The last USB device you connected malfunctioned and windows cannot recognize it", so i restarted the phone but superuser access was lost as SU binary couldnt be installed.
Troubleshooting Already Done:
1- Restarted phone and Laptop
2- Re-installed drivers on laptop still couldn't recognize and also tried re-installing SU bin and superuser from CWM after disabling the superuser apk on-board.
3- Flashed the complete Rom once again from CWM but still laptop couldn't recognize neither root access gained.
Click to expand...
Click to collapse
Try flashing Stock ROM via SP Tools !!
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
Try fix permission in cwm. If it doesn't help, post the question in the ROM thread. The developer would be able to help you more
SaketJoshi said:
Try fix permission in cwm. If it doesn't help, post the question in the ROM thread. The developer would be able to help you more
Click to expand...
Click to collapse
hi Saket, tried fixing permissions in CWM still not working...also cannot flash Stock rom as device is not getting detected on PC.
AmythP said:
hi Saket, tried fixing permissions in CWM still not working...also cannot flash Stock rom as device is not getting detected on PC.
Click to expand...
Click to collapse
Have you installed proper drivers ??
AmythP said:
hi Saket, tried fixing permissions in CWM still not working...also cannot flash Stock rom as device is not getting detected on PC.
Click to expand...
Click to collapse
Woah. Wait a min, you said win8 right? Turn off driver signature verification and install the drivers again. It'll work
SaketJoshi said:
Woah. Wait a min, you said win8 right? Turn off driver signature verification and install the drivers again. It'll work
Click to expand...
Click to collapse
Saket- i have done uninstalling the USB drivers from device manager and rebooting the laptop still showing USB malfunctioned.
AmythP said:
Saket- i have done uninstalling the USB drivers from device manager and rebooting the laptop still showing USB malfunctioned.
Click to expand...
Click to collapse
Try Using a Windows 7 or XP PC/Laptop !!
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
AmythP said:
Saket- i have done uninstalling the USB drivers from device manager and rebooting the laptop still showing USB malfunctioned.
Click to expand...
Click to collapse
that's not what I a telling you to do...
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Follow this link and you will know what to do
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
WalkerBales said:
Try Using a Windows 7 or XP PC/Laptop !!
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
Click to expand...
Click to collapse
changing the computer isn't the answer. there's always a walkthrough bro... just need to search for it
SaketJoshi said:
that's not what I a telling you to do...
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Follow this link and you will know what to do
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
changing the computer isn't the answer. there's always a walkthrough bro... just need to search for it
Click to expand...
Click to collapse
Agreed.... :thumbup:
Sent from my A116 using XDA Premium 4 mobile app
SaketJoshi said:
that's not what I a telling you to do...
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Follow this link and you will know what to do
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
changing the computer isn't the answer. there's always a walkthrough bro... just need to search for it
Click to expand...
Click to collapse
Yes you are also right @SaketJoshi In today's world of technology there is a solution for everything !!
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
WalkerBales said:
Yes you are also right @SaketJoshi In today's world of technology there is a solution for everything !!
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
Click to expand...
Click to collapse
Thanks alot guys for the suggestions.:laugh: Ive tried checking the device on another PC and Volla" its working!!
Would be following the steps to disable drivers signatures and would let you guys know whether it is fixed or not.
AmythP said:
Thanks alot guys for the suggestions.:laugh: Ive tried checking the device on another PC and Volla" its working!!
Would be following the steps to disable drivers signatures and would let you guys know whether it is fixed or not.
Click to expand...
Click to collapse
You are welcome bro... And congrats that it finally worked !!!
Sent from my SGT 7 running Omni ROM Official Kitkat Nightlies
So, my fire HD has the Android composite ADB interface as the driver.. I can find the tablet on prompt ADB devices but when I put the device into adb reboot recovery I lose it.. The cme can't see the tablet anymore, any thoughts on a solution? Windows 8 x64
Thanks very much
Are you saying "adb reboot recovery" doesn't boot you into recovery or that once in recovery adb commands don't work. If you're booting into stock recovery, that seems to be how it works.
If you can't get into recovery with the generic drivers, I swear by Google Galaxy Nexus from Koush's Universal Android package. Someone recommended the HTC dream driver.
EDIT: I see the prob. Wouldn't be able to issue "adb sideload" would you? Sorry, not much help.
---------- Post added at 10:25 PM ---------- Previous post was at 10:06 PM ----------
Well, this is good to know at this thread too!
limitedxj said:
I fixed my own problem, when in recovery the tablet was acting like a new tablet, wondered if that was true so i checked the managed devices, sure enough, the fire had a new name, added the Adb composite to the new name, boom..
Click to expand...
Click to collapse
Correction
Thanks for pasting that, I originally posted it in the specific thread I was trying to duplicate then realized it was a driver issue and more Q/A related. The fix for my problem was checking the driver setting at each step of Adb on 1st initation. Simple fix but threw me off a bit..
Thanks for the quick reply
So I'm seeing this exact issue. (As you said in other thread, adb devices returns device id, then in recovery it doesn't.) Can you clarify "first initiation"? I've had these drivers installed for months. You just updated, checking driver setting in device mgr? thx
limitedxj said:
The fix for my problem was checking the driver setting at each step of Adb on 1st initation.
Click to expand...
Click to collapse
DoLooper said:
So I'm seeing this exact issue. (As you said in other thread, adb devices returns device id, then in recovery it doesn't.) Can you clarify "first initiation"? I've had these drivers installed for months. You just updated, checking driver setting in device mgr? thx
Click to expand...
Click to collapse
limitedxj said:
Thanks for pasting that, I originally posted it in the specific thread I was trying to duplicate then realized it was a driver issue and more Q/A related. The fix for my problem was checking the driver setting at each step of Adb on 1st initation. Simple fix but threw me off a bit..
Thanks for the quick reply
Click to expand...
Click to collapse
DoLooper said:
Are you saying "adb reboot recovery" doesn't boot you into recovery or that once in recovery adb commands don't work. If you're booting into stock recovery, that seems to be how it works.
If you can't get into recovery with the generic drivers, I swear by Google Galaxy Nexus from Koush's Universal Android package. Someone recommended the HTC dream driver.
EDIT: I see the prob. Wouldn't be able to issue "adb sideload" would you? Sorry, not much help.
---------- Post added at 10:25 PM ---------- Previous post was at 10:06 PM ----------
Well, this is good to know at this thread too!
Click to expand...
Click to collapse
limitedxj said:
So, my fire HD has the Android composite ADB interface as the driver.. I can find the tablet on prompt ADB devices but when I put the device into adb reboot recovery I lose it.. The cme can't see the tablet anymore, any thoughts on a solution? Windows 8 x64
Thanks very much
Click to expand...
Click to collapse
Try this when you are in sideboard mode forum.xda-developers.com/showthread.php?p=36523572#post36523572
Sent from my Nexus 7 using Tapatalk
powerpoint45 said:
Try this when you are in sideboard mode forum.xda-developers.com/showthread.php?p=36523572#post36523572
Click to expand...
Click to collapse
ok, by "sideboard," I'm guessing you mean sideload, but figure you must mean recovery Anyway, thanks!
I think I see problem. I saw this post over here in Q&A, not as part of your upgrade to 5/downgrade to 4.5.3 guide. So, I'm trying this on 4.5.3(!) which doesn't have any "Apply update from ADB" option. When OP said he was able to fix drivers so he could give adb command from recovery, I thought he meant on 4.5.3 and wondered why I couldn't do that.
Makes perfect sense that adb wouldn't recognize a 4.5.3 device in recovery, where it's basically turned off while waiting for a manual reboot or reset. (Eagerly awaiting method to preserve root through 5.0 upgrade ) Ah, well . . .
DoLooper said:
ok, by "sideboard," I'm guessing you mean sideload, but figure you must mean recovery Anyway, thanks!
I think I see problem. I saw this post over here in Q&A, not as part of your upgrade to 5/downgrade to 4.5.3 guide. So, I'm trying this on 4.5.3(!) which doesn't have any "Apply update from ADB" option. When OP said he was able to fix drivers so he could give adb command from recovery, I thought he meant on 4.5.3 and wondered why I couldn't do that.
Makes perfect sense that adb wouldn't recognize a 4.5.3 device in recovery, where it's basically turned off while waiting for a manual reboot or reset. (Eagerly awaiting method to preserve root through 5.0 upgrade ) Ah, well . . .
Click to expand...
Click to collapse
Lol yes I mean sideload. Dumb auto correct. I say sideload instead of recovery because recovery alone has no adb access. Adb is only activated whenever you put it in sideload mode
Sent from my Nexus 7 using Tapatalk
Ah. . . now i get it. Thanks!
Looper,
In cme, using adb devices I was able to see the fire, when typing adb reboot recovery, then adb devices I could no longer cme find the tablet. Well sideload was not going to happen till I could see it again, even tho the tablet was on the recovery prompts. The fix was just checking the driver in device manager after doing the reboot recovery prompt.. Added adb composite to that and then I could find the tablet again, I then sideloaded fine.