Hello, a long long time ago I installed an Android ROM onto my phone because we all know that WM 6.5 was a total fail. Everything up until now my phone's touch screen completely stopped working, no response at all. The only thing that is functioning properly are the buttons.
As of right now I have tried installing a new ROM, but I can't because in the ROM that I have, the connection default is to charge the phone but I can't access the menu after countless tries getting to it. I also looked up past threads with those who had similiar issues, but I want to know if there is any new methods to fixing this issue. Any help is greatly appreciated, thank you.
Related
Hey guys,
So my touchscreen totally died yesterday, wouldn't respond to any touches at all, hardware buttons still worked however.
Assuming this was a hardware fault I was just going through the motions to book the phone in for a repair, first step was to restore a stock ROM from the SD card, i was previously running hspl 2.08 with one of dutty's recent ROM's.
To my surprise the stock rom has fixed the screen so this was obviously some serious rom or spl error (I tried a hard reset yesterday before coming to the conclusion it was hardware related)
I thought I would post my findings in case it helps anyone else, and would be interested to know if anyone has come across this before, do you guys think this must have been an spl issue if a hard reset didn't fix???
lancemate.
thank you
this just happened to me its after 7pm pacific time htc is closed and im going to try it now
it did not work my touchscreen has still failed and if its because i should remove the spl then i havent done it yet and how do i do it if the touschreen is gone
ok i did remove the spl and put back the stock telstra rom still touch screen failure, so tired of working with winmo crashing hardware and software, i went to android twice and came back to winmo because its what i know, i just keep getting let down, before this the latest let down was winmosquare, i dont know how much longer i can hold out for windows phone 7, i just may go evo 4g
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
Guys,
Few days ago i installed TOMTOM Navigator on my HTC HD2, after few days the phone freezes on regular basis and rebooting by itself, also the booting is locked on the HTC White screen and won't boot until i remove battery for few minutes and have it back installed.
I did a hard reset and still facing the same problem .
Any ideas guys what it seems the problem ?
Thanks in advance.
First of all, This is HD2 section. Therefore any threads opened within it or its sub-forums are obviously going to be related to the HTC HD2. Thus I see no reason for you to title your thread as "HTC HD2", You should have the wise mind to realize that yourself.
Back on topic,
Since you installed TOM, maybe you installed it on the sd-card. Try to remove the sd-card and boot
Or since you reached the "Hard-reset" step, try to upgrade your ROM
recently my trophy is behaving strangely. the hardware buttons stop to respond after several hours after reboot. The automatic screen lock then doesn't work anymore but all apps are. I have hard reset the phone but it keeps behaving like this. The only way to recover is to take the battery out and replace, then the phone starts and the time is totally incorrect, it appears to be back to the prevïous "crash".
can anyone help? thanks for reading!
Have you tired a factory reset? (If this is GSM Trophy, it should be okay to do. CDMA Verizon Trophy... flash back to stock first).
yes
Hi
yes i tried a factory reset but didnt help. I found out that if I keep the wifi off the phone is fine but after wifi is switched on the phone freezes after heavy use or few hours.
If anyone has any ideas...
Has your phone been updated via Zune to the newest software? I'm guessing this is a hardware issue though.
well.... yesterday i read about a way to force the tango updte through zune. I tried it and it worked. Zune updated my phone in 2 steps. I immediately turned wifi on and it has been stable (touch wood so far.... Looks like some bit went missing
Yeah, I can't really offer any advice other then to try restoring the backup Zune made before you made the update. If it was working fine before forcing the update, I'd say stick with that for now.
Am I understanding correctly that your phone was fine before the update?
If you can't restore your Zune update, you may need to flash a new stock rom to fix the problem (good-by data).
What carrier are you using for your Spark? Football's rom thread in the dev forum may have a rom you can use.
Hello everybody,
I'm relatively new to the world of ROMs and I'm hoping some people smarter than me can help.
A few weeks ago, I started having issues with my phone, on the stock ROM for Wind Canada, restarting continuously. It would sometimes work for up to 10 hours, but sometimes no longer than 10 seconds. There didn't seem any rhyme or reason to it doing so. I figured that it was a good time to play around with a new ROM, and I took a backup (of a faulty operating system). It's been a bit of a ****show since then, and I don't remember exactly everything that I've tried, but here is a sampling:
CM13.1 - the ROM successfully loads, but then I get stuck in a reboot loop.
CM12.1 - I figured that if 13.1 didn't work, I shouldn't try 14.1, so I went down to 12.1. This worked beautifully, until I tried to make a call - and I can't hang up. To hang up, I need to reboot the phone. Annoying, to say the least. Everything else seems to work really well, other than a slightly shortened battery life, but I can live with that, if everything else works.
CM14.1 - I tried loading it, but it says right off the bat that the L03 isn't part of the compatible list and doesn't process. I know I can suppress that message, but I figured that if it was meant to be on that list, it would be.
Resurrection 5.1 - I don't remember what happened here, but I think it ended up in a bootloop.
I can't find the original ROM on Huawei's site, and the one that seem similar for different countries are meant to be done within the OS as an update (Update.app).
So, I'm stuck here - I can't seem to revert back to the original ROM (which was Android 4.4.4, which was fine), and I can't seem to update to any other ROMs. I want to fix this, because as far as I'm concerned, the hardware is pretty good and I can make this phone last. However, my wife is pushing me to replace it...
Does anybody have any advice as to what I should try next? I really don't feel like using CM12.1 in its current state, which is what is installed now, since I need to reboot between phone calls, but it seems to be my only option for now.
Three notes - 1) I am currently on my 5th or so install of CM12.1. I have tried to look for ways to replace the dialer, since that seems to be the problem, but I haven't found a way. Can one replace the stock dialer?
2) I have tried installing multiple GAPPs packages, including ones that supposedly replace the dialer, but this hasn't helped.
3) I don't know if this is relevant, but in CM12.1, under "About phone", my Device model is "unknown". Is that always the case?
Somebody out there must have a better solution and my hair's all gone now, from me pulling it out...
Any help you can give me is appreciated!!!
Thanks,
Steve
UuUuPpPp....
Exactly in the same boat as Steve...... "Cant hang up" is seems to be the only major problem.....i have the exact phone too.....and tried same things too to no help....any help wud be appreciated...