Related
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???
Worked ok last night, then it crashed (mad colours on screen), so I had to do a FULL restore of radio and rom (seemed to be stuck in bootloader).
So, reinstalled everything, all good, I just cannot get it to turn on WIFI. I go into comm manager, click on wifi, and it tries to turn it on, then comes back with a X next to the icon.
Also the front today screen plugin (the wifi/bluetooth one) doesnt say WIFI: off anymore. Just has Bluetooth:Off
Any ideas
THANKS!
Try to flash back the rom again..
By the way, what rom do u used?..
I only just flashed it again ..
I used the O2 rom 'Xda_Exec_Upgrade_v1.30.162'
Can you recommend another ROM that might fix it?
Also, does reinstalling a ROM reinstall all the drivers? As I've noticed some things stay resident even after a flash; call timers for one..
thanks
while im waiting for replies, im going through roms
trying different AKU ones now from the ftp
could it be a radio issue?
My QTEQ 9000 are on the same situation, made some stripes on the screen and now can´t detect anything!!
The wifi apears I start it but can´t get any signals!!
Any help please?????
i upgraded radio to 1.14 and still same
Try these ROMs
You can find on the forum, Ivan's and Helmi's ROMs.
They are the latest AKU 3.2 and seems to work just fine as O2 ROMs are just AKU 2.X!
I think the problem lies deeper than a hard reset/rom as well, it must do after installing 3-4 roms, and a couple of radios.
Yes ive tried UNI_AKU3_5_WWE_IVAN_Test2 ROM as well.
Same.
Anyone else got any solutions as to what it might be?
installing the latest qtek rom off buzzdev now, includes full radio/rom/ext rom. if this doesnt work, then f**k it, ive spent enough hours on it, and i'll just get a new one on contract tomorrow.
thanks for the people that replied
what about the driver disk, isnt there a wifi thing on there
maybe im dreaming
Have a look in the network adapters list and see if the Tiacxwln card is listed, if not sounds like it is a hardware rather than a driver problem. It's not unheard of for computer hardware to fail for apparently no reason. This is likely if you have tried different ROMs and none of them work.
I´ve tried upgrade radio to 1.14 and I tried Ivan's and Helmi's ROMs.
and the problem persists!!!
Tiacxwln card is listed.
Strange situation because during one year worked very well and suddenly make some stripes on the screen and now don´t detect nothing!!
Maybe antenna problem??
Help us??
Is there a problem with o2 official rom?.. Heard few people also got a problem if flashing to o2 rom..
Nope, not working, tried qtek roms, a new orange rom, still wifi not coming on.
Yes the card does show in network cards.
Oh well
Any help Please???????????????????????????????
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.
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Sprite?
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
ruffruff said:
i too have many problems with 1.93.456.2 WWE baserom. somehow, it just doesn't seem so stable ... not sure if many others are feeling the same for 1.93 roms. i guess 1.37.456.2 ME WWE is still the most stable at the moment...
if only we can have a review on all official rom consolidated in one thread.
Click to expand...
Click to collapse
Yes i had same problems. imo the 1.93 isnt a stable rom(yet) so im back with 1.37.456.2 this one is just perfect,very stable,less memory leakage.
Well, the problem is still on going. I can't flash my phone anymore for some reason, even though I've tried both, unsigned and signed Hard-SPL, which both of them flash fine. However, the phone gives me error [276] update error. So not sure what exactly is going on here.
Also, no, didn't sprite backup, phone's just being retarded, mobilecityonline will repair it, but it will take almost 4-6weeks, I cannot wait that long. What else should i try?
Okay, nope not fixed... Flashed it with 1.37, connected to the network for a few seconds, dialed somebody and no ring or anything, but when i called my phone i could hear my own voice. So I guess i have to send it in for repair. Damn.
berlinberlin said:
Did you use Sprite to backup your previous rom and store it in 1.93xxx?
This could be the cause.
Click to expand...
Click to collapse
Could you please detail? I've flashed 1.93.xxx just in the day it appeared on the site and after flashing, I've restored the backup made with Sprite Backup to preserve the settings and so on. I wasn't worried about the contacts/calendar since I have them in Outlook, but I didn't want to start all over with settings, install programs and so. I've made the restore in "upgrade mode", restoring also the databases. The result was that I got a verry strange TF3D, displaying "Home" between the operator name and date, and strange behaviour. I've seen also that the animations were taken out so I've flashed back 1.37.xxx.3. Could be any problems generated by the restore operation? Should I use a different restore type (eventually not selecting "restore databases")?
I have had no problem with the new 1.93xx rom.
Touch FLO 3d is quicker (probably because the animation is disabled)..
and the battery life is about 20% better
Radio ROM Anyone
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
mhbr12742 said:
Sounds like the Radio...
What version is everyone on? The 1.93 ROM updates the Radio, have you tried downgrading to 03?
Click to expand...
Click to collapse
I am on 05 and has no problem ( have been using it for a day now)
I don't know, but If i plug the diamond into my adapter, the network suddenly works and I can actually make calls and everything's fine and dandy, but just on the battery, I can't call anyone, and if I pull out the adapter when the phone gets a signal, the signal stays but again, can't call anyone because i can't hear anything.
It's an awkward problem. I'm not sure if it's my battery or something. So I'm getting another battery off ebay since they don't sell HTC Touch Diamonds in the U.S. yet.
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
adwinp said:
I've been having random freezes with the 1.93.xxx
Anybody else experienced that?
A.
Click to expand...
Click to collapse
Yes, me I had same problem twice - freezes on PIN input screen, second problem with this release is that sometimes PIN screen doesn't appear. Now I'm back on 1.37 and everything seems to be ok
Intradvocate said:
I have a imported DIA100 phone, and trying it on the T-mobile network here in the states. everything was fine up until today when i upgraded my phone to the 1.93 series, now it randomly shuts off, and it cannot connect to the T-mobile network, keeps saying (searching). I don't know what's going on, I reflashed the device and it still does the same thing, infact it might even be worse now. Restarting the phone doesn't work, as it keeps restarting from the boot. Anyone have any idea what to do? I'm going back to 1.35.
Click to expand...
Click to collapse
THe Problem you've encountered:
1. Random auto reboot
2. Random freeze
3. etc.
It's sounds familiar to me. Well it's maybe have to do with SPL just like the Kaisers do.Well, I said maybe... So, what we did to our Kaiser before is flashing the HardSPL which has the same version number as the ROM flashed. So, if you're using ROM 1.93 then the HardSPL should be flashed is Olinex HardSPL 1.93 or you can try one by one of the developed HardSPL existed in this forum. My saying is, go with HardSPL 1.93 and see what happen. If it's still no go then it must have to do with the ROM itself.
Just my 2cents.
hi,
i have been experiencing a problem with my diamond for the last couple of weeks. i lose the alignment on my screen and when i start moving the touch flu taps the icons are shaking and not moving as i want!
is it something related to ROM, SPL or radio?
i keep formating, changing cooked Roms, lastely i gone back to the offecial rom but the problem still comes. It is always the case that when the device starts after formating i have to keep alignming the screen up to 10 times or more!
can anyone help please?
join the club....
http://forum.xda-developers.com/showthread.php?p=3892993
People all you tryings are ilusions, this kind of problem nothing can't resolve, with trying of software solutions, cause i tried everythings possible to resolve this problem!
I tried, all versions of SPL, signed-olinex, unisgned - olinex, stock SPL, this means all versions from 1.34 to 1.93, and again, and again same problem...
Phone works 3-4 hours ok, and again same... I think this problem occured when i installed IGO8 app for GPS, and start to use this app, i felt phone start to warm up, and often when i used IGO8, it was very hot, something like overheating of computer's component, MB, CPU, etc..
After 1 month, it started to not respoding touch screen, and i couldn't fast align screen!
Then i tried manny cooked roms, one of the best, Cloudy1.0, Shaks4.2, Duty, etc.. And nothing, i go back to 1.93 , 2.03 STOCK roms, and notging ...
And at the end, i tried with formating rom, with MTTY tool, it passed ok, but nothing, after formating , again, and again same...
I spoke with people from HTC support, but they couldn't tell me nothing new, what i didn't try!
This is i think more hardware problem, touch screen problem when phone start to warm up, touch screen has a problem, same is when i go out, and expose phone directly to the sunny, touch screen start to freeze!
And i decide to send phone in service for repairing, cause phone has 2 years warranty, i hope they will give me new one, like some people wrote here...
I hope they will not discover , that i used HSPL olinex, and my problem is i didn't remember what was stock rom on my phone, when is buyed, stock rom was 1.93, but SPL i forgot, today i added 1.37 STOCK SPL, and today i send my phone to service! And now i have to wait...
Greetings and good luck all you!
I'm sorry for my bad english, cause it's not my native language...
p.s.
You can try with MTTY tool, to resolve that problem ,before sending phone, you can find MTTY tool, in thread "strange problem" just write "strange problem" in search, and follow instructions from that thread, some people succeeded to resolve that problem, with that tool, then you can try... I had not lucky... Before trying that, go back to STOCK rom , and STOCK SPL 1.93...