Windows 8.1 two ones only one works - AT&T HTC One (M7)

so as stated windows detects one att htc one in fastboot bootloader but will not detect my other one . windows makes a noise like it knows its being plugged in and it charges but it will not accept any commands on this other htc one im so confused at what the problem could be ? i have tried every htc cord and nexus 7 cord i have all work on one of them but none on the other ? could my usb port be broke and still charge the phone ? any advice or help would be greatly appreciated i usually know what im doing with htc phones so i will prob understand any ideas you think i should try in device manager it recognizes the one that works correctly but the problem ONE has yellow triangle and says
Unknown USB Device (Device Descriptor Request Failed) thats what it says in device manager for broken ONE. if you need more info let me know and please please please let me know if you know how to fix this on windows 8.1 i dont know why it recognizes one but not the other
Update after digging around in wondows device manager
windows has stopped this device because it has reported problems code 43 which is a hardware failure
so i guess i cant fix that huh makes no sense if i can boot recovery bootloader and rom
windows doesnt detect and adb doesnt detect

ac3kill said:
so as stated windows detects one att htc one in fastboot bootloader but will not detect my other one . windows makes a noise like it knows its being plugged in and it charges but it will not accept any commands on this other htc one im so confused at what the problem could be ? i have tried every htc cord and nexus 7 cord i have all work on one of them but none on the other ? could my usb port be broke and still charge the phone ? any advice or help would be greatly appreciated i usually know what im doing with htc phones so i will prob understand any ideas you think i should try in device manager it recognizes the one that works correctly but the problem ONE has yellow triangle and says
Unknown USB Device (Device Descriptor Request Failed) thats what it says in device manager for broken ONE. if you need more info let me know and please please please let me know if you know how to fix this on windows 8.1 i dont know why it recognizes one but not the other
Update after digging around in wondows device manager
windows has stopped this device because it has reported problems code 43 which is a hardware failure
so i guess i cant fix that huh makes no sense if i can boot recovery bootloader and rom
windows doesnt detect and adb doesnt detect
Click to expand...
Click to collapse
you have different hboot versions
here's the fix I used to make hboot >1.55 work on windows 8.1
http://forum.xda-developers.com/showthread.php?p=49131915
use the old dirty method it worked fine
http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072

Related

Htc Usb Sync

hi my device is still unusable since i flashed it no bootloader or no rom on device and all i get is when i plug in the usb cable in device manager on my computer i get HTC USB SYNC <<under windows ce devices
so what can i do to reflash my pda while it only comes up as that on my pc again i have no bootloader so i can forget about flashing it via sd card
please can someone help me out here
tried to redo the rom flash from the pc ?
after a bad flash my pda showd up as such
and i could just reflash
htc usb sync
ok if you flashed it while the device is in that state and showing htc usb sync in device manager can you tell me which rom you used to do so and what software you used ,,as i said i have no bootloader on the device so if you can help i would be very grateful
try taking a look at the broken bootloader part
http://wiki.xda-developers.com/index.php?pagename=XDAtools
htc usb sync
you no i have been asking around for nearly 1 yr about this problem those tools pnewbootloader.exe or xda tools dont work
let me make it more clear what the problem is on my xda
IT WAS A WORKING DEVICE PERFECT ,UNTIL I FLASHED IT WITH A WIN2003SE ROM ,,,,since then i have no bootloader i cant boot up nothing it comes on all i see is on the bottom right corner of the screen is
g32s54
v4.08
3.04
on the top ozup logo thats the rom i tried to flash and it messed up my xda
again i have no bootloader ,,i cant flash it via sd card ,,alll i have is this to work with .....when i plug in the xda to a windows xp pro sp2 computer i get HTC USB SYNC IN DEVICE MANAGER,,, nothing else ,,,so please tell me what software can i use to reflash my xda while it shows HTC USB SYNC ON MY DEVICE MANAGER USING THE USB LEAD ,,,there must be something to sort this out
the pnewbootloader tool i tried it several times but activesync doesnt work as my xda is not working right i cant active sync so that pnewbootloader dont work i cant upload any files to my xda even if i did i have no os on it
so again in my device manager it shows htc usb sync and all i got is version numbers on my xda screen on the bottom right corner
please someone help me bring it back to life i have tried every means

how to rescue from bootloader ??? help ??

