Hi guys, I couldnt find the solution to this in the forums so I thought I would contribute my own.
A few moments ago I ran a rom upgrade to to get rid of the O2 rubbish in an effort to fix my TT5 SatNav/Phone problems. However, half way through, my computer crashed. I soon discoverd that the pda was dead (would not load past the O2 screen even after a hard reset) and ActiveSync couldnt see a connection to re-run the upgrade again. :shock:
Solution:
1) Hard reset the pda with the addition of also pressing the navigation key. The PDA screen will go black and say 'Serial'.
2) Run the upgrade software again for whichever rom you choose.
Sorted!!!
Related
Hi all,
Im looking for some advice to restore my XDA2S. My pc crashed through the o2 upgrade process and Im stuck in bootloader - I cant create an active sync session to run the upgrade again. Any help appreciated.
Sorted It.
OK, sorted. There were lots of similair posts with no reply, so here goes.
Disconnect from cradle
Disconnect battery.
Reconnect battery
Hard reset the device
Insert into cradle - activesync wont start.
Run the upgrade.
Be patient, it takes a while to recognise (at least a few minutes).
Thank God!!! Now have a copy on my SD card.!!!!
Rom upgrade
Thought I'd broken mine within 6 hours of having it too! It all goes wrong if you don't power the docking station. You method for recovery is quite right and it's how I got mine back from the boot loader. Are you suggesting that you can upgrade from the SD card as well?
how long does it exactly take to respond?
PLEASE HELP! i have a xdaIIs i only see on the screen serial v2.07 when i press on, soft reset button and the volume bar nothing happens! i have the rom on a SD card. what am i suppose to see on the SD card? PLEASE HELP!
not to worry, bogs
i had the same problem once, just follow the procedures eskimofisherman gave in the 2nd post and it'll be ok
hope this helps
upgrade problem
had exactly the same thing happen to me!
hard reboot the xda2s
powerbutton held, push bottom reset.
reboot PC reload software ie Xda_IIs_v131139_upgrade.exe then when asked put pda in cradle.
worked for me.
although i have to say the upgrade is ****E! tom tom navigator doesnt like it at all, we were better off with the old one.
I'm trying to find out where to get a copy of it.
http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades
This is the second time in two days.
After upgrading my Diamond to official ROM 1.93 ITA it happened for the second time (so far) that it crashed while it was in standby. I couldn't receive calls/sms nor turn it on pushing the power button. I had to remove battery, wait a few seconds and then re-insert it soft-resetting the device.
Did anyone experienced the same problem ?
I've never had such a problem on the 1.93 WWE ROM.
Work Ok for me no problem so far, did you make a hard reset after you flash the rom? I allways make that after a flash even twice
I installed the .93 official ITA rom from HTC site three days agò and no problem so far.
I have had also one 'hang' when the device came out of stand-by. The screen was messed up and the device hang completely. I did it a soft reset and it worked again.
Take out Sim Card and hard reset.
help foor ?
where would i find my sim card and how would i remove it? I have the
Sprint HTC Diamond
My diamond keeps resetting itself to the splashscreen page and goes no further. I try to hard reset and it will just get me to the same splash screen as I got before and it won't go any further into the hard reset.
I think that if i can get it to do the hard reset, that i would be ok and be able to get rid of the ROM that seemed to cause this situation. I had last put SwiftBL-WWE-Diamond-v7-0-Full-16MbPP on my unit and this started happening right after it was done.
I am open to any suggestions that any of you have for me. I haven't been without a phone or my pda for many years and don't know how long i can go without before happens.
Dorothy
ezzie said:
where would i find my sim card and how would i remove it? I have the
Sprint HTC Diamond
My diamond keeps resetting itself to the splashscreen page and goes no further. I try to hard reset and it will just get me to the same splash screen as I got before and it won't go any further into the hard reset.
I think that if i can get it to do the hard reset, that i would be ok and be able to get rid of the ROM that seemed to cause this situation. I had last put SwiftBL-WWE-Diamond-v7-0-Full-16MbPP on my unit and this started happening right after it was done.
I am open to any suggestions that any of you have for me. I haven't been without a phone or my pda for many years and don't know how long i can go without before happens.
PS I don't think this is the right thread to ask your question, but w/e...
Dorothy
Click to expand...
Click to collapse
The problem with your phone is that you used a rom that is intended for the GSM version Diamond, and the Sprint one you got is a CDMA, so there's no SIM card in the Diamond you got. You should just try to get into bootloader and go from there...
sorry, wasn't able to find a thread that addressed this. I can't get into bootloader. any idea's how to get into it other than the vol down/reset?
Nevermind. Sprint is sending me a new one. they said it was looped and nothing can be done.
Three questions
MY computer has vista so it has no active sync
also my diamond is ****ed all the sudden it got stuck on the screen where it says windows mobile
so how can i install one of the rom that you guys made
but my phone doesnt actually start and y computer doesnt have active sync
so how can i install a rom on my diamond
does any one know???
i really need help guys thanksss alot
i didnt even download or any thing on my phone
it just stopped working suddenly
when i turn it on
first its the touch diamond screen then bell screen and then green sscreen saying windows mobile and it gets stuck there
also i cant hard reset it
i have tried every thing in the worlddddddd
vol down and enter both at same time then reset it then took the pin out kept my fingeres on bol down and enter key and it just goes to touch diamond screen the first one doesnt hard reset
Problems, problems, problems....
Firstly, Windows Vista does have ActiveSync... it's just 'under the skin' of Windows Mobile Device Centre.
If, as you say "It just stopped working" and you haven't done anything, the obvious answer is to get it replaced or repaired under warranty. The Diamond only came out last May, so none of our devices are out of the one year warranty period.
What's more likely is that you've tried to flash a ROM to your device without reading and understanding how to go about it. Either way, you need to search the 'Diamond ROM development' forum... you will definitely find an answer there.
Just one more thing, without trying to give you a lecture (which I often end up doing without intension ), you'll get a better response from the forum users if you keep your posts short and 'to the point'. Asking a load of questions all at the same time just puts people off wanting to help... very time consuming is this!
I appologise for the rant, I really am trying to help
Hello
Ive finally got round to putting new radios and ROM on my diamond, a year after buying. Didnt want to before now incase i cocked it up (theres a lot of things to remember!)
Hard SPL went fine and i was putting the new radio on (1.00.25.05 in this case) when, at about 80% of the way through the install my pc froze (as its having a habit of doing at the most awkward times recently!)
I soft reset the diamond but now its at what i assume is the bootloader screen (?), its got red, green, blue and white bars and various writing, along with a message saying 'Upgrade ROM code error Please try again'
I had a hunt round and found something for another device saying how to get it back by loading a factory ROM through the bootloader menu but i dont know how to do this as i dont have a connection to activesync (phone wont go beyond this screen) etc.
If someone could explain in relatively simple steps it would help!
I should also clarify that the only way i can get this screen off is to remove all power but as soon as i put power back on it loads up direct to this screen again!)
When you device is in bootloader mode, you dont need active sync connection. just run the update utility and it will work without it, as it uses different drivers when connecting.
This turned out to be quite easy actually, i stumbled across the answer somewhere else!
Thanks for the help
I've two problems which lead into one big problem.
First im stuck in the bootloader mode. Every time I start the Qtek 9090 it's in bootloader mode (btw it says v2.06 on the bottom). When the reset button is pressed the normal WM 2003SE should start, but there's always the bootloader. I've tried reset, hard reset and camera+power+reset. This problem exists since I used EnterBL.exe, when I used camera+power+reset, I were always be able to get back in the normal mode. I read suggestions how to solve this problem, but they contain ActiveSync. This leads us to the second problem.
I'm not be able to establish a ActiveSync (V4.5) connection when the BA is in bootloader mode. It worked perfect in Windows 2003SE. In bootloader mode the BA says "USB" on the display and XP shows the device in the device manager (I hope that's the English name, it's just a translation from the German name), but ActiveSync doesn't find a device.
I've shriked extrom to 128 KB, because I wanted to upgrade to Win 6. Maybe that's necessery infomation.
I hope someone has the answer for my little problem, because my mobile phone is currently just a expensive paper weight.
welcome to the forum!
no, it's not an "expensive" paperweight.
let me please first say, stop messing around in the device manager (yes, that is the correct name), everything is just fine, it is normal that it does not connect as usual!!!
you are exactly where you should be, and apparently you already read about how to basicly get to wm6. ok, let me explain...
since you already your extrom space, you are ready for upgrading, and that is what the bootloader is for. of course you don't start the bootloader and try and reset again, the bootloader is for opening ports to access the rom, which, otherwise would be rom=READ only memory.
another thing is, the "serial" changes to "usb" when cradled. that is no problem, that's perfect.
you are now at the point where you take the rom (nk.nbf file) and put it in a folder containing the RUU (rom upgrade utility, basicly a bunch of files named maupgradeut_noid, enterbl, getdevicedata and so on, you know where to find those apparently )
and start the maupgradeut_noid, then the rom flashing begins. after it is done, you simply perform a hard reset, but not the old fashioned way (power+reset). wm5 and above use another hard reset.
you have to press power+reset and then quickly press camera+record to access a boot menu, then you use the camera and record button to switch the options in that menu to say the following:
clear registry hive: YES
format storage: YES
enable kitl: NO
then you confirm that by pressing the mail button, your screen turns white and after a short time you are done, and wm6 will start for the first time!
have fun!
with best regards
Chef_Tony
Thanks for your effort, now it seams that think are not so bad as I thought.
I did all the steps, but I was uncertain wheater maupgradeut_noid worked right, because the program didn't show the versions of the mobile phone's software. So I thought it wasn't correctly detectet.
So it's normal that these informations are not shown by the program?
After these incidents I'm a litte bit afraid bricking my beloved BA.
that depends, my upgrade utility never showed any information on the "from" side, just the version of the rom i was going to flash, and it is fine, for some people it seems to show all the information after killing active sync first by opening the pc's taskmanager, and kill the wcesmgr and wcescommmgr processes, i can't confirm the file names though, as i have wmdc because of windows 7, but you should be able to find the active sync related processes yourself. maybe after killing them, you have all the information there.
if there is no information at all, then something went wrong and you should start playing around until you find something there again. but even if flashing wasn't successful, you would realize that, because it would be awfully fast, and nothing would have changed to your device, or it would be formatted, but nothing bad like "bricking" would happen there, you can always re-flash the device, and if you actually got stuck in bootloader, which is totally different from your situation now, you would still have ways to get the device back to life, but that is very unlikely and you are right to ask first, but you are fine so far.
You made my day!
It worked just as you said. Now I've a proper running WM 6.
Thanks to Chef_Tony and the other people putting their effort in the community.