I am using my device with WM6.1 19900 build ROM for about a week. All that time the device was very stable, no lockups, no resets.
Today I upgraded my friend's device (exactly the same one) to the same ROM with the same settings and additinoal programs. On the first hour of use, he had 3 (!) hard resets that occured with no reason during a normal work.
The only change is that I changed the pagepool size of his ROM to 4Mb (mine is 6Mb). Can it possibly happen because of pp size?
ochakov said:
I am using my device with WM6.1 19900 build ROM for about a week. All that time the device was very stable, no lockups, no resets.
Today I upgraded my friend's device (exactly the same one) to the same ROM with the same settings and additinoal programs. On the first hour of use, he had 3 (!) hard resets that occured with no reason during a normal work.
The only change is that I changed the pagepool size of his ROM to 4Mb (mine is 6Mb). Can it possibly happen because of pp size?
Click to expand...
Click to collapse
No it can't be related to PP size at all.
If you had even bothered to search the forum or the Wiki you would have found the answer to your question which has been extensively covered in this forum.
Eventhough i will humour you and tell you waht to do:
1. Flash an original carrier ROM [you can find lots of them in the Wiki]
2. Hard reset
3. Install the desired ROM
4. Hard reset
5. Proceed with normal usage
If you have problems or doubts, before asking, please read the Wiki and search the forum.
Cheers.
Thanks for the quick reply.
I am pretty experienced with ROM upgrading and I did the upgrade exactly as you (and Wiki) describe!
Now I updated the pagepool back to 6Mb and reflashed the ROM.
No hard resets yet, but I am still testing. Will post the results.
It might be the problem with your ROM. Change to a different ROM and see if it fixes it!
ai6908 said:
It might be the problem with your ROM. Change to a different ROM and see if it fixes it!
Click to expand...
Click to collapse
I believe you do have a point there... Page pool can NEVER be related to hard resets...
Curiosity: From which part of India are you? PM me wiht the answer if you like
Cheers.
Ok, This is not a pagepool size. The device is still hard resetting.
How is it possible that two identical devices, the same ROM performs so differently!?
That ROM is so stable for me, I like it, but the other device just refuses it!
I will start trying other ROMs. I will try to flash the original ROM and then flash the new one again. With all the required HR in the middle.
for me hard resets did not stop until i flashed a cingular rom but i dont know if thats because i have an 8525 or the extended rom is different some how.
for example i flashed a dopod rom twice trying to fix it and only a cingular rom did the trick if your still having hard resets its worth a try
ochakov said:
Ok, This is not a pagepool size. The device is still hard resetting.
How is it possible that two identical devices, the same ROM performs so differently!?
That ROM is so stable for me, I like it, but the other device just refuses it!
I will start trying other ROMs. I will try to flash the original ROM and then flash the new one again. With all the required HR in the middle.
Click to expand...
Click to collapse
What type of hermes are both devices? Are they alike? Are they from different sub-builds? Are they HERM100, HERM200, HERM300?
Maybe the problem is related to that.
Cheers.
neva dinova said:
for me hard resets did not stop until i flashed a cingular rom but i dont know if thats because i have an 8525 or the extended rom is different some how.
for example i flashed a dopod rom twice trying to fix it and only a cingular rom did the trick if your still having hard resets its worth a try
Click to expand...
Click to collapse
Thanks, I will try to flash Singular ROM and then reflash with WM6.1
Kevlar-Source said:
What type of hermes are both devices? Are they alike? Are they from different sub-builds? Are they HERM100, HERM200, HERM300?
Maybe the problem is related to that.
Cheers.
Click to expand...
Click to collapse
These are both IMate JasJam devices sold by the same cellular provider (Cellcom) on the same date!
Both devices had the original WM5 ROM from Cellcom.
Both devices were HR before the upgrade. On the first one (mine), I flashed about 10 ROMs including both WM6 and WM6.1, before I found the perfect one (WM6.1). On the second device, I flashed it with that ROM from the beginning.
May be flashing WM6 on the other device before WM6.1 will solve the problem.
Does anybody know why this happens? How reflashing the ROM solves the problem?
Related
Hi Everybody!I have SPV M650 Orange(Artemis).I update my ROM to Artemis Touch 4.01 Vanilla and now i have problem with calling.After night i try to call but... my phone not respond,others programs and function working normally.Restart(big battery drain 10% down after soft reset !!) and my Artemis working fine.Before im using Artemis 4.01 Vanilla ROM and problem will be the same!I update my radio to 03.08.90 but problem stay.Please help lads!
Sorry,bad english.
Regards.
the same
I have the same problem, but I have a FULL version of 4.02 ROM (ENG). The problem is exactly the same - after some time (one night for example) the "phone application" stops responding when I want to make a call. I think it's the ROMs fault. I thinking of going back to the original WM5 or original WM6 from HTC.
kosiara said:
I have the same problem, but I have a FULL version of 4.02 ROM (ENG). The problem is exactly the same - after some time (one night for example) the "phone application" stops responding when I want to make a call. I think it's the ROMs fault. I thinking of going back to the original WM5 or original WM6 from HTC.
Click to expand...
Click to collapse
I think the problem is from the OS ROM. I had same problem with vanilla 4.02.
Just try it another new build ROM.
Cheers
Same problem here
Zecanilis said:
I think the problem is from the OS ROM. I had same problem with vanilla 4.02.
Just try it another new build ROM.
Cheers
Click to expand...
Click to collapse
Hi Zecanilis,
I encounter the same problem that is described here by user kosiara an Novy
The GSM signal is excellent, but the phone does not work from time to time and when I try to make a call, I get the message "the operation failed". of course nobody can reach me neither... When I do a soft reset everything is back to normal...
This is very anoying and I do not know what to do.
I bought this PDA second hand, with the upgrades already done for me. Since I do not have any personal data or programs on it yet, I wouldn't mind doing a hard reset and installing everything from scratch.
What would you suggest as a stable system OS and ROM versions?
Any help would be much appreciated.
Here are my actual data:
XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 03.08.90
OS 3.13.0.0
ROM version : Artemis Touch 4.02 WWE
ROM date 4/08/08
Protocol version 4.1.13.52
Model Nr : ARTE 200
WM 6.1 Professional
CE OS 5.2.19199 (Build 19199.1.0.0)
Regards
But, yet again, I don't understand...
Vanilla 4.01 and 4.02 seem to be very popular and appreciated roms.
How come we are the only ones to complain about phone not working properly?
Is it really the OS build? CE OS 5.2.19199 (Build 19199.1.0.0) I don't think so. I have seen it also a lot in Devices.
What could it be then?
I hope it is not a Gsm radio hardware pb......
Any suggestions?
Thanks
Zbootsom said:
But, yet again, I don't understand...
Vanilla 4.01 and 4.02 seem to be very popular and appreciated roms.
How come we are the only ones to complain about phone not working properly?
Is it really the OS build? CE OS 5.2.19199 (Build 19199.1.0.0) I don't think so. I have seen it also a lot in Devices.
What could it be then?
I hope it is not a Gsm radio hardware pb......
Any suggestions?
Thanks
Click to expand...
Click to collapse
I'm not "guessing". I had the same problem and i think my problem is solved after this new rom i have.
Just try one recent build of OS. My build is 19591.
Before upgrading, just turning off and on the phone in the "comm manager" whould give me that problem sometimes. Now i've allready tested it and all is ok.
Cheers
Zecanilis said:
I'm not "guessing". I had the same problem and i think my problem is solved after this new rom i have.
Just try one recent build of OS. My build is 19591.
Before upgrading, just turning off and on the phone in the "comm manager" whould give me that problem sometimes. Now i've allready tested it and all is ok.
Cheers
Click to expand...
Click to collapse
Hi, and thanks for your reply.
I am new to this and althought I read many post, I am not sure.
Can I just upgrade the OS Build without flashing a new ROM.?
If Yes, How do I do it...any tutorial?
Thanks
No.
You have to flash a complete new ROM.
Cheers
OK Thanks
Whish me good luck,,,
Good luck and good choose...
!Novy said:
Hi Everybody!I have SPV M650 Orange(Artemis).I update my ROM to Artemis Touch 4.01 Vanilla and now i have problem with calling.After night i try to call but... my phone not respond,others programs and function working normally.Restart(big battery drain 10% down after soft reset !!) and my Artemis working fine.Before im using Artemis 4.01 Vanilla ROM and problem will be the same!I update my radio to 03.08.90 but problem stay.Please help lads!
Sorry,bad english.
Regards.
Click to expand...
Click to collapse
I experienced that problem a few weeks ago and it's happening more often in the last days. My ROM is Artemis Touch 4.02 full.
Some people started complaining that they couldn't phone me while I didn't see any problem with my phone (as long as I didn't try to make a call myself).
Funny addition to that problem: Sometimes I find my phone (usually in the morning) with a blank white screen. I don't know why that keeps happening but I sure would appreciate any hints what's the root of all that evil.
I'm happy with the 4.02 ROM so I'd rather avoid some things if it keeps the ROM stable.
novy said:
I experienced that problem a few weeks ago and it's happening more often in the last days. My ROM is Artemis Touch 4.02 full.
Some people started complaining that they couldn't phone me while I didn't see any problem with my phone (as long as I didn't try to make a call myself).
Funny addition to that problem: Sometimes I find my phone (usually in the morning) with a blank white screen. I don't know why that keeps happening but I sure would appreciate any hints what's the root of all that evil.
I'm happy with the 4.02 ROM so I'd rather avoid some things if it keeps the ROM stable.
Click to expand...
Click to collapse
when you installed your new rom did you flash it twice ?
this will make sure that all system files are copied 100%.
its really important to do this on all new roms that you install.
neilhhardy said:
when you installed your new rom did you flash it twice ?
this will make sure that all system files are copied 100%.
its really important to do this on all new roms that you install.
Click to expand...
Click to collapse
Thanks for your answer. Yes, I flashed it twice and I even flashed a factory rom before that. All Artemis Touch roms were fine until 4.01 and 4.02.
So Zecanilis is probably right blaming the OS version for that malfunctions.
New Rom
I have flashed my device using USPL (took me 2 days to setup the program to work with vista drivers). Then I flashed the same ROM I had before (Artemis Touch 4.02 full Red and Black) but with a different OS build. (as Zicanillis advised)
I will use it for a while and let you know if the freezing phone problem has been corrected.
Cheers
One other change that is on my build is page pool.
My page pool is 6 MB, and some Touch and vanilla (included the 4.02 i had) is only 4MB.
In my opinion that could be another issue to test.
My PDA is working just fine now.
Cheers
For me the problem was the OS Build.
I flashed my device with the same 4.02 vanilla but with a different OS buid and the Phoneworks great. Been using for 2 weeks now, never freezes or looses signal.
Cool
Thanks to Zecanillis advice! obrigado !
After trying six or seven WM6.1-based ROMS from three different cookers (19199 and 19209), I'm starting to wonder if there's not something 'seriously' wrong with the WM6.1 base image.
I begins to strike me as some sort of duration-based memory degradation. My experience has been that runtime lasts between 2 and 48 hours before a hard reset is necessary. In my case, I pared my installs down to adding merely my password safe as the only add-on, and still it crashed.
The most interesting pre-crash was going to "Programs" and noticing the number of icon substantially reduced (...and reducing...), and the remaining icons as default program icons.
After about five days of fighting with these and trying different methods of extending runtime, I reloaded an older copy vp3G's 3.0.0 from last summer and haven't had a problem for the past 72 hours. In fact, I had no lock-ups with WM6-based, previously.
I'd be interested in other people's experiences with WM6.1-based ROMs on the Hermes...
- Marc
i may be wrong, but i think recall reading that flashing back to your stock rom, then flashin to 6.1 may fix some hard reset problems....
as for me, ive used 4 or 5 6.1 roms and havent experienced a hard reset.....my latest and favorite so far is faria's and dr.p's 6.1 rom, been running a week no hard reset...
im usin an at&t branded 8525
i was having a few issues with this but ended up changing radio versions from my standard 1.16 to 1.48.
havent had an issue since doing that.
i had the crash problem also, but after I not install htc cube in any of the wm6.1, everything ok and stable.
problem is with cube in wm6.1 i think.
Faria's is the best so far, but they all have problems to varying extents. Have you tried running Oxios Close apps? That will help you claim back memory and maybe help prevent the need for a hard reset. you can get it here: http://www.oxios.com/memory/
lupes5 said:
i may be wrong, but i think recall reading that flashing back to your stock rom, then flashin to 6.1 may fix some hard reset problems....
as for me, ive used 4 or 5 6.1 roms and havent experienced a hard reset.....my latest and favorite so far is faria's and dr.p's 6.1 rom, been running a week no hard reset...
im usin an at&t branded 8525
Click to expand...
Click to collapse
Interesting. I did notice that on some ROM flashes that boot screen retained a previous ROM's splash. That might mean that some ROMs are not including all facets (OS, Radio...Bootloader?) of the complete image. Will give that a shot now that I'm back to a stable WM6.
st3v3 said:
i was having a few issues with this but ended up changing radio versions from my standard 1.16 to 1.48.
havent had an issue since doing that.
Click to expand...
Click to collapse
Radio is 1.45 with vp3G 3.0.0. Will check again after a Faria re-flash and upgrade to 1.48 if it isn't included.
fizzy15 said:
i had the crash problem also, but after I not install htc cube in any of the wm6.1, everything ok and stable.
problem is with cube in wm6.1 i think.
Click to expand...
Click to collapse
I had that thought too, but my last ROM didn't include any of the HTC apps, at all, so I think it's some conflict or something lower level. The cube 'is' a resource hog, however...
hamster0914 said:
Faria's is the best so far, but they all have problems to varying extents. Have you tried running Oxios Close apps? That will help you claim back memory and maybe help prevent the need for a hard reset. you can get it here: http://www.oxios.com/memory/
Click to expand...
Click to collapse
The resets are always due to hard lockups, and they can be with only Activesync running as an application. I try to keep the number of running apps at a minimum for reasons that are probably fairly obvious to all here...
you are not alone...
http://forum.xda-developers.com/showthread.php?t=376211
Im also having the same problem .. all sorts of experiments has been done to test on why WM6.1 crash when I install them .. but 1 thing i noticed that it always hang before softreset that eventually lead to hardreset .. i thought hardware accelerations problem ... so what i do is .. every WM6.1 i changed to 8mbpp .. until now my machine ok.
My2Cents.
-/Abid.
Flash to stock rom then to wm 6.1... Apparently there is a problem if you flash from big storage rom to wm 6.1(not sure why this is so) but there have been a huge number of people who say this works for them, myself included.... I tried every wm6.1 rom that came out then doing something stupid eflashe stock os. No problems with wm 6.1 since. Also I believe that 19209 is somewhat more stable than versions 19199 or 19202... I'm using PDAViets 19209 rom,just changed to black edition, and have had NO trouble EVER since installing it when it first came out, no soft resets and more importantly, no hard resets... Cheers
milleniumbug89 said:
you are not alone...
http://forum.xda-developers.com/showthread.php?t=376211
Click to expand...
Click to collapse
Yep, sounds like the same behavior I'm seeing. Soft lock, reset, soft lock, reset, hard reset...lose data... (rinse and repeat)
fix
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
I have the same problem! Tell schaps so in his next rom he may fix this serious problem
Shadow CE 6.1
chronosxx said:
After trying six or seven WM6.1-based ROMS from three different cookers (19199 and 19209), I'm starting to wonder if there's not something 'seriously' wrong with the WM6.1 base image.
I begins to strike me as some sort of duration-based memory degradation. My experience has been that runtime lasts between 2 and 48 hours before a hard reset is necessary. In my case, I pared my installs down to adding merely my password safe as the only add-on, and still it crashed.
The most interesting pre-crash was going to "Programs" and noticing the number of icon substantially reduced (...and reducing...), and the remaining icons as default program icons.
After about five days of fighting with these and trying different methods of extending runtime, I reloaded an older copy vp3G's 3.0.0 from last summer and haven't had a problem for the past 72 hours. In fact, I had no lock-ups with WM6-based, previously.
I'd be interested in other people's experiences with WM6.1-based ROMs on the Hermes...
- Marc
Click to expand...
Click to collapse
Use Shadow CE 6.1's rom .. I have been using it for months, and it is near flawless. Do it, you won't regret it . I've tried everything else .
Fix works...
raidzx said:
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
Click to expand...
Click to collapse
After trying almost everything to get more than a few hours of runtime out of WM6.1, I followed the above instructions to the letter and WM6.1 has worked for 24 hours now (yes...a new record). I will update in a few days if the Hermes/Faria 6.1 combo continues to function.
One note: I was not able to use Vista to update to Hard-SPL after the Stock AT&T 6.0 ROM re-flash. Each attempt resulted in an updater error on the PC after the handheld entered bootloader mode. Did the same procedure on XP and it worked flawlessly.
Hey. Had the same problems but i solved it with flashing a AT&T Stock Rom first.
Now my Hermes with PDAVIET B&C WM6.1 Rom running like a flash
Without any freezes.
here is the link to my problem thread:
cu
poPY
raidzx said:
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
Click to expand...
Click to collapse
Sorry, but following those instructions does NOT solve my problem. It does for some, but not all.
What works for ME, is to turn off the Storage Card power saving.
gregma said:
Sorry, but following those instructions does NOT solve my problem. It does for some, but not all.
What works for ME, is to turn off the Storage Card power saving.
Click to expand...
Click to collapse
I will update the thread with your information, thanks!
Here is the link to the new MDA Compact IV Rom from T Mobile in NLD ver 1.93.1142.nld radio 1.0025.16
http://www.t-mobile.nl/persoonlijk/htdocs/page/service-contact/software-updates/mda.aspx
And STILL not available from T-Mobile UK!
What's the changes? Worth flashing? I use Tmobile but never did any of their roms, got an unbranded device...
Richard van der horst said:
Here is the link to the new MDA Compact IV Rom from T Mobile in NLD ver 1.93.1142.nld radio 1.0025.16
http://www.t-mobile.nl/persoonlijk/htdocs/page/service-contact/software-updates/mda.aspx
Click to expand...
Click to collapse
seeing as you use a T-mobile MDA IV NL like I do, can you tell me what the original HardSPL is ?
I need to reflash mine so I can send it back for repairs (bluetooth not working properly anymore), I flashed the above mentioned rom using the quick method (copy to internal storage) so I now have an original T-mobile rom and radio but the HardSPL still is not original.
Technically it should not matter for warranty but I would rather not take any risks and also restore the HardSPL, I just have no idea which one it is (1.34, 1.35, 1.93 from the SPL thread here on xda ?)
tismij said:
seeing as you use a T-mobile MDA IV NL like I do, can you tell me what the original HardSPL is ?
I need to reflash mine so I can send it back for repairs (bluetooth not working properly anymore), I flashed the above mentioned rom using the quick method (copy to internal storage) so I now have an original T-mobile rom and radio but the HardSPL still is not original.
Technically it should not matter for warranty but I would rather not take any risks and also restore the HardSPL, I just have no idea which one it is (1.34, 1.35, 1.93 from the SPL thread here on xda ?)
Click to expand...
Click to collapse
Restoring your MDA IV back to tmobile defaults is a bit tricky. You beter use the new rom update, a new SPL should be in the ROM (in the Chech version it was). I used the Chech ROM to resore my tmobile picture and used SPL 1.37, ROM 1.37 and radio 1.00.25.03. All of these can be found in the forum.
Riel said:
What's the changes? Worth flashing? I use Tmobile but never did any of their roms, got an unbranded device...
Click to expand...
Click to collapse
Well,
I've used custom roms all the way from dutty's to leo's... LAst week i've flashed the new t-mobile rom. I must say it is very stable and with a few tweaks it is a very good rom.
I did this flash because always with a custom rom there was something i didn't like or didn't work. The feeling i have from this rom (I'm also on the t-mo network of course) is that this one must be tested with the best settings and the best radio for this network... because i need an stable phone.
bdanen said:
Restoring your MDA IV back to tmobile defaults is a bit tricky. You beter use the new rom update, a new SPL should be in the ROM (in the Chech version it was). I used the Chech ROM to resore my tmobile picture and used SPL 1.37, ROM 1.37 and radio 1.00.25.03. All of these can be found in the forum.
Click to expand...
Click to collapse
so the Chech ROM also replaced your HardSPL, which you then replaced again with SPL 1.37 ?
(why replace the HardSPL again ?)
I guess I will round up a windows PC and reflash using the the rom update .exe and see if my HardSPL gets replaced.
(I kind of asumed the HardSPL never gets updated with a rom update, hence my confusion)
Shame there isnt a way to update the HardSPL without a windows PC
Should the HardSPL not get replaced by the update I can safely use the 1.37 version from xda ?
I am useing this rom at the moment and it is very good and very stable and very fast rom.
With other roms i had problems that my phone wouldn't wakeup anymore and needed to softreset it. With this rom so far i do not have the problem.
Ofcause i only use it for 2 days so far but i will let you know how it will be after a while. For the problem that the phone does not wakeup anymore with other roms i had that problem after 1 day already so i think the t-mobile diamond is differend then the real HTC diamond.
Only the t-mobile colors are terrible but there are enough themes and skins to change it to what you want.
Jan
feestbeest said:
I am useing this rom at the moment and it is very good and very stable and very fast rom.
With other roms i had problems that my phone wouldn't wakeup anymore and needed to softreset it. With this rom so far i do not have the problem.
Ofcause i only use it for 2 days so far but i will let you know how it will be after a while. For the problem that the phone does not wakeup anymore with other roms i had that problem after 1 day already so i think the t-mobile diamond is differend then the real HTC diamond.
Only the t-mobile colors are terrible but there are enough themes and skins to change it to what you want.
Jan
Click to expand...
Click to collapse
Did your HardSPL get updated too when you updated your rom ?
If no which HardSPL do you have now (if it is the original that is) ?
I run 1.40 olinex, it says wrong device ID.
?
I have original DIamond, is that problem?
I made a new rom which will work on DIAMxxxxx (all) diamonds.
It's full 143mb (including SPL and RADIO, so Stock, only diam200 is removed).
IF interested I put online. Made with Olinex nbh thing,
same problem here
Riel said:
I run 1.40 olinex, it says wrong device ID.
?
I have original DIamond, is that problem?
Click to expand...
Click to collapse
Same for me
This ROM will fix that. Please, use it if you NEED it to save my bandwidth
http://www.rielity.nl/RTC/RUU_signed.exe
(Its sfx-exe, no worries, not many people have 7z)
Riel said:
This ROM will fix that. Please, use it if you NEED it to save my bandwidth
http://www.rielity.nl/RTC/RUU_signed.exe
(Its sfx-exe, no worries, not many people have 7z)
Click to expand...
Click to collapse
Sounds great. So this includes a stock signed spl?
It is 100% the same rom, and you will not get the Device_id error.
T-mobile service-desk WILL see this is not original T-mobile rom I think because ROM name is not the same (T-mobile instead of 1.93.blabal).
sms problem
Help, I flashed this new t-mobile ROM and now I an't send SMS. They stay in postvak uit. In tried flashing another radio and settings in comm manager. But nothing happends.
Try this, I had the same problem with several other roms.
Thank you very much. I tried it and after a softreset it is possible to send SMS now.
REmoved the rom.
It's really too slow
Sorry to bump this one, but does the t mobile NL rom update the SPL to stock?
Yesterday I started to get problems with my HTC Touch Diamond. I flashed my device with udK Syrius HD R0 (BETA 5) and everything was going smooth, restored my contacts, my messages and tweaked WM6 a bit.
But after a soft reset to apply all changes the device welcomed me with the ordinary "You're using your device for the first time" message and I had to setup my device again. After another soft reset my device hung at the boot screen with ROM information and the "Touch Diamond" text.
All I could do now was a hard reset. But the problem didn't go away... the device kept freezing and resetting, and I had to do 2 or 3 more hard resets before I decided (actually I already had, but had to wait for the download to finish ) to flash to another ROM.
So I downloaded Vic Hybrid 2 Diamond ROM UC. Flashed and everything seem to went fine. But just as before, after a soft reset the device hung. Hard reset...
Why's this!? Is my HTC Touch Diamond broken or is there anything I'm missing? Perhaps this occur because of the ROM's is based on the firmware 1.97??
EDIT #1: sorry, wasn't meant to create this topic under "ROM Development"... Any mod, feel free to move it.
EDIT #2: Seems one more guy had this a relating problem after ROM flash (udK's ROM for that matter too): http://forum.xda-developers.com/showthread.php?t=455335
EDIT #3: "The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source. Press SEND to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to its factory default settings."... didn't have time to press any "SEND" button either... it continued to... guess? The setup! Entering date + time + calibrating the stylus...
*sigh*... not it happend again. Just restored all my SMS and tried to thread them again (screw that either way!), soft resetted my device... and the damn WM6 setup guide for clock, calibration showed up, and now "Installing..."
*sigh - again*
hi dude i had the same problem
i have a DIAM300 and had the olinex 1.40 hard spl with mossis rom 2.5 (ger)
i flashed mossis 2.6 which is based on 1.97 and i had those problems too, after a few softresets it makes a hardreset...then i tried olinex 1.93 thought it could be the bootloader but the problems were still there...
i tried some other roms, udk Syrius too which is fast as hell, but unfortunately the same problem here and sometimes it even didn't boot...
i made about 50 softresets, 20 hardresets, flashed bout 10 times....then i had enough, flashed the original O2 rom, flashed the original bootloader, flashed the original rom again, and now everything is allright, it's runnin, no hardresets, i tried about 20 softresets, installed software blabla....
but now i'm wondering if the problem will be there again when i start to flash
and its really annoying when u flash a rom, customize everything, everyting seems to be allright and then it makes a hardreset instead of a softreset....
gizz68erz said:
then i had enough, flashed the original O2 rom, flashed the original bootloader, flashed the original rom again, and now everything is allright, it's runnin, no hardresets, i tried about 20 softresets, installed software blabla....
Click to expand...
Click to collapse
Damn, I don't want to flash to the orginal ROM! Just flashed to a ROM I've tried earlier, based on 1.93, Panosha ShineOn, so let's see if there's any more trouble...
gizz68erz said:
but now i'm wondering if the problem will be there again when i start to flash
and its really annoying when u flash a rom, customize everything, everyting seems to be allright and then it makes a hardreset instead of a softreset....
Click to expand...
Click to collapse
Yeah, I feel the pain. Getting sickin' tired of this **** now!!!
Try this one
Hi
Whenever i have this kind of bizar issues [ also with previous devices i had before my Diamond] i did the following:
1. Flash back to original official ROM including Radio [ no need to compelrte the initial setup , just flash and go back to bootloader screen right after]
2. Flash again to the targeted cooked ROM
3. Probelm disapeared
My assumption is that for some cooked ROMs the coverage of files been flashed and replaced is not 100% and therefor we face inconsistancy issues.
Try it
my view of this
my view of this:
new roms have other architecture such as new manila new drivers etc etc (1.97)
when you "tweak" them such as manila mods wich are made for older versions this kind of problems can happen. the problem is we have to many modded roms right now. we have 1.37 roms 1.93 roms 1.94 roms (ported from raphael) 1.97 roms and so on. all of this roms you cant compare with each other.
a example: HTC Diamond Manila has no LANDSCAPE files. every rom wich has landscape support had included RAPHAEL Manila parts. no one can deny this. cause its the only device right now that offered the landscape support on manila. but looking to diamond application and software section here and the date this files were made are back in the past. this is just a example where this problem result of.
just my 2 cent
alphazero said:
my view of this:
new roms have other architecture such as new manila new drivers etc etc (1.97)
when you "tweak" them such as manila mods wich are made for older versions this kind of problems can happen. the problem is we have to many modded roms right now. we have 1.37 roms 1.93 roms 1.94 roms (ported from raphael) 1.97 roms and so on. all of this roms you cant compare with each other.
a example: HTC Diamond Manila has no LANDSCAPE files. every rom wich has landscape support had included RAPHAEL Manila parts. no one can deny this. cause its the only device right now that offered the landscape support on manila. but looking to diamond application and software section here and the date this files were made are back in the past. this is just a example where this problem result of.
just my 2 cent
Click to expand...
Click to collapse
Yeah, I bet there's some issues with the new 1.97 and all the new drivers. The chefs need to get stuff straight before I'm trying any new 1.97 based ROM out again.
My issue seem to have been fixed after flashing to Shine On 2.4 Full (1.93 based!). My device now soft resets OK, and I keep all settings... well, atleast for the moment. I'll continue to soft reset every now and then to see if the problem comes back to me.
Yeah, got EXACTLY the same problem with ROMs based on Touch HD or Quartz OS built Hard SPL 1.93 And I don't use any manilla mods, prefer its original view with original tabs. All I have is some portion of software to install:
- Inesoft Cash org;
- Inesoft Address book;
- Agenda Fusion 8;
- Alreader;
- Auto keeper;
- HiCalc;
- Navitel Navigation system.
and the only "tweak-like" soft I use is Answerkeysdisabler. But having serious intentions to reach the truth I didn't install it.
When I've tried to flash syrius beta 02 AND beta 05) I got a STABLE hard reset after 3-5 reeboots. And it doesn't correspond with the quantity of soft installed, it's just resets and thats all.
When using Aztor v7 i had 99% hangup when installing my software just after HR, and it always hangs on different program installation, then, after reeboot manilla cannot start.
These are very interesting ROMs, especially I like AZTOR's pholosofy, but... couldn't manage to give it a try
Tried SwiftBL's, Dutty's, Bepe's ROMS - all smooth and fine. And the STABLEST FOR ME was the old bElite 0,99d. NO issues at all! Now i'm usind Dutty's 3,4 in general it's stable and ok, but with some minor issues. Would be really nice to have issue-free ROM based on new versions of software.
Hi all,
I've been having ROM trouble lately. I flashed 2 ROMs over the last 2 days (the latest AZTOR & the lastest Morna, both excellent, btw), but they're both just not stable. A crash always occurs, whether due to ActiveSync, Manila, or during SetUp. Usually the fix is a hard reset, but obviously, I lose my contacts. Sprite BackUp helps, but a Hard Reset every 4 hours or so is really not an option. Carburano has recommended I flash a Stock 2.03, I haven't gotten around to that yet, cuz I need a workin phone 2 transfer the .nbh. Will that solve all my issues? Anything else I can do 2 increase stability?
For the record, I have Unsigned Olinex HARDSPL, the .25 radio, and was running the 1.93 based SwiftBlade ROM prior to the issues.
Thank you in advance for your assistance.
Yassin said:
Hi all,
I've been having ROM trouble lately. I flashed 2 ROMs over the last 2 days (the latest AZTOR & the lastest Morna, both excellent, btw), but they're both just not stable. A crash always occurs, whether due to ActiveSync, Manila, or during SetUp. Usually the fix is a hard reset, but obviously, I lose my contacts. Sprite BackUp helps, but a Hard Reset every 4 hours or so is really not an option. Carburano has recommended I flash a Stock 2.03, I haven't gotten around to that yet, cuz I need a workin phone 2 transfer the .nbh. Will that solve all my issues? Anything else I can do 2 increase stability?
For the record, I have Unsigned Olinex HARDSPL, the .25 radio, and was running the 1.93 based SwiftBlade ROM prior to the issues.
Thank you in advance for your assistance.
Click to expand...
Click to collapse
My friend, it's not a Rom stability problem... It's a known issue of all cooked roms... Please flash official 2.03 rom (if you cant from internal storage, install it in the classic way)... and then the rom you want... you will never have stability problem.