Develop Bugs

White screen of death

Hello everybody,
I seem to have a major problem with my XDA Orbit: Not only it shuts down with no apparent reason so that I have to reset it, but it shows sometimes the dreaded "white screen of death" - from now on "WHISOD". The screen all of the sudden slowly goes white and sometimes shows dark vertical bands. After that - if I am lucky - I can reset the device, however a couple of times I already had to hard reset end even reflash it.
I have already checked software and plugin problems and would rather say that it seems to be a hardware problem. Any ideas out there. They would be highly appreciated.
Best regards,
Smack

i had the same problem and as at now my phone is dead becuase i did not flash it with the original rom. look for the rom it came with and flash it to the phone ,like how u first got the phone or u will loos ur phone very soon

I am not at all sure if it has to do with the ROM. I have tried different ROMs to check the error but it appeared with all of them. However the next time I will try again with the latest official ROM.
Thanks for the comment and your help. BTW Did you send your Orbit in for repair?
Regards,
Smack

Hi, do you use the uspl before every new rom install? Try it.
I have the same problem, my htc3300 is almost dead I think. No way I can even turn it on, allways end in the windows screen, and it was because I didn`t use the uspl before last rom install.
Give it a try, and let us know.
See ya.

Thanks. No flashing problem. I have flashed a couple of devices (always unlocking them before ;-) )and have had no problems whatsoever.
The problem I mentioned is not connected to any earlier flashing. The device works a couple of hours perfectly. However suddenly it starts to behave like crazy.
Now to your problem: If you can get into boot loader modus you will most probably be able to unlock your item. Search for uspl and download it. Then get into boot loader mode (press voice recorder button and power button while resetting the device) and you will get a three colored screen. Then connect the USB cable. You will see "usb" in small fonts on the screen of the device. Now you can run uspl. With a little luck the device starts again. However you can flash it again with a fresh ROM the same way (after unlocking it). This may (!) work.
Regards,
Smack

Hello,
I have the same problem, I already hard reset end even reflash my p3300 many times with different ROM.
I even tried running it for some time with and without the micro SD, ending with the same result: the screen of death.
Any ideas , tips, anyone ?
Thanks,
Roundi

Ok, I tried the following: Just take the battery out for six or seven hours and insert it again. The device seems to run smoother. Will keep you posted. Tell me if it works out for you.
Regards,
Smack

Ok, just removed the battery, I will leave till tomorrow morning.
I will keep you updated.
Thanks,
Roundi.

I have same problem here - though mine is the second phone and the fifth motherboard I've had. HTC just don't seem to able to fix it. I'm now trying to get a refund.

Hi, Jem.
Yes that's something I have thought about too. Did you you use the original ROM? However right now the system seems to be more stable. I have had only one blank screen after removing the battery (and one shut down).
Regards,
Smack

I have just put in the battery and switched on the phone after almost 24h.
So far so good.... I will try to use it for a while and will let you know.
Regards,
Roundi

Had the same problem again, when using Mortplayer. I have Mortplayer installed on the SD card. Could it be that the problems arise, when there is heavy usage of the SD Card?
Any ideas are welcome.
Regards,
Smack

Again it went SOD shortly after turning it on. I didn't launch any applications.
I am stuck here.....

indeterministical crashes

Hello,
I have a strange problem with my HTC Artemis (O2 XDA branded, bought in Germany, no lock)
It behaves unstable and indeterministic.
Unstable means that it crashes/stucks or turns off.
Indeterministic means that it happens when i plugg it to charger, when i'm syncing, when a phone rings, when using applications/tomtom or just i arrive to work and i find the device off.
When it crashes or i find it off, the biggest problem is to boot the device. It takes me typically 10mins, when i'm always trying to press the power button, push the reset button or unplugg the battery for a while in random order until i bring it to work.
After first crach, the device also often crashes or stucks again during the boot process.
Once, the device was so dead, that it took me two days to bring it into bootloader mode and then i could at least flash the ROM.
All these was happening with ARTEMIS TOUCH 4.01 WWE - LITE NO CUBE.
Yesterday, i switched to ARTEMIS TOUCH 4.02 WWE - LITE NO CUBE (burned FW twice) without installing any other applications and the problems are still here
My personal feeling is that it is getting every week worser.
When i bought the device (eBay), there was original FW with Win Mobile 5 on it, i immediately flashed to ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device. So i flashed to 4.01 and this issue was away, but approx 2months ago, the above described behaviour has started and nowdays i'm fighting with it 2-3x a day.
so, can anybody help?
GiZMo

Similar here
I have a similar problem, what's really strange to me is, that as far as i can recall it started happening 2 months ago or so also!! weird huh...
my device simply reboots from time to time! even while i'm making a call.
the weird thing about these reboots is that when it comes back to live i do not have to enter my pin to enable the phone! everytime i perform a manual reboot (by software, using the pin or remove battery) i have to insert my pin to able to make a call...
i have upgraded from 3.01 full touch to 4.02 full touch about the time it started, i have now 4.02 vanilla touch but problem still occurs from time to time.
any ideas?

Im another one to join this boat!
Bought an MDA C 3, two days ago, bought of someone from gumtree.com.
Worked fine for the first hour, and then locked up - nothing on the screen, no LED. Only way to get it going was to remove battery and then press power button.
I upgraded the ROM from the original t-mob UK WM5 to mechles fine release: http://forum.xda-developers.com/showthread.php?t=371182
The lock-ups / crashes have now become rarer, on average every 4 hours (before was every 1 hour).
There is no pattern to them either, although I have saw the screen trun all corrupted just before it happens. The last one was caused when I pressed the 'start' button.
I'm on a T-Mob contract, and lost my Kaiser, got ripped of when I tryed to replace it by a tosser on here for $375 Thief on the loose thread, and was hoping my luck had changed when I bought this one!!
It is T-mob branded and I wonder if there isn't a fix on here, would T-Mob repair it under warranty??

same "issue" with no entering of PIN after reboot. But not always

GiZMoSK said:
ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device.
Click to expand...
Click to collapse
here i found a good description of that issue:
"
Originally Posted by lasertony
I've got the same problem as !Novy, but nobody seems to have noticed his question. Are there any other guys out there with this strange problem ? I have been using this rom for a while and sometimes, without any visual warning the phone freezes up. This is particularly ennoying because there is no way to check wether it is working or not. Every other function or software keeps working ! The phone is just not receiving any calls or sms. So you can miss an entire day of calls and sms without knowing... Only when trying to call somebody the dialer says 'Dialing...' and nothing happens. No connection.
A soft reset is needed to get the phone working again.
"
btw, now i'm again trying to turn the device on, it's again stuck. grrr

Hello,
i had a few weeks ago a similar strange behaviour.
After changing the sd-card I had problems to turn the device on. After a hard reset it began to boot but hang.
The I flashed back to original O2 ROM. Then I had a unpredictable behaviour. Somtimes no sound. Sometimes I cound not be called. Sometimes Error message "no sim card". After every reset i had an other error.
Hard reset and flashing was no solution. Removing battery for less than 4 hours has no effect.
Then I wanted to send it back for repair. I took of the battery. The next day I wanted to try a last time and surprise: The device works fine without an error. Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
regards
Andre

It is Happening to my device too!!
It stucks every 2-3 hours!Tried many of the cooked ROMs but nothing.Also tried all the radio roms for 1-2 days.still the same!
It stucks with no particular reason.SOmetimes in s2u2 sometimes when am receiving a call.... etc.
Had the pin problem too for 3-4 times!
I will try your sugestion ANDRE and we will see!
Also i will try flashing the original rom,cid unlock and then flash the cood rom twice!
Fingers crosed....

Andre1210 said:
Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
Click to expand...
Click to collapse
didn't help
happy u
now, i will try to flash back original german o2 rom

I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!

bricked or not?
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?

Vinnie1 said:
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
Click to expand...
Click to collapse
I thought it was a battery problem too, but I've 2 batteries and both are died in the same time? I think it's too strange...
My P3300 have this problem from when it is returned from assistence and with original firmware (without other applications).

dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
GiZMoSK said:
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Click to expand...
Click to collapse

jahrami said:
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Click to expand...
Click to collapse
but i cannot get into bootloader mode so no flashing from SD card or PC

bricked device
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?

GiZMoSK said:
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
Click to expand...
Click to collapse
the good sign are the leds that means you have a very good chance...the guy made the piont...check the wiki

random crashes are often caused by hardware malfunction...sometimes the connection on the motherboard stuck,get broken or make a short-circuit...so check the hardware

T-Mobile Dash doesn't want to boot

Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.

hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
Take out the memory card and try to boot her up. If that does not work.. call T-Mo and get a new one

To get past the error 270, download the SDA Unlock app. That should get you past the error there. As for not getting past the Windows screen, I had that problem too. You should be able to get it working by hooking it up to the charger. I found that my Dash was not reading the battery as having a charge. I am not sure if I have solved the overall problem yet but, just in case, you might avoid using the USB as a charger and go with the wall charger. Just keep it on the USB long enough to sync and unplug.
Hope that helps

hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
do a hard reset hold da 2 soft keys and press the on button keep holdin da soft keys until u see a screen asking u do u want to do a hard reset hope dat works

Thanks for the responses guys but i've already tried all that. The only thing i haven't been able to try is do a hard reset with the wall charger plugged in, for some reason it doesn't matter how many times i do the steps it never shows me the black screen. I might be on the same boat as you because the battery i got with the phone is some cheap counterfeit chinese crap. I'll keep trying to get to the black screen with the phone plugged in but any other help would be greatly appreciated.
Btw, i can't do anything with T-Mobile because this is an unlocked phone i got somewhere else and can't return it so i'm stuck trying to make it work.

Check sticky to make sure doing correctly
Hard-Reset & Bootloader there is 2 x options there.

I was doing it right.
So after a million retries i got the phone to boot and do the cold boot thing. Then, i did the usual steps for putting a newer rom with WM6.1 on it (RUU_Excalibur_WM61_Kavana_080408_WWE). It worked, rebooted and went into the home menu, i thought i had brought it back from the dead until i inserted the sim. I got the sim failure message and when i pressed done it crashed. Now it won't go into the home menu no matter if the sim is inserted or not. Already tried to see if the sim was making good contact by putting pressure on it, no change.
This is too frustrating.

Ok so i've semi gotten it to work by booting it up without a sim, turning flight mode on, inserting the sim and then turning flight mode off. I get asked for my pin, the phone registers and i can make/receive calls. The problem is that a) it eventually loses the connection and b) i don't want to be doing this every time i turn the phone on.
Any ideas?

Password Problem

Hello guys,
I have a TP2 with T-mobile.The only Update that I've done to it was the Htc update to 6.1 and the 1% increase update. nothing else. Today on my BIRTHDAY, all i did was wake up turned my screen on to type my password in which hasn't changed since I first got the phone, and every time i typed it in and touch on the UNLOCK key, it would say it was incorrect. I know what my PASSWORD is im 100% sure of it..moving on I tried for a few more times and it kept on saying the same thing, So i decided to take the battery off and turn it back on . It started up just fine, I typed in my PASSWORD and touched the UNLOCK Key and Didn't let me go through with it THERE WAS NO !Notification that it was PUT IN incorrect or nothing:/...I did the battery off, and back to On, I Also took the Sim out and put it back in, but still same thing...Thought about the HARD RESET, I pushed it in with the Stylus pen..and when it took me back to the PASSWORD screen, I typed in my PASSWORD and it did the same thing :/. I really don't know what else to do.

I suddenly discovered that my TP2 with a 6.5 ROM which has been working for a while now is no longer accepting my password. This password is the same for all my phones and so i am 100% sure that it has not been changed. Is there any other way i can get past this password screen and clear it without hard resetting the phone?

stop stealing peoples touch pro2's...

da9th_one said:
stop stealing peoples touch pro2's...
Click to expand...
Click to collapse
They do not try to steal anything.
The WM Password system is buggy: the enter button after you have entered your password is not functional (it does not even say wrong password !)
And it is not funny at all, you loose ALL your data because of this stupid Microsoft bug.
If someone has a solution ?

I just had the same damn problem. Does anyone have a solution at all? It happened right as I entered the NY AutoShow and really wanted to take pics. WTF is this nonsense.

KnightmareCS said:
I just had the same damn problem. Does anyone have a solution at all? It happened right as I entered the NY AutoShow and really wanted to take pics. WTF is this nonsense.
Click to expand...
Click to collapse
I have investigated heavily on this problem.
... unfortunately no other solution than hard-reset (so I did it.. )
And then NEVER reuse this crappy WM built-in password login.

What a buggy POS! Looks like I'll be testing S2U...
THANK GOD I HAVE My Phone! It saved all my pictures/texts/contacts/tasks! All but the only video I had, which luckily wasn't important.
Now just gotta hassle with a hardreset and reuploading contacts.
Thanks Chris for confirming there's no other way.
PS to other people reading- using 1,0000,1234 does not work!
Also: DOWNLOAD My Phone and set it to sync EVERY NIGHT if you have a data plan. Definately is a LIFE SAVER!

KnightmareCS said:
What a buggy POS! Looks like I'll be testing S2U..
Click to expand...
Click to collapse
I have done the same, I moved to S2U2
It is a slick software... the only annoying thing it that it requires you to slide a cursor EVERY time you turn on the screen !!
that's a lost of time. Having to do that after a certain number of minutes in idle, would have been better. I wonder if there is a solution for this.
That's what I missing from the WM built-in locking feature.

Desire broken for good in just a second?

Hello all,
BIG problem here.
A few hours I update the MildWild oxygen rom from 4.6 to 4.6.5. For a few hours everything went totally amazing. But a few minutes ago I turned on wi-fi, but he didn't connect. So I went to MySettings app, but he didn't response. Nothing worked anymore. Only screen of and on, but then I hadn't also the lockscreen. Then the screen turned off, and I couldn't get it on
Pulled the battery out, and put in back in, but my phone didn't restart. Now I plugged in the charger, even the light of charging isn't turning on.
What the hell is the problem with my Desire? He can't be broken in a second if everything worked super well a few seconds before that all?
Tried a different battery but also then he isn't doing a ****... This whole problem came just out of the blue, that's what makes it really awkward to me.
I hope you can help me, I don't want to leave my lovely Desire.
Greets Ramon.

After all sort of things trying, I thought... let's take the sd card out. And luckily he turned on, feels like heaven...
Sd card back in, phone worked also. Don't know what the problem could have been, but my Desire works again.
I hope this maybe could help some other people who had/have/ gonna have this problem!
Close thread please :good:

Hello,
This morning suddenly, the same problem happened... Turned the screen on, swiped to unlock, but during the swipe the phone hang.This time no fear, because I knew what I had to do: take out the SD card.
Too bad, this doesn't work this time. The problem is exactly the same as last time, but know even without the SD card, the phone don't boot, don't charge. Couldn't get into bootloader also. The day before yesterday I flashed Mildwild REDUX V1, but this worked good.
What could it be?
Thanks in advance!
Greets Ramon
Edit: The last time this happened, when the phone finally booted, I directly got a message called something like "android.....com stopped unexpectedly". So that was the reason the phone stopped. Now it would be the same problem I think, but I can't turn the phone on. I just called with HTC, and because I'm out of the warrenty period, I will have to pay the repair (if needed) I think it's not broken, it's probably the same problem as last time...

The phone 'works' again... But it's in a bootloop, and going to recovery results into a bootloop also so I can't access the recovery. So I flashed the recovery again using ADB, but still I get the bootloop! What should I do?