Related
Ok this is the situation:
yesterday my phone started malfunctioning, my screen was flickering going to white then back to color, when i turned it off using the power button it dies and needs a reset to turn back on. i contacted imate and they said to reinstall the ROM i started to do so but it kinda got stuck and said there was a different language rom (even though it was what i put on it a month ago) anyway i disconnected it and now i am stuck with the bootloader screen (says serial v2.06 and when i connect it to the hub it changes to USB v2.06) i canceled the active syncs usb connection but when i tried to reinstall the rom it just gets stuck and gives me an error 201 cant get data from device, also when this happens the device gets stuck on USB even if i take it off the hub (it is supposed to change back to serial) and if i dont reset it windows says the device malfunctioned and doesnt communicate with it. Please help
Try using the usb lead direct to the usb port, sometimes the hub will make it fail.
I cant cause this imate just came with the hub and it specifically states that it has to be connected to the hub AND the hub has to be connected to the power supply
please help
it is fixable
hi my friend, i had the same problem with my t mobile mda 3. it is fixable . the problem simly is that your rom is erased and you need to get another one by upgrading it. that's all and i recommend using cradle if you have one. i upgraded mine to 1.40 i mate rom.
tell me if you need more help,
next time back up your phone beforehand
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,
I've tried to upgrading with 9000_WWE_20202_20307_11500.exe found in this forum, but the notebook power off (bad economic mode also with the AC plugged) at the ExtRam update on 1%, just after the Radio.
But when I tried to re-run the program nothing change, just the bootloader v1.01.
Now the program recognize that there are nothing installed and ask to install all new Roms but after the second screen the utility tell me everytime: "ERROR 114 RADIO ROM UPDATE ERROR"
Somebody can help me?
Since the OS ROM is updated in the last step(to be precise, Step 3), you can easily take your device out of this bootloader mode.
1)open MS activesync on your desktop
2)go to connection settings and disable 'incoming USB connections"
3)run the exe(see the attachment)
your device should be out of bootloader mode.
PS: you can re-run the ROM upgrade again after your device gets back to life
Now my Universal is completly OFF
Hi, thanks a lot for your attention, I trye to follow your instructions but now after the Exit of bootloader, I can't update my Universal.
After read dozens of messages... I try to explain better my situation:
1) the first update was blocked by the power off in my notebook in the beginning on the ExtendedRam (1%)
2) after this I tryed to re-run the update program and this recognize NO ROM on my UNiversal and asking for replace with all new ROM, but a "error 114: Radio Rom update" don't let make the update. (that repeated many time and every time I tryed to reset, cold reset, warm reset... following all the messages that explained many different way to de-block the situation)
3) Now the screen is absolutly black and the PC say me taht the "USB Device Not Recognized"
Can you help-me?
Thanks for all...
I've search and now I've found the way
Thanks for your help, I have come back at bootloader mode and I can put in the wm6 version !
Bye
hi,
I've trie to update my qtek and during the update I've got an error.
And now I'm blocked on the boot loader mode...
I've tried the joined program, I disabled the USB connection,
and the program can't connect to USB...
I don't what can I do.
please help me...
seranares said:
hi,
I've trie to update my qtek and during the update I've got an error.
And now I'm blocked on the boot loader mode...
I've tried the joined program, I disabled the USB connection,
and the program can't connect to USB...
I don't what can I do.
please help me...
Click to expand...
Click to collapse
It's ok, after a reboot of my pda & PC, I can exit the bootloader.
Thks for this program
Hi, I have reflashed my ROM I dont know how many times. Yesterday I tried to connect via activesync on a new ROM and it wouldnt connect. These are some of the things that happened:
Device orange charging light flashes a few times then goes off [never seen THAT before]
Activesyc menu comes up on device but activesync doesnt connect
Get 'this device can perform faster' message on desktop
Sometimes get USB devce not recognized on desktop
SOmetimes device orange charging light it stays on if I plug direct into PC but still doesnt activesync
I have tried to connect as DISK DRIVE but I dont see the device on my PC.
Have tried different ROMS, 6.5, 6.51, sense 2.1 and 2.5 but all have same issue. Have also tried connecting to other computers. same issue.
Have played around with USB to PC menu options (enable / diable faster data sync etc) but doesnt make a difference.
Anyone had this problems? Thoughts?
Have you tried diselecting "ask me 1st about usb connection type when I connect the device to the pc" under USB to PC settings
It worked for me
This is the exact problem I am facing!
I tried everything - as diskdrive, activesync (with/without speedup), etc.
On many ROMs, even the original one (WM6.1)
Can't connect - every PC gives an 'unknown device' and on some ROMs I cannot charge via USB, only via mains...
I also tried without the question on connection.
Just some thoughts:
Do you have corruptions on screen sometimes? (Some graphical glitches)
Any .CAB files you cannot install?
Did you try to reflash the same ROM more than once?
tried to connect without card in the device and in flight mode? (Uses less power)
With me it started after a ROM flash from Miri... (I don't blame him!!)
The Hard SPL did not give me any problem, the radio was not flashed, just the OS. But reverting did not help.
I certainly hope you will find a solution, since I have the exact same problem!!
Do you stil know what ROM you flashed when this problem occured?
I reverted to original ROM 6.1 AND 6.5 which included everything - boot, radio, os, stardup image. But it did not change!
I figured it out after trying everything i could: i think its a hardware problem. I have dropped my devicetoo many times, or plugged it in too many times. Who knows.
ekerbuddyeker said:
I figured it out after trying everything i could: i think its a hardware problem. I have dropped my devicetoo many times, or plugged it in too many times. Who knows.
Click to expand...
Click to collapse
And how did you figured it out? Did you return the device to the shop?
I have this exact same issue except I am on AthineOS... I thought it was my PC until I read these posts. No OS updates or any other machine updates were performed except on my device. Any clues as to a fix?
Somehow I don't think this is just hardware.
I did drop my device once, but that was even before first flash. After that it still worked.
So, some weeks later I HSPLed without any problem. After that the device still worked.
Then, after investigating which ROM to use I flashed the ROM a few days later.
Right after the first flash it all still worked. So, had to flash another and from that moment on the device cannot be reckognised by any PC.
I still think it has something to do with the flashing. I think the device does not give correct feedback when it receives some commands from PC (eg. the command to reply the device type/number)
Does anyone know a program which can check the USB port for the HTC Touch Pro 2? Just to test wheather the connector pins are ok?
download activesync 4.5 and run the setup. it will perform a repair. that usually solves the problem. if not, try a different usb cable and try plugging into different ports on your pc.
crazythunder said:
download activesync 4.5 and run the setup. it will perform a repair. that usually solves the problem. if not, try a different usb cable and try plugging into different ports on your pc.
Click to expand...
Click to collapse
These are the first things done. And this was already written in here.
It happens with many PCs, including some on which the device never connected to.
Also tried different cables, ports, etc.
Also disabled the fast transfer etc. etc.
Even tried several other ROMs, inclusding original Dutch 6.1 and Dutch 6.5
I'm having the same issue. I can connect via bluetooth, but not usb. And I'm stuck with 6.1. I was tole my phone was brand new, but now I'm starting to think otherwise.
waynehead05 said:
I'm having the same issue. I can connect via bluetooth, but not usb. And I'm stuck with 6.1. I was tole my phone was brand new, but now I'm starting to think otherwise.
Click to expand...
Click to collapse
Some questions, to verify this is due to flashing or is a fault in the design of the device...
- Where did you get the device?
- Have you flashed the device?
- Did you accidentally drop the device?
hi just to say had a completely orignal o2 xda orbit 1 flashed with new rom everything worked perfect before now active sync plays up i can sometimes connect but get usb device not reconigsed then click cross then pull out usb then reinsert then active sync connects works fully functional then after 5 min it disconects this is driving me mad as use active sync for a fast internet connection on my pda as my wifi is crap