I have just joined the community and updated my TYTN to 4.31 ROM - look great
I was wondering if anyone is facing my problem:
I have set in the Pwer settings to "turn off the device after XX minutes"
The device does turn itslef off, but it seems that only soft reset can get it back on!
The hard buttons are not responding, the devce cannot even accept calls!
Did anyone face the same problem and manage to resolve it?
As a workaround, I am currenty using, Not to trun off the device, which probably consumes alot of battery!
no i don't have this problem it is working OK with me with same schaps rom 431
did you update your bootloader? I would hard reset again. If that doesn't work then try to reflash. Make sure your bootloader was updated first though.
Lets me see if I got this straight
When I load the RGB screen, I see this information in the RED block:
HREMES200
IPL-1.01
SPL-1.40.Olipro
The Device information shows
ROM Version: Schap's 4.31
ROM date: 10/03/07
Radio Version: 1.16.00.00
What is the bootloader exactly?
What should I select when I run the Schap's 4.31 ROM, there are several options there
BTW - the OS is SLOW, is that how it is with every wm 6.1 for Hermes devices?
I got confused when I first flashed a different rom (after installing HardSPL Olipro) - I just choose Safe SSPL as a tutorial recommended I do, and I've flashed three ROMs now without an issue just by using the Safe SSPL option.
After reflashing (and updating to hardSPL) I managed to find out the problem - it was the hebrew language by Orange which has casued this.
After removing it all worked well (almost)
Related
Hi folks,
It seems I have quite a major issue with my device in that I can't type anything without the machine freezing-up... To narrow down the issue I've tried a few different things and it seems to be a software issue rather than hardware issue because it also happens when typing using Cerdisp (this circumventing the physical keyboard/hardware used to type)
Does anyone else know of these issues by chance?
Device Information
ROM version: 3.30.0.1
ROM date: 04/17/07
Radio version: 1.41.00.10
Protocol version: 32.74.7020.18H
Bootup
M05
S04
B06
R3.30
I'm thinking about rolling-back to my default Orange WM5 OS at the moment as my phone is pretty much useless except for calls
I used to get it sometimes with the custom roms.. When I woudl send a txt message as soon as I hit a letter the backlight would go off along with the keyboard lights and then a couple seconds later it would turn back on.. is this similar to the problem you are having?
No no, I've had the problem you speak of in the past but it's not that... What happens at the moment is a complete system freeze. The text stops being entered and the cursor just sits there blinking and won't let yu enter any more. Then if you close the keyboard it doesn't switch back to landscape. If you then hit "start" the menu comes up but that then doesn't work and it just gets completely tied-up in knots until you have to soft reset it
UPDATE: Vid is available here (very apt music if I do say so myself! )
http://www.youtube.com/watch?v=DwB-fI_TrkA
Hmmm... I've been perusing MrVanx's Downgrade Guide (http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=41&Itemid=27) but the ROM I'm looking to downgrade to is a pre-packed .exe I've downloaded from my official provider's website...
MrVanx's guide states:-
NOTE: If your radio version is currently HIGHER than 1.27.00.00 then it is very likely the radio bootloader is version 0108, this WILL NOT allow the radio to be downgraded to a radio containing BL 0106 and will result in a "NO GSM" error.
I have Radio Version 1.41.00.10 as mentioned before so that puts me in a bit of a catch 22... How can I find out if the ROM contains BL 0106?
EDIT: I found a thread on here for a new Orange ROM and someone had tested that it was downgradable from WM6 so I ran the installer on that version (up until the version screen appeared) and the same with the downloaded version from Orange website and they were the same version so I've now successfully downgraded using Force SSPL.
did you find a quick fix to the text messaging problem? i noticed the system freezes when i type "w" and "n" also when i type "w" right after the word "it" i cant type "it Was" without the machine freezing...im using funkeys rom and it's great but im concerned now because the only reason i switched from blackmajic was because the same keyboard problem was occuring...what could it be?
Did a resolution ever come out of this? I have the some problem and it is driving me nuts. I can type the alphabet but if I enter a full stop and the type i, my pda changes it to an upper case and it locks up. same if it tries to change it mid sentence from a lower case i to an upper case I. Any ideas?
greywolf20k
This is a serious WM6 bug, im suffering it too on my HTC touch.
Hi
My device is running Dopod WM6 (EASY_INSTALL_new_HK_WWE_wm6_Chun..exe)
OS 5.2.1437 Build 17944.0.3.1
ROM 3.54.707.3
Radio 1.47.00.10
HERM200
IPL-1.04
HERM200
SPL-2.03
but it don’t allow me to install any ROMs like Schap's 3.57a or someone else.
I do this from a XP pc with ActiveSync 4.5 and the ROM upgrade wizard cannot auto detect then tell to use SSPL.
But nothing happened except the upgrade get ERROR [260]
Did try to select SPL-1.11 or SPL-2.02 and if I do that it start upgrade to 1% then device reboot by itself.
Has also try with Hard-SPL-V7 but it refused to do something with that!
I have tried everything now but best I can get is 1% starts to download, and then the phone restarts by it self
is your phone superCID? thats probably the issue even though it shouldnt be if you have Splv7 on your phone which you do right? If not thats the first thing you need to do before you brick your phone!
I did install many different ROM before the last how works good
Dopod WM6 (EASY_INSTALL_new_HK_WWE_wm6_Chun..exe)
But what happen with phone with Dopod ROM has they build in some security ???
how can i step back to another ROM
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.
dear friends
I am facing a strange problem on my diamond.
After flashing any ROM (whichever it may be) the loading of cabs etc takes place successfully.
But, after few minutes/hours the contents of strat/program are gone. and no program functions. I have flashed re-flashed and reflashed. cannot get over this strange proble.
Can any body guide me what wrong is happening with my diamond???
PS: I have hard SPL 1.40 olinex on my device.
Problem Solved -->http://forum.xda-developers.com/showpost.php?p=3433851&postcount=22 (Thanks cmonex)
c_shekhar:
I have a similar problem. I have had no issues flashing in the past and am very familiar with the procedure. The other day however I noticed a problem where by some of my apps would "disappear".. odd. Also after some time my phone would hard reset instead of soft reset, at first I put this down the ROM as I have had this before with udk's ROMs (no disrespect intended!) and had tried his topaz ROM. It seems to have got to the point now that once a few hours have passed my phone will lock up and then when I reset, it just hangs at the "touch Diamond" screen and I have to hard reset.
I have tried reflashing Radio, Hard SPL, OS.. I have also tried installing my apps one by one and soft reseting after each install. just whenI think it is working it will freeze again.
I have tried flashing different HARD SPL's but it always completes but when I go into boot loader it still says OLINEX 1.40.
What was the last ROM you flashed before you started noticing the issue? The last two I tried where udk syrius topaz and DIB 1.33.
I wandered if it was something to do with the data on my internal storage???
Going to try a hard reset and format movinand next to see what that does.
P.S: yours was the last ROM I used for my Polaris, it was awesome!!
I tried uDK's topaz based latest ROM and after that it started givind problem.
many a times when I prick for soft reset it hard resets the device. I have hard resetted my device several times but it does not set the problem right.Huhhh
Thanks for liking my Polaris ROM..
any headway found by you pl share.....I had borrowed somebody's Diamond and it is F*##ed up.
Same problem here
I have the same problem.
Started with morna 1.8 and then vic 3.5 and then windows net 6.5.
Seems like it keeps doing it. I just flashed a complete standard stock rom from htc from my internal storage instead of via active sync which had radio os etc all included. i then did nand reformat and copied all my data back. its almost like it forgets the apps that was installed. I also tried redoing olipro 1.4. Its running now on the stock rom from this morning. I did reset about 15 times and its still "sticking". Ill update you guys to see if anything changes.
Very very odd.
I know its not rom related and not a flashing problem - unless i flashed the diamond too many times. Ive been flashing from the good old Imate days, Kaiser, Kaiser 2 etc. So Im NOT doing anything wrong...
I new I wouldn't be the only one!!
I have just hard reset and formatted movinand AND re-downloaded all my apps so for now nothing will be going back on my internal storage that was on before.
I'll post any updates.
I have the same problem with the Morna. Flashed, reflashed, soft & hard reset.. nothing solved. Every about 24hour the TF3D won't start, the SMS&Emails folders are empty, no contacts and on desktop an error on file BOOT.MSC (can't find associated program to open that)...
After 3 days, I have flashed the Touch with the TIR11 and no one problem. I don't know if the problem is of the rom or else...
Sounds like a virus...
never encounter this problem,but some of my friends does.neither do I know why
offtopic: Are you working on a Diamond rom? I really loved (in fact I'm still using it) your 1.60.21014bCS on my polaris... I think it will be permanent... Have you thinked of making a M2D rom for Diamond ?
I had this problem if i cooked a bloated rom on my Artemis, it was easly solved by flashing an untuched stock rom directly from the operator and then flashing a custom rom again and then no problems untill i next flashed a bloated rom, i think that if the rom is too big it fills the area designed for the rom the starts to overright the hpl/spl or radio then the phone starts to crash and loose programs.
so get your opperators rom, flash, flash stock SPL, then flash h/SPL to re-unlock so you can try another custom rom
don't forget to use the H/SPL custom ruu-flasher to flash stock spl or it won't flash (its overright protected)
garymeg said:
I had this problem if i cooked a bloated rom on my Artemis, it was easly solved by flashing an untuched stock rom directly from the operator and then flashing a custom rom again and then no problems untill i next flashed a bloated rom, i think that if the rom is too big it fills the area designed for the rom the starts to overright the hpl/spl or radio then the phone starts to crash and loose programs.
so get your opperators rom, flash, flash stock SPL, then flash h/SPL to re-unlock so you can try another custom rom
don't forget to use the H/SPL custom ruu-flasher to flash stock spl or it won't flash (its overright protected)
Click to expand...
Click to collapse
Thanks for the info, i'll give that a go. Makes sense. Will have to wait till tomorrow so i'll have to put up with a crippled phone till then!!
I posted about this issue a couple of days ago,I had all the symptoms described.
After using the clear storage option on my diamond,clearing the phone and internal storage then flashing a new rom,the problem seems to be resolved.
I also experienced similar issues yesterday and for the first time ever, during the use of a udK rom.
Update
Grumps said:
I have the same problem.
Started with morna 1.8 and then vic 3.5 and then windows net 6.5.
Seems like it keeps doing it. I just flashed a complete standard stock rom from htc from my internal storage instead of via active sync which had radio os etc all included. i then did nand reformat and copied all my data back. its almost like it forgets the apps that was installed. I also tried redoing olipro 1.4. Its running now on the stock rom from this morning. I did reset about 15 times and its still "sticking". Ill update you guys to see if anything changes.
Very very odd.
I know its not rom related and not a flashing problem - unless i flashed the diamond too many times. Ive been flashing from the good old Imate days, Kaiser, Kaiser 2 etc. So Im NOT doing anything wrong...
Click to expand...
Click to collapse
Update : ITs 17 hours later and still going fine. So maybe the reflashing of the stock rom resolved it. I must say the stock rom i flashed is huge. its over 110Mb so maybe it cleaned out all the jazz. Or maybe when i reformatted the NAND it resolved the problem. I dont know. I also did a softreset about 50 times during the night removing the battery every now and then and its still ok. Ill Update again as soon as something Happens
same problem here...flashed tons of rom before...never had problems...upgraded from monrna 1.7.1 to 1.8 and the problems started..no programs...reset and install procedure restart...i've solved downgrading radio to 1.09.25.23 and flashing 2.03 original italian rom...but now i want to try to re-flash morna 1.8...i'm so curious...u know?!
Im Going to
sakara said:
same problem here...flashed tons of rom before...never had problems...upgraded from monrna 1.7.1 to 1.8 and the problems started..no programs...reset and install procedure restart...i've solved downgrading radio to 1.09.25.23 and flashing 2.03 original italian rom...but now i want to try to re-flash morna 1.8...i'm so curious...u know?!
Click to expand...
Click to collapse
Ill try another rom tonite probably morn 1.8 or wm 6.5 beta 3. and see what happens
i flashed to a HK 2.03 rom and try udk's again, so far so good, will report back any issue
I got exactly the same after the huge 6.5 beta
Clear storage was enough to get rid of it for me (no need for the internal format or the std ROM)
Thanks
goRt said:
I got exactly the same after the huge 6.5 beta
Clear storage was enough to get rid of it for me (no need for the internal format or the std ROM)
Thanks
Click to expand...
Click to collapse
Simply running clear Storage didnot solve my pro...
superpc said:
i flashed to a HK 2.03 rom and try udk's again, so far so good, will report back any issue
Click to expand...
Click to collapse
Can you kindly write more details?
Is HK 2.03 stock ROM?
Which hardSPL did you have on your device before flashing the HK 2.03?
etc...
Stability Restored
Got mine stable again by following post #10.
Flashed stock 1.93 rom then flashed stock 1.93 spl.
Now back with oli 1.93 hspl and pda corners v3 rom.
My ATT 8525 is running
ROM version 2.15.502.3
ROM Date 04/09/07
Radio version 1.40.30.00
protocal version 32.73.7020.16H
I've been having problems with my screen fading out to white, physical send and recieve buttons not always working, and alarms that restart after every on/off cycle of my phone. Despite unchecking all the alarm boxes. I've done soft resets, to no avail. Have not done a hard reset yet.
I downloaded the WM 6 file from the ATT site back when it was available, but never installed it.
My question, Is this SW or HW trouble and might an upgrade to WM 6 fix these problems? I'm trying to keep this unit running until I can get hold of the Touch Pro 2, or whatever ATT is going to call it.
hmm.. normally a default rom would fix most software issues.. its unsure if your problem is due to hardware issues..
from my point of view.. it seems like a hardware issue.
flash out the AT&T striped without the radio and try it out.. if its software issues.. most probably its gonna be fixed.
well if it doesnt fix.. tat should mean a hardware issue.
jus keep flashing rom until u find the right one.
Thanks for the reply