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.
Related
I was running the XDA-developers-SER-v12.exe from my laptop with my sx56 connected through the cradle beacuase it said to hook up to active sync. During the upgrade it said it couldn't verify a com or usb port or something like that and the upgrade just stopped. Now my device is frozen at Upgrading... and I'm not sure what to do. Was I supposed to connect with a serial cable to do the install. Please can someone give me baby steps - step by step, I'm not very good at this kind of thing. Thanks!
Hi ...
1. what was your original ROM version before the upgrade ?
2. Can your device be recognized by Active Sync ? ... if yes, go to \windows\startup and delete the upgrade batch file and soft reset.
3. Did you try a hard reset ?
No, my device is not recognized by Active Sync. I have tried a hard reset, but it has no effect, the screen is still frozen...
mbilson said:
I was running the XDA-developers-SER-v12.exe from my laptop with my sx56 connected through the cradle because it said to hook up to active sync. During the upgrade it said it couldn't verify a com or usb port or something like that and the upgrade just stopped. Now my device is frozen at Upgrading... and I'm not sure what to do. Was I supposed to connect with a serial cable to do the install. Please can someone give me baby steps - step by step, I'm not very good at this kind of thing. Thanks!
Click to expand...
Click to collapse
There still maybe some hope! Rerun the XDA-developers-SER-v12.exe and the upgrade should start where it left off, so give it a try.
If that fails your next option would be the SD card boot loader method. So if you don't have a PC SD reader plan on getting one.
HTH
Thanks for the advice. I tried re-running it many times, still no luck. It is still under warranty so I sent it back to Siemens, they authorized flashing the ROM. When it comes back, I now have the unlocking software from gsmlocker.com and I will start again.
Just tried to upgrade my S200 with a 9100 ROM ver 2.8.7.1 WWE (by mistake of course) and I can't turn it on anymore. Somehow it didn't even warn about wrong ROM.
Tried to hardreset it but no luck. When I keep the camera button it goes to RGB only when connected to the charger.
When connected to PC, the red and blue leds keep flashing and my PC gives Error 260 when I try to revert back to the S200 RUU.
Does anyone know how to bring it back to life? Is there a way to boot it from SD card?
-
I-mate Jam
Qtek 9100
Qtek S200
Don't panic!
I did the same thing some time ago!
What you need to do is make sure that the battery is fully charged. (The flashing of the screen can be a result of the flat battery.) Unfortunately, it is not possible to charge the battery when the wrong ROM is installed, as the ROM obviously tells the Prophet how to charge.
Let's assume you have an okay battery.
1) Start the Prophet in Boot mode. This is done by pressing and holding the Camera button and then pressing the soft-reset button. Keep holding for about 7 seconds, and the coloured bands should appear.
2) Connect to PC using the UDB cable.
3) Run the correct ROM upgrade. You do not need to be paired with ActiveSync, as the update programs are intelligent.
4) If the update does not work (and it fails at 95%), then try again. If it still fails, try again and do a soft-reset mid-way through. This will kill the ROM upgrade and you should then be able to do it fine after that.
The really important thing is that the battery is charged before you do this. Unless anyone makes a USB cable that can charge AND connect to PC, then a fully charged battery is a must.
Let me know if this helped.
Check this Out
one more step need to be performed which by not ticking off the ALLOW USB CONNECTIONS in the connection settings of the file of the activesync. After configuring it, it would absolutely carry out thy upgrading of ROM for thy Prophet which is in Bootloader mode. Good Luck!
Check this Out
one more step need to be performed which by not ticking off the ALLOW USB CONNECTIONS in the connection settings of the file of the activesync. After configuring it, it would absolutely carry out thy upgrading of ROM for thy Prophet which is in Bootloader mode. Good Luck!
Re: Boot from SD?
zealerc said:
one more step need to be performed which by not ticking off the ALLOW USB CONNECTIONS in the connection settings of the file of the activesync. After configuring it, it would absolutely carry out thy upgrading of ROM for thy Prophet which is in Bootloader mode. Good Luck!
Click to expand...
Click to collapse
I am a bit confused, does that mean that ALLOW USB CONNECTIONS has to be chacked or unchecked?
I did the same exact mistake. Now, my baterry is fully chaged (which I can check on another phone) but when I put it in S200 it shows that the battery has 0%. Conseqeuntly, when i unplug the power cord the phone dies. I have no way of running the new ROM on it. I tried running a bootable SD but it only installed part of the software. i read on this forum that such a thing happens and that one would need to run a full version ROM from a computer. So, how do I do it??? I am almost giving up all hope of ever making this phone work
Does anyone have a file to boot from SD and is it possible to run a full ROM from SD. Please help!
My o2 neo got stucked on the o2 reset screen.After going through this forum i came to know that few others too had this problem, so i went ahead with flashing of rom (RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_ Ship.exe) as suggested. But i am having a problem connecting my o2 with my PC using activesync 4.1 as well as 4.5 as it is required for the process. I tried all the option for connecting it through activesync, but it failed to connect. can somebody please help me with any kind of setting that is needed to rectifying this problem, I have also tried some windows firewall setting but it also failed to connect to my device to my PC. Pls pls pls pls somebody help
Ok, let me see if I understand you problem correctly:
You reset your Neo, and it won't boot past the O2 splash?
This kind of problem usually results from installing a program that runs on startup or changing some vital registry settings.
Have you tried hard resetting your device to solve this? It's simple: press and hold power + comm manager + camera the press reset. You should get a black screen with white text asking you to confirm clearing the device. All data and programs you installed will be lost and the device will return to the state you got it in.
I am not sure why you think you need to change ROM to get rid of this problem (unless it happens often for no operant reason) but if you still want to go through with it (I hope you understand the risks involved) you will have to hard reset your phone first so it fully boots in to windows before you can connect to ActiveSync.
Thanks for replying Levenum,
I have tried to hard reset it but nothing happens, it won't go past the O2 splash screen. I have ever install any program on it, it just happen that one fine day i found that my device was off and when i pressed the power button it got stuck on the o2 screen and remained there.
I have been using this Prophet for past 3 months but i have never ever connected it to my PC for synchronization, could this be the reason for it not getting connected to the PC with activesync. if so what should i do.
Even when it is in the bootloader & i connect it with the usb cable it shows usb written on down left corner of the screen, but activesync says device not connected.
pls help...
Ok, now I know changing ROM is NOT the solution for you!
Now, sorry for the stupid question, but is your device fully charged?
Let it charge for at least 3 - 4 hours then try again - use a wall adapter not USB from PC. (These things get stuck on splash when they do not have enough power to fully boot)
Assuming that is not the issue, since it is a new device I suggest you use your warranty (I assume its under warranty from O2) because your problem might be hardware. If you try messing with the ROM you will only void any warranty you have and then you might wind up with a very expansive paper weight!
Finlay, unless you can get in to windows you can not connect to ActiveSync. There are ways of changing ROM through bootloader, but they are complicated (and I am not familiar with them well enough to help you). Please read the WiKi.
Once again, I think you should send it in for repair as this might be a hardware issue.
My friend's jamin when he tried upgrading with smart1 wm6
after the flashing process finished it gives the 3 colors of boot loader
the screen flickers continously with the 3 colors
no way to hard reset the device
and activesync doesn't feel it
I searched all the forum for a problem like this but I didn't find any
any suggestion please, or any help?
Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.
NetrunnerAT said:
Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.
Click to expand...
Click to collapse
Please how can i flash with the activesync doesn't notice my device and where's NVID Rom
Ok. I'll search for it but please help how can I flash it to the device which doesn't recognized or felt by PC
If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now
divxmaniak said:
If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now
Click to expand...
Click to collapse
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.
must use NVID rom. maybe qtek nvid one from here? http://wiki.xda-developers.com/index.php?pagename=Prophet_ROMs
hasanemara said:
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.
Click to expand...
Click to collapse
If the problem still there, Try to release the battery for 1-3 hours and put it again to the device, go to the boot loader and pray. Hopefully it could work. Actually, this way worked on my Himalaya and Prophet.
Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).
ekto said:
Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).
Click to expand...
Click to collapse
I shall try and tell you the result
error 260 this is the result
i have a slight variation problem like this...
1. i was upgrading my O2 Neo to the latest WM05 & the phone went to bootloader mode & the upgrade started searching for the phone as normal..then some error & it stopped upgrading while the phone was in bootloader mode..
2. at that time,i got an urgent call & had to leave the phone in bootloader mode...
3. when i came back..the phone was dead & now it wont startup at all.. not even in the bootloader mode.
4. Maybe the batteries dead...so i charged it (Over night)..nothing happened in the morning..
5. kept the battery removed for about 5-6hours & still nothing happens..it simply does not startup.
6.I've tried holding the camera button & resetting, but it wont go into bootloader mode.
7. i;ve tried holding the connections button + camera button _ reset but it wont hard reset...
can anyone help me here...
what can i do???
hasanemara said:
error 260 this is the result
Click to expand...
Click to collapse
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.
ekto said:
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.
Click to expand...
Click to collapse
No I didn't change any and I can connect my o2 xda mini to the same cable
I want to ask few technical question
HOW CAN A SOFTWARE DAMAGE THE DEVICE?
CAN A SOFTWARE FOR EXAMPLE BURNS A PROCESSOR OR SOMETHING LIKE THIS?
If So there will be a big problem with those types of devices
a virus for example can destroy my device's board or processor!!
Yesterday My friend went to an I-mate customer service who tel him that
the board had been destroyed by the bad software !!!!!!!!!
Please Give me technical advice about this problem
and is there a web site for him to buy this board (i-mate jamin)?
I've tried everything... even tried it on my desktop... but my phone just wont turn on now. i've kept the battery removed for more than 8hrs now... i've even charged it for more than 8hrs non-stop..nothing happens..
maybe i should get hold of a charged battery & try it with that battery...?
Any clue how to get my phone started??
got it working !!! PHEW... i used my HP battery which was charged & put it into it..now i've got my bootloader & i'm installing the new OS as we speak... 15% done.... keeping my fingers crossed
done.. got my HP Ipaq battery , which was charged & my new started up in bootloader more.. PHEW !!!
66% done... keeping my fingers crossed
ok, installed...now, one more problem..my touch screen's not working...???
Any idea what to do?
i installed "Prophet_PDAViet_Step1"
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.