I was upgrading my Hermes 8525 with the latest black pro when my computer turned off. The Hermes boots into windows but displays a black back ground. There is no screen interaction and no buttons work. It does not active sync either or I would have reinstalled.
Is there a way to re-install a rom with out being in active sync mode ?
Also windows recognizes a USB devices but it does not recognize it as a Hermes any more
I need some advice and help
thank you,
Brian
tried to reenter the bootloader and reflash ?
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Also check out the WIKI site for upgrade problems HERE.
I've also found that have Hard SPL keeps a lot of problems at bay. You can get that HERE
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 recently tried reverting my PDA to WM2003 (so I can run GoodLink) and the process failed part-way through (my laptop bluescreened). Now my BA won't even get to the boot loader.
Things I've tried:
Removing the battery for 30 minutes+ and reinserting
Hard resetting the device
Removing the battery and plugging directly in to sync station
None of the above work. Is my device truly dead or have I missed something crucial here? I've tried mtty as well and that failed saying it cannot open USB.
Cheers,
ffb
Hey there,
Are you using Windows Vista by any chance?
If you are, use Windows XP, and try reinstalling, your pda is in a "special" mode and awaiting prompt from the updater
Thanks, I'll try that when I get home in a few weeks
Matt
Got a Jasjar and it had AKU1.? installed. I tried to upgrade to 2.0 (JASJAR_WWE_20106_20301_11300_wwe_ship.exe) so that I can setup the push-mail. Bad choice by me, the upgrade completed and I just clicked the finish button (I recall it says something about hard reset PPC). So I did, and upgrade activesync to version 4.5.
Now my PPC doesn't even turn on, and my computer doesn't recognize the PPC either with an error saying "USB device not recognized".
Since I can't turn the ppc power on at all, computer can't recognize the ppc either, I have absolutely no idea on how to fix this problem. Anyone know what's the issue and the solution to this?
hi everyone ive had this problem with my spv m2000 being stuck in bootlad mode
i just cannot find a way out of it
i dont have a manual for the device
any help would be greatly recived
i have read through the htc blueangel service manual posted by chef tony but carnt get any response from the handset
ghostmachine said:
hi everyone ive had this problem with my spv m2000 being stuck in bootlad mode
i just cannot find a way out of it
i dont have a manual for the device
any help would be greatly recived
i have read through the htc blueangel service manual posted by chef tony but carnt get any response from the handset
Click to expand...
Click to collapse
Have you Windows 7?
i have windows xp and a windows 7 pc
the phone was running wm 2003
in case you tried upgrading from windows 7 you should follow d-two's tutorial here: http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
i have followed the guide and got nothing
its still in bootloader v2.08 i just hope its not a faulty phone
please post more detail, it is hard to guess, what actually caused it, when you just say, you are stuck in bootloader mode. what driver version shows up in device manager, does the BA's display change from serial to usb, when you connect it to the pc, what error do you get from the RUU, please post the RUU.log in C:\
which rom did you try to flash?
did you use d-two's new RUU?
can you connect using mtty?
the screen changes from serial to usb it has v2.08 at the bottom of the screen
the RUU dosnt register the device cannot conect using mtty
i havent tried to upgrade the device ive tried to leave the device with a battery to see if it will reset to default
but it just loads into the boot screen