Help if possible please? - MDA III, XDA III, PDA2k, 9090 ROM Development

Hi all, am a noob to this and have dloaded and tried several roms here but got nowhere.
I have an orange SPVM2000 running WM2003
my PC is running Vista Premium ( so no active sync as such)
and i have a dock station
alot of the roms require to put the update to SD then boot to Bootloader and run, but i cannot do this as when it is in cradle i have no access to reset button and if i goto bootloader first then put back on dock the PC will not read the device.
I AM WELL LOST.
please could some one reply with a dummys guide please?
i have read as many tips guides and stickys and still lost.
I do not care if i upgrade to WM 5 or 6 but woud prefer 6
THANKS!!

for BA particularly, you will flash direct from your computer.
I dont know whether your Vista is compatible with the flashing software, but XP surely does.
Do further reading, I am sure u will understand what I mean.

And a comment for the bootloader problem: first you put the device in bootloader mode, then you put it back in the cradle. Simple as that.

ALL DONE
All sorted cheers, WM6 up and running, i did a bit of fiddlin and away i was, no need for bootloader as it did it itself, it would not use vista so i use xp with active sync. cheers all

Related

Why ActiveSync always disconnects the BA while upgrading to the new ROM.

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.

I desperatly need help!!!!

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.

I-mate JAM problem, URGENT.. Please help?!

I have a problem with my I-Mate JAM, It loads the OS.. but after everything Installs it converts to the BootLoader screen, and remains unuseable.
If I rest the phone, it loads straight to the Bootloader screen, but if I take off the Battery cover, leave it for a few seconds, then replace it and turn the phone on... It will load the OS setup again, but go back to the BootLoader.
So how can I fix this, and what must I do? Please help me ASAP. The Rom/OS is Windows 2003 SE.
Thanks
Sikuri
try flashing the ROM to a latest windows mobile, i encountered this problem on my HTC Magician, i downloaded the compatible and latest windows mobile for my phone extracted the files on my PC and while my phone is in boot loader mode i connect the USB to pc cable (you'll notice the serial changing to USB) after that i run the update.exe on the files i extracted and just follow instructions on the updater. And now my phone is fix. Hey im not an expert on this, I got thru it by reading the forums here, and there are more experienced experts in here that you can ask. Hope this helps and give you an idea. By the way run the update.exe on a Windows XP machine for it to work perfectly.

upgrading rom

friends...mine is an 64 MB O2 Exec tomal build device
n i tried to upgrade it using Uni_21127v2.3-64 but my phone got
switched off n since then it stays only in the bootloader mode n ntn else happenes even if i remove the battery n again insert it, the device still stays in the bootloader mode...i dont knw wat has happened to it...as i dont havemuch knowlege about it..plz can anyone help me out n guide me...n m also in search of wm 6.1 or 6.5 rom by tomal...any help wud b appreciated....
Welcome to forums
Have a deep read on the Wiki
Good luck,
.... =]
if you cant find the usefullness in the wiki, firstly
Basicly the ROM hasent loaded propperly, but your uni can be saved.
So firstly,
what Operating System (Windows XP / Vista / 7)
1. Windows XP - good, as you can reflash quickly
2. need to load Windows XP as a VM (Vista)
3. Need to load Windows XP as a vm (Vista)
I would download a different ROM just to reflash with, say a tomal rom
then connect your uni to your pc, and let activesync give its nodification, then open the RUU and your uni should load the rom you have selcted to flash,
Flip, that shows how much of an ORD i have... now am writing tuts on re-flashing phone... HELP HELP
rom upgrade on locked sim?
just wanted to ask if one can upgrade the htc universal to wm6 even though it's locked on orange sims.
Thanks
Welcome to forums
More than one can upgrade ROM
Just be sure to read the Wiki instructions
Good luck,

how to upgrade the bootloader?

does anyone know how to upgrade the bootloader on the himalaya at the moment mine reads at the top of the screen SERIAL and at the bottom V1.01.
I have a file which i think is a upgrade [boot_1.06.nb0]
but i have to need to know the do's and dont's as i would think this would be if done wrong brick my himalaya?
any help or links would be thankfull?
advanced15 said:
does anyone know how to upgrade the bootloader on the himalaya at the moment mine reads at the top of the screen SERIAL and at the bottom V1.01.
I have a file which i think is a upgrade [boot_1.06.nb0]
but i have to need to know the do's and dont's as i would think this would be if done wrong brick my himalaya?
any help or links would be thankfull?
Click to expand...
Click to collapse
The only one question is
Why the hell you want to do that?
I have 1.01 also on my second today-use himalaya and it is really stable and works same as 1.06, but has some debugging output in mtty which is so useful
I tried also to upgrade it and I failed.
I have an O2 XDA II with windows mobile 2003 on it.
When in Bootloader Mode it says v1.01
when connected to the PC it says USB so i know its working in its own little way
I am trying to upgrade it to windows mobile 6.5.
I have tried everything so far and searched forums and tried things suggested on them but i just cant seem to do it.
Can someone send me a guide on how to do it please.
id be very greatful.
Thanks in advance.
mikeymcmk said:
I have an O2 XDA II with windows mobile 2003 on it.
When in Bootloader Mode it says v1.01
when connected to the PC it says USB so i know its working in its own little way
I am trying to upgrade it to windows mobile 6.5.
I have tried everything so far and searched forums and tried things suggested on them but i just cant seem to do it.
Can someone send me a guide on how to do it please.
id be very greatful.
Thanks in advance.
Click to expand...
Click to collapse
Hay mickey tell me that are you able to sync data or contects,msgs etc with system without disconnecting ?????????
or sometimes connection disconnects automatically ????/
if yes then put something stable thing in between data cable & device.
reply soon
KAASHP said:
Hay mickey tell me that are you able to sync data or contects,msgs etc with system without disconnecting ?????????
or sometimes connection disconnects automatically ????/
if yes then put something stable thing in between data cable & device.
reply soon
Click to expand...
Click to collapse
if anybody have same problem do as per my suggestion
put something in between data cable & device if you connect it without disconnection then it works flash the rom after putting it in bootloader mode
Don't do it
the bootloader is the main program which executes the system programs so avoid to upgrade bootloder.
the result will be permanent damage to your lovable device...
it can't boot more. so be careful.
no need to upgrade it as per my suggestion.

Categories

Resources