I'm opening this thread to find out the answer as to why the Hermes freezes or lockups on WM6.1. It gives you no other option but to soft reset. Unfortunately, it stays on your second splash screen after a soft reset; so, you will resort only to hard reset your device.
In some cases, it even causes to hard reset your device without warning after a freeze. It's not how long you use the device... it's what you are using most frequently.
In my observation over the last two weeks, it freezes in the following occasion:
1. restoring messages using dotFred PIM Backup
2. introducing exchange server settings
3. frequent closing and opening of SMS application
4. frequent sliding in/out of keyboard
To single out the problem, I have not introduced any changes to the ROM or even installed CABs. I am merely trying to use the base ROM like I used to with WM6.
I have tried various ROMs todate: Schapps, PDA viet, TNT, No ROM maker, Faria's and they all result to sudden system fault in the two Hermes that I have in my possession. I figured, this must be a 6.1 thing, but I noticed that it has not been given attention.
So, let us hear your freeze and hard reset problems on WM6.1 guys!
the only rom that hasnt froze on me has been CRC's rom. All the others seem to suffer from this weird problem.
After so many testing, one more would not hurt thanks for the feedback. Will give it a try.
tjlabais said:
I'm opening this thread to find out the answer as to why the Hermes freezes or lockups on WM6.1. It gives you no other option but to soft reset. Unfortunately, it stays on your second splash screen after a soft reset; so, you will resort only to hard reset your device.
In some cases, it even causes to hard reset your device without warning after a freeze. It's not how long you use the device... it's what you are using most frequently.
In my observation over the last two weeks, it freezes in the following occasion:
1. restoring messages using dotFred PIM Backup
2. introducing exchange server settings
3. frequent closing and opening of SMS application
4. frequent sliding in/out of keyboard
To single out the problem, I have not introduced any changes to the ROM or even installed CABs. I am merely trying to use the base ROM like I used to with WM6.
I have tried various ROMs todate: Schapps, PDA viet, TNT, No ROM maker, Faria's and they all result to sudden system fault in the two Hermes that I have in my possession. I figured, this must be a 6.1 thing, but I noticed that it has not been given attention.
So, let us hear your freeze and hard reset problems on WM6.1 guys!
Click to expand...
Click to collapse
I have semilar issue and now the problem is solved. please click on my signature below why did I go back to official ROM for the detail threat.
same here
i even got my device changed since i thought it was a hardware problem.
it only happens on wm6.1 though, so as much as i like the added speed and threaded sms, flashing the original wm6 rom fixed it and from there im going to keep to wm6.0 - it worked quite nicely.
I suspect (a lot) of bigstorage or some bug on the write-to-internal-rom cache/buffer (if exists) associated to any app that writes to fast to the ROM.
I notice when I use anything on SD card that nothing bad occurs but if I use the internal mem (SMS, internal apps, etc) it freezes all the time.
I had these issues until I used mtty.exe to clean up some bad blocks and then flashed Faria R32, since then no more issues (though opera 9.405 sometimes will freeze my hermes).
I had the same problem until I flashed the offical AT&T WM6 rom with radio and then flashed back to wm6.1..
No freezes or hard resets since..
I don't think this is a big storage issue... if it were, wm6.1 in other similar devices like the trinity would have suffered the same fate, but it doesn't.
I really don't see the point of going back to an ATT official ROM before flashing 6.1. But a lot has said that they no longer have this issue after doing so, then it must be RUU related.
It might also mean: a full ROM flashing for 6.1 might be necessary.
Either way, I'll continue testing, but it would be nice if other guys with this issue will be willing to help test it...
I just made some digging, and just found out how some wm6.1 users get their freezes/lockups. There issue was due to radio compatibility.
hmmm... if the WM6.1 ROM was built with OEM from the AT&T Official, then the radio that best match for it is from the AT&T as well.
This might explain that flashing the AT&T official prior to flashing the wm6.1 sets the radio to AT&T.
Hope this will solve the freeze/lockup mystery.
Have any of you guys tried changing/switching RADIO ROM while in WM6.1?
I just did, trying to experiment. Prior to WM6.1, I loaded an Official Dopod WM6 ROM. Then I loaded the Faria-R32 Full version.
Although, I did not have freezes on the first day of testing... I decided to switch to Radio 1.54 since most users flashed the AT&T Official prior to flashing WM6.1. Guess what? It flashed successfully and boot successfully for the first time. However, when I make a call, the audio has a very poor quality. So, I reset it using the reset button just to clear it up; however, it hanged on first screen... then I reset one more time, it hanged on 2nd screen, then I reset again, it hanged on WM screen.
Enough of it, so, I loaded back 1.47.0.10, and I'm back in business? No. The switching of the Radio ROM has caused the ROM to be corrupted... Somehow, the RADIO has something to do with the freezing...
WM 6.1 ROMs are very unstable (Faria, TNT, etc. I tested several, including those "naked" or clean)
After I install some (useful) software like HTC Home and some other 2-3 programs and after some hours it froze (it did with Faria, TNT, etc). TNT´s WM6.1 is a little more stable (takes longer to froze) but Faria´s WM6.1 is faster.
The more we use the internal flash memory, the faster it frozes and requests a hard reset. Since Friday I hard rebooted some 20x (Faria + TNT roms).
I´ll go back to WM6.0 for now.
EDIT: I installed my radio rom after the last main rom and works very well (I update all roms from the SD card). I updated before and after the main rom (but it never got corrupted) and they frozed. In my case nothing to do with the froze.
I nearly advised my friend to send for service thinking a big hardware problem. Thanks as now I know it's not the phone itself .
Hello,
I had the same problem when 6.1 came out on all 19199.0.7.0 builds. For me the solution was to update to a ROM using build 19199.1.0.0. Since then I had no hard resets at all (I am running CRCs PHK v12 Release 9 for about 2 weeks now).
Maybe this works for you as well.
Cheers,
Uli
mmick said:
WM 6.1 ROMs are very unstable (Faria, TNT, etc. I tested several, including those "naked" or clean)
After I install some (useful) software like HTC Home and some other 2-3 programs and after some hours it froze (it did with Faria, TNT, etc). TNT´s WM6.1 is a little more stable (takes longer to froze) but Faria´s WM6.1 is faster.
The more we use the internal flash memory, the faster it frozes and requests a hard reset. Since Friday I hard rebooted some 20x (Faria + TNT roms).
I´ll go back to WM6.0 for now.
EDIT: I installed my radio rom after the last main rom and works very well (I update all roms from the SD card). I updated before and after the main rom (but it never got corrupted) and they frozed. In my case nothing to do with the froze.
Click to expand...
Click to collapse
I don't think it's the way it's accessing the memory; otherwise, other devices would have suffered the same fate. So far, only the hermes suffer the freezing syndrome which means that there is something in the hermes that is not fully compatible with the WM6.1 build.
did you try to flash the AT&T build prior to flashing the wm6.1 build?
hukoeth said:
Hello,
I had the same problem when 6.1 came out on all 19199.0.7.0 builds. For me the solution was to update to a ROM using build 19199.1.0.0. Since then I had no hard resets at all (I am running CRCs PHK v12 Release 9 for about 2 weeks now).
Maybe this works for you as well.
Cheers,
Uli
Click to expand...
Click to collapse
I was hoping someone would release the 19202.1.0.0 build since it has the updated GWES...
After 24hours with Faria-R32 Clean version. I did not have any freezing syndrome. This is after I flashed with a Dopod Official ROM. I only got the freezing syndrome by flashing 1.54 Radio ROM.
My next move is to use a different RUU for flashing.
My Faria 6.1 also hard-resets and locks up
I had just recovered from a previous hard reset and read all posts in this thread and the other one currently dealing with this topic (http://forum.xda-developers.com/showthread.php?t=370185), and had gone down to a previous ATT radio rom and switched off SD power management out of desperation, when my Hermes locked up again. This time, however, after two soft resets (stylus induced) I managed to get it running again. Everything seemed to be in the previous state (all my preferences had been preserved), but I found that all contacts, history and calendar items had gone.
I had installed no other software than the network wizard. I had recovered most information from Outlook and the rest from Pimbackup (which by the way keeps crashing when restoring speed dials in 6.1).
As this must be the 6th hard reset in 6 days, I think I'm going back to Schap's good old 6.0 and wait for a solution.
BTW Don't take me wrong: I'm extremely grateful for all the great work done by the various cooks.
Lockups
I thought I was going crazy;my 8525 would lock up an have to be soft reset and when it came back, the contacts would all be gone.
I use Yahoo!Go to sync my contacts. I use Photo Contacts Pro for my contacts manager. I was trying to figure out if it was either of those causing the problem.
I even have a thread going on Microsoft's windows mobile forum about this.
I get NO answers from anyone. I'm running Schaps 4.30 OS and Radio 1.54.07.00. I have a 2gb sd card that I run a few apps from.
You just described the same problem I have. Thank you for confirming my limited sanity!!!
tjlabais said:
I was hoping someone would release the 19202.1.0.0 build since it has the updated GWES...
After 24hours with Faria-R32 Clean version. I did not have any freezing syndrome. This is after I flashed with a Dopod Official ROM. I only got the freezing syndrome by flashing 1.54 Radio ROM.
My next move is to use a different RUU for flashing.
Click to expand...
Click to collapse
If i could get hold of the 19202 source I would probably post a clean naked version for testing....but alas no such luck. Naturally it would help had i got a source for new ROM builds lol!
mrvanx said:
If i could get hold of the 19202 source I would probably post a clean naked version for testing....but alas no such luck. Naturally it would help had i got a source for new ROM builds lol!
Click to expand...
Click to collapse
I totally agree with you... when I cooked ROMs for the XDA Atom, I didn't want to work with none official ROMs because I wouldn't know what has been altered in the adopted device.
mda4 the problem is only getting worse, I'm from the 1.73 t-mobile version went to 1.93 and is now with swifb7.5 however
crashes every day (useful in conversations and your alarm clock to expire)
often with a soft reset after installation problems with startup touchflo3d and often error manila.exe below uberhoubt as he is already so far
hard reset is also often already halfway down.
In short ideal device to send back to my old mda3 again to use
But is it possible to go back to the original 1.73 Tmobile and where is it located?
Use Search
marz01 said:
mda4 the problem is only getting worse, I'm from the 1.73 t-mobile version went to 1.93 and is now with swifb7.5 however
crashes every day (useful in conversations and your alarm clock to expire)
often with a soft reset after installation problems with startup touchflo3d and often error manila.exe below uberhoubt as he is already so far
hard reset is also often already halfway down.
In short ideal device to send back to my old mda3 again to use
But is it possible to go back to the original 1.73 Tmobile and where is it located?
Click to expand...
Click to collapse
Hi there,
A simple search through the few posts below yours would have lead to here
http://forum.xda-developers.com/showthread.php?t=435826
However, instead of just giving up, why not try to find out why your device is behaving as it is..?
With a little reading, I'm beginning to get used to the Diamond and it's litte needs. Mine's running very well on a slightly older ROM from one of the developers on here.
I hope this helps answer your needs..?
Cheers,
thx for the answer,
I have tried my mda4 for a few months now but is getting every day worse and worse.
I have tried serveral roms now.
I don't know what else to do besides then sent the mda4 back.
I will try this rom to sent it back
http://forum.xda-developers.com/showthread.php?p=2600096
have you tried changing to a different Hard SPL. These can cause problems.
tried the HardSPL-1.24 and the Unsigned-Hard-SPL-Diamond-OliNex
I have downloaded the RUU_Victor_TMO_NLD_1.37.114.3_Signed_Diamond_52.26a.25.09_Radio_1.00.25.03.nbh
How do i start this file?
i have put the t-mobile file in the 1.24 map.
But the radio stay on 1002505?
rom is now 1371143.nld and till now no problems
Hello,
I have a O2 XDA Stealth, it has hanging habit. Sometimes at startup, today screen, during incoming call, while browsing etc.
It also has problem of missing shortcut. I did hard reset, but it got failed.
I have flashed the ROM but getting same problem.
I've googled for the problem but couldn't find any help.
Any help? I'm irritated with this problem, this doesn't seems more than a brick to me
Hey,
Which ROM do you have..... if Lesser than 6.0 than go to the link below and upgrade your ROM from there....
and strictly follow the Instructions there
http://forum.xda-developers.com/showthread.php?t=352468&highlight=o2+stealth
I can't start phone, how can enter to bootloader mode?
any help guys?
Phone is working fine now....installed WM5 and everything is working like normal
First off, great forums, it has been a great help so far. So i've just bought the Touch Pro 2 from Telus, great phone so far. But I've been having a problem everytime i'm in Updates and Events, I select Update and after a few seconds it crashes "A problem has occurred with manila.exe". Any help would be a appreciated.
ROM version: 1.19.661.3
I've fixed the problem but not the way i really wanted to. After a hard reset the error has gone away.
That sucks you had to hard reset but it was probably needed! Glad you got it working though. I haven't experienced this problem.
Thanks I'm still not sure what caused the error.
Here is the solution that I have found for manila.exe error
This same thing happened on my Touch Pro 2, all it really seemed to be is annoying. Functionality hasn't seemed to be a problem. All I did is turn off reporting to microsoft (there is an option to turn this off when the error comes up) and since then I haven't seen the annoying error anymore. Whatever it is doing to make this error may still be happening, but I am never aware of it and I have no problems with the phone now. I hope this helps someone else because I know that no one wants to do a hard reset on their phone.
I'm experiencing the same problem but on Hd2.I tried to copy my contacts from my old sim which is with O2 and starting getting this error every time I reboot my phone.'' AN ERROR HAS OCCURED WITH MANILA.EXE'' .The only way out is ofcourse the hard reset which is really annoying.If someone has a solution please do mention.
Regards
Hi everybody! The same problem with HTC HD2 and also the message error on services.exe. this happened sudenly. Then hard reset and all sems ok at the first. But on the way that I instaled all the programs both errors appears again. It's sems that the OS run ok. but I don't have found any solution
Regards
Hello,
Today i wanted to try the new 3volution rom for the s620 when i got an annoying bug
I spent most of the afternoon looking for an answer but found none.
Everything works well in the beginning until i got to push the center button for the screen to turn white. It turns white indeed but then activesync desynchronizes and doesnt resync anymore, so im unable to upgrade (either it stops at 3% or with kavana's doesnt detect old rom) and in some cases it says the new flash rom is corrupt..
Its like my 5th flash, and prior to today i never had a problem flashing and upgrading
So i tried reinstalling activesync multiple times, changing cables, even hard resetting my s620 (i got the nrg rose 1.7 rom on it), i even restored my comp on a previous state.. nothing
It just keeps breaking the sync when i push the center button and doesnt resync for the rest of the procedure
If someone has an idea im all ears ^^ and sorry it it has been already posted
Welcome to forums
Try a hard reset or reinstall ROM
Have a deep read here:
http://forum.xda-developers.com/showthread.php?t=537151
Hope it helped,
redownload the rom. then read this http://forum.xda-developers.com/showthread.php?t=493266
3% freeze up it very common
I am seing something similar. If I set my device down without locking it the screen goes completely white. When I first loaded the rom it didnt do it for about a week and now it does it everytime. The only changes I've made since loading the rom is that I installed Google Maps and TCPMP.
Hmm its very weird, i did the hard reset.. well it didnt work..
The 3% error i got that only once
I tried installing the official htc 6.1 windows mobile rom and got the error 244 ...
and same as always, the moment the screen turns white it disconnects from activesync and doesnt reconnect. Imho XP needs reinstalling..
So my theories so far are: activesync is buggy to the core. Ill try flashing on my laptop as soon as i get to it.
Also one thing ive noticed: in all my previous flashes i had the original htc battery.. now i got an extreme energy battery with a blue and white sticker, ill try replacing the original battery before reflashing.
As i said in my first post, this is not my first flash, and i have flashed before to kavana's then rose then kavana's again and it always went smooth.
I have been using the S620 for like one year and a half and never had a prob.
Its an htc version and it was not locked; anyway in belgium locked phones are forbidden to sale
Greetings from the land of the beer and thanks to the developpers
Which Bootloader are u using ?
The official shipped one or the modified one ?
Hmm good question, where can i see the version ? When it boots up i see the nrg rose 1.7 black screen with white writings.
Another weird thing: my keyboard is azerty, so prior to hard reset i had a language pack for french keyb, after the hard reset my keyb works just fine without any language pack installed ... not that it is a problem but i just dont understand ^^