hi
guys i am newbie in upgrading and tried to run athena wraper and it died and after searching forums i still cant find cure ok so here it is i can do hard reset but it dosent help no boot up it still gives me ring round joystick good news is i can get it to bootloader screen (or at least thats what i think ) its red green blue and white screen with usb or serial (depending on cable )
screen reads
ATHE100
IPL-V0.90
ATHE100
SLP-V1.20.Olipro
now can any one help me ??
how can i upgrade rom with out device being detected by active sync every time i run upgrade utility it just comes up with connection error
still no luck
hi
still no luck
do i need special drivres to detect device if its in bootloader ?
it dosent show any thing in device manager when i connect it while its in boot loader
on running upgrade utility it comes back with error 260 connection error saying cannot find device (i am stuck in bootloader)
any advices ??
please help !!!!
The fact that you can still enter the bootloader means that it is not bricked, so first advice would be, as is so well presented in the Hitchhicker's Guide to the Galaxy, "Don't Panic".
Enter bootloader without any SD Card or SIM left in the Athena.
Then, plug it to the USB port, and see if it goes from "serial" to "usb".
Then try to flash first the Black Dual PK ROM available on the forum (in the WM6 section), or an official ROM available from the Wiki, for instance.
hi
tried to flash it with both and came out with same error
260 connection cant find device
and i cant even see any changes in devicemanager but it dose goes serial to usb when i connect
and my pc is not detecting the device (just like that depressed robot from hich hikers guide to galaxy )
Do you have Windows XP or Vista ?
Ecraseur said:
Do you have Windows XP or Vista ?
Click to expand...
Click to collapse
xp (pc i am trying to upgrade i also have vista on other pc which i havent tried yet should i try that ?)
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
vijay5264 said:
nop no luck in vista ether same error still no connection
both pc have netframework 2
activesync in xp and mobiledevice center in vista
but after connecting device nothing happens in device manager there is no new device
(could it be beacouse of faulty cable? )\\(noi have tryed 2 different cable )
is it worth getting cradle ??
Click to expand...
Click to collapse
Hi
Try a hard reset ( Volume down+reset) and then get into the boot loader(Camera+reset~10seconds) then flash the PK dual rom. Don't panic, Your athena is hard spl patched therefore not bricked. If that not works down load the exact official rom for your device flash that then flash the PK dual rom. try Redownload the rom again.
Good luck
HeartOfDarkness said:
No no. I think the problem comes from the flash utility that requires that the Athena be detected prior to flashing.
I know that with the Universal, some flashing utilities could force flashing when connecting the device already in bootloader mode...
So there must be an easy way to bypass the device detection and go on with the flash process. I'll try and find out, and maybe one of the gurus will cruise by and find it for ya in the meantime.
In the meantime, don't freak out and be patient. Your Athena's not bricked, probably the ROM that's screwed up. We only need to find a way to do that exclusively from the bootloader (chich I know is possible, that's the whole point of the bootloader ).
Click to expand...
Click to collapse
hi
thankes i think u understood the problem it is utility which fails before even starting beacouse of no connection see if u can find any thing
and yes i tryed hard reset and then tryed to flash with project black rom and i have downloaded latest t mobile rom from oficeal website but as i said before it fails with connection error it starts up and box says ''verifying information on your pda fone please wait'' and minut later it comes up with error 260 connection error '' please check following
1 your pdafone is connected to usb cable /cradle
2 usb cable connected to pc
(wich is basicly same if you try to nrun upgrade with out connectind pda )
(and yes i have tryed it with 2 different cables and it dose change from serial to usb)
some ting intrestin i foun in orignal update utility faq
 ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
