So, the phone was working perfectly. I was on ARHD 6.1.1 with the default kernel. All of sudden the screen has stopped working. The touchscreen works well, as in i can still unlock the phone by swiping across the screen and everything seems to working but the display is just black.
So, it started working again randomly, but another hour or so and it is gone again. Both these times this issue happened when Nes.Emu(nes emulator app) was running on the phone. Could it have to do something with that? If it comes back on again i think i am gonna uninstall nes.emu.
Anyone?? I am truly lost. And the fact that i have installed a custom rom means the warranty is void.
Anyone?????
Cmon someone?? I really am desperate for some sort of advice.
If i were to take it to HTC would they refuse to fix it(for free) cause of the ROM i installed. If i manage to flash a stock rom, go to stock recovery and relock the bootloader will HTC still charge me or would they cover it in their warranty then?
Related
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
I'm running CM 6.1.1 Stable on my G2 (just a couple weeks old) and I've noticed that my home button doesn't work sometimes. It works about 95% of the time, but then it will do the occasional hiccup where nothing happens. If I touch it a few more times it will eventually start working again. Not sure what it is, but I read in another thread here that it could have something to do with how the CM ROM is configured for capacitive touchscreen sensitivity. And I believe I read that this has only been reported in CM and not other ROMs.
dutman said:
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Does it completely not working??, delayed maybe??
Sent from my HTC Vision using XDA App
Had this issue yesterday. I did a factory wipe from Clockwork and reflashed CM. Fixed it.
even iam facing the problem, but i guess mine is worst as the all(4) softkeys doesn't respond, but when i press it, i receive the feedback i.e it vibrates.
2nd issue: my physical keyboard layout is pretty much messed up, the symbol key which i press on my keyboard doesn't display the exact symbol
it would be kind if someone offer some solution for this
Rom: CM 6.1.1 (even tried nightly build #85)
Build: HK
P.S: i never had those problems in the stock rom
I'm having the same problem with CM6.1.1. I noticed it after installing Twidroyd app. I couldn't exit it via the home button...had to back all the way out. Uninstalled and still having the problem. Doesn't seem to be working at all now.
I had this sort of problem with my G1, I flashed the BiffMod ROM and some day, the phone just randomly did a factory reset, the background is set to how it was when I first flashed it and the home screen was back to normal like how it was when I first flashed it. My home button would not work, when I pushed the end call button to put the phone in sleep mode, it would turn off but if I were to press it again,the screen would turn on but it didn't go to the lock screen it just turned on. To fix it I went into recovery and wiped all five(I'm using Amon_Ra's recovery on it) then I booted back up and my home button worked again and when I put the phone to sleep, it turned back on like normal with the lock screen. That has happened a few times, some times when I did the wipe, every thing would start working again and my home screen still had everything placed where it is suppose to be. You could try to wipe everything, but I can't guaranty it because I don't even have my G2 yet so this has never happened to me on a G2.
i wiped everything data / cache ,flashed GingerVillain 1.4 , the softkeys won't work even in this rom, the only place where softkeys work is HTC's Stock rom. iam just wondering is it due to my build, as its Hong Kong build, so there is a possibility that the keymap for softkeys are different?
Update: Fixed! http://forum.xda-developers.com/showpost.php?p=9353194&postcount=1
Hey guys.
Maybe somebody could help me with my problem. I debraned my DHD from T-mobile some month ago... rooted it, installed Bootloader, Rom Manger and Clockwork recovery...
all works fine... then i installed Leedroid 2.3.2.. all worked fine, system was stable.
Then some weeks ago, i noticed, that my touchscreen doenst work anymore... I turned the phone off, took the accu out w8 some mins, rebooted over CW.. then it wokred again...
today i got a phonecall, wanted to take it... again... no reaction from the touchscreen or the keys down.... i tried all today, wiped all data, did a recovery, installed new ROM's.. nothing worked.. the volume buttons and the power button did work... i dunno what to do anymore?
Maybe anbdy got some ideas?
Greetz
I would suspect LeeDroid, has issues. Have been hearing a variety of issues....
When you said installed new ROM's, does that mean different ROMs, versions of Leedroid, or what?
first of all i reinstalled, the current leedroid... doesnt work
then i wiped all data and installed MIUI... system, all is working fine (it seems so)
but the touchscreen still doenst work...
i read something about to install a RUU rom.. but that wasnt based 100% on my problem
nobody got any idea ? :-(
If its not a software problem.. than you can try some hardware stuff....
take any hair dryer and .. blow some hot air on the screen boundries... and just press it ....not too hard, just a bit softly.. as if you are trying to stick screen back. This might help you... Please try this at your own risk
Just a note: This is the Desire forum, not the Desire HD
Hello!
For some time now my phone's been rebooting itself completely random it seems. I just got it back after sending it away to get this issue fixed. Obviously the "repair" didn't really do anything at all. All they did was to flash the latest software apparently.
I got quite fed up with the crashing and rebooting stuff, and figured that it wouldn't hurt to try to flash a custom ROM, in this case I chose to root the phone and try MiUi. I had no clue wether it would solve the issue I'm having, but I figured it was worth a try. So i rooted the phone and flashed the latest version of MiUi (1.11.18).
At the start it seemed like it had worked, and had stopped the phone from crashing. But after some time I realized that the issue is still there, only difference now is that it ONLY crashes when I lock the screen with the Power-button. EVERY SINGLE TIME I do this, in a matter of minutes it will either reboot or just turn black and totally unresponsive. Only way to get it on again is to take out the battery and put it back in.
This is starting to annoy the **** out of me, so I talked to my brother for advise this morning, and he told me to wipe my Dalvik Cache. So I did, and nothing changed, the phone keeps on living it's own life.
I have absolutely no clue what info you guys might need to help me with this, but I'll start with this:
Phone: HTC Desire HD
Android-version: 2.3.7
Kernel-version: 2.6.35.14-cyanogenmod-g319b6e2
ROM: MiUi 1.11.18
Also, the motherboard's been switched once, cause of another issue that is now gone.
ANY help is appreciated, I just want to be able to use the phone normally!
EDIT: Also it seems that the phone won't reboot or crash whenever it's charging.
Sounds like a hardware/software issue your best bet is getting a replacement and re rooting .
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though
Hi, I recently flashed a jellybean in Rom on my HTC one x and the rotation stopped working. So then I decided to return to factory settings with an ruu. So I did that and it was functioning again. So I reinstalled jb still worked.I then decided to try the 4.2 camera on my one x and it stoped working again, I then tried the ruu but this time it did not work. Next day I go home from class decide to unlock and relock the bootloader and it worked again, I then tried to install a in Rom ( once again) but this time it did not work. So I tried the ruu again, didn't work, tried unlock and relock bootloader, factory reset, wipe cache, everything and yes screen rotation is on. I alsotried the app android sensor and it showed my accelerometer/gyro not working. Can someone explain how to fix because its hard for me to believe that its hardware since it happens after I install a Rom or flash something. Please help.
dyslecix said:
Hi, I recently flashed a jellybean in Rom on my HTC one x and the rotation stopped working. So then I decided to return to factory settings with an ruu. So I did that and it was functioning again. So I reinstalled jb still worked.I then decided to try the 4.2 camera on my one x and it stoped working again, I then tried the ruu but this time it did not work. Next day I go home from class decide to unlock and relock the bootloader and it worked again, I then tried to install a in Rom ( once again) but this time it did not work. So I tried the ruu again, didn't work, tried unlock and relock bootloader, factory reset, wipe cache, everything and yes screen rotation is on. I alsotried the app android sensor and it showed my accelerometer/gyro not working. Can someone explain how to fix because its hard for me to believe that its hardware since it happens after I install a Rom or flash something. Please help.
Click to expand...
Click to collapse
take a look right here, contact shinigamikris he solved this problem
dyslecix said:
Hi, I recently flashed a jellybean in Rom on my HTC one x and the rotation stopped working. So then I decided to return to factory settings with an ruu. So I did that and it was functioning again. So I reinstalled jb still worked.I then decided to try the 4.2 camera on my one x and it stoped working again, I then tried the ruu but this time it did not work. Next day I go home from class decide to unlock and relock the bootloader and it worked again, I then tried to install a in Rom ( once again) but this time it did not work. So I tried the ruu again, didn't work, tried unlock and relock bootloader, factory reset, wipe cache, everything and yes screen rotation is on. I alsotried the app android sensor and it showed my accelerometer/gyro not working. Can someone explain how to fix because its hard for me to believe that its hardware since it happens after I install a Rom or flash something. Please help.
Click to expand...
Click to collapse
That can happen from time to time with gyros. Even if you get it to work with the right RUU, then you reset the device, it might stop functioning again. I'd say your motherboard needs to be replaced. You can always try with different ROMs and stuff but my thought: your HW is problematic
miHah said:
That can happen from time to time with gyros. Even if you get it to work with the right RUU, then you reset the device, it might stop functioning again. I'd say your motherboard needs to be replaced. You can always try with different ROMs and stuff but my thought: your HW is problematic
Click to expand...
Click to collapse
don't think so, every person who encountered errors like this were on cm10 and its kernel ncx, theres should be something wrong with those things... or people don't flash it correctly
I have this problem as well, but I'm using ARHD rom, right now.
Although I also think it's more a hardware fault, I'm not really 100% sure about it.
Sometimes a new Rom flash or a reset can fix it.
But after a few reboot it gets stuck again :-/
So confused about this problem too
Although, my phone is unlocked now and got Hboot 1.33. I'm gonna wait till the official RUU is out and reset my phone fully (with locked bootloaders) before sending it to HTC for repair.
Maybe you should do that too
I had this problem too. It was fixed for a while after I flashed stock rug but then I clashed another recovery and wham they got knocked out again. Then I installed viper, cm 9 still not working. Installed latest paranoid android 2.53 and they are working again oh and I have latest twrp recovery installed. I really can't say if it is hardware or software. Maybe a mixture of both. I dunno. Only just flashes pa this morning but I have rebooted and they still work. Usually it will get knocked out if I reboot so I'll see what they are doing after a week or so. I'll probably keep pa on here until my official j b OTa is released. I think it did have something to do with either that ncx kernel or a recovery I tried. As that what knocked them out each time. Good luck in fixing it as different people gave had different things that fix the problem. For me it was reverting back to stock ruu. It was 4.03. 1.29..... something. But it also was fixed when I flashed latest paranoid android. Just a fee things to try....
Sent from my HTC One X using xda premium
Edit - sorry for the spelling mistakes....
one x gyro sensor probs
I also hv same probs. in one x.
sometimes reboot can fix d probs. of gyro sensor. n when u restart d device it stop again n smtime u restat device its working again. i dnt knw its a hardware probs. or software probs. ??? Plzz help me guys.
also give me a rpl in my mail id. [email protected]