Related
I'm having a problem with my touchscreen that started happening yesterday after I flashed a new ROM. I flashed Android Revolution HD 1.1.1, and on the lockscreen after the first boot is when it first started acting up. This youtube video shows exactly what my phone is doing: http://www.youtube.com/watch?v=iIrmLOTiUZk
I've nand back to other roms that I've used in the past, and still the same issue. Superwiped and flashed different roms, and it would solve the problem for several hours, but the issue comes back. When the problem happens, a restart will solve the issue for maybe 15 minutes. It seems as if it's a hardware issue, but I don't get why rebooting/wiping and reflashing would solve the issue for a period of time. If anyone has any advice or the same issue with a fix, it would be much appreciated. Thanks in advance.
*Idk if it matters, but I'm hboot 1.4, zagg invisishield screen protector on.
Also, the touchscreen issue only happens at the bottom center of the screen - where the lock ring is located.
Update: I nand backed to stock rom, no issues for about 24 hours, started happening again. Any thoughts anyone??
Might be a hardware issue. If it keeps occurring I'd suggest taking it in to be looked at. Or you could try reflashing your recovery and doing a full data wipe and flash a stock rooted rom and see if that helps. Hope it does. Good luck.
Locked & Loaded
""shooter on Deck""
Thanks, I'll try reflashing my recovery tonight. It seems to be hardware related, but the temporary fix (data wipe and flash Rom) is what confuses me. I just hope I don't have to send it in and get a refurb with hboot 1.5.
Also, when I do super wipe, should it automatically boot into recovery? It just hangs on the white HTC screen, and I have to.pull the battery to get into recovery. And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Well if your doing a super wipe and it still keeps some of your old settings of a prior rom then I'd suggest trying a different wipe method or redownloading the the super wipe zip, you might have gotton a bad download. As far as if it's supposed to boot right into recovery that I don't know because I don't use any wipe method but the recovery. It hs always worked for me. Try reflashing your recovery and wiping with just the recovery options. Wipe data "complete factory" ,cache and davlik-cache. Then try flashing a stock rooted rom. Or if that doesn't work try the official ruu.
Locked & Loaded
""shooter on Deck""
b1gsby_02 said:
And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Click to expand...
Click to collapse
Well it keeps your wallpaper because Google syncs it with your Google account. That's normal. But as for everything else, it sounds like a hardware issue.
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Sent from my PG86100 using Tapatalk
I flashed twrp 1.1.1 over 1.0.3 and did a data wipe, cache and dalvik. Flashed a rom and so far so good. I'll see if I can go more than 24 hrs without an issue. If it's a hardware issue, I don't understand why flashing a new rom temporarily fixes the issue, and since the issue started right after I flashed a new rom. I'll continue to update on here and hopefully the reflashing of recovery helps - thanks laie.
Didn't know wallpaper was synced with google account - thanks gumby
Gumby63 said:
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Click to expand...
Click to collapse
Did you do anything else to try fix the problem?
b1gsby_02 said:
Did you do anything else to try fix the problem?
Click to expand...
Click to collapse
I'm not sure what else to do. I suppose I'm stuck with contacting HTC about a repair. I've done a little bit of research and some people having similar problems have said that it could be a problem with the digitizer. But most explanations were very vague so I'm still not sure what I'm going to do.
Sent from my PG86100 using Tapatalk
Well you should be good to go. Post back in 24hrs with what's going on. Glad your running ok for now.
Locked & Loaded
""shooter on Deck""
Phone was fine all last night and this morning. Early afternoon it started acting up a little bit. Nothing like it used to, but I notice when I set it down or shake the phone a little, it will trigger the issue. So it's more than likely hardware related. Does anyone know Sprint's policy on fixing a phone that is rooted? I am jw if I should revert back to s-on before I go to a Sprint store to have them look at it. I don't know if they check that or not. Usually the first thing they always do is make sure everything is up to date too. Any insight is appreciated, thanks.
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Rob the plumber said:
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Click to expand...
Click to collapse
Please update us after you talk to Sprint. I am curious to what they say about you being rooted and what the problem may be. My phone has been running fine for awhile now. After I reflashed recovery, data wipe, flashed rom, it acted up for a short while about 12 hours later. It's been almost 24 hours since it last acted up and has been fine so far.
Rob, just wondering if you talked to Sprint yet?
Also, does anyone know if I should go back to 100% stock and S-on before bringing my phone into Sprint? They always seem to update everything, and if there is an update, they usually tell you that's the reason why your phone isn't working the way it should.
UPDATE:
I went back to 100% stock and S-ON following this guide: http://forum.xda-developers.com/showthread.php?t=1194053 Then I went into my Sprint store, told them about the issue, and the first thing they did was asked if I had reset the phone and they checked to see if there's any updates available. The phone started to act up again while they were looking it, luckily, because they have to replicate the issue before they can fix the problem. They said it was probably the screen and they were going to replace it. They had me come back an hour and half later, told me they tried replacing the screen and that wasn't it. They didn't know what was wrong, but concluded it was a bad phone. They replaced my phone with one that someone returned within their 30 days. It's not a refurb, but not a brand new one either. I had to pay $35 for the service charge for fixing my phone. I hope this helps anyone who's having the same issue.
Of course my replacement phone has hboot 1.5.
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Rob the plumber said:
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Click to expand...
Click to collapse
I have tried a few different batteries, and it didn't seem to matter. Maybe your situation is different. Hopefully that fixes your issue!
My issues have returned. Off to the sprint store!
Rob the plumber said:
My issues have returned. Off to the sprint store!
Click to expand...
Click to collapse
Good luck! Did you revert back to stock and s-on? Or are you going to tell them you're rooted?
I think I'm going to just put a stock ROM on it and ask them first before I hand over the phone.
I'm very hesitant about posting new threads but I've been trying to fix this issue for a few weeks now and I can't seem to figure it out. I've searched the S-OFF forums, formatted, reinstalled, rebooted, reflashed, and have exacerbated all my limited knowledge and now I come to you for help.
The moment I finished the S-OFF process, the problem started. I can send and receive text messages (sometimes it resets itself), and when I open the phone program and press a number or anything on the numberpad, the phone freezes and resets. I've verified that the phone is set to CDMA/LTE and so I know that isn't the problem.
I can choose a contact and press call, and sometimes it resets, but other times it completes the call. At one time, I used the phone trouble free for a few hours and then it started resetting all on its own.
I can also browse the internet (connected to 3G, 4G, or WiFi), and sometimes the phone will reset itself.
What I've done to try and fix it so far:
I initially had a problem with internal and external storage, so I did the fixes listed in the S-OFF post, and they worked like a champ.
I also installed the following roms and had the same issue:
Ineffabilis-Deus_v1.0.1-Odex
RezROM_S4_v2.5
CleanROM Pro 4.5
NeWts-OnE-XxX-RC2-Signed
vigorOTAStockRooted
Currently have the following rom installed (seems to reset less often than the others):
Business_ICS4.0.3_Sense3.6-v5.3
I tried this, but I can't type anything into the numberpad without the phone resetting, with or without the back cover on.
I've installed the Stock Radio from 3.14.605.5 and 3.14.605.10 leak (5/7 & 6/10)
This is what my bootloader currently has
= JuopunutBear =
VIGOR PVT SHIP S-OFF RL
HBOOT-2.21.2121
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
The recovery I have installed is:
AmonRa 3.15 (GB/ICS)
Any ideas?
Update:
I attempted to sync Google goodness, and now it bootloops...
Try flashing this:
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/[ICS][2.25][JB][5-7]PH98IMG.zip
This in the newest ICS Firmware, courtesy SuperChilPil
Sent from my evolving Rezound.
Worked
I'm not sure what Voodoo this is, but I think it worked. I'll know for sure in a few days...
It is frustrating that I couldn't find it on my own... How did you know about it and how did you know that it might work? I'd like to know for the future so I can troubleshoot better on my own.
An RUU completely restores and/or upgrades every single part of the software and firmware. So therefore ANY possible software problem would gave to be fixed by an RUU. If an RUU doesn't fix he problem, its a hardware issue.
Calibob2001 said:
I'm not sure what Voodoo this is, but I think it worked. I'll know for sure in a few days...
It is frustrating that I couldn't find it on my own... How did you know about it and how did you know that it might work? I'd like to know for the future so I can troubleshoot better on my own.
Click to expand...
Click to collapse
I've had to RUU mine due to tinkering so many times I've developed a digital nose for when it'll work lol.
Generally speaking, I've noticed two common issues with the Rezound:
The firmware not having been flashed completely (thus reboots and other weirdness) and the kernel/boot.img not having flashed (resulting in the phone getting stuck at the splash screen).
Also, I fancy myself to be some sort of dark Technomancer...so it's my job to know!
Glad it worked though!
Sent from my evolving Rezound.
Thanks
Well thanks for your insight. I've installed at least one other RUU, but it didn't fix it. Good catch and I think your Technomancerness is right on the money.
Props :good:
Ok I have been having an issue where my phone randomly reboots or completely powers off. This started after I started using newtsone ics ROM. It was suggested I try other ics roms which I did and then it was suggested I switch back to a gb ROM which I did. However it is still doing it. I thought maybe the battery was lose and it was losing power so I tried to wedge a small piece of paper in there to make a tight fit but that didn't work. It doesn't do this if connected to a power source and I don't have a battery to test my battery theory. Has anyone else had this issue or have any ideas on how to fix it? My newest issue now also is that texts don't come through. They only come through when I make a call then six or seven of them will finally come through. Any thoughts? I'm hboot 1.40 s-off and running the latest radio.
Are you overclocked?
Sent from this 3D thing
Try this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
#Root-Hack_Mod*Always\
Ye I gR this.before too. r u using boost or virgin mobile. also reflash your radio. I was having reboot issues with the baseband 1216 but it was because I didn't use freezas all in one. my pro wasent right now I have 1.43_003 where I had 1.24_003
No I'm not overclocked and not on boost or virgin. I don't know if mentioned it before in my first post, but it only does this when the phone is sitting idle and the screen is off. If I unlock the phone and the screen is on, actively using it, or it's on the charger then it's fine. I'm going to try reflashing the radio or going back to my old one and see if I have any luck with that. Anything else you can think of in the mean time let me know.
As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Something is wrong with the software hes using if working on regular sense build and not cm,best aaking in the rom developers thread.
paradoxed said:
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Click to expand...
Click to collapse
Yes but after 4.1.2 RUU it still cuts data on and off. Is it possible it's a bad radio or should we try a differentRUU?U
first id say get to an area where the radio reception is better, get an att card and not straight talk and test.this could very well be a hardware issue as well, but it seems more of a simcard issue/software issue than a hardware issue