is possible because device is in bootloader ?
or am i doing some ting wrong?
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Pantaloonie said:
Reboot your PC, make sure you are not using a USB hub, try it with each USB port on the PC.
Click to expand...
Click to collapse
good idea but dident work after 4 on board ports and 2 hub ports no joy at all
by looks of it upgrade utility is trying to read info from my device and could be failing for 2 reasons
1 it is not detecting device
2 info in pda is corrupted and could not get any info from device
well thats my theory but not really sure any suggestions??
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
eaglesteve said:
Is your PC running XP or Vista? I got the impression reading the post that XP machine works better in unlocking. I think the info was posted by Olipro himself if my memory is right.
Click to expand...
Click to collapse
it is running xp the one i am working on now (i do have 2nd pc running vista 64 bit )
but i am doing unlocking in xp
all i want to find out is dose device needs any drivers or dose it gets detected if device is in bootloader ?
if thats the the case i dont see any new devices in xp devicemanager
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
HeartOfDarkness said:
No no, it doesn't. Couldn't find it for Athena, but don't have much time lately, alas.
Maybe you should PM one of the gurus asking how to flash a ROM straight from bootloader without having the device detected by WinXP. I believe there's a small, easy manipulation to make, but can't remember it for the life of me. :-S
Click to expand...
Click to collapse
i found this in wiki and first three posts are empty but followed the procedure and downloaded all three roms and still no joy error
''Problems using the Athena Unlocker - the Black Screen of Death
Using The Athena Unlocker tool (developed by Olipro) is a 3-stage process. Most users get through the first stage but as they start stage 2, get a black screen where their device becomes unresponsive and so cannot proceed with the unlocking. See these posts
http://forum.xda-developers.com/show...&postcount=169 or http://forum.xda-developers.com/show...&postcount=176 or http://forum.xda-developers.com/show...&postcount=226
It is always recommended that you first take out your MiniSD card. You can then follow the instructions below.
* Get one of the ROMs in this link and extract it http://forum.xda-developers.com/showthread.php?t=314672
* Get your device into bootloader (the three-colour screen; You can get there by pressing the Camera key + Volume key + Soft Reset at the same time)
* Connect your device to your PC (even if the PC shows no sign of recognising it, it does) and the SERIAL shown on the screen of your device will change to USB)
* Hit the ROM Upgrade Utility and upgrade your device.
* Once the upgrade is completed, configure your device (Calibrate screen, set time zone, etc).
* Now continue with the Unlocker, to the end.
It is important to complete the unlocker to the end or else you will miss out on flashing your radio, with a common symptom of your gps not working.
Good Luck and enjoy your improved device!
''
now i am still stuck will it make any difference if i try it in different xp pc other then the one i started the process ?(and screwed it up)
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
lpsi2000 said:
Please ensure all software firewall or IP filtering apps are turned off then reboot the PC. After rebooting, confirm the apps are not running and blocking anything. If you are unsure, then try it from a freshly installed XP.
Put the device in Bootloader mode and try it again.
Click to expand...
Click to collapse
good idea
i have already tryed with firewalls and virus protection off but doing it in fresh xp might just work small question do i need to install active sync or is it not needed (any way ill try both first without and then with )
ill report back in about 3 hours (i know i am sad and havent got a life but its worth a try )
Yes, the wiki confirms what I thought but didn't voice out loud as yet (I was sure about it for the Universal, but not for the Athena): the upgrade utility doesn't *require* that it be Activesynced. That's, as I'd said, te whole point of the bootloader.
If you still have problems uploading the new ROM to your Athena after following the wiki thing, then it *does* mean that there is some external factor playing dirty, so the firewall to check (and some anti-virus software also scan network connections) indeed is a good idea.
Keep us posted, and I'm keeping my fingers crossed.

[Q] Rezound problem with Unlocking and rooting

I have a problem with using HTC dev.
After pressing Fast boot and plugging it into my computer and my computer (windows 7) makes an error sound. I thought nothing of it and continued, when it came to the time when i had to get the identifier token, it didn't show.
Instead it said "Waiting for Device".
I googled it and i found a page, I uninstalled HTC sync and it still came with the same result.
Might there be something wrong with my drivers? If so how can i fix it?
Please help me , i wanna get back into rooting after leaving the iP4.
Thanks
Did you have HTC Sync enabled while you had the phone connected to your computer? If so, it should have been disabled.
Have you made sure you have the necessary drivers installed?, I had the same problem I think and this was my problem (I think), also did you restart your computer after uninstalling HTC Sync? Cause (I think ) it has to be disabled for the DEV unlock to work.
I had the exact same problem when trying to unlock the bootloader on my Rezound, I tried everything that was mentioned above and had no luck. But the second I used my friend's computer to do it all, it worked perfectly fine. I don't know why but for some reason my computer just would not recognize the device in fastboot no matter what I did. Hope this helps.
While the drive is connected, get to the devices screen.
You should see an Android section.
Right click on the device listed under Android. Click uninstall.
Unplug the device and wait for the device list to update. The Android section should disappear.
Now plug in the device again, and it should load the device driver again.
Give it a sit.shot after that.

