Related
I am trying to upgrade from Ivan's ROM beta 13 to beta 15... Using the MAupgrade utility... however, everytime the utility resets the device to start the ROM update i get "USB device not recognised" from my PC and the update fails to start... eventually i get a connection error message.
This used to work just fine... however, recently i installed Activesync 4.5 Beta 2. Could this be causing the problem...? otherwise i'm not sure what else might be causing this...
I have also tried running the tool in bootloader mode with and without "USB connections allowed" ticked in Activesync but with no success...
Can anyone help me please?
Trying to clear registry before upgrading ?
Have you tried to clear registry before upgrading?
Hi Kassel, thanks for your response.
I have done a hard reset prior to upgrading... wouldn't that clear the registry?
If not please let me know what else i can do that might help.
Also, it seems very strange that i can't seem to do the ROM upgrade from bootloader mode.
I think i might be having a problem with GetDeviceData as it seems to stay in the "checking the information on your device... please wait" for forever when i try to upgrade from bootloader mode.
If it does come up, then the panel which says which version is on my device and which version it will be replaced by is blank?
This is not the case if i try to do it through activesync (with the device set up as guest).
What might get in the way of reading the device data? I made sure it went from serial to USB when i plugged the USB cable into the device and i have tried different cables...
My bootloader appears to be V1.00
hmmm... any thoughts?
Same here...
I also have the same problem.
I installed ActiveSync 4.2
Alse after having installed AS, the MTTY program doesn't see the USB port anymore, just some COM ports.
Same to me too
I have ActiveSync 4.5 bata at work (Which couln't upgrade ROM)
while my notebook with ActiveSync 4.2 work fine
Wow, it's great to hear that people are having the same problem...
Is it possible to back track with Activesync? Is 4.1 still available?
If not, i think i still have an older version running at home (i hope!)...
Is this definitely the issue then?
l_pete_l said:
I have ActiveSync 4.5 bata at work (Which couln't upgrade ROM)
while my notebook with ActiveSync 4.2 work fine
Click to expand...
Click to collapse
I have ActiveSync 4.5 and upgrading my Jasjar was successfully done with the ROM Version: (1.90.96 / 1.13.00 / 42.47.P8)
Sorry for not knowing, but is that one of the AKU3.2 ROMs. Not sure if it should make a difference, but just curious.
Also, did you need to use the MAupgrade Utility?
Cheers,
What happens with the USB drivers after installing ActiveSync 4.2
The strange thing is, that I tried connecting my MDA Pro to a PC without ActiveSync on board.
USB ports were visible using MTTY
I installed ActiveSync 4.2 and only COM ports are visible in MTTY, the USB port has vanished.
Can this be caused by the USB driver that comes with the ActiveSync install ?
If I put my device in bootloader mode, it sais USB on the PDA screen, but the utility for the ROM upgrade doesn't see the PDA and comes up with a device not connected error.
I would really like to try out one of the new ROM's by Ivan or JwRight, but am unable to, because of these USB problems.
So please someone help !!!!!!!!
I have the same problem... if i put the device into bootloader mode, "serial" changes to "USB" but the PC comes up with "device not recognized"...
As the title states: Why does some computer fail to recognize the Universal via USB on bootloader mode?
I recently reformatted my computer, which I usually do once a year. After installing all my apps back and running windows update on my computer, I installed active sync. Performed a normal reset on my computer, attached my Universal and active sync worked.
Here comes the problem: I decided to roll back to my old AKU 2 QTEK ROM. Of course, I know how to use the Ma_Upgrade No ID file. The problem is my computer now fails to recognize my Universal no matter what I do on bootloader mode. To make it worst, I am now stuck at the bootloader mode with my computer not recognizing it. Any suggestions as to why my computer failed to recognize my Universal?
OK, I was able to get the ROM upgrade going again, by removing my SIM Card and 4GB SD Card. I'll post back if I was able to revive my Universal.
So it seems that my computer failed to recognize my Universal because either the SIM Card or SD Card is causing the conflict.
I had the same problem.... I have two computers one with Win Vista (with the same problem) and another with XP sp1. This computer recognize my pda in boot loader, doesn't matter if still SD card and SIM inside....
Sorry for my english and I didn't tell you a solution...
Hi,
i had the same (very annoying) problems but i always was able to get the Universal back into Windows Mobile.
It was very strange because i started the ROM update and than e.g. it did not go in the Bootloader but back in Windows Mobile so i started it again and than it stucked in the Bl. Hardreset and putting the device again into Bl did not help and i was already very annoyed. I tried to plug in and out the USB-cable but it was always telling me SERIAL and not USB and Windows showed this ****ing popup that one device is not recognized or something like that. I tried a trick to let the cable plugged in USB and than reset and it showed me USB but wheter MA_Upgrade (No ID of course) nor mtty were able to find the device. After several trys and resetting and resetting again i was able to bring it into USB but MA_Upgrade did not work.
The only way to bring back the device from the Bl is the method described in XDA-Wiki (http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen)
The problem is that this method does work only half. I did the steps until the command "set 14 0" and started MA_Upgrade BUT it always told me that the device is not connected, it never worked. I was already frustrated so i did again the reset and what happend? It started back into Windows Mobile!
So what i think that after using the command set 14 0 AND running MA_Upgrade reactivated the start of Windows Mobile. I tried the steps very often because i tried to find a solution for the contacts between WM5 and AKU 3.2 or higher but the only way is to ActiveSync them. This really works and this is for sure the guaranteed way to get (at least my) the Universal back to Windows.
Btw for the people who are to lazy to use the search function:
The damn ROM upgrade does NOT work on Vista until now! Even not with the Windows Mobile Device Connection Center (or how it's called). I tried several steps on the RTM Vista but it never worked. Don't waste your time on it!
So far from my side, i hope these experience will help some people
I Got It To Work!!!
I was so worried. Wheeeeew! Anyway back to normal again. I got it to work.
My observation is: My computer failed to recognize my Universal because I was using Active Sync Version 4.5 Beta 2 to update my Universal. The solution is to completely uninstall active sync using the windows remove program under control panel, and manually deleting the active sync folder from the hard drive. I then installed Active Sync Version 4.1 and all was well again.
So my next question to all the guys/gals who had problems with upgrading their device because the computer FAILED to recognize their Universal via USB is: ARE YOU USING THE BETA VERSION OF ACTIVE SYNC?
Actually when you try to upgrade with SD card inserted - only then you will get this error - I spend so many hours of GOD prays for my Universal - and after that I just remove a SD card and everything is back to normal
agisofttm said:
Actually when you try to upgrade with SD card inserted - only then you will get this error - I spend so many hours of GOD prays for my Universal - and after that I just remove a SD card and everything is back to normal
Click to expand...
Click to collapse
What is the size of the SD Card you are using? Because when a 2 GB SD Card is inserted, it works just fine. But I experience the error with my 4 GB SD Card.
Unfortunately, i don't share the same luck with all of you.
I've already take out both SD and SIM and try thousand times with ActiVeSync 4.1, 4.2 and 4.5 beta, softreset, hardreset, mtty'ing, but what i got? BIG ZERO.
So my pc always recognise my ppc as "Unknown Device" and there is no, even some slim chance, to get it to work.
Any idea for reviving my uni from black slumber of bootloader screen?
Any help would be appreciated.
DuLanTus said:
Unfortunately, i don't share the same luck with all of you.
I've already take out both SD and SIM and try thousand times with ActiVeSync 4.1, 4.2 and 4.5 beta, softreset, hardreset, mtty'ing, but what i got? BIG ZERO.
So my pc always recognise my ppc as "Unknown Device" and there is no, even some slim chance, to get it to work.
Any idea for reviving my uni from black slumber of bootloader screen?
Any help would be appreciated.
Click to expand...
Click to collapse
use MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual, then If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself
go to
http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??
moixalakix said:
i have done all this... but there is something with vista... they do not recognised it when it is on bootlad screen... what should i do can anyone help me??
Click to expand...
Click to collapse
Hi, yes you could be bang on in saying there is a problem with vista, my machine did that as well, I really thought I'd turned the phone into a brick, luckily I've got an xp machine that let me connect with the tools that everybody else is talking about here, the one I used was UNI_ExitBootloader.exe (from this site somewhere) which sends all the codes for you and it only worked from the xp machine, it totally failed on the vista machine.
Tried all suggestions, but no luck
So a failed upgrade has left my Uni stuck in bootloader mode saying "Serial" and "v1.00". When I plug the thing into my Windoze XP machine with Active Sync 4.5 one of three things happens seemingly at random:
1. My mouse stops working
2. It tells me that the USB device is malfunctioning and cannot be recognized
3. Nothing happens
In all cases the Uni still shows the same "Serial" message.
The Uni has no SD or SIM cards in it. I have tried hard resetting it. I've removed and reinstalled Active Sync. I've rebooted this windoze pile of crap about a thousand times.
Anyone got any ideas?
Thanks,
Saline
Welcome to forums
Have a read here:
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Hope it helps,
Hi. Thanks for the quick reply. Unfortunately I have already tried the suggestions on that page (that's how I found this thread). As I mentioned above, the device has no similar nor SD in it.
Have you tried to reflash from SD card?
instructions on the link on my sig
Hi all,
I was trying to upgrade my Qtek9000 with an official ROM Updater, but my device went immediately into the Serial bootloader mode and I've not been able to do nothing to run out from this mode...
I've tryied the solutions suggested in http://forum.xda-developers.com/showthread.php?t=290234 without any luck...
The problem is that neither Mtty nor the UNI_exitbootloader tool are able to connect to USB.
I'm using no usb hub, I'm running on a Dell Precision M90 notebook, I've disabled USB connection in Activesync (4.2.0) and also tryied with a pc without activesync installed.
Any idea?
Thanks
Paolo
Are you on XP or Vista, and what version of AS/WMDC do you have?
Hi,
I'm running Xp, ActveSync is 4.2.0, don't know what WMDC is sorry, can you please explain?
Don't worry about WMDC - it's only relevant if you have Vista.
Are you using the proper cable that came with the Universal? Some cables don't have all the pins wired. That (or a broken USB port) would explain why your Universal isn't going to USB mode when you plug in the USB cable. Have you looked carefully to see if it changes from saying "Serial" to "USB" at the top of the Bootloader screen when you plug in the cable?
If it does change to "USB", I would try upgrading to ActiveSync 4.5 - go to http://www.microsoft.com/windowsmobile/activesync/activesync45.mspx
Make sure you disable USB Connnections in the Connection settings before plugging in your Universal. Then try flashing the CE ROM again.
Good luck
BTW did you try doing a hard reset to get out of bootloader (both soft keys and then the reset button, then select 0).
Good advice, especially with upgrading to AS 4.5, it's a full release now on Microsoft Update site, and I have a feeling the WM6 ROMs may require it... Good luck with it, keep us posted.
Ok, thanks all!
This morning I connected the PDA to my office's PC with it's original cable and it instantly switched to USB mode...
So, I launched the upgrade and it's now in progress... let's hope!!!
It might really be a cable problem, yesterday night I tried with 2 different PC and a not original cable (I think it's my camera one...)
Thanks a lot, by now... I'll let you know own this story will end...
Ok, new ROM is up and running!
Thanks all!
Bye
Paolo
Good stuff.
i tried to do a beasty wm6 rom update, everything went well, and at the end of the procedure, it ask me to "press 0 to restaure factory setting" for rebooting, i press 0 and then....nothing. Impossible to start the htc, i can only access bootloader mode, but ain't no more recognize by the pc, i tried to plug it to AC power as i thought of a battery prob, and still nothing, no start, and no led telling me that it's recharging...
i ve done some search on the forum, but can't see something similar to this.
anyhelp welcome
regards
Hi,
did you try to downgrade it to WM5? I also had problems with WM6 and after a downgrade to WM5 it worked again.
Cheers
Michael
sorry wrong thread.
well now when i connect it to my pc it says unknown device, so i dunno how to reflash to wm5
im on vista 64, and when i try to install the 64 driver it gave me on error about a corrupted driver...
Hi
I have the same problem,cannot recognize the usb port.
Anyone has an idea??
try changing your cable and if possible try using a xp machine. i have heard of people having problems when flashing with vista (i did it and no problems)
If after you change the cable, and use a differente computer the universal when you put it in bootloader mode and the word SERIAL does not change to USB i would say its pretty much bricked but if you only flashed your device i would say it is still possible to bring it back from death.
try changing your cable (specially if its the one you usually use) im almost sure thats your problem.
also make sure you dont have the sd card or the sim in it that seems to help too.
best regards and best of luck
Erik
luxeomni said:
im on vista 64,
Click to expand...
Click to collapse
Thats your problem! Vista is very shaky at best with flashing via USB on HTC devices.
Reflash to WM5 using the SDCard method.
Psi
this worked for me
follow the directions on this thread it worked for me http://forum.xda-developers.com/showthread.php?t=291723
Have done several upgrades with vista in the past. Had to format the hard drive and re-install vista. Old drivers that I dowloaded (wceusbsh.inf) will not work. Get a message problem with driver. Have tried re-downloading the driver and same problem. Any help would be greatly appreciated.
Now have gotten the drivers to load o.k. but still no luck in a connect to the device
After spending a couple of hours screwing with everything I could think to try, I have got the Hermes to update again.
# 1 After following Mr Vanx's directions for the Vista upgrade prosses
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
# 2 DO NOT place the unit into bootloder mode, start the Windows Mobile device center (WMDC), plug the usb connection into the unit and wait for the WMDC to show connected, NOW you can run any of the RUU update files.
As Always Mr. Vanx is the man!
Bootloader Mode - Will it Erase Data
I have been having similar problems since I got a new computer that runs VISTA. I have tried everything, and the Device Manager, Portable devices has never given an indication my Mogul 6800 is present. I read the guide that captainrick747 referrs. I am concerned that going into Bootloader mode my system will lose all data and get reset to the original configuration. Should I be worried?