Part of my touch screen does not work so when I go to install a custom rom with twrp I cannot factory reset delvik cache and all the other stuff. What can I do? I would use clock work mod but the roms I want to install need twrp. For example the ViperXL Rom says to install with twrp? Is there anyway to get viper installed on my phone? Is there something else I can use to clear the cache?
You should be able to use CWM to flash Viper, I think it's just a recommendation to use TWRP. I'd say give it a try.
Sent from my HTC One XL using XDA Premium 4 mobile app
jluca98 said:
Part of my touch screen does not work so when I go to install a custom rom with twrp I cannot factory reset delvik cache and all the other stuff. What can I do? I would use clock work mod but the roms I want to install need twrp. For example the ViperXL Rom says to install with twrp? Is there anyway to get viper installed on my phone? Is there something else I can use to clear the cache?
Click to expand...
Click to collapse
What version of TWRP are you using? Some of the older versions of TWRP won't work with the updated touch screen firmware, which you would have if you ran the 3.18 RUU or took the OTA JB update.
timmaaa said:
You should be able to use CWM to flash Viper, I think it's just a recommendation to use TWRP. I'd say give it a try.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unless it's been changed, Viper won't install on anything other than TWRP. I tried to install it using Philz AdvancedCWM and it stops the install and prompts you to install TWRP instead.
Oh, I stand corrected then. Thanks for clarifying that.
It sounds like a hardware fault to me though, only part of the screen isn't working.
Sent from my HTC One XL using XDA Premium 4 mobile app
pside15 said:
What version of TWRP are you using? Some of the older versions of TWRP won't work with the updated touch screen firmware, which you would have if you ran the 3.18 RUU or took the OTA JB update.
Click to expand...
Click to collapse
This is mostly likely the issue. It's a rather old version of TWRP that has this touch screen issue, so update to the latest (2.6) posted in Development.
I do have twrp 2.6 installed. The thing is that the touch screen under my status bar does not work in most apps but in some of them it does. This problem is occurring in twrp but when I play games that part of the touch works so I do not understand what is going on.
Sent from my One X using XDA Premium 4 mobile app
This is pretty confusing, since you haven't given a lot of vital info, and didn't completely describe (as far as I can tell) the issue in your original post. First it sounded like touchscreen wasn't working in recovery only, now it sounds like its not working when the OS is booted also.
What ROM are you running?
What hboot?
Ok, so like I said, it's a hardware issue, it has nothing to do with touchscreen drivers. I think at the moment you only have two options:
1) Have your touchscreen repaired.
2) Use CWM (non touch) and flash something other than Viper. There are plenty of great ROMs available, now the official Sense 5 update has been released you'll see even more pop up. There's already a stock Sense 5 ROM by Turge, and MagioRom will have our own modded version released in the next day or so.
Sent from my HTC One XL using XDA Premium 4 mobile app
timmaaa said:
Ok, so like I said, it's a hardware issue, it has nothing to do with touchscreen drivers. I think at the moment you only have two options:
1) Have your touchscreen repaired.
2) Use CWM (non touch) and flash something other than Viper. There are plenty of great ROMs available, now the official Sense 5 update has been released you'll see even more pop up. There's already a stock Sense 5 ROM by Turge, and MagioRom will have our own modded version released in the next day or so.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
'
Problem Solved. The Viper aroma installer actually has a feature that automatically clears the delvik cache. I flashed the ROM and all is working. Thanks for the help guys.
Also, to clarify my problem, my touchscreen has a spot on it that does not work in some apps and works in some apps. For example, I cannot click the install button in the Google Play Store (I rotate the screen to install apps.) but I can click in that same area in the lockscreen and get a touch reaction. This seems to me like a hardware issue because the affected area does not work in TWRP either, but then why does it work in some apps and in some locations of the ui?
jluca98 said:
'
Problem Solved. The Viper aroma installer actually has a feature that automatically clears the delvik cache. I flashed the ROM and all is working. Thanks for the help guys.
Also, to clarify my problem, my touchscreen has a spot on it that does not work in some apps and works in some apps. For example, I cannot click the install button in the Google Play Store (I rotate the screen to install apps.) but I can click in that same area in the lockscreen and get a touch reaction. This seems to me like a hardware issue because the affected area does not work in TWRP either, but then why does it work in some apps and in some locations of the ui?
Click to expand...
Click to collapse
because of the response area specified within the app. Chances are the ones that are working just have a larger area of response and therefore it recognizes within those confines. there are apps that test the touch screen try one to find out where you lose responsiveness
You are correct. I used the touch screen test app and that strip is completely unresponsive.
Sent from my One X using XDA Premium 4 mobile app
jluca98 said:
You are correct. I used the touch screen test app and that strip is completely unresponsive.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi I have the same issue with you, a segment of my touch screen is not responding but it's pixel is alright.. No dead pixels, only segment of screen not responding. The affected segment is in line with the send key in text message so I have to rotate everytime i need to send a text message in order to change the location of send key. What did you do in order to solve this problem? Did you bring it to HTC Service Center? Thanks!
mabrinez said:
Hi I have the same issue with you, a segment of my touch screen is not responding but it's pixel is alright.. No dead pixels, only segment of screen not responding. The affected segment is in line with the send key in text message so I have to rotate everytime i need to send a text message in order to change the location of send key. What did you do in order to solve this problem? Did you bring it to HTC Service Center? Thanks!
Click to expand...
Click to collapse
If what you're experiencing is a hardware issue, which it probably is, you need to replace the digitizer. Whether you attempt it yourself or get an experienced repairer to do it is up to you.
Sent from my Evita
Got the same issue as posted above but my touchscreen works perfectly in landscape mode (touchscreen test apps don't work here either but other apps do) while that silly strip still doesn't work in both recovery and booted OS, whichever recovery/OS installed, in portrait. Tried to find different touchscreen drivers but that thread seems to be deleted. I'll try an older firmware (2.14 seems to be the last one to have tp drivers inside).
=edit=
Firmware flash didn't help.
=edit2=
Ordered new digitizer, I'll see when it arrives.
also ordered screen
PlayPetepp said:
Got the same issue as posted above but my touchscreen works perfectly in landscape mode (touchscreen test apps don't work here either but other apps do) while that silly strip still doesn't work in both recovery and booted OS, whichever recovery/OS installed, in portrait. Tried to find different touchscreen drivers but that thread seems to be deleted. I'll try an older firmware (2.14 seems to be the last one to have tp drivers inside).
=edit=
Firmware flash didn't help.
=edit2=
Ordered new digitizer, I'll see when it arrives.
Click to expand...
Click to collapse
new screen did not help for me. how did the new screen work for you?
Moto Mouth said:
new screen did not help for me. how did the new screen work for you?
Click to expand...
Click to collapse
Did you change just the screen, or the screen + digitizer?
Sent from my Evita
changed the lcd and the digitizer but in two parts so not to run into broken digitizer issues in the future and need an assembly.
Moto Mouth said:
changed the lcd and the digitizer but in two parts so not to run into broken digitizer issues in the future and need an assembly.
Click to expand...
Click to collapse
Mine didn't arrive yet. Will probably tomorrow or early next week. Also ordered an lcd screen + digitizer combo just to be sure. Funny how stuff is cheap on ebay.
Moto Mouth said:
changed the lcd and the digitizer but in two parts so not to run into broken digitizer issues in the future and need an assembly.
Click to expand...
Click to collapse
Ok, was thinking you had only changed the screen.
Sent from my Evita
I can not format your partitions in, because I do not work in the sensor recovery menu, I tried to reinstall all else fails Please provide help
Related
Hi, i've bought an unlocked T-Mobile HTC Sensation and was running Android Revolution HD for Sensation gingerbread. my Camera app has suddenly stopped working... I've tried updating to latest ICS from Android Revolution HD 6.5.1 but still the camera is not working. when i start the app... the screen flashes and then again I'm back on the home screen. Strangely, when using application "mirror" it starts the front camera... and that is working fine... and i've tried multiple apps from market for back camera...but its not working using any of them... can you please help me out with this... any help in this would be deeply appreciated.
Thanks
Dipil Jain
Got exactly the same thing happening with me guys...any ideas?
Have updated to the latest firmware etc and wiped everything several times and tried installing it with different options but still cannot get the camera to work
Deadringers said:
Got exactly the same thing happening with me guys...any ideas?
Have updated to the latest firmware etc and wiped everything several times and tried installing it with different options but still cannot get the camera to work
Click to expand...
Click to collapse
this is weird did you tried other camera apps?
if its still not working then
do a superwipe and flash rom again and see(this method erases data ..so backp them before hand)
Similar problem, if i click the camera or camcorder icon the screen goes black, it either stays black until i take the battery out or it crashes and restarts?! Weird, cant use it to take pics in any other apps either. front camera is fine on skype though...!? everything is uptodate nothing was updated recently?! Anyone
(Im on stock)
This happened to me once when i was stock. I would do a battery pull and it would work again..but finally did a hard restore through recovery and cleared all the caches and that worked. Now im rooted and on energy GB rom and I have not had that problem anymore.
Just flashing a new rom did not help. I actually had to do a factory reset on the ROM as well..in the Setting/storage.
Never ran into this problem
Sent from my HTC Sensation using Tapatalk 2
Have u tried maybe a different rom??
sent from thy phone
I would suggest clearing the app data.
Have you news. I have the same problem and have yet to find any solution. If you have one I'd be grateful for it.
LuckyD
Go to Task Manager>>Advanced>>All apps>>Find the Camera app and select it>>Force Close if it is running & then Clear Data.
This should fix it.
If not, get this app. Go to primary and secondary camera, & check if they both work.
If it works, then there's a problem with the stock app.
If not, there is either a problem with the camera or with camera access.
I would suggest reflashing your current ROM, since this seems to solve issues, many a time.
Try installing another pyramid
have you tried to download a special or customized pyramid from the sensation android development department and then tried out your 4g??? a customized pyramid + tweaks will allow the htc camera to work because the htc family usually creates htc's like as if they were real babies.. the htc's adapt to you and then little by little all the problems like "over-heating reset, camera faults and random keyboard touches" are common problems with the htc... installing a different pyramid or returning it for another new one will usually fix this..
kgs1992 said:
Go to Task Manager>>Advanced>>All apps>>Find the Camera app and select it>>Force Close if it is running & then Clear Data.
This should fix it.
If not, get this app. Go to primary and secondary camera, & check if they both work.
If it works, then there's a problem with the stock app.
If not, there is either a problem with the camera or with camera access.
I would suggest reflashing your current ROM, since this seems to solve issues, many a time.
Click to expand...
Click to collapse
Thanks for this mate...As I said I have re-flashed the rom several times but get the same issue!
the main Camera has a red cross through it on that app..I guess it is broken?
Any help would be much appreciated!
Deadringers said:
Thanks for this mate...As I said I have re-flashed the rom several times but get the same issue!
the main Camera has a red cross through it on that app..I guess it is broken?
Any help would be much appreciated!
Click to expand...
Click to collapse
hi there
go here
and download the one that suits ur sense 3.6 or 4 and flash it over clock work recovery it will reflash ur camera apk with moded working fine apk i hope this will fix it peace
musa91 said:
hi there
go here
and download the one that suits ur sense 3.6 or 4 and flash it over clock work recovery it will reflash ur camera apk with moded working fine apk i hope this will fix it peace
Click to expand...
Click to collapse
okay done that....took about 2 seconds to flash and when rebooted it said "android is upgrading"...
Is the camera working!?
NOooo!
I guess I will have to take it back to vodaphone shop now?
Thanks for your help mate
Deadringers said:
Thanks for this mate...As I said I have re-flashed the rom several times but get the same issue!
the main Camera has a red cross through it on that app..I guess it is broken?
Any help would be much appreciated!
Click to expand...
Click to collapse
As far as I can tell, your camera is not being detected.
I would recommend that you do this:
1>NANDROID backup
2>SuperWipe (it can be found in this post at the very end)
3>Re-install ROM (Remember to check MD5 before installing)
4>Check if the Camera works.
If not, then Super Wipe and restore your previous backup.
If it works, get back to me. (PM me if I don't reply)
If you have further questions, feel free to ask.
Deadringers said:
okay done that....took about 2 seconds to flash and when rebooted it said "android is upgrading"...
Is the camera working!?
NOooo!
I guess I will have to take it back to vodaphone shop now?
Thanks for your help mate
Click to expand...
Click to collapse
U welcome any time
Last try the kernel is the 1 who responsible for device driver defention try to flash
Stock or moded defrrent kernel from development section there's allot of
Good kernels there it may fix ur device peace
Hey guys, there's something wrong with my phone and I'm stumped on what the problem is. I am currently running Team Venom ViperXL 3.2.6 with the Bulletproof kernel, wifi partition, and newest ATT radio. After roughly three days of using the rom, my homescreen just completely crashed and I could not load my applications through the app drawer or recent menus page. I basically couldn't use my phone to access anything, but I could still receive and pick up calls. I reset the phone the same issue would occur where I unlock the phone and all I get is a white screen with the status menu on top.
I did a factory reset on the phone and it works fine now, but this isn't the first time I have experienced this issue. In one of the previous roms I was using, my phone completely froze on me on two separate occasions. My phone would hang on the boot animation for hours at a time each time I reset the phone. I had to reflash the rom in order to get around this.
I don't know what's causing these deathfreezes and I doubt its the problem with bad flashing or individual rom concerns. Any opinions and advice is greatly appreciated. Maybe I didnt unroot my phone properly? Is there a difference between S-On and S-Off?
Heres my phone info:
tampered/unlocked
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Apr 2 2012, 21:08:24
I flash all my roms via TWRP
Well for you, s off would not matter. Don't get me wrong, its simple, but one flaw could f you up. As for the home screen, could be the launcher. Haven't worked with viper, so I don't know if holo or another launcher is used. I use nova and haven't had any issues. For the hanging on the boot screen, could be a bad download. Do you use goo or ROM manager? I tend to stay away from those and get the complete download using a PC and match it up with md5.
Other than that. I couldn't tell you what is wrong.
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
Well for you, s off would not matter. Don't get me wrong, its simple, but one flaw could f you up. As for the home screen, could be the launcher. Haven't worked with viper, so I don't know if holo or another launcher is used. I use nova and haven't had any issues. For the hanging on the boot screen, could be a bad download. Do you use goo or ROM manager? I tend to stay away from those and get the complete download using a PC and match it up with md5.
Other than that. I couldn't tell you what is wrong.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
I used apex and this was the first time it happened. I dont think it was a launcher issue because I did a force close on it in settings and I still got blank screens. Didnt revert to default launcher or restart apex.
As for the boot screen, it only happens after I have been using the rom for some time. I download the roms from my mac and flash it via twrp. At first I thought it was an inherent issue with scratch build jb roms so I grabbed viper only to get the same problem much quicker.
joshuaadude said:
I used apex and this was the first time it happened. I dont think it was a launcher issue because I did a force close on it in settings and I still got blank screens. Didnt revert to default launcher or restart apex.
As for the boot screen, it only happens after I have been using the rom for some time. I download the roms from my mac and flash it via twrp. At first I thought it was an inherent issue with scratch build jb roms so I grabbed viper only to get the same problem much quicker.
Click to expand...
Click to collapse
Hmm haven't got the slightest clue. My suggestion would be to do a for factory reset again clear evert cache and reflash. If that doesn't work, then could be hardware issue
Sent from my Carbon-ize Evita using xda-developers app
Wich version of twrp are you using?
Sent from my HTC One X using xda premium
Venomtester said:
Wich version of twrp are you using?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Keep forgetting 2.3.x.x is the best to use...
Sent from my Carbon-ize Evita using xda-developers app
I am using version 2.3.1.0.
I tried to find a answer but have been unsuccessful.
Since upgrading to JB whenever I reboot, my keyboard reverts to the stock keyboard and I have to go into settings to turn back on SwiftKey and then re select it.
Also on reboot, switch pro widget will not be loaded nor will audio manager profile switcher.
Any advice?
Sent from my HTC One X using Tapatalk 2
DucRider749S said:
I tried to find a answer but have been unsuccessful.
Since upgrading to JB whenever I reboot, my keyboard reverts to the stock keyboard and I have to go into settings to turn back on SwiftKey and then re select it.
Also on reboot, switch pro widget will not be loaded nor will audio manager profile switcher.
Any advice?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I recall having the same issue with JB at one point but I think after I RUU'd it stopped. I could be wrong, ofcourse. I know there's a bug with some settings switching back after reboot and I remember thinking this was part of that bug. But I was on Viper for a couple days a few days ago and don't remember it happening during that time.
I have the same issue. SwiftKey almost always is disabled on reboot and frequently overnight. Not sure if this is a glitch or some new memory management thing with the AT&T JB based ROM. Doesn't happen with my N7.
Running CR6.X - also happened with a ported ROM I flashed over the holidays.
Pretty annoying. Not really into RUUing at this time, since that has always been painful for me on other HTC phones. I have attempted clean flashes in an attempt to fix, with no luck.
Sent from my HTC One X using Tapatalk 2
So a ruu might fox the problem?
Sent from my HTC One X using Tapatalk 2
DucRider749S said:
So a ruu might fox the problem?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Might, RUU up to 3.18/3.17, make sure your S-OFF and don't relock your bootloader. Report your findings.
exad said:
Might, RUU up to 3.18/3.17, make sure your S-OFF and don't relock your bootloader. Report your findings.
Click to expand...
Click to collapse
Shoot, now I just need to figure out how to do that
DucRider749S said:
Shoot, now I just need to figure out how to do that
Click to expand...
Click to collapse
There's a thread about S-OFF in the original android development section.
Ruu, is simple, download the exe and run it with your phone plugged in. Don't relock the bootloader.
An update,
I didnt RUU but I found out that if I power off and then powerback on it keeps the keyboard and widgets
I also had At&t send me a new device, but it had the same problem
the rep called HTC and they have never heard of this problem, but have no fixes, so that sucks
the end response was just dont restart the phone, power it off then back on
Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk
It IS about time.
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.
robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.
orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)
G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app
bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)
UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective
UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)
Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.
UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.
UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).
hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?