I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
I have also tried to use ActiveSync to version 3.8 (I found this suggestion from this web site) but bad luck it can't detect my BA device at all. I have also tried to revert back to WM2003SE but still get the same problem. My system is WinXP SP2 & O2 IIs. So Please help I am in the dark right now.
Same problem here...
su2003 said:
I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
Click to expand...
Click to collapse
get into boot loader mode,then try
(press record button + power button and reset at same time)
addan said:
get into boot loader mode,then try
(press record button + power button and reset at same time)
Click to expand...
Click to collapse
Have tried that already but still get the same error. I have even reformatted my PC and reinstalled WinXP and ActiveSync 4.5 just in case there are viruses or so but also get no luck.
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Yes, at this time you asked me. Nothing changed.
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Yes.
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Yes. I did it.
More over, if I started BootLoader mode before execute MaUpgradeUt_noID.exe the program get struck while performs device information checking, I have to pull it out from Sync station the program then continue running but without any information (like the existing OS version etc.)
how long did you wait for the program to respond before you find that its stuck ?
Here it takes about 2 min to find the device
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
2. place it to cradle
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
4. start upgrade utility and follow the onscreen instructions
5. perform hard reset (the three options thing)
thats all
Xplode's new cube cab
deleted... off topic
how long did you wait for the program to respond before you find that its stuck ?
It was about 5 min and the program still had no responses. I then have to pull it out and the program continue running but without any information (like I had mentioned it before).
Here it takes about 2 min to find the device
Unfortunately not with mine.
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
Yes. I did it.
2. place it to cradle
Yes. I did it.
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
I have tried it both with and without killing the activesync.
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
su2003 said:
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
Click to expand...
Click to collapse
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
Good luck!
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
First of all, Sorry if I make you and other confused. I have began to unsuccessfully upgrade my device since Friday. So I decided to help myself at first by try to do everything I can do by myself. I have formatted PC HDD and also reinstalled activesync because I thought the utility may conflict with other program on my PC or from Viruses. I have also tried many ways with hard reset and cold reset etc. to upgrade my device but have no luck. That was with very fresh new installed WinXP PC. Unfortunately, I have to use this computer for my job also. So that's why I have to install printer & scanner driver including MS Office, AutoCAD and other necessary program to serve my job . I have falled with upgrading but I do not want to have problem with my job. Hope you understand my essential.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Since I began to upgrading and everytime I have executed the utility I have always wait & wait but I just never look at the clock to see how long I have waited. Xplode has just warned me to take enough time so I started to upgrading but with clock at this time. I have already mentioned that I have successfully upgrade from WM2003SE to the WM6 (previous version) so as a user I have enough experience and know what I am doing.
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
This is just my opinion to let you guy see and understand the problem. That's it.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
I think I have already put a lot of effort about upgradind my device. I have reformatted and reinstalled all necessary programs. It took me out almost half a day to do this. And not only with my PC I have also reinstalled all programs on my device with an old OS version since I have lost them all from hard reset. Other than that I have also tried & tested upgrading the device during the time. The only word I can say that It was not funny to do all of this. It was not really a hard job but it took almost my weekend time.
Good luck!
Yes I do need it barely. Actually I have already felt a little lucky got from all of you that try help me solving the problem. Thanks.
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
April 1 said:
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
Click to expand...
Click to collapse
Thanks for your additional.
I have also tried using different PC to upgrade the OS but got the same result.
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
I am quite sure that the screen has displayed USB but the number is 2.07 not 2.06. I am not sure about the meaning of the number, it could be the version.
I have also brought a new USB-XDA IIs cable yesterday, just in case the cardle was defected but it doesn't work also, I have got the same result.
khanem said:
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
Click to expand...
Click to collapse
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Conclusion:
Bad Hardware(Flash ROM)?
Your Bootloader is toasted or had it's LAST flash of it's lifetime???
We can say that... but hopefully not for your sake.
Because as you have said you've done EVERYTHING that was posted.
and though our Senior's "inputs" didnt worked out the way it SHOULD work.
I cant say it's a waste of time to answer your questions.
But there are no more questions to ASK
and there are no more questions to ANSWER
They're all been said here.
All you have to do is PRAY HARD leave the BA rest for a day...
remove the battery...
think things out, clear your mind... sleep...
then execute Xplode's Walkthrough from Step 1 the next day.
but be sure to have the battery fully charged.
Your BA is not dead and your bootloader is not toast. The only problem you have is probably you are impatient. Go to the Wiki and follow the procedure exactly as it is written. It will work. By the way, if you kill Activesync (ie disable USB connection in activesync connection setting), put your device in bootloader mode and connect your usb cable (in that order), run the upgrade and it will work. Forget about activesync.
su2003 said:
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Click to expand...
Click to collapse
I use xda IIs and the bootloader mode shows ver 2.07, and i dont have any probs installing. I dont think the version 2.07 has got something to do with your problem.
You said that you tried other pc and it doesnt work, and it worked before when you upgraded previously. I think you know enuf about upgrading if you have done it before....
did you have problem with sync connection before? I was just thinking maybe there is something wrong with your BA....like actual hardware problem with the cable connection??
what about firewall? would it affect it - I doubt it cause its not in sync mode.... but at this stage, maybe just try all possibilities to try to get it working.
Good luck
Mhm. I'm not sure I've really followed all the intricacies of this case ... But whatever, here's my two cents for a safe upgrading procecedure:
1) use a cradle, not a USB cable, and make sure the cradle's
power supply is plugged into a wall outlet. It also helps to make
sure the cradle is plugged directly into the PC, not via any kind of
USB hub. No other devices should be connected to that same USB
channel. I suppose temporarily disconnecting other (unneeded) USB
devices from the computer can't hurt, either.
2) I guess "kill ActiveSync" can mean various things ...
however, here's the best way to do it I think: as sofene mentioned,
disable USB connections (what the hell - disable ALL connections) in
ActiveSync settings. Then reboot the PC. No need to look for ActiveSync
processes and kill them manually -- disabling the connections will take
care of that. Rebooting ensures that ActiveSync's driver code is really
unloaded.
3) remove SD card and, for good measure, SIM card from the BA.
4) perhaps soft (or even hard) reset your device
5) put device in Bootloader mode
6) insert device in cradle, start upgrade utility, off you go ...
By the way, ActiveSync has got nothing to do with the ROM upgrade utility, and it should therefore not have been necessary to re-install ActiveSync, etc. You just have to make sure it does not get in the way of the upgrade process. As far as I understand the process, the ROM upgrade should work equally well on a PC that does not even have ActiveSync installed.
Well... I've been without a phone for close to 3 weeks now (because the phone is bricked) and have been reading and reading and reading..
anyway.. the point being is I think i have came close (I've tried the SD method and it hasn't worked) is there any way at all, to be able to connect the phone on activesync, even when bricked, because thats the only way i can flash the rom!!
respond please!
Not sure what exactly your specific issue is but, having just recovered my, Hermes from "Brick-Hell". I'll try to help.
First, do you have access to an XP machine and AS4.5? This would make things easier... if not have you read MrVanx's guide to syncing on Vista?
But try this anyway:
In WMDC de-select connect via USB (or whatever it says, I forget as I dumped Vista for Linux).
Remove the battery from your device for several minutes. In the meantime reboot your Vista machine. When it comes back up, make sure allowing USB connections is still un-checked.
Go here and download the T-Mobile ROM (2nd Link) to your desktop.
Return the battery to your phone and connect via USB cable. Then run the T-Mobile ROM app from your desktop. If it doesn't work, at first, keep trying until you get by the "Erasing" part. The ROM update will eventually return an error but after that you should be able to flash any ROM to your phone. But first I would Hard SSPL upgrade.
I just did this under XP (in a virtual machine, no less) and it worked like a charm.
Good luck.
just loaded Windows 7 on my laptop and went to flash to the latest energy rom. Im not familiar with WMDC but when it goes to flash, it gives me the RGB screen when rebooting my tp2 then my pc reports cannot complete update due to lost connection... wtf... why? win7 not compatible? am I a retard?
Not at all
XITruthiX said:
just loaded Windows 7 on my laptop and went to flash to the latest energy rom. Im not familiar with WMDC but when it goes to flash, it gives me the RGB screen when rebooting my tp2 then my pc reports cannot complete update due to lost connection... wtf... why? win7 not compatible? am I a retard?
Click to expand...
Click to collapse
I have Windows 7 and flash my ROM. It's not a Windows 7 issue more than likely. It sounds like you have not connected with Activesync before you tried to flash your ROM. The reason I say, you haven't established a communication port with your pc and it therefore cannot enter a usb connection in bootloader. I have had this happen when I didn't wait for activesync to sync with my computer. I got an ERROR: screen, so I know what you're talking about.
Just sync your device with Mobile Device Center and as soon as activesync completes, run the ROM install.
Let me know if this doesn't work. We'll proceed from there.
XITruthiX said:
just loaded Windows 7 on my laptop and went to flash to the latest energy rom. Im not familiar with WMDC but when it goes to flash, it gives me the RGB screen when rebooting my tp2 then my pc reports cannot complete update due to lost connection... wtf... why? win7 not compatible? am I a retard?
Click to expand...
Click to collapse
Its compatible but it can be rly retarded if you dont do it like it wants
1st install wmdc and let it connect to you phone
2nd disable usb connections on wmdc
3rd and so forth go onto flash your device
if it still says that then connect to the internent and boot your phone into the tri color screen WHILE still connected to computer and try flashing from there
I have flashed roms and done Task29 several/many times from my W7-32-bit laptop and my W7-64-bit desktop, and both work fine -- no issues. I didn't do any special procedures or settings (none on purpose, anyway)...it just worked.
I know this doesn't solve your problem...but it might help to know that W7 should work.
I guess by now this should be solved. If not, try getting into bootloader mode (turn your phone off, and turn on by holding power+volume up button). Then connect the USB cable and try flashing.
I also use Windows 7 64b, sometimes when flashing roms got the same problem, and had to reset the phone from the color screen using the button. This has never happed after I started using Task29, because I have to get into bootloader mode manually.
Ok... Id like to continue this post for only one reason, I am in fact a retard...
Simply reading the stickys is always crucial in your quest to not appear far more retarded than you actually are. Apparently windows 7 update DOESNT update WMDC to 6.1. I Re-Read the "For Noobs" sticky and realized hm, maybe I should check to update WMDC and WHAM, no problem.
The moral of the story, read the previous posts. Asking questions in text based form on the forum when perfectly good answers already float about right in front of your eyes is just a complete waste of precious bandwidth, so dont do it.
I apologize.
Sometimes I post things and feel like a complete idiot, I actually just had a lot of trouble flashing my tp2 to a cooked rom for the first time, but I've had HTC phones since the wing and still run into problems. This last bout of problems I had was fixed by simply reseting my phone to factory default :O
I tried to root my Magic however it has perfected SPL 1.76.2008 so I tried the goldcard method but I only managed to change the firmware from 1.6 to 1.5. I cannot use fastboot so now I'm trying to install a new RUU so that I can follow the steps to install CM however I get the USB error (on windows 7).
I already tried reinstalling the latest HTC Sync and that seems to recognise my phone but when I open the Setup for RUU, Sync doesnt recognise it anymore until I close setup and replug USB. And yes, I inserted the goldcard already. Any help is appreciated.
I have pretty much the same problem here, but I do not have a goldcard (which I dont thing its necessary). When I try to transfer some file to my phone, it starts and after a couple of seconds, unplug from storage mode (Robot turns green again :[ ).
I have Cyanogenmod 6.1.0-DS and Windows 7 32bit.
Even over wifi, this happens. Seems to me thats some storage problem with the rom, but cyanogenmod is widely used and tested.
Can someone help us?
Debugging on?
Of course, I followed every single step correctly maybe theres a problem with windows 7.
BMN12 said:
Of course, I followed every single step correctly maybe theres a problem with windows 7.
Click to expand...
Click to collapse
On linux now and had forgotten this. Reread everything from the beginning and recalled that I've had issues with the drivers from HTC Sync driver not working when I had downgraded my G1.
The "official" google sdk driver covers all builds and modes (RUU uses adb mode.) Maybe try reinstalling with them instead?
Kind Regards,
Kevin
Sent from my T-Mobile myTouch 3G using XDA App
Hi,
i am having lots of trouble with my HD2. I just got it so im kinda new to this new stuff. I previously came from the HTC Desire.
My problem is that i can't run any RUU. Even the original one. Or the magdrl one.
It is always stuck at 0%.
Steps i have taken: I established activesync unfortunately it does not sync properly because it asks me to log in in my phone and i cant seem to do it. though i still go to the bootloader and have USB at the bottom.
I have installed HSPL4 with 2.08.0000. It was succesful. I tried different USB ports on my computer.
Its only the RUU problem where i am stuck at 0% and after awhile it fails and gives me error 276.
Please help me...
Thanks
Vevek
I also had this problem seldomly.
Possible reasons are:
- battery charge level
- virus scanner on PC
- firewall on PC
- non removed SD
- other devices connected to USB (printer, scanner, ...), disconnect which you don't need.
- USB 3.0 ports on PC
- ...
- Have you tried to reboot your PC?
- Which OS are you running on PC?
- If Window 7 try to install Windows Mobile Device Center again
- Have you already tried LeoAdvacedRUU?
shockem said:
I have installed HSPL4 with 2.08.0000. It was succesful.
Thanks
Vevek
Click to expand...
Click to collapse
2. 08.0000 is stock, so won't allow flashing. Run hspl4 again and choose "2.08.hspl" .