Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Just for future reference...never has your phone been a brick. A bricked phone is just that...a brick, a paperweight, won't do anything at all. It can't be turned on, it can't boot, it can't be reflashed or fixed. It's obvious you're having a problem with something, but I constantly see people on a daily basis saying their phone is bricked when in actuality, very very few people have actually bricked phones.
Sorry, but I have no idea. You're apparently alone in facing this.
Have you tried reflashing to another third party or stock radio/ROM combination to help rule software or a bad flashing out as a cause?
mrfantastic said:
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Click to expand...
Click to collapse
What bootloader are you running? Maybe a bad install of the bootloader?
no, that's not a possibility, the bootloader isn't like a copy of Windows... besides, it's getting stuck on the windows mobile logo, that means its at the kernel.
my advice is to dump that ROM and flash something else.
Olipro said:
my advice is to dump that ROM and flash something else.
Click to expand...
Click to collapse
In case that is interpreted negatively, quite a few are using builds from my kitchen and he's been quite alone in reporting this.
Sorry, I just had to chime in to defend my work.
That said, if one is facing such problems the first avenue to problem solving is not to keep flashing the same radio/build of an OS ROM into perpetuity. Mix things up. Isolate.
I'm not saying i'm 100% positive on this one, but sounds like to me he's using some kind of software that is coded poorly, or something that is corrupting his kernel or the necessary files that boot the os. Sounds like the phone is getting hung up right when it's trying to execute these files at boot.
My advice to you, that is if you want to keep using key's rom, is to create a CLEAN rom, and don't install any software. Run it for a while clean and see if the problem goes away...if that's the case, you need to re-evaluate which software you use.
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
This is a very misleading title for this post. You can't unbrick a true 'brick' - unless it was a brick because you left the battery out.
A true 'brick' can't ever be turned on. It's a dead paperweight. So, there's no chance of unbricking it.
Flashed Keys rom to few phones....never had a problem !
I used olipro 2.40
Right now the phone is fine, it appears to happen randomly, Keys rom is great otherwise (no insult intended). What was meant by the problem with HTC home?
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
Click to expand...
Click to collapse
The windows mobile splash screen or the "silly green screen that says windows mobile" as you put it is not HTC Home. It is not HTC Home that is causing him to lock up at boot time.
To the OP, read my post, it's some piece of software that is causing your lockup. Guaranteed, if you make a clean rom (no software installed except the rom, with nothing cooked into it) I bet you see your problems go away. I then would install each piece of software one by one testing to see if you see the lockups after each one.
help
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
kaos29205 said:
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
Click to expand...
Click to collapse
Kaos,
You will find you get more answers by posting in the appropriate thread. This is not a WM6 thread so chances are that most ppl would ignore your post.
As you are probably on dcd 3.0.x, I have answered your question over there in the dcd 3.0.4 thread. http://forum.xda-developers.com/showpost.php?p=2177772&postcount=459
Apart from the fact that your are more likey to recieve an answer when posting in the correct thread, it will also help others with the same problem find the answer wheb they do a SEARCH.
Also another good place to find general information is in the titan wiki (see the sticky at the top of the titan upgrading section).
Lastly, you could try starting a new thread if you just cant seem to find the appropriate place to get your answer.
Related
I have searched this and could not come up with any fixes, but here goes.
On my 8525 most of my front buttons would quite working (Send, End, OK, Start Menu, and Both Top Menu select buttons) on every Cingular 2.06 Rom. This would be a daily thing that could be fixed by a soft reset. Then I upgraded to XDA Live 2.0 everything worked great for a while when all of a sudden all of the front buttons stopped working, all of them except the dpad. I did a soft reset and even a hard reset, and every time it would still not be working. I freaked out the only thing I could think to do is to downgrade to the original Rom 1.34 that was on it when I received it so I could try to send it in for warranty. After the downgrade all the buttons have been working now.
So in my mind I am thinking this is a software issue rather than a hardware problem. But if that is the case what would cause this? Is there any kind of fix?
I really want to put WM6 back on my device, but not at the cost of my hardware buttons.
Any help or advice would be greatly appreciated.
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Never heard of this problem before. There is a fix for the 8525 keyboard in the XDA Live extras, but I'm almost certain it doesn't affect the front buttons.
I'd almost say that its a problem physically with a broken/barely connected button membrane or something similar.. and the action of you moving the phone to reset it/pressing the button is enough to connect it again.
If you're sure its working 100% now, try flashing XDA Live again and seeing if it kills it again!
Philux-X said:
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Click to expand...
Click to collapse
Just a couple ideas. First, what 3rd party apps have you installed after upgrading and have you changed anything in the "softkey" program? Also, when you said you did a hard reset, was it a real hard reset, or just a power down? Some people at first get the two mixed up.
Also, the radio and bl wouldn't have anything to do with a problem like this.
Like TAURUSBulba said, I would think that it HAS to do with some cab/registry or executable you install that is common to all the ROMS that makes it do this. I would suggest you check out your installed applications and research what might create this problem.
The Rest was an actual "hard reset" with nothing else installed on phone except for system files (fresh system). I did not think the BL or Radio would have anything to do with it, I just wanted to be sure. I will try to re-upgrade to XDA Live 2.0 again when I can find some extra time. I will post results if anything changes or I continue to keep having this problem.
I appreciate your feedback.
Thank You
Hey guys,
I successfully put Gullum's V5 Touch ROM on my Jamin and I have been using it since it came out which is a few weeks I think. Today I went to reset it and it's just stuck at Gullum's grey themed Prophet Touch the boot screen.
Does anyone know why that would happen after using it no problem for a while? Can I get any of the info on it back as I didn't syncronize it for a week. I'm guessing a Hard reset will do the job but now I don't trust the ROM if it just randomly locks up.
why didnt you flash to v6 instead?make sure you do step 1 first then proceed to doing step2.gullum is one of the best.beta testers rules!
rovert said:
Hey guys,
I successfully put Gullum's V5 Touch ROM on my Jamin and I have been using it since it came out which is a few weeks I think. Today I went to reset it and it's just stuck at Gullum's grey themed Prophet Touch the boot screen.
Does anyone know why that would happen after using it no problem for a while? Can I get any of the info on it back as I didn't syncronize it for a week. I'm guessing a Hard reset will do the job but now I don't trust the ROM if it just randomly locks up.
Click to expand...
Click to collapse
My advice: look an search a bit more before you start a new thread. There is one (very heavy) allready about this topic. There's even an tips and tricks Wiki-page that makes notice of this problem.
My personal solution: don't restart with the cube active.
It's difficult to search threads that have pages and pages of information. My eyes can only take so much scrolling. And even using the right combination of words to search for is the next thing to be successful at. Anyways I don't want to argue with you as I have been trying to keep up with information as some of you more 'experience' have learned and retained.
I always downgrade before I upgrade and I have done it many times as ROMs just keep coming out by the week!
I'm just wondering if there is anyway to get my Pocket PC back up and running to at least get an excel spreadsheet that is in internal memory. If not then I will suck it up and hard boot it. I'm just confused why a soft reset lead to a full boot screen freeze after countless soft resets before.
We don't going to argue my friend.. it was just a friendly advice!
But did you find the thread that deals with this problem? http://forum.xda-developers.com/showthread.php?t=320689 It realy tells a lot about problems and solutions experienced by other pp.
As about your wish to backup from the bootscreen (if I understand you correctly) I really don't know, never heard nor red about it.
But I did read that someone managed to start up again by removing his SD card, perhaps worth trying.
First I'd like to truly apologize if this question has been answered before (which I am afraid it may have been).
But today I flashed my Verizon XV6800 with a 6.5 beta5 rom.
Well, after it installed, um, well it won't load basically. After the "Windows Mobile 6.5" screen pops up, a white screen comes up. I don't exactly know how to fix it and reflash it or anything, because my phone isn't detected.
Is there some way to reset the ROM? Like, holding down buttons while it's loading?
I'm truly sorry if this has been answered before, and greatly appreciate the help.
Flash a GPS radio and then hard reset. Followed by a battery pull for a few minutes.
How to get into bootloader is power camera and reset button at the same time. I usually press power and camera at the same time, then press reset button for a sec and let go of them all.
First off, thanks for the reply. Also, I am from Pittsburgh, PA. Cool coincidence. Well, a little north.
Now that I'm at the boot screen, it was able to update again. I know you probably get this question often so thank you for taking the time.
I'm afraid to reinstall that 6.5 mobile beta I tried before. (I'm going back to 6.1 right now). Is there a good 6.5 you recommend? I'm going to try the search feature here, but was interested in what you think was best.
ThomasX said:
First off, thanks for the reply. Also, I am from Pittsburgh, PA. Cool coincidence. Well, a little north.
Now that I'm at the boot screen, it was able to update again. I know you probably get this question often so thank you for taking the time.
I'm afraid to reinstall that 6.5 mobile beta I tried before. (I'm going back to 6.1 right now). Is there a good 6.5 you recommend? I'm going to try the search feature here, but was interested in what you think was best.
Click to expand...
Click to collapse
Once your bootloader is unlocked and you have a GPS radio you can try as many as you like. I guess I would stay away from Beta ROMs. Other than that I dont have a recommendation.
Hey!
I've noticed that in a few applications (or settings) i have issues with my touch-input. This is e.g when changing the default ringtone i can't just tap "ok" but have to press the "ok" button from the side with my whole finger, otherwise it won't be regocnised. Sometimes when using the keyboard, the buttons on the right side are very hard to use. That would be the "p" "l" and "backspace". Have anyone else had this problem? The weird thing is that sometimes it works perfect, but sometimes it's just a pain in the ass to get things done?
I think sometimes the touch screen can just not work properly, just luck of the draw I guess.
Has yours always been like this or is it a recent change? I am assuming its always been like this.
if it has then its a hardware failure (most likely) and will need to go back under warranty for repair.
If its a new change, then what has happened to cause it? Could just be a new rom or something causing the calibration to be off.
It hasn't always been like this. Lately it has begun to screw with me. And i don't think it has anything to do with luck, since it's always the same programs that do this. e.g. changing ringtone, accepting the google maps license on first run etc.
One could think this is a hardware failure, that's what i thought at first, but the strange thing is, that the same "area" on the screen works prefectly in other applications. I've tried several roms, but they all act like this. Perhaps I should install the stock rom and try with that.
I have a similar issue, and even more, sometimes once I am pressing the screen, the keys are starting to "dance" like the hero is trying to think which button to choose, by itself, and I am watching it, and smiling :-(
I've had it since SenseHero 1.5 and others as well. I just reinstalled the official htc rom and calibrated again the screen... but I am afraid the issue is still there, though less frequent...
Next week at the doorsteps of Orange I guess
Possibly is lag related?
Maybe the phones memory management is not working very well on the ROM you have installed and is causing large amounts of lag that the phone is interpreting touches (or not touches).
Lennyuk said:
Possibly is lag related?
Maybe the phones memory management is not working very well on the ROM you have installed and is causing large amounts of lag that the phone is interpreting touches (or not touches).
Click to expand...
Click to collapse
Possible, But with all the speed tweaks, task killer and stuff, maybe even the overclock widget that I started to use only after this issue appeared... don't know, have no idea how to solve it.
Now it is like beginning, with official htc rom, no additional apps installed neither contacts, and still, I have this issue.
Suggestion?
Got the exact same problem.
Almost exclusively buttons on the bottom of the screen and as you already said the right part of the keyboard (especially the goddamn backspace drives me nuts sometimes!).
It hasn't always been like this, started somewhen after flashing more than just Modaco I think.. And the severity varies a lot, sometimes I got barely any issues and then again I can't even finish an sms. Unnerving.
At htcpedia someone who obviously has the same problem pm'ed me his solution:
Your Problem with Screen
I had to wipe everything of.... installed the WWE original ROM, then re-root the phone and now working with Modacco 3.1, seems to be working ok now....think the problem was with LOX latest ROM.
Click to expand...
Click to collapse
I think - not sure - it startet with some lox rom for me too. Do you remember which Rom you were using when this first occured?
Well anyway, might give it a try.
I haven't tried it yet for 3 reasons:
1 - the link for the german version of the original firmware is down
2 - i don't have a windows computer, so the .exe is pretty much useless for me
3 - I'm way too lazy as currently it's not that bad
same problem
hye there, I seldomly post here..
But i got the same problem before... keyboard dances, hard to click OK... could not finish a sms without swearing F*** F***..
yep, its a hardware problem.. maybe its bcoz of the shape of the hero making its touch screen easily damage.. Not sure though..
flashed so many roms, to try to fix this problem.. thought it was a software issue.. but.... nothing..
went to HTC care centre.. and changed the touch screen (warranty, had to revert everything to stock) and now...
Good as New with Villain 3.4
hope this helps...
Oh thx guys. "Happy" not to be the only one with this issue. For starters I'll try the solution with the original rom. I think I still have some version of windows installed on one of my harddrives. If it don't work I'll have the screen changed. I'll report soon.
rehet said:
hye there, I seldomly post here..
But i got the same problem before... keyboard dances, hard to click OK... could not finish a sms without swearing F*** F***..
yep, its a hardware problem.. maybe its bcoz of the shape of the hero making its touch screen easily damage.. Not sure though..
flashed so many roms, to try to fix this problem.. thought it was a software issue.. but.... nothing..
went to HTC care centre.. and changed the touch screen (warranty, had to revert everything to stock) and now...
Good as New with Villain 3.4
hope this helps...
Click to expand...
Click to collapse
When you revert to stock Rom, do you need to reinstall a stock recovery as well? or is it automatic? because I reverted and when I try to boot into recovery with "power + home" I get a kind of error: the symbol of a triangle with an exclamation mark in it, and a phone symbol lies down beneath it.
Is there another way to go into recovery? or is it not installed actually? (I went back to the official RUU from htc site).
Thanks for the help.
Ok, I've just tried the solution with the stock rom. As a matter of fact, it does fix the keyboard-issues. However, some of the other random touch-input-issues still persist. I can't really see how this could be hardwarebased, since the same area on the screen works in other applications just fine.
The official rom from HTC completly restores your phone as it was when you got it. You'll have to install your custom recovery again, as you did the first time.
I had a similar issue.
A fix for this: VillainROM6.1-Full-signed.
Now, keyboard its ok.
Try it.
Hi, im having a MAJOR problem with my HTC HD2. Every time i lock the phone, and turn it back on with the End button the touchscreen locks up and does not work. sometimes it goes on for hours, Unless i take out the battery which is getting quiet annoying..
I think its the New T-mobile Update, or could it be the HSPL? my friend said its software issues but im just not quiet sure, please help me!
DONT REPLY TO THIS THREAD, Instead, Reply here where me and others will post our ROM, Radio, and HSPL version.:
http://forum.xda-developers.com/showthread.php?t=841505
I had to send mine into HTC, and this is becoming a problem for many now, and it looks like it's growing. Try waking up with any other button besides the end key after a hard reset or battery pull, this is a temp fix at best, but occasionally it will still freeze. If under warranty I would suggest sending it in under repair and not mess with the new T-mobile update.
What am i supposed to do? Im using my Motorola RAZR until i find a fix or get a new phone which will be a very long time.
Hey,
I had the same issue, we should start tracking it so we find out a common problem, Try posting your HSPL version, rom, and radio in this forum and we can see if we can find a common solution.
http://forum.xda-developers.com/showthread.php?t=841505
Lucky
yep. not uncommon:
http://forum.xda-developers.com/showthread.php?t=757117
http://forum.xda-developers.com/showthread.php?t=758846
http://forum.xda-developers.com/showthread.php?t=775333
http://forum.xda-developers.com/showthread.php?t=814584
http://forum.xda-developers.com/showthread.php?t=822777
http://forum.xda-developers.com/showthread.php?p=9248922