HTC Sensation XL Fastboot USB Not Detected

Hi guys. I am new here. Any help will be appreciated.
So i have dead HTC Sensation XL. It has an unlocked bootloader but with an S-On. So i cannot install any custom OS in it. For S-off, i have read it that i need to update my hboot version. Current hboot version is 1.25.0005. Hboot is only upgraded through fastboot command line tool as i know. But the problem is that my pc is not detecting my dead android in fastboot mode. I tried 2 different pc's. First one is loaded with Windows 7 (x64) l. The other is laptop - Windows 8.1 (x86). I have also installed HTC Drivers,HTC Sync and minimal fastboot (8 mb). HTC Sync is not running in background because it conflicts with ADB. I also tried too different cables. One is of samsung, the other is of HTC Sensation XL. But no gain. My HTC is giving red light durjng charging means thr cables are right for it. It is stuck on HTC Logo. I also connected HTC Explorer with those cables and it has been detected in fastboog mode. My HTC Sensation XL is also not appearing in Device Manager under ADB Composite Device. Don't know what is the issue. I have utilized 7 hours on it but no gain. Please help me soon. Thanks alot to all XDA members and XDA Community for creating the forum. If my posting is not in the right section please move it and let me know. Waiting for reply. Help me please.
syedbilal093 said:
Hi guys. I am new here. Any help will be appreciated.
So i have dead HTC Sensation XL. It has an unlocked bootloader but with an S-On. So i cannot install any custom OS in it. For S-off, i have read it that i need to update my hboot version. Current hboot version is 1.25.001. Hboot is only upgraded through fastboot command line tool as i know. But the problem is that my pc is not detecting my dead android in fastboot mode. I tried 2 different pc's. First one is loaded with Windows 7 (x64) l. The other is laptop - Windows 8.1 (x86). I have also installed HTC Drivers,HTC Sync and minimal fastboot (8 mb). HTC Sync is not running in background because it conflicts with ADB. I also tried too different cables. One is of samsung, the other is of HTC Sensation XL. But no gain. My HTC is giving red light durjng charging means thr cables are right for it. It is stuck on HTC Logo. I also connected HTC Explorer with those cables and it has been detected in fastboog mode. My HTC Sensation XL is also not appearing in Device Manager under ADB Composite Device. Don't know what is the issue. I have utilized 7 hours on it but no gain. Please help me soon. Thanks alot to all XDA members and XDA Community for creating the forum. If my posting is not in the right section please move it and let me know. Waiting for reply. Help me please.
Click to expand...
Click to collapse
You said you're stuck on the HTC screen... Does this mean that you can't get into the bootloader mode via Volume Down and Power? Is it the white or black HTC screen? And for future reference, you can install another OS if you are S-On (providing you get fastboot connected).
Sir i can get into bootloader menu via volume down + power key but my OS is not booting. Yes you are right that i can install a custom OS but my fastboot usb mode is not detected. What should i do to make it work.!
Attached is the image of Sensation XL for reference. It is dead. Only able to boot into bootloader, fastboot and CMW recovery. One last thing, in CMW recovery, when i "Mount USB Storage" under "Advanced" section. My device neither appear in my PC nor in Device Manager.
Anyone ? I need help guys.
syedbilal093 said:
Anyone ? I need help guys.
Click to expand...
Click to collapse
You gotta hit the power button to select Fastboot. Then it should change to red highlighted with the words Fastboot USB and then the PC should recognize and load the correct drivers for fastboot, if available..
I hit the power button to get into fastboot but no fastboot usb option.
And have you checked the Device Manager for driver errors? If it is not displaying at all on any PC, with any cable, on any port, then it's quite possible the phone's USB port is damaged. And yes, it can be damaged and still charge as the charge pins and pins for connection of this type are usually different or have multiple parts. I never have luck with these kinds of HTCs on Win 8.1, despite knowing about every trick in the book for loading drivers for phones. It only works in Win 7 for me. It is recommended to only use 2.0 ports, though I never have luck with either on 8+.
Thanks alot sir. You are right that my charging port is maybe damaged. Will figure it out tomorrow. It is not appearing in Device Manager as you described. Yeah Windows 8.1 is not made for us it does not detect device. I also used windows 8 but my pain still lasts. I am using 2.0 ports not 3.0 but i am now sure that my usb port is damaged. Will repair it soon & if the problem persists, i will contact you soon. Thanks alot for your amazing response. Expert!:thumbup:
Charging Pins & Connecting Pins Difference.?.
I want to ask one thing sir. I am confused. Don't know about hardware much. So, i want to ask that how are the pins different, like you said charging pins and other sort of pins. I mean, i can charge from the same port and it shows that charging port is somewhat OK. But when connecting to a pc, same pins are communicating with my pc, so thay should have worked on pc. But they didn't. I haven't explained fine but i hope that you will understand what i want to ask.
syedbilal093 said:
I want to ask one thing sir. I am confused. Don't know about hardware much. So, i want to ask that how are the pins different, like you said charging pins and other sort of pins. I mean, i can charge from the same port and it shows that charging port is somewhat OK. But when connecting to a pc, same pins are communicating with my pc, so thay should have worked on pc. But they didn't. I haven't explained fine but i hope that you will understand what i want to ask.
Click to expand...
Click to collapse
Some pins are strictly for charging while others handle data transfer. So that's how it can charge, yet not connect.
Thank You Very Much Sir. I will get them repaired soon.
Hey man. I have repaired my charging port because my Sensation XL wasn't charging. I got them repaired. Charging's fine but still not detected in my pc. Tried another pc but no result. I still think that i have to repair those connecting pins because it wont show in my Device Manager. What are they named? Are they are Connecting pins or some other name. Don't have an idea about hardware. What should i say to the repairer? please help.
syedbilal093 said:
Hey man. I have repaired my charging port because my Sensation XL wasn't charging. I got them repaired. Charging's fine but still not detected in my pc. Tried another pc but no result. I still think that i have to repair those connecting pins because it wont show in my Device Manager. What are they named? Are they are Connecting pins or some other name. Don't have an idea about hardware. What should i say to the repairer? please help.
Click to expand...
Click to collapse
If they replaced the charging port and it's still not working, I really don't know what to tell you...Sorry. I've never had or worked on a phone with a good working USB port with a good cable not at least try to load some kind of driver, even if it isn't the right one.
Ok i will try to do the best. Anyways, thanks for the support #esotericchaos
Solved the problem #esotericchaos. My connecting pins connection to the main board was missing. So the person to whom i gave it, put back the prints of connecting pins and then the reading in Ohm meter was great, fine enough. Now i will flash a rom soon. Thanks man. Thanks alot for the help.
I KNEW something was wrong with the USB port. I was feeling kind of bad that you might have spent money on a repair that wasn't needed! Glad all is well though! :victory:
Yeah but still dead. . Will fix it soon.
syedbilal093 said:
Yeah but still dead. . Will fix it soon.
Click to expand...
Click to collapse
I must've misunderstood... What's wrong with it now?
The software is gone. Will flash a stock RUU to it after making it S-off.

