Hi Guys,
I am facing a strange problem since a few weeks. My Blackstone sometime does not switch back on again when I press the Power Button after it was suspended(=NOT switched off).
The only way the get it running again is removing the battery and putting it in again. After that the device takes a really long time to boot. Stays at the Smart Device Screen (with ROM info displayed) for about 30 - 40 seconds.
This happened about 4 times the last 6 weeks.
All ROMs used were from LEO - all kind of different versions. It also happen with the newest one 3.2
SPLs: HSPL, HSPL 1.56, SPL 1.56
Did anyone else notice such a behavior? Do you think this is a sign of a Hardware problem, or could it be software related?
Greetings,
Tommi
got that often when i do something stupid with it ie installing some software wrongly.
ive had to hard reset it each time, but luckily i had sprite backup before that at some point. and it works then
posted twice
Related
Hi,
I have a Qtek9090 which I upgraded yesterday to Helmi BA WM2k5 AKU2.6 Beta (v.1.1.2 Beta).
Everything went fine and I do like it (apart from the usual problems with WiFi, BT,...).
However I got into a shock-state when I turned it on this morning after leaving it in the craddle during the night for charging:
It would turn on, but the screen was completly f..ked up!!!
I did a Softreset -> screen still messed up
I did a Hardreset -> screen still messed up
I did reflash the upgrade -> screen still messed up
I took out the battery for half an hour and put it back -> still the same
After many resets and so on, suddenly I got the color stripes again and the phone booted normaly. I did not even loose any data.
Next I put it to charge again and after a while (the screen went off meanwhile), I turned it on and guess: scrambled screen again.
This time, I did the Reset this way: battery-notch off, kept the Softreset pressed and simultaneously put the battery-notch on again.
Is this a known problem (shouldn't be - I searched the forum!)?
Why does this happen?
Any ideas???
Also, I have these questions:
- What is this selection one has to do after the upgrade for (2. and 3. item YES)? What should the first item be: YES or NO? Can this be the cause for my problem?
- Would it be wise to downgrade again? (In case this is a defect -> so I can try to claim warranty, if things get worse...)
- What is the patch for energy management for? Where can I download it, as the link in the Wiki does not work? (Has this to do with my problem?)
Thanks,
vma
The problem remains.
It does not seem to depend on the charging, but happens when the device is turned off for some time.
When I turn it on it will either work fine, or funtion with a wild flickering screen.
Arrggghhhh!!!
Am I the only one with this problem?
Cheers,
vma
Hi,
Some month have passed on this issue. The reason I did not post about it, was because I had to send my BA for repair and one never knows if the "enemy" is listening... Now the warranty has expired anyway and mey BA is fully working.
It may have been a coincidence, but one day after the upgrade the screen went mad and totally messed up. Only 1 Hardreset in about 100 tries would bring it back to normal for some period of time and even reflashing it with WM5 or 2003SE would not make it work normal again.
The screen would get messed up suddenly for no particular reason, normally during a standby.
At the end I had to send it in for repair, which was actually a good thing, as I complained about the loose stylo and bad working hardkeys, all within warranty.
I got a new key-pcb, backside and they reflashed the device with 2003SE.
I am almost sure that I must have done something wrong with the upgrade to WM5.
Strangely I was able to flash 2003SE onto it, though it did still not work properly: hours with messed screen and sometimes out of the blue I would turn it on and the screen was OK again for a few hours.
Could it be a bad cable connection, which got repaired as well? Was it just a software problem?
One of the things I was in doubt with: when you enter this menu to format the device, the instructions say to switch two options, but the menu on my device had three options. Sorry - I do not exactly recall the details.
Anyone with an idea, why my device went mad?
As a side-note: while WM5 was great, while it worked during the one day it worked. I specially liked to be able to turn the device completly off or being able to remove the battery without loosing data.
However: not having my beloved BA fo two weeks made me reconsider doing experiments on it. Since I have it back I did not reconsider flashing it again.
But I would like to understand what had happend...
Cheers,
vma
May I assume from the lack of replies, that this was a pure coincidence on my device?
Nobody else experimented this weird problems after upgrading to WM5?
I am considering upgrading my phone again, essentially because I am tired of being afraid of discharging the battery and thus losing all data...
Cheers,
vma
Does anyone experience "Grey Screen of Death"??
Every couple of days my Diamond crashes, the screen is stuck displaying a noisy grey screen.
Most likely I will have to reinstall the ROM (I'm using SwiftBL 5.5) ... but if there is a simpler solution out there I'd love to know it,
Thanks,
Mike
I've seen that kind of screen but only when I'm playing a particular game and if I switch the Diamond off before closing the game down; when I next switch it on I get the noisy (mostly) grey screen. When this happens to me though I just need to toggle the power on and off a couple of times and it sorts itself out. Or just not switch the thing off when playing that game of course.
None of which helps you of course as yours sounds like a much more serious and randomly occurring issue.
never heard of it before. try changing to a different Hard SPL, these can have funny effects sometimes.
Thanks for reply. Well, at least I'm not alone.
Mine is more worrying alright. I left the Diamond in standby last night, it wasn't running any apps before that, and the phone didn't wake me up with my normal alarm as it had crashed sometime during the night, not doing anything in particular.
do you notice it get unusually hot at any time?
with some diamonds, when it is processing a lot and on charge it can get very hot, and this may have caused ur problem.
Maybe the Hard SPL will help.
One possibly odd thing I notice is that my ROM is listed as 1.93.00.00 on the bootup screen, I expected this to be 1.93.405.1. Is that usual?
It's not the hot or charging possibilities.
I can't find a pattern really, it definitely crashes just sitting there doing nothing.
Does this also happen with a stock rom?
I didn't see it on the stock rom, but that didn't last too long in my diamond and I've been running the Swift one for a couple of months now.
To rule out SPL and radio, you could try different versions there. If that doesn't help, try flashing another rom (maybe also the stock rom).
If this still doesn't get rid of the GSOD, I would send the phone back for repairs.
Sorry, I couldn't be of more help...
Good suggestions, thanks. At least there's something to try without flashing whole rom.
mine is the same, seems to only do it when phone is charging but idle overnight, and certainly not hot when it does it. I am running the stock 1.93 ROM. Maybe it just gets bored lol!
Then mine was very bored.
Always restarted itself during the night - and lost half the battery charge while doing so.
Had it repaired twice and now it works great. They told me it was a software problem, but I wonder what they fixed, because I have flashed the same SPL, radio and rom on my phone as before.
Glad you fixed it. Mine was ordered on the cheap from HK (to Ireland) so I'm reluctant to send it back except in dire need.
I often see it get very hot around the crash time, as if some app is running crazy, would explain the low battery.
BTW, what rom, spl, radio do you use?
I had the same exact problem up till a week ago.
Now I'm happily a satisfied Diamond user. To solve this issue, do either of the following:
1. Find a rom with a newer Manila version, e.g. Dutty > v2.6.
2. Install the latest Manila cab.
Changing hard spl doesnt work, as I had tried them all. Stock rom was more acceptable but the problem still occurs once in a while.
I had changed to Dutty's rom more than a week ago I haven't had the problem ever since. Try it and share with us if it works.
Reason I say its due to Manila is becos Dutty is using a newer version of Manila as compared to the rest.
Oooh, tasty. A confirmed software method of fixing the problem! I'll give that a go and observe the phone for a week. I'll post then if all is well.
Many thanks,
Mike
I'm running Olinex HardSPL 1.93, Radio BS14 and O2 Germany stock rom 1.93.207.2.
I hope knave's solution will do the trick for you.
Hi...
This just append to my phone sometime tonight..!
A left it charging over night ... like I always do..
and when I wake up... there's just a gray screen of death!
I've just flashed my first cooked rom... had stock HTC ROM before...
and my TF3D version is 1.2.35091.2_1813.6..
maybe this was just a freak accident... one time happening??
lets wait and see...
i'm backing up my phone at the moment to hard reset it later. i've got the problem, that in opera when the page (spiegel.de especially) is fully loaded and it idles for 5 secs, the screen turns grey with stripes and blocks slowly. after hitting power on/off 2 times it's normal again, but as soon as it's idling for 5 secs it fades to grey again.
must have messed up something while updating opera
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.
Ever sense I had this X1 (My second one now) some times when its in stand by and I try just waking it up by pressing the power button one time nothing happens...
I try holding it down nothing happens wont shot off wont wake up wont even wake up if I plug-it in to the computer I just have to restart it.
It has done it on every single ROM so far I have tried and 2 different radios.
Some times if some one calls it will ring through but I have to answer it with the hard keys.
I am at a loss here any one have any ideas?
So no one has had this issue?
Could it be hardware?
Mine does that too :-(
Hi,
I've had that same problem for a month or so. Can't think what the problem is but I believe its only been happening since I changed my rom.
I'll let you know if I discover anything!
omg this started happening to me recently i keep pressing it loads of times before it comes on and i am on generic uk stock rom!
its messing up -could this be a hardware issue? because if so thats not good >.<
I have smiler issue but it only happens with a Leo roms, never had it with any other rom (stock or custom)
At least I dont feel alone on this =P
I have only tested WM 6.5 on this one so I guess it could be Leo roms causing this. Any maybe some one can pin down a fix for it =D
I've had this problem ever since I've had this dreaded phone. And it normally follows by 100 attempts of pressing the power button, and finally a response, only to see a process has crashed and terminated... i cant remember which process though.
I used to have this. It has to do with a process crashing, then no key inputs respond and you have to restart the device. I can't remember which process but i think it was services.exe or device.exe
I'm not sure if it a freezing problem or it just won't accept any input
Basically after my Kaiser has been on charge overnight I will get around to using it and can't. What will happen is the screen & buttons will not work, although they can be used for a split second every 3 seconds.
After a reset everything is back to normal, so I'm not sure what the problem is, I don't have a lot of programs installed and only 1 has been install in the past month which is A2DP Today Toggle, so far I've un-installed it and left it again but I still have the problem.
Thanks for any help
I have a similar problem. In the morning i have to soft rest the phone for it to work. Issues started after 6.5 upgrade. There must a solution somewhere in here..........
Does a hard reset fix the problem? Does this happen with every ROM you've tried?
I have only stuck with the official rom, I bought it on 6.0 and then updated to 6.1 after it's release. A hard reset does fix it but some time after it will return, bear in mind this has never done it previously just about a month ago.
I guess it might be a issue with some program that is being installed