Hi everybody and sorry for disturbing you guys.
I've got a very strange problem with my friend's O2 XDA IIs (BA Device). The unit was upgraded to WM 5.0, however, I could not HR it. When I Reset the device and press Camera and Record button simultaneously (to make three lines appear), it is possible for me to move up and down and change the options but I can't finish the HR process by pressing the Messaging Button (it does work normally, not a physical prob). Besides, when I tried to upgrade the unit to another ROM (my friend was fed up with the current ROM since it was too slow), the unit couldn't recognize an USB Connection when it was in Bootloader mode (it could sync normally with my PC, already tested this). The screen kept showing Serial at the top and v2.06 at the bottom. As the result, no ROM upgrade Utility could do its job.
I've been using Pocket PC Phones for 2 yrs and this is the 1st time I've seen this problem, even though I used to use a MDA III for half a year.
Looking forward to hearing from you soon.
Tks and rgds.
Same here - device no longer recognized as USB in bootloader mode Previous ROM? helmi_c 2.3
In one of helmi's posts, he mentions something called "clearstorage". This might be what you are looking for. See here:
http://forum.xda-developers.com/viewtopic.php?p=356258#356258
After some playing around I have noticed that my BA hangs in BL mode, sometimes before I put it on the cradle, sometimes after I do that :/
try mtty software
it might be helpful in your case
search the forums for it and for available commands
Related
tried to upgrade my XDA to 2003 microsoft, i reset the phone, and now its just dead,i can't even boot to bootloader, PLEASE HELP!!!!!!!!!!!!
Have you used the reset hole under the headphone socket. Push once then push once more after 60 seconds.?
yes tried that,follow your instructions and all that happened was the internal lights came on,and thats it,even tried the bootloader again and still nothing,i can't even use active sync to flast the rom again.please help its doing my head in now.
dead xda
Do you mean an XDA 2? Because I've just done the same thing. And am (or have been)tearing my hair out too.
Then having got it into boot loader mode (which is tricky) and then cradled it I tried getting active sync 4 to find it but it couldn't. In despair I did bootload mode again and cradled it (grey screen says 'USB' now) and ran (and I can't encourage you to do this of course since it is illegal probably) a beta of mobile 2005. Now this found the mobile! And it's ...at 98% installed.
Watch this space...
dead xda
and no (karma comes home) it doesn't work: get a message 'device authentification failure consult the product maufacurer..."
Damn
its an XAD 1 AND CAN'T EVEN GET THE BOOTLOADER UP ANYMORE!!!!!!!!!!!!!!!!!!!HELP
PLAN B
O.K
(it's worth saying this all started because my pc crashed during an upgrade to the legitimate 2003 final rom for XDA 11. )
I couldn't get this installation to restart (I think because I expected active sync to say, 'yes, found the device' before re-installing - and it doesn't seem to need to do this. Or maybe not. Perhaps I'd just stuffed up getting it n boot loader mode? Who knows. Anyhow. Having another go at putting the legit rom upgrade on now. Fingers crossed & much praying.
dead?
I suspect that for you (and possibly for me also - the jury is still out on my machine) we may need to say hello to our local phone shop in the morning. But that's not the end of the world - tho' it'll probably cost a few £.
undead
Note to self: have a look at other massively helpful forums on this site before doing dumb stuff! There are smart and well-informed people who have all the answers. (notably RAGO in the "stuck in o2 Splash screen forum")
Yippee
(I send apologies for posting all this in what I now realise is totally the wrong forum. (Newbie!)
Adios!
I had just the same problems,
I removed the battery & Sim
I held in the power button and reset button at the same time
but kept them both pressed for 1 min!
I Put the battery & sim back and it all seemed to reset.
Fluke?
not to sure yet but i had no problems
after.
Mac.
I, have Siemens SX66 GSM ( PH20B) Upgraded to wron version and now it boot with colored horizontel straps (red,green,blue,white) and goes to WM 5, with slow to none functions and also lost radio.
Now I, tried with several WM5 versions and it display error message ( Model ID error 100) Can some one help how to remove / clean it and recomend working WM5.
See some post at the bottom of this topic
If you you have lost the Radio, ie, no version number is displayed on cold booting/hard re-set, then all is lost.
As i had the same problem with a phone I was given to fix.
As most/all of the Upgrade programs Check to see what Radio version the phone already has, and if it cant see one it fails
My only course of action was to get the Phone fixed under warenty
Read all about it here
Hope.......
Mine did the same thing, it was sooooo slow that I was thinking about buying a new unit but at the last breath I did the following and it worked:
- Go to the BootLoader screen (Press: Power Switch+Media Player+Recorder+Rest) all at the same time, your PDA should say “Serial” at the top of the screen.
- Plug you PDA to the cradle and it should read “USB” at the top of the screen.
- Use At least TuMa 1.3 with Radio 1.13.
Note:
The upgrade EXE should load up with a picture of the PD at the left side of the screen that DOES NOT look like your SX66…it looks like an HP PDA…!!!
Mine came back to life but sometimes you might have to SOFT reboot your PDA to get the Radio to work (Hard boot then use a third party software to softreboot).
Good luck.
so using the MaUpgradeUt_noID.ZIP and radio rom only you were unsuccessful at flashing?
Black6spdZ said:
so using the MaUpgradeUt_noID.ZIP and radio rom only you were unsuccessful at flashing?
Click to expand...
Click to collapse
I, went through all upgrades without issue but now PDA is so slow it takes ages to change selections..
have you downgraded back to 03se and still have this issue?
You will have to follow the steps very accurately...if you leave any step out you might end up like me at the beginning when my device was sooooo slow it was useless.
I took these steps from this forum...try it
Best Luck…
Thanks for all help did every thing but still some of menu are so slow that take several minutes to open , still looking for some tips and suggestions or if some one one knows how to turn it back to W2003
I, remoed some of programs from my SX66 that seems to be causing problems and were npt compatible with and got my PDA back...its now working awsome...Thanks for all who helped
Hello,
I have been a member for about 3 months or so but not been a heavy poster. (sorry about that)
anyway I have a small problem which normally gets solved by a few searchs but I don't seem to be having any luck.
I Have an Orange build kaiser (installed the today screen) and have hard reset the device a few times after encounting the same problem again and again (about to hard reset for the 4th time i belive)
back to the point, the problem seems to be a simple one in that new SMS don't appear on my today screen... weired?! and last night was the worst my phone was on charge but in standbye mode but my girlfriend couldn't connect any phone calls and when i checked my phone i had a mountain of missed calls and a bundle of txts which all came through at the same time on wake up..
(I've mentioned the fact my phone was on charge because search results suggest it was due to a 30% or less battery)
when i had the problem before I thought at 1st it was one of the many many cabs that have installed so this time i made sure i+I only had on the minumal
(forgive me but with the phone not being with me I am not sure on the names but here is the list)
HTC Home (maybe an old verison but i have tried many verisons)
HTC Home customiser (with IPHONE apps theme)
TOM TOM 6
HTC touch Keypad
A program to stop the phone connecting to the internet
A program that on start up my phone switches directly to the Keypad
Like I said used to install loads and loads of cabs but now limiting my self to a few to try and rectify the problem.
any one else had this problem? should i send it back to Orange? (I have insurance), will there be problems reinstalling TOM TOM? is one of the apps i have currently installed a problem?
any help would be much appricated and thank you in advance.
Does it exhibit this behaviour if you leave the phone in shipped condition, with NO software installed by yourself? If so, then it's faulty; if not, then install your apps one by one and test until you find what's causing it by process of elimination.
thanks for the reply...
I was going to leave it this time around with the dreaded orange home screen, was hoping someone else had a simular problem with one of the apps i have already mentioned
I'll give it a go tonight and see how it goes
thanks again for the reply
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.
hi guys
got my htc diamond 2 yesterday. it's nto branded and it's not locked. it has a 6.1 windows on it. tried to do a hard reset but it did not work :| (took sim out and battery)
anyways...
as you imagine, I wanted to instal a nice ROM, so dowloaded 6.5 official ROM
when I try to instal it on my phone, after I press UPDATE, the phone goes on standby, active sync disconnects and the process of updating the ROM doesn't even start.
then I downloaded hard-spl, tried to install it but is says that the device is not connected to PC - although it is connected via active sync...
any ideas on how can I sort this out... your help is much appreciated!
forgot to mention some details...
when I try to instal a ROM, I get Error 260 (No connection)
I tried restarting my laptop, the phone and even tried on a different laptop - nothing works...
about the hard spl, I also instaled the required cab but nothing...
just hard reset manual...
hold both volumes and then hold power button
keep holding down until press "up volume" message appear to erase
after hard reset, use 1.83 HardSPL and after use whatever rom you wish
On e.g. Windows 7 you need to install another driver when TD2 is in bootloader mode (can easily be downloaded using winupdate while in bootloader mode).
BTW hard reset means pressing vol up AND vol down AND once reset button (with stylus).
HTC Touch Diamond2 SD Card ROM flashing
Look here: SD Card ROM flashing
Or Let me Google that for u.
DalvuS said:
just hard reset manual...
hold both volumes and then hold power button
keep holding down until press "up volume" message appear to erase
after hard reset, use 1.83 HardSPL and after use whatever rom you wish
Click to expand...
Click to collapse
thanks for your answer... I have tried doing the hard reset in all the ways, but it is not working.... i have tried with power button and reset button, while volume up and volute down were both pressed.. it does not work...
i've put a sd card in it and tried to run rom from there ... the way it's done is keeping volume down pressed and then turn the phone on.... the thing is that I don't get the tri-colour screen... it boots normaly and loads windows...
this is amazing... nothing seems to work on it...
Hard reset
Device must be turned off:
http://www.hardreset.eu/htc_touch_diamond_2_hard_reset_soft_reset_en.html
hmmm
@S-Line - i have tried on windows xp and vista... and hard reset does not work on my phone :|
@Tom Lenferink thanks for the idea, i've got a card, formated fat32, put a rom on it with name 'TOPAIMG.nbh' and tried to do volume down and turn on the phone... it loads normaly, doesn't go on the coloured screen...
any more ideas guys? I can see 2 things that can be wrong
1) is not hard slp yet
2) buttons don't seem to work, btu they work in windows mobile
fake fake fake
don't bother guys, i just realised that the phone I got is a fine fake after diamond 2.... sorry for the trouble and people who want to buy diamond2, be very carefull.... it looks identical, windows is the same etc
andreti said:
don't bother guys, i just realised that the phone I got is a fine fake after diamond 2.... sorry for the trouble and people who want to buy diamond2, be very carefull.... it looks identical, windows is the same etc
Click to expand...
Click to collapse
Interesting, it means that they even copied the serial number if you could download the ROM from HTC website.
Could you pls post pictures of your phone from front and back side ?
How do you know it is not real TD2 (I mean, what is the difference ?)
Post pictures and I'll do a comparison so others know what to look out for. They're very rarely identical.
Andreti ???
hi guys, I just randomly found this thread. been looking for a diamond2 from second hand. bought one a week ago and had exactly the same problem with flashing. after some time i realised that it was a fake clone ugly piece of junk.
so you asked about the differences, here they are:
- the one i had, had no front camera.
- overall build quality was weird, you could tell just by opening it and removing the batt. all the inside parts were somehow covered/sealed with a ducktape - really not htc style
- terrible screeen - terrible colors, contrast, brightness (my good old s710 has much better display), not calibrated - you had to push 2mm below the actual button, slow cpu (all i know it wast really fast, dont know about the speed of the original, never held it)
- no g sensor, no gps module. not sure 100% but it had a shortcut for external gps and you had to push a button to rotate the home screen (i guess both of these kind of imply missing these features)
- when i tried to download the official fw, imei wasnt recognised - which i think, is the best way to find out. after downloading fw from other sources, i got the 260 error.
peace and be careful
Most clones have a 3.5mp camera and 128mb RAM
hard reset
Just a quick note, I tried to carry out a hard reset as in the manual. I could not get it to work - until I found that if I removed battery, refitted it, then a hard reset worked every time. Read my new post to see why I had to do a hard reset....!!!!!