[Q] Stuck on fastboot not recognizing my device

hello.
i think i have already tried everything to get fastboot on my pc find my device, but no luck.
I've got an old laptop with usb 2.0 + windows 8.1 x64 Pro and the same OS on my PC with usb 3.0 (according to some of threads, my CPU is i7 4770k and my MOBO is MSI Z87-G45).
I use my HTC Desire X every day and it is simply slow. I cannot try every ROM cause of need to flash boot.img. And i Dont have any idea how to get the fastboot recognize my device....
Maybe someone have some time to help mi wlak through this 'issue' idiot friendly? I'm really confused and i dont have any idea what to do.
my hboot is 1.25.** JB. S-ON. I have installed TWRP recovery.
:crying: halp
EDIT:
SOLVED. Windows 7 FTW.
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Will_Xda said:
Also had this issue, quite frustrating as no drivers seemed to work for me, got if fixed now though (no need to go back down to win7)
Click to expand...
Click to collapse
So,what did you do ?:d
evnee said:
So,what did you do ?:d
Click to expand...
Click to collapse
Installed a HTC sync like program named PDAnet, and updated the drivers from that program, once in fastboot mode device is recognized in pdanet and in a command prompt (adb). this only worked on a usb2.0 port though.
(didn't bother replacing usb3.0 drivers as suggested elsewhere as this has caused big issues for me before.)

Categories

Resources