halpmf
24th March 2009, 08:03 AM
I've been lurking on these forums since I got my diamond, about 5 months ago, and i would like to say, I would have sold my diamond about 2 weeks after buying it if it wasn't for all the knowledge and tools available here. Thank you.
Now, I've been flashing my phone every so often, with ROMs such as Swtos, Panosha, Duttys, AZTOR, Wildberry, Dia Diut, and most recently (wherein the problem lies), NATALY 2.1, Cloudy 1.0 and udK Syrius R3.
Now with these latest three roms (2.03?), i started to encounter a similar problem over and over again, without exception. If I try to launch a program while another is using the CPU, the phone will begin to crash. First it will become unresponsive, then programs will no longer open, and eventually, the only thing that can be done is a soft reset.
For example, the alarm will activate (klaxon), i'll flip the phone, and hit off. Now I know the problem has begun because though the phone has returned to the home screen, the title bar may still show the image from the alarm. Now the phone will work like its cpu is being heavily engaged and I can never reach task manager to see what it is. The hard volume keys frequently cause the phone to begin behaving in this manner. Soft reset only solution again. TF3D still animates, but programs will never appear on the screen if you try to launch them.
Same sort of effect on Cloudy's and udK's, except after the soft reset, the phone would begin to reinstall the rom again, as if some sort critical error occurred.
I have a DIAM130, and i've heard that to install 2.03 base ROMS (such as NATALY2.1 and Cloudy, is that correct?) you should first install a 2.03 SPL and a 2.03 stock ROM, then upgrade the SPL, then the ROM.
The latest SPL i've seen here is 1.93, and installing this increased the stability of these ROMs from 30 minutes to about 1-2 days, but the same problem occurs.
(also, haven't been able to find a stock 2.03 ROM on here... am I blind/illiterate?)
Latest addition to this problem (first occurred a few minutes ago after the phone began reflashing itself again after the aforementioned problem): Windows began the usual first-time boot customization procedure, and is now giving me an error: Run FILEOP \Windows\Menu_FILEOP_Operator.txt failed.
Is there some sort of corruption or hardware failure going on?
Well, thanks in advance
EDIT: Problem solved by reflashing stock SPL and 2.03 ROM, then flashing what I wanted. The impression i get from the pros here is that I flashed a ROM which wrote to some memory location that shouldn't have been written to.
Now, I've been flashing my phone every so often, with ROMs such as Swtos, Panosha, Duttys, AZTOR, Wildberry, Dia Diut, and most recently (wherein the problem lies), NATALY 2.1, Cloudy 1.0 and udK Syrius R3.
Now with these latest three roms (2.03?), i started to encounter a similar problem over and over again, without exception. If I try to launch a program while another is using the CPU, the phone will begin to crash. First it will become unresponsive, then programs will no longer open, and eventually, the only thing that can be done is a soft reset.
For example, the alarm will activate (klaxon), i'll flip the phone, and hit off. Now I know the problem has begun because though the phone has returned to the home screen, the title bar may still show the image from the alarm. Now the phone will work like its cpu is being heavily engaged and I can never reach task manager to see what it is. The hard volume keys frequently cause the phone to begin behaving in this manner. Soft reset only solution again. TF3D still animates, but programs will never appear on the screen if you try to launch them.
Same sort of effect on Cloudy's and udK's, except after the soft reset, the phone would begin to reinstall the rom again, as if some sort critical error occurred.
I have a DIAM130, and i've heard that to install 2.03 base ROMS (such as NATALY2.1 and Cloudy, is that correct?) you should first install a 2.03 SPL and a 2.03 stock ROM, then upgrade the SPL, then the ROM.
The latest SPL i've seen here is 1.93, and installing this increased the stability of these ROMs from 30 minutes to about 1-2 days, but the same problem occurs.
(also, haven't been able to find a stock 2.03 ROM on here... am I blind/illiterate?)
Latest addition to this problem (first occurred a few minutes ago after the phone began reflashing itself again after the aforementioned problem): Windows began the usual first-time boot customization procedure, and is now giving me an error: Run FILEOP \Windows\Menu_FILEOP_Operator.txt failed.
Is there some sort of corruption or hardware failure going on?
Well, thanks in advance
EDIT: Problem solved by reflashing stock SPL and 2.03 ROM, then flashing what I wanted. The impression i get from the pros here is that I flashed a ROM which wrote to some memory location that shouldn't have been written to.