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.
Related
Please someone, anyone, help me out.
I recently flashed my trinity to Bepe's Rom...everything went alright.
Then today I attempted to flash it back to LVSW's rom.
I've done Hard SPL, updated the radio etc...
when I flash LVSW or MUN rom's rom, everything seems to go smoothly, but when the device resets I still have Bepe's Rom.
Tried several times to no avail.
Can anyone help me?
Flash once with an official HTC ROM, then flash with the ROM of your choice
Official Rom DOn't Work
Thx for suggestion re: flashing with an official rom. I flashed with an HTC rom, but still no joy.
It seems to flash fine, but after finishing still got bepe rom!!!
God this thing is like a curse, I just wanted to try it out now it seems that I'm stuck with it permanently.
Someone plz help...
How long does it take you to flash the ROM? Approximately.
It usually takes about 1min 30sec - 2 min to flash the cooked roms.
The official rom takes about 7 or 8 min... definately longer than the cooked ones.
Remove your SD Card an try to flash again, thats very strange!
Sorted...thx.
I was starting to freak out. The SD card was the problem.
You're a legend mate...
Thanks, good to hear that there is no problem any more
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.
Hi All,
I just bought a HTC 3600.
I have flashed it with the Hard SPL 1.20, Radio 1.50.08.11 and latest ROMS (Schap's 3.2,FInixNOver_3.1.1 etc..) .
The unit seems to work fine but after a while and I think this is random or when I use wifi the OS just crashes. When I reboot I am stuck in the boot up screen not matter what. I have reflashed with 5 different roms and the same result after a while the OS crashes.
I am currently downgrading the radio to 1.46.0 to see if that has any effect. I hope it isn't a hardware fault.
Any input would be helpful.
Try to downgrade to original WM5.
svetbg said:
Try to downgrade to original WM5.
Click to expand...
Click to collapse
or try to use DES hspl...
never I had a problem whit it!
How old is your phone? Was it OK before the ROM updates?
Did you follow ALL the instructions e.g. typically performing a hard reset before update, not allowing vendor "customisations" to run at first start up, performing hard reset after update??
Get back to the original ROM to check it still works.
Good luck
Thanx for all the replies.
After a hardreset and loading DES SPL.
I have successfully ran ADW ROM 1.2 and radio 1.38 without any problems for the last 2 days. Hopefully it stays that way.
I wasn't aware you had to perform hard reset and then load up the hardSPL, ROM and radio. There was no mention of performing a hard reset in the trinityguides.info.
If this is the case then that was probably why the OS started to become corrupt after half an hour. I was probably loading up bad ROM images.
I will continue to monitor unit for the next couple of days.
Why are some ROMS causing devices to automatically hard reset for some people and not for others?
what roms are these?
i have tried all the roms here and its never happened to me????
It 'happened to me, always on Saturday for 2 time!!
Now I have flashing the original rom and also try this Saturday.
The hard reset is not complete, the icons of the programs remain, and manilla is not loaded. If I do so "physically" vol down, circle button and reset all ok.
Yeah i have the same problem. Tried 4 different ROMs in last 2 days. Found a stable one now and seems to be working well.
Even tried the WM6.5 Beta ROM. Worked very well and was stable. Just didn't like it.
What ROMs have you tried and what ROMs kept hard-resetting?
The first was a rom dib 1.28, last 2 hard reset and always on Saturday with enhanced Morna 1.10
Now i flashed the official HTC rom RUU_Diamond_HTC_ITA_2.03.408.2_Radio_Signed_Diamon d_52.51.25.26_1.09.25.23_Ship found on this forum :
http://forum.xda-developers.com/showthread.php?t=471699
Until now, never happen to me also.
I have tried almost every rom in this forum, now with udk r6.
I have hspl 1.93 since beginning.
Normally what I do is, before changing to a new rom I always go back to an official rom, then hard reset, then new rom, then hard reset.
Also I always use laptop and keep the official nbh or a tested rom inside internal memory just in case.
hope this help.
This can happen if the storage memory (not 4gb but rom memory) is corrupted.
I would try 1 of these methods to fix:
Flash a stock rom then flash the cooked rom.
or:
Follow the following thread to use mtty to format your memory:
http://forum.xda-developers.com/showpost.php?p=3433851&postcount=22
What happens is that some of the memory is corrupted and mtty/stock rom formats the device and can either restore the bad memory or mark it out of use (there are spare's)
This should fix your issue. This issue appears to be caused more by the newest roms for some reason but only affects a small minority and doing one of the above restores their device fully.
Hope this helps
happend to me once,not sure why...
hspl 1.93
try different hspl.
I had same prob when I had hspl 1.93
flashed back to hspl 1.4 sloved the problem
I`ve been using several wm 6.5 ROM`s and only ROM what did the same thing was udK WM6.5 BETA1 and BETA2 21500 ROM. Now i use sone`s RC2 ROM, and everything is working great. No more hard resets
I have flashed nearly dozen of ROM's but it never happen with me.
i must of flashed 20-30 diff roms and my diamond has neva hard reset itself
This happens to me a lot. Best thing is to use the method posted on Page 1 of this thread using mtty. Unfortunately, mtty doesn't like the Vista USB driver for activesync, so XP is a must. Manually "rolling back" to the XP driver has been reported to have worked in Vista for some people, but sadly not for me. I personally have to use XP on VMWare as I only have a Vista laptop these days
I still get a bad read out out though, something about a certain set of blocks being unable to be deleted, which looks as though it means I have to use this method EVERY TIME I flash, which isn't too bad, but if I don't, I get an unstable device that randomly starts deleting everything in it and eventually itself.
cerisu said:
I`ve been using several wm 6.5 ROM`s and only ROM what did the same thing was udK WM6.5 BETA1 and BETA2 21500 ROM. Now i use sone`s RC2 ROM, and everything is working great. No more hard resets
Click to expand...
Click to collapse
UDK's roms did it to me to. After flashing around a bit settled on bsb 6.5a atm im having no problems.
tried all ROMs and everyones get me this error then only way is to go into bootloader mode and flash again to other ROM. got Hard SPL 1.93.
never tried MTTY, cause i never had any issue with any other Rom.
atifsh said:
never tried MTTY, cause i never had any issue with any other Rom.
Click to expand...
Click to collapse
The time is coming
I had this problem. never bothered with MTTY because I have 64bit windows 7 and it seems like a complete PITA, just download one of the original operator rom flashers (I downloaded O2s) flashed that, then flash my new rom. Its been fine ever since.
atifsh said:
tried all ROMs and everyones get me this error then only way is to go into bootloader mode and flash again to other ROM. got Hard SPL 1.93.
never tried MTTY, cause i never had any issue with any other Rom.
Click to expand...
Click to collapse
Just flash with a stock ROM and then the ROM you want.
I've had same problems with previous versions. Never had any problems since I started doing that.
very strange... i flashed to HTC Official ROM, then used haseed's 23075 and it works. will be tring other 23075 and post back. thnks for the answer
It generally just confirms the advice from Matzen, my own and many others personal experience. A couple of months ago i flashed a 6.5 ROM and it worked perfectly. Then i wanted to play a bit and flashed a lot of ROMs just for curiosity After about five flashes problems started, until i could NOT get any rom running flawlessly any more.
Back to a stock ROM and everything is fine again. If you flash an "intermediate" stock ROM before it is completely stuck, you can avoid MTTY.
I was having same issue, flashed O2 stock rom and 23071 roms worked fine.
@IceMan:
O2 stock rom ? It is O2 Ignito , isn't it ? If so, where do you get it ?