Hi Guys,
I need help. I really appreciate if someone could help me.
Current Evo 4G LTE
Running Rom : Meanbean 2.71
baseband 1.12.11.0809
build 3.15.651.16.cl124461
kernel 3.4.10
HBoot 1.19
Radio 1.12
S ON,Unlocked
TWRP 2.3.1
My touchscreen won't work. Sometimes it's respond, but most of the time it's not respond. I have tried to upgrade TWRP 2.6x to see if i have update the touchpanel driver (but i think i have not update anything, just incase) still doesn't work. I have downgrade the touchpanel in Capt Throwback post, still not working. Is my panel or digitizer borked?
I thought in first place it was software issue, i have uninstall most added app, but not helping (doing it while the touchpanel work, tiba backup, nandroid backup also). but now I can't even flash anything since the touchpanel in TWRP also not responding. Does it related to power? since my batt drain so fast at this time.
Is there a way to flash ROM from fastboot/adb? just to make sure i have clean install, and see if the touchpanel related to software or hardware problem.
Please help. :crying:
You're software is really out of date. Having said that, it would appear that you are still on the older TP driver. If your screen works intermittently, your issue is most likely hardware-related.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You're software is really out of date. Having said that, it would appear that you are still on the older TP driver. If your screen works intermittently, your issue is most likely hardware-related.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I see. It's kindda sad since i love this phone that is why i haven't change to another. Yes it's outdated, since i haven't got time to play with it.
Is it possibly the digitizer?
Yea I am experiencing a similar thing over here mine however, will work fine then the screen recognizes random "ghost" touches and I have to lock then unlock the phone to make it quit. I'm hoping it's just the digitizer.
Sent from my EVO using xda app-developers app
Related
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
I rooted my phone about two months ago and didnt have any problems at all. Used HTC's website and loaded cleanrom reborn 1.1 and the kernel that came with it is 2.6.35.13-g277012f
Recently, about a week or two ago, I noticed the camera starting to fail. It occasionally wouldnt load in 2D mode, just give me a black screen. Now, it rarely loads at all. Either the whole screen is black or it brings up the camera app (stock, instagram, fb, all the same) but the part of the screen that would show the picture is black. When I turn it to 3D mode the screen freezes, then flickers, and quickly closes to the home screen and still flickers for about 3 seconds then is fine.
My questions are this, could this be caused due to needing an update, a new ROM or new hardware? Also what do you all recommend as far as the best ROM for taking pictures?
And on an unrelated note, does anyone know a good ROM that supports 4G hotspot instead of it just automatically switching to 3G??
Thanks
As for the camera failing sorry to here that but you can down load the amaze camera from the dev section and they have all different version of it and its for both CDMA and gsm
Sent from my HTC EVO 3D X515m using xda premium
That sounds like a software issue.. Might be the rom or the kernel.
Are you on ics?
Sent from my EVO 3D S using xda premium
My camera just started acting up also, I went ahead and wiped everything and installed bone stock rom (rooted only) and camera is still messed up.
When I use the main camera it works fine, when I switch to front facing camera - it stays on the main camera and just inverts the image
Is this a hardware or software issue? I am guessing it is the hardware
Let me know what you guys think.
Heaterz16 said:
My camera just started acting up also, I went ahead and wiped everything and installed bone stock rom (rooted only) and camera is still messed up.
When I use the main camera it works fine, when I switch to front facing camera - it stays on the main camera and just inverts the image
Is this a hardware or software issue? I am guessing it is the hardware
Let me know what you guys think.
Click to expand...
Click to collapse
Nobody has seen this issue???
Try running an ruu.
#Root-Hack_Mod*Always\
laie1472 said:
Try running an ruu.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
If am S-off would I have to re-root if I tried that?
Yup. Running an ruu removes root. Just don't run the hboot1.5 ruu if your on hboot1.4. It will save you a headache.
#Root-Hack_Mod*Always\
I would reflash the rom before ruuing
Sent from my PG86100 using Tapatalk 2
Nah. Just run the ruu. Make sure your battery is over 85% imo things go a lot smoother.
#Root-Hack_Mod*Always\
I really do appreciate the replies, but not sure I am willing to run the RUU and re-root since it is a pretty high likelihood that it is a hardware failure since I went back to completely 100% stock (only rooted) ROM. Torn on getting a replacement and having to deal with the Hboot 1.5 mess just so I can use the face unlock feature in ICS or stick with what I have an no FFC.
Every once in a while, my screen will go white when I try to connect to the internet or the play store. Back button won't work, only the home button will. Then I have to restart my phone to access the internet. This has been happening since the update. Anyone else?
Sent from my EVO using Tapatalk 2
Yes I see this also. I wounder if it is Sprint network?
I've seen this also, it seems to do this in any browser that i've thrown at it. I don't think it is the network as a web page that isn't loading due to traffic shouldn't lag the phone. When mine does it i can't even turn the screen off until its done being stuck. I was trying meanrom so i updated to the newest firmware and baseband, but i reverted back to an old nandroid of charmelon rom which is 1.13.
The nandroid didn't seem to restore the baseband nor do i think it was designed to, but long story short i'm still on the newer baseband and being that the common point between you and I is probably that, i'm going to guess there is some kind of issue in the radio thats locking up the phone.
I'm going to flash back down to the original radio and see if it changes things.
I'm on stock.
Sent from my EVO using Tapatalk 2
you're on the update, so you're on the 1.22 firmware with 1.05 something radio. I was saying that it might have had something to do with the radio.
Im stock and i have been getting this white screen after the update.
I thought it was an app i had , but i see other people having this, so i dont know what could be.
Sent from my EVO using xda app-developers app
lacrossev said:
you're on the update, so you're on the 1.22 firmware with 1.05 something radio. I was saying that it might have had something to do with the radio.
Click to expand...
Click to collapse
Is there anything that can be done about it? I'm not tech savy, so I know I won't be rooting.
Sent from my EVO using Tapatalk 2
I've just flashed back down to the older radio so i'll have to try it a few days and see if thats even the issue.
I'm not sure if theres anything to be done on a stock unit, unless maybe you're able to run an RUU of the original rom and have it restored back to the day you recieved it.
First off,
Thanks for taking the time to view this post and offer any help.
Second, sorry if it's in the wrong place (Never really sure of the right place these days)
Finally, the problem:
This morning my phone had no signal at all for a good few hours till restart. I got signal back then shortly afterwards it drops again not to come back on till a restart. I have done a clean flash of the ROM and it is still persisting. Oh and I forgot to say that now my radio is asking for superuser access constantly which makes the phone unusable, this doesn't restore the signal though. I have also tried flashing Evervolv with the same result.
Any ideas?
EDIT: Now the phone won't get any signal at all, even after a reboot and full wipe, it's like the rom can't access the radio receiver (No idea if i decribed that right)
EDIT: I have a feeling this may relate to my problem. Could anyone confirm or correct me?
http://forum.xda-developers.com/show....php?t=1497246
Seems like that link you provided is down right now. Have you tried flashing the stock ICS ruu? Not sure whether your CDMA or gsm.
Just checked the link there and its working now. I'm not sure what I did but after reflashing disarmed toaster (for like the 10th time) it seems to have done the trick. No problems with signal anymore.
I would still like to know what caused it for future reference though. And I'm gsm
Sent from my Evo 3D GSM using xda app-developers app
Joe.Tolchard said:
Just checked the link there and its working now. I'm not sure what I did but after reflashing disarmed toaster (for like the 10th time) it seems to have done the trick. No problems with signal anymore.
I would still like to know what caused it for future reference though. And I'm gsm
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Maybe not, the problem is back again, going to get a stock rom and test that
Recently my touch screen has not been working so well. The bottom 1/4"-1/2" works sporadically and sometimes it goes crazy acting like I'm touching different parts on the screen rapidly when I'm not touching the screen at all. I don't know if this is a hardware or a software issue. Anyone have an idea?
Specs:
CM10
Baseband 1.12.1.1119
Kernel : 3.0.51-geb1844c
Did you update the touch screen? It is in Captain Throwback's thread with radios and stuff. I'm not sure if CM10 supports it, but you need to be on a rom that is based off the newest build. Otherwise the update will make your touch screen inoperable and have to go into bootloader/adb to flash a supported rom.
I have noticed that my capacitive buttons are less consistent on the Sense 5 rom. Maybe it is just me, I'm not sure.
Anthonicia said:
Did you update the touch screen? It is in Captain Throwback's thread with radios and stuff. I'm not sure if CM10 supports it, but you need to be on a rom that is based off the newest build. Otherwise the update will make your touch screen inoperable and have to go into bootloader/adb to flash a supported rom.
I have noticed that my capacitive buttons are less consistent on the Sense 5 rom. Maybe it is just me, I'm not sure.
Click to expand...
Click to collapse
I did the 3.15.651.16 update, but not the 3.16.651.3 because all my software was a little older.
Anthonicia said:
Did you update the touch screen? It is in Captain Throwback's thread with radios and stuff. I'm not sure if CM10 supports it, but you need to be on a rom that is based off the newest build. Otherwise the update will make your touch screen inoperable and have to go into bootloader/adb to flash a supported rom.
I have noticed that my capacitive buttons are less consistent on the Sense 5 rom. Maybe it is just me, I'm not sure.
Click to expand...
Click to collapse
I am having the EXACT same problems as described in OP. I have updated the touch screen via Captain Throwback's thread. I am currently running 3.16.651.3 with Mean Bean. I have tried Stock with Goodies also but the problem persists. Over the weekend I unrooted the phone just to see and I noticed that the touch screen was back to normal. I am running out of thoughts on this one. Sprint has offered to replace my phone but I hate to do that if there is nothing wrong with it until I root again.
The touch screen issue started before I did the firmware update. Everything I did was right when root, unlocked bootload and s-off became available a year ago. Then the issues started and I updated the firmware to 3.15, which didn't change anything.
phoenix0783 said:
The touch screen issue started before I did the firmware update. Everything I did was right when root, unlocked bootload and s-off became available a year ago. Then the issues started and I updated the firmware to 3.15, which didn't change anything.
Click to expand...
Click to collapse
My issues started recently, I have been upgraded for some time now. I am starting to wonder if it is a rogue app update or something else along those lines.
If you are having sporadic issues with the touchscreen not working, particularly if it doesn't work if you touch it in a certain spot, the issue isn't with your touch panel driver. The issue is most likely the touchscreen itself
Sent from my EVO using xda premium