Related
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 tried to upgrade my rom but the process crashed. The utility mtty doesn't work because when I connect the universal, boatloader mode by the cable, to the pc, it says "USB not recognized" (sometimes when I connect the computer is frozen till I disconnect the cable of the universal)
Please, I tried to have some solutions in the forum but all the posts indicates is needed previously the usb connection.
Do you know if should be possible to run the flash of the rom in other way, for example using a serial cable connected into the miniusb of the universal, because the boatloader screen says "Serie, v.1.01"
I apprecite what you can say please, I'm really in a hole.
Try this...
Try taking out the battery for a few minutes (10-30mins) and reboot your PC then repeat upgrade process. Hope that helps. Good luck!!!
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...
sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...
Click to expand...
Click to collapse
In my case it still happening in other computers. Conclussion: some piece of the software in the universal has been lost. The screen shows "Serial" that means on some way that is opened to comunication but not USB.
My questions are:
- should be possible to put some starting software in SD and do the universal boot on it.
- do you know how to connect to the computer COM! port from the usb miniport of the Universal.
I appreciate, I was not planning to replace now the Universal...
beginner said:
sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
Now works.... I still thinking windows is so stupid software made for distroy our mind ....
Solved after install drivers for a converter usb -rs232 ( I was looking for the way to connect from rs232 the universal)
I'm happy again and I promise don't try to change rom again (at least for a while)
If some person is interested in what brand of software/hardware I installed, send me a mail...
Thanks hearing me ...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD
zedino said:
i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD
Click to expand...
Click to collapse
I want to say that is running after doing some things and obviously some of it solved my problems. I made:
- unistall last version of activesync and go back to version 4.0
- delete all the applications using ports usb.
due the connection still not running (windows message: device not recognized) and because in the screen of universal I saw: "COMM1" I tried to connect from computer port rs232. By that I purchased some special cable, name: hama brand, rs232 serial, 9 pin - usb.
As you can imagine all the steps I followed were followed by the typical restart of windows. In this sense is important to say that the universal, after connect, need to do a soft reset each time (again windows....)
Other comment is that I unmark the option to connect by usb in activesync and mark the connection by com1.
and after all was done, connecting by usb the unniversal, kill wcescomm, windows said "NEw usb device, sync device". I started mtty and now appears the USB option, great! same time the screen in universal changed from comm1 to usb, more great....
and that's all.
does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port
zedino said:
does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port
Click to expand...
Click to collapse
I think my english wording was not fine. I mean I solved my problem after install the sofware -drivers- of the rs232 connector, but connecting to the universal by usb as on standard way I was syncronizing previous the crack with activesync.
OK, where to get this driver?
thanx
?????????? NOTHING ?????????????
zedino said:
OK, where to get this driver?
thanx
Click to expand...
Click to collapse
Try here.
http://www.hama.de/portal/type*3/action*1026/searchMode*1/q*039703
I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.
shrubbery said:
I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.
Click to expand...
Click to collapse
not works, probably is this device lost forever, i have restarted device and PC almost hundred times, still the same result, uni stuck in Bootloader screen top of page "Serial" bottom of page "v1.00"
nothing changed, even if i connect to USB port
if someone have some solution to this s*it pls let me know
thanx
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
no, my problem persist, hundred times i tried to recover friends device using upgrade by original shipped ROM but the device is not recognized by system so there is allways connection error, so this kind of reliving this UNI is not usable
anyway, thanx for raply and suggestion
ZeD
mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
If you're stuck in bootloader mode only, visit www.buzzdev.netand look for ExitBootloader utility written by the great Buzz. Just follow his instructions or scroll thru' Universal's forum here and there for problems relating to "stuck in bootloader"
hope this helps
no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD
i had the same problem with the QTEK of my principal after I upgraded his ROMs.
(after the hard reset, the pocket remained in bootloader mode).
you can solve this problem in a very simple way:
you have to launch the bootloader installation (BL1.01_RUU_UNI_V.1.2.EXE) from the PC (still connected with the PPC through USB) while the PPC is in bootloader mode (on your display you see "USB > Serial 1.01" or something like that).
then you do a SOFT reset and the pocket boot normally.
very simple.
i hope to be helpful to someone.
zedino said:
no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD
Click to expand...
Click to collapse
I had some problem. After uninstall all usb applications in the pc and install the software for cable usb -rs 232, doing some softreset in the pda connected, it turned the screen message "Com" by "Usb"
Hi Guys
This is my first post so i will also say hello.
I have the Vodafone v1640 and have been trying to upgrade my device with a new rom, ive been trying to follow the guides but without much luck.
If i understand correctly the MaUpgradeUt_noID.exe will force the device to accept other generic roms (am i correct?)
So i run the MaUpgradeUt_noID do everything it says, then try to update the rom using the UNI_AKU3_2_WWE_IVAN_beta14 and all i get is a error 120 saying this is not the correct rom for your device.
I have also tryed to use the o2xda version but i get the same error.
If anyone could point a newbie in the right direction that would be cool.
Thanks Kev
Sorry, I can`t help you.
But i have a similiar problem.
I try to flash the newest aku 3.2 but it stucks on "Checking the information on your device... Please wait..."
Maybe it is a problem with the usb cable?
(In the past I used another one but the usb "port" of it is broken ;-) )
Syncronisation works fine.
Maybe someone could help us
I failed when flashing my Uni for the first 4 attempts with the same error:
"Checking the information on your device... Please wait..."
This happened when I was flashing using my Dell laptop equiped with USB 2.0 port. When I did it again using my old machine with USB 1 port, everything went through smoothly without any problem. Around 20 min or so, its completed without any single glitch.
May be you encounter the same issue.
lie_ui said:
I failed when flashing my Uni for the first 4 attempts with the same error:
"Checking the information on your device... Please wait..."
This happened when I was flashing using my Dell laptop equiped with USB 2.0 port. When I did it again using my old machine with USB 1 port, everything went through smoothly without any problem. Around 20 min or so, its completed without any single glitch.
May be you encounter the same issue.
Click to expand...
Click to collapse
I'm wondering if this might be a case of "USB Hub" issues.
As I understand it many Dell Laptops have a mix of "true USB Ports" and an integrated "USB Hub". IF I am correct, the 4 USB 2.0 ports on the back of my Dell E1705 are the "Hub" whilst the 2 USB Ports on the left side are "True USB 2.0 Ports".
I know from experience that sometimes USB Hubs are problematic for PPCs.
Quick one for everyone,
If you're following instructions for flashboot and adb etc, and you're experiencing USB errors, or just FAILURES..... i've found that there's 2 problems i've come across which quickly resolves things:
1. You are plugged into a USB3 port - for some reason, my usb3 port gives me errors, and not my usb2, try switching different ports
2. You are using a faulty cable - i bought a longer microusb cable from ebay, and it worked fine for a while, then things started to go funny, copying and accessing the phone took a long time etc, and of course flashing didn't work... then realised the cable was stuffed, and went back to my short htc oem cable, and all is good
From a guy who finally worked out how to upgrade from ICS to JB, have fun all!
I suppose that its "fastboot"?
Anyway, have fun with jellybean
haha yes my bad, fastboot, not flashboot.
Also, one more advice that I can give that took me ages is... when flashing RUU... if you're getting battery less than 30% error (even when i was at 99%), or usb connection error.... i overcame both of these by booting the phone into fastboot mode. None of the guides out there say you have to do this...
OK. I am beyond frustrated and I'm about to just give up all together. I followed these directions to root my HTC EVO 4g HBOOT-2.18.0001http://forum.xda-developers.com/showthread.php?p=22013438&nocache=1 I followed the directions at http://www.htcdev.com to a T. And STILL my device is not recognized. When I plug my phone into my laptop it gives me this message "USB device not recognized. The last USB device you connected to this computer malfunctioned, and windows does not recognize it. Recommendation Try reconnection the device. If windows still does not recognize it, your device may not be working properly." The USB ports on my computer work fine. I meet the qualifications I have 2 USB 2.0 ports and 2 USB 3.0 ports. I installed Java, I downloaded Android SDK. I synced my device like it recommends on htcdev.com but STILL I get this error message. I have reformatted my system 3 TIMES because I plugged my computer in 2 times before thoroughly reading the directions and I thought maybe the phone installed bad software, so I haven't used my laptop for 3 days because of me reformatting and failing to install my phone. But on the 3rd reformat I followed the directions to A T. I don't know what I am doing wrong? I have rooted this model in the past with this same laptop but it just don't work on this phone I'm using now. If ANYBODY has had this issue or if there is a thread I missed on this subject please point me to it! I will be very grateful! I apologize if this is in the wrong section I just desperately want to get this resolved!!
I have both the driver and the usb file downloaded and installed. http://forum.xda-developers.com/showthread.php?t=2179776
I don't know what I am doing wrong!
Have you tried a different USB Cable?
TEAM MiK
MikROMs Since 3/13/11
you make sure that you are following all directions for hboot 2.18.0001? http://forum.xda-developers.com/showthread.php?t=1473373 and new drivers HTCDriver3.0.0.007.exe? hope this helps.
HTCEVO1988 said:
OK. I am beyond frustrated and I'm about to just give up all together. I followed these directions to root my HTC EVO 4g HBOOT-2.18.0001http://forum.xda-developers.com/showthread.php?p=22013438&nocache=1 I followed the directions at http://www.htcdev.com to a T. And STILL my device is not recognized. When I plug my phone into my laptop it gives me this message "USB device not recognized. The last USB device you connected to this computer malfunctioned, and windows does not recognize it. Recommendation Try reconnection the device. If windows still does not recognize it, your device may not be working properly." The USB ports on my computer work fine. I meet the qualifications I have 2 USB 2.0 ports and 2 USB 3.0 ports. I installed Java, I downloaded Android SDK. I synced my device like it recommends on htcdev.com but STILL I get this error message. I have reformatted my system 3 TIMES because I plugged my computer in 2 times before thoroughly reading the directions and I thought maybe the phone installed bad software, so I haven't used my laptop for 3 days because of me reformatting and failing to install my phone. But on the 3rd reformat I followed the directions to A T. I don't know what I am doing wrong? I have rooted this model in the past with this same laptop but it just don't work on this phone I'm using now. If ANYBODY has had this issue or if there is a thread I missed on this subject please point me to it! I will be very grateful! I apologize if this is in the wrong section I just desperately want to get this resolved!!
I have both the driver and the usb file downloaded and installed. http://forum.xda-developers.com/showthread.php?t=2179776
I don't know what I am doing wrong!
Click to expand...
Click to collapse
Ok it could be one of 4 things and you kocked one off the list,your USB ports,now the other 3 are your cable,like the man above me suggested or you could be in debug mode,or it could be you need to reboot your system,here,ill explain:
Simply UNPLUG YOUR COMPUTER FROM THE POWER SUPPLY. Yes that’s it! Note that this does not mean just turning off your computer because modern computers don’t really turn off when you press the power button as the motherboard still gets power.
First to explain, the motherboard is where all of hardware of the computer is connected to, including the USB ports. Sometimes the motherboard needs to be “rebooted” also because something can go wrong, i.e. all your USB ports suddenly stop working. The small microprocessor on the motherboard will reload the drivers and your USB ports should be back to recognizing all devices!
So first turn off your computer using Shut Down or pressing the power button and then UNPLUG it from the wall outlet. Let it sit for about a minute and then plug it back in.See if that works for ya.
I had that same issue and it was cause I had a loose charging port I just place in in its proper place and everything work good
Sent from my PC36100 using xda premium
I have the same HBoot and I tried several methods, all of which failed until I found the following link. It worked like a charm. Step 1 I used the HTCDEV method, on step 2 I used the ADB method, and on step 3 I used "Flash a ROM." It was perfect and easy. I just used this procedure a week ago, so I can vouch that it is valid. I suggest you try that. Lemme know how it goes bro.
http://androidforums.com/evo-4g-all-things-root/488901-rooting-gingerbread-2-3-5-dummies-guide.html
TheEvoNoob said:
I have the same HBoot and I tried several methods, all of which failed until I found the following link. It worked like a charm. Step 1 I used the HTCDEV method, on step 2 I used the ADB method, and on step 3 I used "Flash a ROM." It was perfect and easy. I just used this procedure a week ago, so I can vouch that it is valid. I suggest you try that. Lemme know how it goes bro.
http://androidforums.com/evo-4g-all-things-root/488901-rooting-gingerbread-2-3-5-dummies-guide.html
Click to expand...
Click to collapse
It works if done correctly. I've done it many times.