I have a UK M5000 and updated the ROM to the new Orange ROM without problem. It was still slow so I plunged for the upgarde to the Dopod ROM. Since I did this it crashes all the time. Sometimes I can reset it sometimes I have to take the battery off. After a bit it won't even boot at all!
Despite all this I am always able to get to bootloader and reflash it. I have since tried the QTEK ROM and even back to the Orange ROM but now it still is unstable. Is there any known reason for this that I can try.
PS tried task format commands and mtty stuff as most of the time after a crash it sticks at the splash screen in all ROMs.
PPS IT NEVER did any of this before even after the first Orange ROM upgrade.
ANy help much appreciated.
Thanks
James
Not sure if you've cured this by now but I am a UK Orange user with SPV M5000 and went ahead with Dopod upgrade wihout any problems.
Presume you tried Hard Resetting, formatting card etc?
I have the same problem... It starts 2 days ago... Its terrible!
I have T-mobile. Now i flashing with original T-mobile ROM and i hope that everything will be ok.
If anybody knows whats happend???
I thought that the problem is on hardware...
30 minutes ago i flashed with latest I-mate ROM and when after flashing i do hard reset nothing happend. I see black screen and thats all!!!
Yes! With T-mobile ROM it seems to be ok. Now i try to flash with I-mate ROM again.
May be the problem is in the "MaUpgradeUt_noID.exe"?...
MaUpgradeUt_noID.exe
I find out that there are some issues with this file. Is this the same file we used to use during upgrade/change language??? If yes, than why when I tried to dawnload from the buzz web side i find that there said that the file is 365kb but when you dawnload the file is 165 and that is why some people are having problems when upgrade their rom or change operators/languages.
So if I want to change language it sais that you shoul run MaUpgradeUt_noID.exe and than I see in the picture of Magician. Is this NORMAL and should I go forward or WHAT.
Flashing with T-mobile original ROM didn't resolve the problem...
It's still bad...
What the hell is going on with my Universal???
Hi everyone!
I'm Ray from Portugal, greetings to you all
I've been trying to upgrade my HX4700 to WM6 (using several methods) Kozhura edition but every time I upgrade and do a hard reset I get stuck on the "clering data" screen
I used the method explained on the readme.txt and the boot loader method.
I upgraded from WM5 standard version
I managed to revert to the WM5 standard and It worked, then I tried it again and the same problem occured.
After that~I reverted directly to the AKU 352 WM5 version from Kozhura and it also worked (I am using it now)
The problem is only with WM6...
Any thoughts on this?
Thnx
Ray
How long have you waited at the clearing data screen, its taken mine a few minutes easily and I have sometimes wondered if it would ever finish. I have also found that doing a hard reset with the stylus first and then doing the clear data works much better. Also which version of the WM6, fix 3 or the new ver 4?
probably took some minutes, 5 at most..
what do you mean doing a hard reset with the stylus and then clear the data? you do a hard reset without clearing the data (itask button) and then a another hard reset and choosing to clear the data (calendar button)?
I used release 4
wm6 not start
HI!
did you have found how to solve this problem is have the same condition that you have an can not found how to fix it.
thanks!
raybanana said:
Hi everyone!
I'm Ray from Portugal, greetings to you all
I've been trying to upgrade my HX4700 to WM6 (using several methods) Kozhura edition but every time I upgrade and do a hard reset I get stuck on the "clering data" screen
I used the method explained on the readme.txt and the boot loader method.
I upgraded from WM5 standard version
I managed to revert to the WM5 standard and It worked, then I tried it again and the same problem occured.
After that~I reverted directly to the AKU 352 WM5 version from Kozhura and it also worked (I am using it now)
The problem is only with WM6...
Any thoughts on this?
Thnx
Ray
Click to expand...
Click to collapse
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.
Hello all,
I'm having problems upgrading my HTC Touch Pro2 to Energy ROM (Standard). It's probably a problem with the connection rather than the upgrade.
I downloaded the Standard Energy ROM for Touch Pro2 from EnergyRoms.com, and did everything as specified in the instructions: made sure the battery is charged, and established an ActiveSync connection.
However, when I proceed with the upgrade, the following happens:
1) ActiveSync disconnects
2) HTC USB Upgrade software gets auto-installed (if it's the first time run on that PC)
3) The ROM upgrade starts, and progress bars appear both on the phone screen and on the PC utility
4) .... nothing happens. The progress bars stay at 0% for a few minutes.
5) The upgrade utility reports there is a communication error [262: Update Error].
No harm done: after removing and replacing the battery, the phone works as previously. Something just doesn't let the ROM upgrade through. I've tried this on two WinXP PCs and one Win7 PC already.
Note: Currently there is no SIM card in the phone. But I suppose this is not relevant? (haven't tried it with the SIM card present yet)
Anyone else run into this problem? Any insights appreciated.
Maybe a dumb observation... but you don't specifically mention if you've done the hard-spl step?
Thank you for your reply. Not a dumb observation at all, the joke is on me. I haven't done that step. I didn't know. n44b.
I'm located in Finland and ordered my phone from the UK so it's a GSM phone. After posting this question I did some Googling around but only found links to old threads which I wasn't sure if they were still valid.
I presume there's a recent, up to date thread on the subject somewhere here?
Ah, found it, via the Wiki:
http://forum.xda-developers.com/showthread.php?t=550131
All right, then! I'll attempt update again later this week.
All done. And all this went easier than I thought (the only obstacle I ran into was that I had to disable my anti-virus while hard-SPLing).
Yes, it's very stable and fast. I can't believe my phone is still operational after being left alone overnight. Before this, my TP2 (with official HTC ROM updates) froze 3-5 times a day and had to be reset by removing the battery.
Welcome to the world of custom ROMs. Good luck with your new addiciton.