I've recently upgraded my MDAc with the T-Mobile 1.13 ROM upgrade from their website.
Everything else seems to be fine except for ActiveSync, it's very tempremental- I managed to sync up data on the first connection but later that same day, I connected the device again and it doesn't seem to do anything except charge. I don't even see the AS tray icon either.
Anyone else had similar problems (and solutions for it)?
Thanks.
Had same type of problem myself, fix was to shut down Activesync on computer completly and deinstall, the reinstall active sync(3.8.0) connect device and give a new device name.
Ok thanks- I will give that a go.... I've got AS installed on 4 PCs :shock:
Still doesn't work- I remember actually trying re-installing AS on another machine with the same result.
Think I may have to go back to the 1.12 ROM.
Try hardresetting device sometimes it takes more than one go to get it stable!!!!!!!!!
I've tried about 5 hard resets now...
But it seems to work for the first couple of times then no more.
Another thing, I tried installing Card Export again and the icon for that also does not show up on the tray.
Anyone know if it is possible to downgrade to 1.12 with a shipped ROM?
If u get an AS connection that is stable then yes
Just to 'close' the topic; I went back to 1.12 ROM and all seems fine again.
Hey guys!
While working on my PPC this weekend, I noticed that the system froze while just trying to open NYDITOT Virtual Display.
I tried doing a soft reset and after doing so the system freezes at the "Welcome to T-Mobile" bootup screen and it does not go into the OS (windows Mobile 2003 "Non-SE")
I tried pushing the soft reset button with the device OFF, without the battery, without the sim card, and nothing seems to work.
I cant even re-load the original ROM as Active Synch doesnt see the device due that I dont get into the OS.
Now luckely for me, T-mobile advised that i only had a 3 month warranty with them, which of course "expired" so i was hoping someone could suggest something that might help me resolve this problem.
Any help will be greatly appriciated.
Will V.
Hello friends, this is my first post in prophet forum, though I had been a ppc user for more than 2 years. 5 months back, I bought an O2 XDA Neo, which was loaded with a dopod rom, with numbers coming up as 2.09.001 etc during startup. Shortly after purchase, I flashed with RUU_Prophet_220734_2207114_024721_QtekWWE_Ship rom. Everything went on well, and I was using the phone without problems for the past 2 - 3 months. Well not exactly without problems, some times when I reset the phone, it gets stuck at the spl, ipl screen, and I have to reset again many times to get it to load windows. I initially thought the problem may be due to the battery not being charged fully, but later I found that battery charge is not the problem, as the phone not booting became more and more common even with a fully charged battery. Even when I managed to get the phone started after repeated and frustrating soft resets, I started to get corrupt PIM data, like the contacts and calendar applications not starting up. ALso strange folders with name y? and y?? appeared in the phone memory. THese folders could be deleted only with Resco Explorer. Also the bluetooth was not working properly, that is when I turn it on using the comm manager, the blue tooth icon gets activated but actually no bluetooth is turned on. Later after a soft reset, bluetooth turns on but now the icon in comm manager is not activated. I did a hard reset a couple of times thinking that this problem will be rectified, but all the problems continued.
Going through the forum i read some where that JAMin_WWE_213923_2139123_022021_ship was one of the most stable roms for this phone, so I set about flashing this rom. I used ROMUpdateUtility-NoVendorID and the update went on till 95 % when it showed error 326. I tried again, with the same result. I later flashed RUU_Prophet_220734_2207114_024721_QtekWWE_Ship back, and the phone is working as before.
NOw I would like to get the following problems corrected
1. Phone getting stuck at ipl, spl, gsm screen
2. Proper working of bluetooth as I would like to use it with my BLueant Supertooth II
WHat will be the correct these prolems ? will the imate rom correct these problems, if so how am I to go about loading it ? or is there a better one than what I am having now ? or is it a HARDWARE problem ?
I am very sorry for this extremely long post, but I felt if I said all my problems in one post, I would get better response.
PLease help....
You should have stayed with the RUU_Prophet_220734_2207114_024721_QtekWWE_Ship ROM from the beginning, since it's the best and also latest official Prophet ROM. It's a 2.20 ROM which is the latest available.
GAMBIT999 said:
You should have stayed with the RUU_Prophet_220734_2207114_024721_QtekWWE_Ship ROM from the beginning, since it's the best and also latest official Prophet ROM. It's a 2.20 ROM which is the latest available.
Click to expand...
Click to collapse
I am still with that ROM. It is with this ROM that my prophet is causing the above problems.
Can you guys advice me how to load JAMin_WWE_213923_2139123_022021_ship rom with out this error 326 showing up ?
hi! i have an imate spl which was working ok. suddenly the camera stopped working, the camera application just freezes and doesnt switch on at all. the windows mobile busy cursor just keeps running. also, the task doesnt show in any of the running applications.any help available??
Hard Reset or update software if it fails stil could be hardware failure
Im screwed!
tried ahard reset. attempted a rom upgrade. went fine....but had a power cut in between so my phone now shows a white screen which says update again, connect usb and wait. any way to get around that? i have my limited warranty intact. will this cover it? it was an official rom i tried to upgrade to, by the way. can u help?
I have been having this error where the phone prevents itself from booting, showing a screen that tells you to connect to PC , for a while. Only way to fix it is to remove the battery and restart but that is just a temporary fix. What exactly is this? What causes it? Is it a software issue or a hardware issue? Should I get an exchange or do you guys think this will be fixed with the next update?
Thanks
Never seen that error message. I'd say reset once, if you see it again, get it exchanged.
Yea this my 4th HD7 it shows the error code when you plug it to the PC in zune. Funny thing is that I owned a speck case and I reboot the phone in the case till then. This time i pulled the battery out, put it back in and powered the phone on without the case and it is working fine. I guess the case is pushing down a button or sth and that prevents the phone from working properly. Very weird..
Hey there! I've been having the same error! This is my 2nd HD7, I own the Speck case and I do not think its the case. This issue is happening on mine with or without the case. Pulling out the battery just doesn't cut it. I have to:
1. Remove the battery
2. Plug the USB Charger
3. Insert the battery back
4. Turn on.
I love the phone but this is really frustrating!
Edit: Too bad I can't post the link to youtube due to member status. But the video is up just search for it "c101002e"
Just happened to me too. First day using the Speck case too and i let the battery drain till it died and upon reboot it showed the 'plug into computer' screen. Hope it is just the case causing problems.
did you all updated the sd card ?
you could try to reflash this rom (if you are on t-mobile USA ) http://forum.xda-developers.com/showthread.php?t=810346
Take this one "RUU_Schubert_TMOUS_1.20.531.01_Radio_5.51.09.11a_2 2.31.50.09_Signed_SCHUBERT_RELEASE"
its just the stock tmous rom .
Weird coincidence that all of y'all are using the same case. Maybe it is damaging on of the buttons?
nrfitchett4 said:
Weird coincidence that all of y'all are using the same case. Maybe it is damaging on of the buttons?
Click to expand...
Click to collapse
somewhere on the board they did tell that this case make the buttons really sensitive and it make the phone unusable .
theres a thread on tmobiles forums talking about the same issue, and most if not all the people there have the speck case. Someone says they tested it with and without the case and came to conclusion that the case is putting too much pressure on the camera button, which seems to be causing the problem.
would post the link to the other forum but i cant find it lol
pierce_m said:
theres a thread on tmobiles forums talking about the same issue, and most if not all the people there have the speck case. Someone says they tested it with and without the case and came to conclusion that the case is putting too much pressure on the camera button, which seems to be causing the problem.
would post the link to the other forum but i cant find it lol
Click to expand...
Click to collapse
Yea that was pretty much what was happening to mine. Although I remember trying to boot it without the case and having the same error before so what I did that I did a hard reset ( press power and both volume buttons at the same time) then when the phone booted, I rebooted it without the case immediately and its been working no problem since. I am pretty sure that case pushes the camera button since it grips the phone very tightly. I even overloaded the ram by opening lots of apps that runs in the background and then rebooted but it is working perfectly fine as of right now. Weird.. I am guessing its just a weird bug not a hardware defect.
I found it in a post in the mozart forums, so i tried it, as you do, cause its something new to play with cause my TP2 didnt like swimming, but anyway it was something about hoding down the camera button while power on, and it brought up a picture of a phone and cable and instructing you to plug it into a pc and when i did it started Zune and something about restoration error, so like in the previous posts it may be a stuck or faulty button somewhere on the phone that is causing it.
i didnt watch the video so if that had it in it never mind
cheers
Today 11 April 2011 I got notification about NoDo update for my phone.
It is HTC Mozart on Orange France network.
The pre-NoDo update was istalled about 20 days before.
The update got stuck at step 8. It seemed I had an unusable phone. In a periodic reboot mode into the update screen.
I checked on my W7 64 bit laptop the relevant backup folder, where all my phone data was supposed to have gotten backed up during the update. The folder was empty.
I therefore realized my phone got its rom corrupted during the update and I could not get back my pre-NoDo backup, since this latter was missing from my laptop.
Zune was on no help, stating a C101002E error.
The Windows Phone Support Tool was also of no use, reporting an error code while trying to restore my data.
XDA-forum provided me with a solution:
I went here
http://forum.xda-developers.com/showthread.php?t=1000781
and downloaded both bootloaders with relative roms.
After getting into the bootloader screen (red, green and blue screen), I installed the first ROM provided by Ansar. This could not install succesfully.
With the bootloader tool I could nevertheless confirm my idea I did not have anymore a functioning rom into my phone.
The second rom, the one ending with "Signed_by_ansar" could be succesfully installed.
I now have a Mozart fully functioning.
I had to restore my windows live account, Gmail, etc. My apps did not come back up after syncing with Zune.
I realized I just lost all my SMSs and home screen settings.
My phone was originally network unlocked and remained as such.
I got a notification that there is an official update for my phone the first time I rebooted. I will wait before attempting this update. The ROM by Ansar has got anyway copy/paste, being a NoDo ROM.
The ROM from Ansar, although for Orange France, removes the Orange splash screen when the phone starts. I guess if I need to use warranty on this phone right now I may have some issues with Orange France. Maybe when I update the phone following the update notification I got, I will re-establish a fully certified Orange ROM.
i9o pls and any one pls help me , i faced problem with [260] connection problem between my hd7 and pc vista 64 bit, actually i followed to steps in forum (error code C101002E) and drivers were installed (htc usb sync) before i started to flash rom NoDo bootloader 1, But no way still the problem [260]. i also tried another RUU htc asia xxx707xxx. because i have spl 1.23.2250.0(112138).also some links of RUU to download signed by ansar disappeared in rapid and other sourses, pls help to solve connection problem
Microsoft has release the Windows Phone Support Tool to fix this problem: http://support.microsoft.com/kb/2530409
WPS doesnt help in my case, Im malaysian and thought that need Asia RUU, but when i tried Europian RUU it nicely works, maybe because of i have 8G phone. the RRU is RUU_Schubert_HTC_Europe_1.69.401.01_Radio_5.54.09.21_22.33b.50.10_Signed_SCHUBERT_RELEASE(2)
day2die said:
Microsoft has release the Windows Phone Support Tool to fix this problem: http://support.microsoft.com/kb/2530409
Click to expand...
Click to collapse
Do you know what this tool does to the computer?
I would try it but honestly don't want to do it before I have info what it does to my PC settings. Unfortunately MS doesn't share with this knowledge.
Hi everyone!
I have a big problem with my new hd7.
Just bought, and wired for the very first charging but the phone continues to restart by itself.
Tried a hard reset, to set it in download mode and fix with Windows Phone Support Tool but still nothing to do. Even tried to install a new ROM but at the first start it continues with its loop.
In download mode zune tried to upgrade to nodo but it shows the error C101002E.
Don't know what else to do. Any idea? It's new!
MusicMan587 said:
Hi everyone!
I have a big problem with my new hd7.
Just bought, and wired for the very first charging but the phone continues to restart by itself.
Tried a hard reset, to set it in download mode and fix with Windows Phone Support Tool but still nothing to do. Even tried to install a new ROM but at the first start it continues with its loop.
In download mode zune tried to upgrade to nodo but it shows the error C101002E.
Don't know what else to do. Any idea? It's new!
Click to expand...
Click to collapse
No one had this problem? am i the only unlucky on the earth!?
Return for warranty replacement. Your phone is broken.
Thank you...i hoped i could solve it to not to wait september to have my phone back.