Hi everyone, I am new here but not new to rooting phones. I've followed the instructions for installing |ROM| Jedi Mind Trick |V9| 9|19 completely and thoroughly and I've waited the 10 mins (sometimes more) before I rebooted the phone. Every time after the reboot, I start messing with the phone and checking out the features, my capacitive buttons just completely stop working, they are unresponsive and they don't even light up. Also, the lockscreen doesn't work unless I press the power button once and then I can go into the phone and everything else is working except for the capacitive buttons. So that leaves me stuck in the last app that I was in and I cannot go back home since the capacitive buttons are functioning.
I have tried reflashing the ROM 3 times and the same exact thing happened each time. I also tried rebooting the phone and turning the phone completely off and the capacitive buttons will function only for about a minute and then completely stop working again. I was wondering if someone knows how to fix this or if anyone was experiencing the same issue and found a way to fix it. Please let me know, I'm not sure what I did wrong for this happen since the ROM seems to be working for everyone else.
I found I had far less problems and quirks after installing teamwin touch recovery. Then flash.
Sent from my aokp_tenderloin using xda app-developers app
ctrlaltdeln said:
I found I had far less problems and quirks after installing teamwin touch recovery. Then flash.
Sent from my aokp_tenderloin using xda app-developers app
Click to expand...
Click to collapse
Ok, thank you, I will try using TWRP and see if it fixes the issue. Will reply back soon!
myst3ry23 said:
Ok, thank you, I will try using TWRP and see if it fixes the issue. Will reply back soon!
Click to expand...
Click to collapse
i had exactly the same problem. I second the advise above. In the nutshell, it seems, that the flashing sequence didn't clean something.
Related
NOOB HERE
Hi, I am using eugene373's newest PLANE JANE ICS ROM, the whole system seems to me is perfect, except the one issue about the touch keys backlight. Sometimes those four keys do not light up even I already unlock the screen, may have to wait for 15-30 seconds, then the backlight comes up. But sometime it works good. So I am just wondering is there any other this ROM users have same problem about this?
Its a little bug, everyone's got it. It'll probably be fixed soon.
Sent from my SGH-T989 using xda app-developers app
whatiznt said:
Its a little bug, everyone's got it. It'll probably be fixed soon.
Click to expand...
Click to collapse
Thanks for telling me that. I already had flashed the rom more than five times!! I thought that only because I installed something affect the lights.
PlainJane
Installed Rom.Everything seemed to work fine.But i could not get Talkatone working that what i use mostly.
Anyone else having this issue?
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
felcom said:
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
BWolf56 said:
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
Click to expand...
Click to collapse
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
felcom said:
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
Click to expand...
Click to collapse
Sounds indeed like software issue. I'm not so sure what would cause it on stock rogers though.
Either way, you can find the stock ROM on sammobile.com or on this thread: http://forum.xda-developers.com/showthread.php?t=1822308
You'll need Odin to flash it. (It doesn't trigger the flash counter)
felcom said:
Phone is out of warranty so no go there....
Click to expand...
Click to collapse
Did you buy your phone with a credit card? Some cc's have warranty built in. Mine doubles what the manufacturer offers.
Thanks for the link. I will try it tonight and post the results. Really hoping it works.
Sent from my SGH-I747M using xda app-developers app
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
felcom said:
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
BWolf56 said:
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
Click to expand...
Click to collapse
Thanks. I might try it. Dont think I have too much to lose at this point. I always try and keep my phones nice so that when I get a new one I can sell the old one for good money to help offset the cost. This really messes with that system as the phone isn't worth much now...just bought an extended battery too...was planning to keep it for at least another 6 months.
Sent from my SGH-I747M using xda app-developers app
So just a quick update. For no apparent reason the phone started working fine again. It now turns on and off just fine. I'm not going to mess around with it anymore. That's really bizzare. I'll give it a couple days and will report back if it continuous to work fine or if the problem comes back. Thanks for the input.
Sent from my SGH-I747M using xda app-developers app
Hi guys, i've got a strange issue. My HOX is working, but the screen is off. Sometimes it turns on but with strange complicated issues like in the photo. The strangest thing is screenshot could't catch that view. i can receive income calls, all notifications, device is working. Only the screen is giving problem. I use my phone for one year and 3 months. It all started to happen a week ago. I was using Blade Elite rom, then i changed to Nik Project Rebirth rom, in aroma I ticked odex option, and after that... Now I don't know if it is a hardware or software issue. Can anybody please help me?
eyfa said:
Hi guys, i've got a strange issue. My HOX is working, but the screen is off. Sometimes it turns on but with strange complicated issues like in the photo. The strangest thing is screenshot could't catch that view. i can receive income calls, all notifications, device is working. Only the screen is giving problem. I use my phone for one year and 3 months. It all started to happen a week ago. I was using Blade Elite rom, then i changed to Nik Project Rebirth rom, in aroma I ticked odex option, and after that... Now I don't know if it is a hardware or software issue. Can anybody please help me?
Click to expand...
Click to collapse
Unfortunately that looks like the graphics chip has failed, I read about this happening to some devices. I think this might be a hardware issue but maybe someone else can confirm?
pakjebakmeel said:
Unfortunately that looks like the graphics chip has failed, I read about this happening to some devices. I think this might be a hardware issue but maybe someone else can confirm?
Click to expand...
Click to collapse
Does it take some time for screen to turn on as wel?. Mine had these symptoms and Mainboard had to be replaced.
http://forum.xda-developers.com/showthread.php?t=1859339
jomy117 said:
Does it take some time for screen to turn on as wel?. Mine had these symptoms and Mainboard had to be replaced.
http://forum.xda-developers.com/showthread.php?t=1859339
Click to expand...
Click to collapse
Thanks a lot mate.
If you chose odex option, did you wait until the device rebooted? On first boot, it does not boot up and rather odexes..maybe you interrupted that process...so just do a clean reflash of the rom, wiping system,data and cache... Make sure you wait for as long as needed before the system finally boots up...remember, first boot odex, then it will automatically restart and then next boot , you can finally access your phone (as in a complete boot)
Sent from my HTC One X using xda app-developers app
Sadman Khan said:
If you chose odex option, did you wait until the device rebooted? On first boot, it does not boot up and rather odexes..maybe you interrupted that process...so just do a clean reflash of the rom, wiping system,data and cache... Make sure you wait for as long as needed before the system finally boots up...remember, first boot odex, then it will automatically restart and then next boot , you can finally access your phone (as in a complete boot)
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thank you for your reply, but i found that this is not a software issue. The same problem in this video is happening with my device now and i think it depends on overheating of device. http://www.youtube.com/watch?v=VFvABvJXDc8
Closed on OP request
So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app
Ameer Shimoga said:
So I am having this problem since 4.4.3 and 4.4.4 update. Once or twice a day the screen won't respond to touch. Should I use a custom kernal or this might be a hardware problems.
Sent from my Xperia U using XDA Free mobile app
Click to expand...
Click to collapse
How do you fix it when it happens? Do you have to restart? Does the touch fail or does the tablet freeze?
Honestly not very sure what you could do, besides maybe trying a factory reset? That would work if a software problem.
What about cleaning it and removing any screen plastic guard.
U can say it freezes then I have to restart it. This is happening after two factory resets.
Sent from my Xperia U using XDA Free mobile app
Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835
mdamaged said:
Firmware fix: http://forum.xda-developers.com/showthread.php?t=2428133, read and follow the op very carefully.
...if it does not help, or you think it may be internal:
http://forum.xda-developers.com/showthread.php?t=2535835
Click to expand...
Click to collapse
OK I'll try..
Sent from my Xperia U using XDA Free mobile app
Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.
nebhead said:
Same issue here, I think.
Just purchased a refurbished Nexus 7 (official factory refurbished) from Amazon. My touch screen works great for a day or so, but eventually touch stops working altogether and sometimes requires a hard-reboot (holding the power for 10-seconds). Downloaded a touch screen test app which works great (even with ten fingers on the screen), tracking well on all parts of the screen. It's just like the touch atrophies over time until it stops working.
First thing I did to the tablet after getting it was to unlock the bootloader and load stock/rooted 4.4.4. Is there some way to update the touchscreen firmware that I'm missing?
I don't want to open this thing up and muck with the hardware for fear of damaging it. I'm holding out hope that there is a software fix, because rebooting fixes it right up.
Click to expand...
Click to collapse
Look 2 posts up from yours.
mdamaged said:
Look 2 posts up from yours.
Click to expand...
Click to collapse
Oops - I looked at the link to the hardware fix, but not the firmware fix. Thanks, I'll give this a try first.
Firmware fix above seems to have alleviated the issue for me. At least I haven't seen the issue over the last several days, which is good news. Hopefully that holds up over the long term. :good: