Hi all,
I have this particularily annoying problem that effects my ability to upgrade the rom files on my universal sometimes.
When I put my device into boot mode I don't see USB v1 or even Serial v1, what I get is Serial v2.01
Sometimes when I then connect the USB cable into the universal this changes to USB v2.01 and windows recognises the device and I can perform the rom upgrade. Most of the time however, it stays at Serial v2.01 and windows complains about 'USB Device Not Unrecognized'.
I have tried 2 different USB cables with the same outcome.
Normally after trying s few dozen times I eventually get windows to recognise the universal and perform the upgrade but I have been stuck like this for 3 days now and am getting close to my breaking point which will could shortly result in a broken universal.
Please help.
i cant quite remember the ins and outs but i have faced this problem as well
firstly ensure your connected directly to the computer and not via a hub,
try to do the upgrade if/when you get the message remove the device from the cable and do a soft reset
try the upgrade again and it should be successful this time .
i have had lots of trouble myself with this and i have found a soft reset always gets me there in the end.
goodluck !
I have just retried the upgrade and the display keep changing from USB to Serial about every 10 seconds.
I also noticed that the mouse kept freezing on the screen for a few seconds whilst this was happening. I tried using my other USB cable and the same thing was happening.
Does anyone else have v2.01 displayed on their screen like me?
Update: I stupidly ran Ivan's AKU3.2 upgrade utility whilst the universal was activesynced to my desktop (not in bootloader mode) and now this has executed the EnterBL.exe program which traps you in the booloader unless you upgrade a rom (or use mtty to issue the correct command to escape).
Unfortunately I can't excape via either of these methods as I still can't obtain a USB connection.
I have even tried a different PC but am still stuck.
Maybe both of my USB cables are knackered, so I will obtain another one and try that. If that fails it looks like Orange will be recieving a little parcel from me...
I have now also tried a 3rd USB cable with the same result.
I have a similar problem, I'm stuck in bootloader mode.
I have version 0.60 and if I put a USB in it keeps on saying serial and my computer says he doesn't recognise the device.
I've tried it on 2 different computers as on my new one apparantely all my usb ports are part of a hub. (they come up as all, inluding the ones in my moniter, being part of an usb root hub) But no succes on my other computer either.
I'm thinking that my only option is to do it via a memory card? Can anyone tell me how I'd go about that as I have no clue :shock:
Thanks!
Tim
Success!
I have been plugging in and unplugging my phone all day (with it still stuck in boot mode) and eventually it was recongised by my PC - I then upgraded the radio stack & ce rom and I am up and running again (I know that I could have used buzz's utility but I wanted to upgrade anyway).
The only thing that I did slightly differently this time was that I actually removed the battery from the univeral for a while and then plugged it back in before trying the USB connection. I did try this once of twice before without success though so can't really draw any conclusions apart from I don't know what is going on.
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Try this it shld work
hdubli said:
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
Click to expand...
Click to collapse
Guru Meditation said:
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Just noticed your user name, I was a big Amiga fan a few years back, still fire up Amiga forever occasionally on my PC when I feel the need.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Click to expand...
Click to collapse
Try it with a different USB cable or in a different USB port (don't go through a hub and if you've been using a laptop then try it on a desktop PC since some laptops have hubs built into them). If that doesn't work then you're out of luck as your Universal isn't detecting that you've connected to your PC and its time to send it in for repair.
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
i am stuck on the same problem and wondering the forum for almost 3 days now with no luck.... please help my device is in boot loader mood but not turning the serial to USB ......... please HELP.......
solution
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Please follow the steps:
1. Plug in ur usb cable in bootloader mode while it is showing 'serial' and version 'x.xx'.
2. Soft reset by pressing Backlight+power+reset pin WHILE KEEPING THE USB CABLE CONNECTED
3. your phone will now reboot into 'usb' mode. Don't remove the usb cable yet.
4. Remove the Memory card while keeping the usb cable still connected and VOILA,your pc starts recognising your phone as Microsoft usb sync.
5. Do whatever you want to do now (upgrade)
Hope it solves the problem now.
Press thanks if it does.
Something else to try
Having had a few issues with my G3 Uni, I've been through my fare share of Uni bootloader issues. When I find that I can't get the 'serial' to go to 'USB', I normally find it's because I haven't taken the memory card or the SIM card out (usually the memory card).
Make sure your memory card is out, then try to enter the bootloader and see if this cures it. If it does, then use mtty and the command 'set 14 0'
This tells it to reboot on reset. if you were to use 'set 14 1' it would go back to the bootloader on reset.
my Htc hd2 t-mobile won't recognize usb on boot-loader mode
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
kaleb2954 said:
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
Click to expand...
Click to collapse
you have the wrong forum friends! This Htc Universal section
to update Android on HTC HD2, you can use the Clock Work Mod Recovery !! for more details should refer to this thread http://forum.xda-developers.com/showthread.php?t=1021837
I-MATE JASJAR hung
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
bechir2013 said:
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
the first point...
A lot easier than to root this device
Hi guys, sorry for my bad english.
Since today can't sinchronize my ppc with wm 5.0.
Here's the problem: when I pug it with usb cable, nothing happens.The orange light is on, the phone is in charge but nothing happens.Usually when I connect the phone I can see windows looking for ip address, and the activesynch shows... but this is not going to happening anymore.
I tried to reistall activesinch, I've cleaned the registry and i tried to connect it with others software.Still nothing.
Firewall is disabled.Any solutions?
Thank you in advance.
Zealot87 said:
Here's the problem: when I pug it with usb cable, nothing happens.The orange light is on, the phone is in charge but nothing happens.Usually when I connect the phone I can see windows looking for ip address, and the activesynch shows... but this is not going to happening anymore.
Click to expand...
Click to collapse
I had the same problem sometime ago. I've changed the wire first but nothing happened. My speaker, my Mic was dead and I could switch on FMRadio without the Hands-free!!!
What I did...??? I updated my mobile's Radio with 3.39.90 Version. How can you do this without active sync???
1. Remove SIM Card and Storage Card from the Mobile.
2. Press and Hold the Right Button (Recording Button) and Press together the Power Button. You will be in the Bootloader Screen. Try to update the Radio first.
3. Check it if it's working ok.
2nd way...
1. Copy the official ROM of WindowsMobile to the Storage Card.
2. Press Right Button (you know the Voice Rec) and holding that press the Power Button...
the mobile will be bootloader mode and will try to install the official ROM from the Storage Card...
wait a bit and then when it finish, check it if it is working properly!
Hope to help... waiting to "hear" sorry, to read good news
I have the same problem i cant sincronize the pda whith the activesync and i wish to change the rom. Now it's in france and i wish to change it to english, and it's locked to orange france i think. What can i make? It starts in bootloader, but the instalation from the card is not starting. thankx
le. and if i want to install something gives error 260
I had the same problem 1 month back, checked the mini usb data cable with a multimeter just to find that one of the data TX/RX wire was short with +5v wire, cable was faulty. the 1st and the last wires (+5v , -5v) were ok thats why it was charging the phone, but not connecting to pc, it was giving error unrecognised usb device.
u can also check for bent contacts at the USB mini connector on ur phone.
strange
hy guys
i´ve got a strange problem with my arte110.
for some reason i cant establish an activesync-connection,a few days ago i had some wm6.5 rom running and couldnt connect my device, then suddenly today (maybe because i reinstalled windows on my computer yesterday, i dont know) i was able to connect the phone while in bootloader... so i flashed happy and lucky the original wm (os 5.2.1620 build 18125.0.4.2) rom i got from t-mobile austria.
now its the same problem as before, i cant connect my device, i've restartet artemis and my computer several times, i've reinstalled activesync 4.5 a million times, i've tried all available usb-ports- different usb cables (same cable works with external harddrives) and even my office-computer, and so on...
my pda is (and was allways) charging but i cant syncronize.
has anyone any idea what could cause this problem?- please don't tell me the usb port of the pda is damaged, I wouldn't want to have to fix anything in this case...
hoping for good news, McPerfuntory
[by the way, please dont judge me for spelling mistakes, i'm from austria!!!]
done
okay guys, no need to respond anymore, i got it right..
but i don't really know how i repaired that one, i disassembled the devive cleaned everthing in there and cleaned the usb connector..
..works again
EDIT:
Most part of that problem solved, I bought new USB socket with ribbon, and replaced it. It worked. it seems there was a cold solder near the socket. USB works now with other devices like Flash drive, mouse, etc..
Still there's a little problem - while connected to a PC, neither phone nor PC show any signs of connection.
Anyone met the same problem? I checked on to computers Win8.1 and Win7 - no response.
I tried to install some additional drivers but with no luck...
------------------------------------------------------------------------------------------------------------------
< Old >
I've got Huawei P6 and used it with a few ROMs, after flashing one I noticed android doesn't detect USB connection anymore.
It sees it as regular charger - no popup on notofication bar, no way to exchange data with PC.
Changing ROM doesn't solve the problem. I tried stock ones with no effect (installed from zip file in TWRP).
I searched over the web and found no similar case. I think rolling back to full stock could possibly help, but I'm not sure how to do it - will creating dload folder with install data be enough? does it contain all the kernels, recovery and so on - to have the software version exacly as from factory?
USB OTG doesn't seen to work now either, It all worked before. Is there a way to force-detect the connection?
Please, don't write me to check the cable or drivers or to clean the USB plug. Each double... tripple checked. Tried different cables, computers. I've no problem connecting other phones.
I'll be very greatful for help in solving this issue. Even copying a photo to a pc is a problem now...
thanks in advance
I have an issue with my MTCB-KLD6 RK3188 800x480 headunit where I can not get any phone to be detected, or do anything other than charge when plugged into a USB port of the headunit.
A USB flash drive has no issue mounting and being accessible on any of the USB ports on the headunit.
Using Easyconnected, the app will not progress past step 1 (connect your mobile). Step 1 times out and tells me to enable USB debugging.
I have tried the following:
- Different roms (DSA and Malaysk 4.4 and 5.1)
- Different MCU versions (KLD6 v2.85, v2.86 and v2.97)
- Different phones with different Android versions (rooted and non-rooted)
- Different USB ports on the headunit (front usb and two rear usb)
- Different micro USB cable
- Different Easyconnected versions (three different ones)
I am at a loss for what to try next.
I am considering attempting to flash an alternative MTC image as I am not entirely sure if I accidentally flashed a KLD6 MCU as part of flashing a custom rom ages ago when I first got the unit. Could this be the issue? Is there anyway of verifying the make outside of the version information in the software?
FYI, the unit looks identical to this image:
https://img.xda-cdn.com/HO6e7mFsPo5pdB5KZz39NyVkCHc=/https%3A%2F%2Flh3.googleusercontent.com%2FpqI4HxuqV5qoWcGXi6yIa8orHxcsbVYcR5RkYagHZVo%3Dw840-h480-no
Any feedback is appreciated.
EDIT: Turns out the shorter USB cable did not solve the issue. I have not been able to reconnect after the one successful attempt. Interestingly though whilst connected to the headunit, the phone sometimes pops up stating that the phone is unable to transfer data to the connect device and to try reconnecting the USB cable [or something to that effect]. Unpluging and replugging, rebooting both the headunit and the phone, toggling usb debugging, none appears to work. Again tried with other mircoUSB cables that I know work, and no luck.
Any ideas?
After a review of more topics in regards to general USB connection issues, I attempted to use a very short micro USB cable I had from a USB charger.
The shorter USB cable seems to have solved the issue. I am unsure why this is the case. But if someone else has this issue, try to use the smallest cable you can find.