Hello,
I have a spv M2000 orange. I tried to update to windows mobile 6 I found here.
everything went fine at the beggining, but then activesync did the usual beep when disconnection occurs between pc and the smartphone. there was still the message saying "checking the information on your device... please don't disconnect... "I waited for a long time. but nothing happened then. still a black screen on my smartphone with "USB V2.07" written on it.
can anyone help me to find out a solution ?
thanks !
there is nothing lost or broken at this point, just try again using the instructions given here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade1_WM2003SE0
there is probably something you forgot.
thanks Chef_Tony, you give me back some hope !
I tried to flash back to wm2003, and it works fine.
I will follow very closely all the steps of the procedure described on the page you pointed at, and tell you afterwards.
thx again.
ok it works fine.
I forgot to remove the memory card when flashing the first time.
thanks again for the help
Hi. I'm a new member. I need your help. I try to flash my PDA2K with HTC_BlueAngel_WM6.1_WWE_Final_by_Ham3r using WMDC on my Pc with Vista... but without put my device into Bootloader mode. The software is started, my PDA2K was blocked with "USB" on top of the screen and "V2.07" on the right bottom. After nothing more. I tried SR, HR, like the instruction on http://wiki.xda-developers.com/index...ade1_WM2003SE0, but nothing. My PDA2K is dead. On screen, nothing. What can i do? I can resurrect my PDA2K? Thank you
ok, first of all, that link does not work. secondly, yes! your Ba is not dead, it is in a state called "stuck in bootloader" which is due to your attempt to flash under windows vista, which does not work the same way as under win xp. because, during the upgrading process windows vista, being smarter than xp, discovers the device changes and downloads new drivers and installs them, which disconnects the device, and in the beginning of the upgrade process the upgrade utility tells you, never to disconnect the device, unless the process is finished, but since vista is doing it on its oqn, you can't do anything about it.
normally i would advise beginners to use a windows xp pc, i even heard of people managing to upgrade from vista, using a windows xp virtual machine, but in your case, with the device already stuck, you should have a deep look over -=this=- and -=this=- before even attempting to flash again. then you should think, whether you deleted wm2003's extrom before you started upgrading, probably not!
so to upgrade, you should flash wm2003 again, first.
the entire process of upgrading is described pretty good -=here=-.
you say, you want to upgrade to wm6 from wm2003 and you use vista, then you get to all the steps needed for the first upgrade, please don't skip anything, please read carefully, if there is anything, you don't understand, please post back here, BEFORE destroying the device
with best regards
Chef_Tony
Thank you for your help. I'm following step by step the instructions of your links, but my PDA2K don't work. It's appeared again "Serial" at the top and "V2.07" at the bottom, but the Perform Reset don't appeared (point 3 of Link: http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5). Also WMDC don't see the devices either before or after the instruction on this link http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista_Pic ( i have never seen the boot option because my device don't make a perform reset). Help me....Thank you for you patience.
P.S.: I have also tried with my other pc with XP, but even ActiveSync see my PDA2K. However, in both my Pc, device manager show mobile device (microsoft usb sync).
I followed this procedure in this link http://forum.xda-developers.com/showthread.php?t=304408 with mtty.exe and my device is raised. Now is as good as new. Try with caution now. Thank you for everything.
Related
Hi all,
I have been trying to check out the forum here, to try and solve my problem, I literally bought my JASJAR today, and it was giving some wierd behaviour. In an attempt to reload the software (I prefere to reload the entire ROM), something went wrong, now all thats on my screen is "USB" and a lil lower down "v1.01".
ActiveSync obviously not connecting now bcos the OS is not on the JASJAR no more, in my device manager is a "Microsoft USB Sync" under my mobile devices.
I downloaded what I am guessing is WM6, 'JASJAR_WWE_20106_20301_11300_wwe_ship' from another thread in this forum, tried to load that but cant communicate with device cos no activesync.
I have tried the different reset options, like the 2 function keys and the reset on the back, I push 0 to clear, and then it jus goes back to the USB v1.01 thing.
I am running windows vista home basic, with the Windows Mobile Device Center, it synced perfectly with this software, communicated properly with the update tool, until my device reset and activsync lost connection, then i was stuffed.
Any help will be appreciated.
Thanks in advance.
Sounds like it is your first time with the upgrade. What you are seeing on the screen is the bootloader, which is what we use for flashing new ROMs.
ActiveSync or Windows Mobile Device Center (how come you have both on Vista?) will therefore not respond. This is fine, because we use a different program to load the new ROMs.
If you look at the folder you downloaded, chances are that there should be a program called "ROMUpgradeUt" or something similar. Provided that you have not changed anything in the folder, you should be able to flash the new ROM by simply following the instructions in the program.
You can also read this link for more information: http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
Here is an instruction guide on ROM upgrading: http://forum.xda-developers.com/showthread.php?t=269118
how come you have both on Vista?
Sorry, I don't mean to sound like I have both, I recently moved to Vista, and am used to calling it activesync and not WMDC.
Thanks, will have a look
Ok, well I have got it up and running again, only problem now is activsync keeps freezing when I try and sync the device...any ideas?
I landed up using my work computer, which has XP on it, and then used MTTY and that connected fine, on Vista it simply didnt wanna work.
I ran the utility for those 'stuck on serial/usb', and that fixed it. Now I would like to load up WM6, but it keeps getting communication failures.
Thanks for the help guys....I got it working...running on WM6 now...whoo!!
I have a TyTN with official Russian WM6 onto it, which includes 1.16 radio version. I want a newer one, because this seems unstable, so i decided to update just radio (i don't want any cooked ROM or whatever for now).
Each new version of radio I found here failed earlier or later on a Vista x64 computer with error 260. What I have tried is 1.54.07.00 and 1.54.00.10 and 1.50.
To my surprise, packaging is different, but the effect is the same: after "Verifying the image on your device" (i can hear USB disconnecting and connecting back as the device enters bootloader) they time out with 260.
Right now I'm trying to revert what have I done to Vista as it won't allow me to turn off driver signing, as advised.
Ah, this doesn't work either (same error 260).
What am I doing wrong? My bootloader is, as said on that screen:
Code:
HERM200
IPL-1.01
HERM200
SPL-1.40.Olipro
Yes, I have installed some...er...thing before, maybe it was called "HardSPL", but it didn't come handy and wasn't any use to me as I decided against cooking a ROM.
Update: What I like the most is, despite all my attempts the device still works! Other than the radio troubles, that is.
I've updated from an SD card.
Try this my friend... http://www.mrvanx.org
Thank you, I did.
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Click to expand...
Click to collapse
This is what I'm unable to do, but I suppose is beyond this forum.
Hi
I have had the same problem with my x64 vista pc and the 260 error msg. It took me hours but what seemed to finally fix it for me was to:
1. completely remove WMDC from the pc, reboot the pc,
2. reinstall WMDC plus upgrade,
3. uncheck the allow USB connections option on your 8525, exit out of the window, then do a soft reset
4. now make a USB connection w the PC
Let us know how it works
Sorry, you'll have to wait till my next upgrade Everything is working so far - so until I need something that can't be achieved using SD flashing I'll stick to this technique. Thanks for the advice anyway.
Hi,
I tried to upgrade my XDA using Ranju's latest updater, the whole process failed and now I'm stuck at the BL screen "USB" at the top (when connected, otherwise it says "serial") and "v1.00" at the bottom.
My PC, SyncCentre and Windows Mobile Device Centre (I'm using Vista) all show the device as being disconnected (up until trying to upgrade everything had been fine).
As it's not showing up on my PC all of the software options for recovering it dont fail, all end with a plethora of USB not connected errors etc
I've tried the how-to on the wiki: http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial to no avail.
Does anybody have any ideas? Greatly appreciated,
Thanks,
Lee
with jasjar-bl1.01-ruu-v1.2 I always restart my JJ Leave your uni in bl and start the application Good luck......
I think the Vista is not the problem this upgrade don't use AS or "in italian centro gestione dispositivi WM"
Bye
M.C.
Well, I flashed my Qtek a while ago, it failed to flash (using Vista) and doing a hard reset after it whas hanging at the startupscreen(the one with all the rom/radio numbers). No matter what I tried, following the instructions on Vista windows mobile center all failed... The good news is that your computer and your PDA still see when it is connected, ie USB/Serial, like in my case!
I then tried it on my desktop/XP, it flashed without a problem...
The funny bit is that I flashed my herald (WM6) 2 times using Vista without any problem...
I cannot explain but if U have the possibility, try and see if it works on XP...!
Good luck!
are you trying to flash it WITH your SIM card and / or SD card inside? If so, try taking them both out! It worked for me a few times!
I would start by getting rid of vista !
i had the same xprience
the different was i downgrade from wm6 to wm5 (i need the vcall)
failed in vista, succeed in xp
-> my advice : try in xp !! don't forget to remove the sd card
Manual for how to flash a rom in Vista
Read this post, you have the solution to the problem here:
http://forum.xda-developers.com/showthread.php?t=313001
You need to update the driver manually, if not, will not be able to install the driver.
You need to do this without sd/sdhc and without the sim.
If you follow these instructions, you can flash with success.
Greetings.
Kali.
After spending many months waiting for the official WM6.1 ROM...
After following the firmware upgrade instructions explicitly (including the notes on Vista)...
I now have a bricked 9502!
The phone just simply tells me to reconnect and try and run the upgrade again immediately after it is powered on. (That doesn't work) I've been searching high and low for a method to reload the firmware.
As anyone who has dealt with iMate knows - their support is worse then useless. Its infuriating! (If you ever do get connected to their online support, they will simply disconnect the session if they don't have a quick answer)
...anyway...
I have the IMAGEFR.mbn and CP.mbn files extracted from the install set and copied to an SD card installed in the unit. I just can't find any info on how to get the phone to load the two firmware files from the card at boot time. (I'm pretty sure the USB connection is going to be useless).
Beware: All this may be due to the fact that Vista-64 wasn't a supported update environment (although the ReadMe specifically gave instructions for Vista - it did not specify 32 or 64).
Help is appreciated!
evanevery said:
After spending many months waiting for the official WM6.1 ROM...
After following the firmware upgrade instructions explicitly (including the notes on Vista)...
I now have a bricked 9502!
The phone just simply tells me to reconnect and try and run the upgrade again immediately after it is powered on. (That doesn't work) I've been searching high and low for a method to reload the firmware.
As anyone who has dealt with iMate knows - their support is worse then useless. Its infuriating! (If you ever do get connected to their online support, they will simply disconnect the session if they don't have a quick answer)
...anyway...
I have the IMAGEFR.mbn and CP.mbn files extracted from the install set and copied to an SD card installed in the unit. I just can't find any info on how to get the phone to load the two firmware files from the card at boot time. (I'm pretty sure the USB connection is going to be useless).
Beware: All this may be due to the fact that Vista-64 wasn't a supported update environment (although the ReadMe specifically gave instructions for Vista - it did not specify 32 or 64).
Help is appreciated!
Click to expand...
Click to collapse
I've read many posts around stating that upgrading WM devices through Vista has proven to be a nigthmare for a lot of devices.
If possible, try to get a WinXP equipped machine, and perform the SW upgrade there normally (i.e. by clicking on the EUM SFX executable file on the PC).
You see, I upgraded mine through my XP lappy, and the process simply ran flawlessly.
Just my 2 cents...
Cheers!
Carlos
the problem is not in the vista, i flash using vista ultimate and no problem, u can unbrick by
pressing fn button and call (green) button then press the reset button, without let the 2 previous button go until u can see the imate logo or hard reset message.
I hope this can help.
thanks a lot i have unbricked my imate
thanks a lot by your code buttons i have unbricked my i mate
Hi there!
I am in serious need of help with my iPAQ hx2490. Yesterday, I tried to do the
official HP ROM Update. Everything went well, up to about a point when the RUU told me that there is a connection problem with my device.
The update went to just about half way through, and I didn't touch anything, I just left the device in it's cradle.
Anyway, my problem now is, that the device won't start the OS, I can't get past the HP welcome screen. The loading bar fires up, and completes it's way to the right, but after that: NOTHING!
I have tried soft, hard and clean reset, without any help. When I do a clean reset, the display shows "Formattin PS", and the loading bar reaches the right. But after that: NOTHING again!
I tried flashing everything again, from WM 2005 first and second edition, even WM 2003. The result is always the same.
I can get it into Pre-Bootloader, normal E-Bootloader. I do get a "USB Connected" message, and I do get the following "USB" message on the screen.
Now here's the odd thing (and I do hope that all you experts are dying to solve this mystery!): when I do the update again, at either 84,1% or sometimes 85,1%, the iPAQ shuts down, and starts again. But this doesn't stop the RUU from continuing!!
I've tried everything I can, I read all the infos in the forums concerning iPAQ problems, but they're mostly concerning entering bootloader, which is NOT my problem.
Money ahead: I'll donate 10€ to the person who is able to solve this riddle!!
The money can go to either this website or the person's own PayPal account.
oh I forgot: I did try ChrisMRulz bootloader method, but I wouldn't work for me. I managed as far as the MTTY program firing up, and I do get a WCEUSB prompt, but can't enter any commands, and the nbf file doesn't get uploaded!
PROBLEM SOLVED!! Sorry.....
Can you tell us how?
Maybe it will be helpful for others that have similar problems in future.
Sure, I can do that:
I managed to flash the official International English ROM Update to my german hx2490 iPAQ. I just used the trick that you have to start the correct HPRUU.exe for your country-specific device, but just before you hit the last "Update" button, you change the .nbf file with the one you want to flash.
But you have to rename it to according filename the HPRUU.exe originally loaded,
if you don't rename it, the update utility will crash.
By doing so, I was able to flash the above mentioned ROM to my device, and after that I just flashed my country-specific ROM.
Now I'm back and running WM5.
If further explanation is needed, I'll gladly help out someone with the same problem.