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.
Related
I RUU'd to Jan2012 OTA update, unlocked with HTCDev.com, installed AmonRa, rooted using AmonRa and everything has been fine....for about four days. Then yesterday, after using IM+ Free for a few days and liking it, I decided to buy the Pro version. Coincidentally, my extended battery was running out and I didn't have time to charge it at work, so I powered down, removed the battery, put my charged stock battery in and voila...boot loop. No signal at unlock screen, sits for 10 seconds, and reboots. I can do a factory wipe and it will boot, but if I restore anything...data only, system only, secure only...all 3, 2 of 3...doesn't matter...issue returns. Anyone know why this might be happening?
It's because you can't post in the right section!
Have you tried wiping and flashing a Rom? Not restoring
Edit: its probably because of a bad backup or because of the ota, its been known to bootloop
Sent from my ADR6425LVW using Tapatalk
Can a Mod please move this to general?
OT: Check the bootloop thread that will more than likely give you the answer you're looking for.
http://forum.xda-developers.com/showthread.php?t=1394659
My apologies for posting in the wrong section.
My concern is that it was running fine, and then suddenly wasn't when nothing but an app install (IM+) was done. I don't want to go through setting everything up again only to lost it all again four days from now.
I am having similar issues as you are. Tried to charge a 3.8v stock battery overnight and it bootlooped all night long. It seemed like it settled down after putting back in my 3.7v extended. So I called HTC and created a rma for the battery, no big deal.
Then today listening to music while the phone is in the dock i had a few reboots/bootloops, noticed some odd stuff in logcat so I did a reset permissions in recovery. Seems better so far compared to before where it would only take a few minutes to bootloop.
*mine is not the network issue, but good to hear you fixed yours
joblabbo said:
I am having similar issues as you are.
Click to expand...
Click to collapse
Yes, sounds similar...however, I ran my stock battery for about two weeks with no issues, and ran the extended battery for a good month with no issues, and even ran fine for a few weeks after htcdev.com unlock, AmonRA flash and rooting took place. This all came about out of the blue.
Right now, I am attempting to use the guide specified concerning connecting to the wrong type of network. I'll update when finished.
------
UPDATE: That worked. It was a communication issue, the phone had changed it's connection preferences. The sad part is that I've been without a phone for almost a day over this, and flashed all kinds of kernels and recoveries, and even considered going back to Verizon for a replacement. The even sadder part is that I already knew of this fix and completely forgot about it. Thanks a MILLION to MrSmith317, not only for directing me to the fix, but also for not bashing me for accidentally posting in the wrong area of the forum.
Hey whats up everyone. Ok long story short, I got the evo3d the first day it came out. Also rooted it with the first solution and never installed a custom rom for a while. Now a while back I started experiencing problems like when i touch a number key it either presses another, or sometimes enters it twice. It basically is making the phone impossible to use. I then figured maybe it had something to do with the original rom and the phone being rooted. So I then installed ViperRom as so many people have good things to say about it. The rom worked good for about a week or so and then the problem came back with the buttons just having a mind of its own. Now sometimes it will work with no issues for hours on end, and sometimes it just goes beserk from the get go. If anyone has experienced this and can please suggest something as Im ready to just call it in lost and have them send me a new one but if I can fix it I would much prefer that as I plan on just having it flashed to boost anyways since I've never used the 4g since the day ive gotten the phone.
Thanks in advance
Frankie
I had this problem with another phone and I reinstalled my keyboard, because that's what was causing it.
Sent from my VS910 4G using xda premium
encryptusa said:
Hey whats up everyone. Ok long story short, I got the evo3d the first day it came out. Also rooted it with the first solution and never installed a custom rom for a while. Now a while back I started experiencing problems like when i touch a number key it either presses another, or sometimes enters it twice. It basically is making the phone impossible to use. I then figured maybe it had something to do with the original rom and the phone being rooted. So I then installed ViperRom as so many people have good things to say about it. The rom worked good for about a week or so and then the problem came back with the buttons just having a mind of its own. Now sometimes it will work with no issues for hours on end, and sometimes it just goes beserk from the get go. If anyone has experienced this and can please suggest something as Im ready to just call it in lost and have them send me a new one but if I can fix it I would much prefer that as I plan on just having it flashed to boost anyways since I've never used the 4g since the day ive gotten the phone.
Thanks in advance
Frankie
Click to expand...
Click to collapse
It sounds like you've got issues with your digitizer. The only sure fix is to get a replacement.
response
Do you think maybe just trying to flash it back to stock would resolve the issue or possibly trying another rom? It happens so sporadic and only started after I rooted the phone. Also, to the poster above how do you reinstall your keyboard?
Frankie
encryptusa said:
Do you think maybe just trying to flash it back to stock would resolve the issue or possibly trying another rom? It happens so sporadic and only started after I rooted the phone. Also, to the poster above how do you reinstall your keyboard?
Frankie
Click to expand...
Click to collapse
You can try to return to stock/unrooted and see if you can repeat the issue. And I didn't mean reinstall the keyboard, the digitizer is part of the touch screen assembly, so if you can repeat the problem for a sprint rep, they may give you a new/replacement phone.
Flashing back to stock, flipping kernels etc... Didn't fix mine. I had to get 2 of these 3d's until the 3rd finally worked. It's the digitizer.
Sent from my EVO 3D using XDA
Ok, so here's the scoop.
Earlier today for no reason that I can pinpoint I lost all Cellular connectivity on my photon while at work. No calling, no 3G, etc. I figured it was just a hiccup or possibly that they where working on the towers in my area and that it would eventually just come back up.
That was over 12 hours ago, and I have already traveled from work, to home and still no change.
I began to think that maybe my PRL was out of date, so I flashed back to a blur based Rom that has worked for me in the past (I normally use CWM7.2 and moved to Imperium_Initiative_v1.0.5 to try and do this) and tried to initiate the update there.
Still, no results. Not only would the PRL & profile not update but I got a general "NETWORK_ERROR" every time I attempted to do so.
I'm getting a little desperate because I really need to have my phone active for work and other reasons.
I've already restored old NAND backups, restarted the phone numerous times, and so far nothing is working...
If it is indeed a PRL issue, is there a way to manually flash an updated version onto the phone?
Any help that anyone can offer is greatly appreciated!
-Timboman
P.S. The only major change that has been made to the phone recently was I purchased a new extended battery about a month back. It's been working great since I broke it in, and have no so much as flashed a new rom image since I got it. It's the Trexcell Motorola Photon 3570mah Extended Battery.
Well I decided to bite the bullet and do a full re-lock and stock re-flash and I now have gotten my signal back.
Still have no idea why it happened to begin with, but I have apparently solved my issue.
If anyone can give me a reason this might have happened then at least this topic can be of future use to someone else.
-Timboman
Timboman said:
Well I decided to bite the bullet and do a full re-lock and stock re-flash and I now have gotten my signal back.
Still have no idea why it happened to begin with, but I have apparently solved my issue.
If anyone can give me a reason this might have happened then at least this topic can be of future use to someone else.
-Timboman
Click to expand...
Click to collapse
This happened to me once while on cm7, again, for no apparent reason. After being baffled for an hour i got pissed and went to bed thinking my radio died. Signal was back by morning. Id be willing to bet yours would have come back too. Pawn it off as a hiccup and keep flashin stuffs.
Sent from my MB855 using XDA
Hi, I recieved a refurbished replacement rezound from asurion when i dropped mine in water a couple of weeks ago. When i got the phone it immediately had the problem of rebooting all the time. I didnt think anything of it assuming that it was just a problem with ics so i rooted the phone and installed a different rom, i still had the rebooting problem so i flashed another rom and i Still had the problem. The phone seemingly reboots at random dozens of times a day. It has even locked up and rebooted in the recovery and even the bootloader. I cant return it because i dropped it and there is damage so i would have to pay 100$ again. any help?
If you tried complete wipe (system, data, cache, Dalvic) and clean flash without restoring anything and it's still rebooting, I would say the next step should be an RUU. (HERE is the latest).
Max725 said:
If you tried complete wipe (system, data, cache, Dalvic) and clean flash without restoring anything and it's still rebooting, I would say the next step should be an RUU. (HERE is the latest).
Click to expand...
Click to collapse
Yup, i always wipe it clean. Ill try an ruu, but that has nothing to do with it rebooting even in the revovery and bootloader does it?
I know very little of how this low-level hardware control stuff works, but it could technically be possible to make a faulty hboot that will reboot sometimes but normally work. An RUU will replace your hboot with stock, so if it's anything hboot related, the RUU should fix it. If it's not hboot related, I'm afraid it could only be faulty hardware. You could try replacing the battery, but I don't see how a battery could cause reboots. Also, if it is faulty hardware that shuts the phone down completely, flashing an RUU could be risky - if it shuts down while the hboot or radios are being flashed, you could be left with a hard brick, which would be even worse than constant rebooting.
As I said, though, I don't know much about phone hardware or low-level software, so it could be some other problem that I'm entirely unaware of.
I have the battery from my old phone that i could try. and could it have anything to do with the sim card? im using the sim card that came with my old phone that i dropped in water and i didnt use the new one they sent me because i didnt really want to go through the trouble of activating it.
I know nothing of how SIM cards work, but you could try taking out the card, and seeing if the phone will still reboot.
If it doesn't reboot right away, just activate the new one and see how it will work then - it's just a 5 minute (or even shorter) phone call.
Max725 said:
I know nothing of how SIM cards work, but you could try taking out the card, and seeing if the phone will still reboot.
If it doesn't reboot right away, just activate the new one and see how it will work then - it's just a 5 minute (or even shorter) phone call.
Click to expand...
Click to collapse
yeah but i have to call asurion and they arent open, plus im not the account holder or whatever its called.
gabezermeno said:
Hi, I recieved a refurbished replacement rezound from asurion when i dropped mine in water a couple of weeks ago. When i got the phone it immediately had the problem of rebooting all the time. I didnt think anything of it assuming that it was just a problem with ics so i rooted the phone and installed a different rom, i still had the rebooting problem so i flashed another rom and i Still had the problem. The phone seemingly reboots at random dozens of times a day. It has even locked up and rebooted in the recovery and even the bootloader. I cant return it because i dropped it and there is damage so i would have to pay 100$ again. any help?
Click to expand...
Click to collapse
And you might want to get a velcro glove and case set.
What is your hboot version, what recovery are you running, and what rom did you install?
Have you tried connecting your phone to the computer in fastboot mode and removing the battery while it's powered by USB and see if you get the random rebooting in hboot when the battery is out?
Try removing the sim and booting as was mentioned earlier as well.
So update, I installed set cpu and set it at performance and the max at 1300mhz and it hasnt rebooted since, which is saying something since it would reboot about every minute before. I fixed it! but its still not as nice as my girlfriends DNA haha oh well. thank you all for your help
gabezermeno said:
So update, I installed set cpu and set it at performance and the max at 1300mhz and it hasnt rebooted since, which is saying something since it would reboot about every minute before. I fixed it! but its still not as nice as my girlfriends DNA haha oh well. thank you all for your help
Click to expand...
Click to collapse
Did you do this on a stock kernel?
Get another replacement. Mine had an issue where wifi would not turn on. Even after I s off and tried installing roms and kernels it wouldn't boot. My replacement works perfect.
I couldn't have gotten a free one because I dropped it and there are scratches on it now.
Sent from my Rezound using xda app-developers app
I installed multiple ROMs and always had the same issue, im using cm9 rage right now
Sent from my Rezound using xda app-developers app
By switching it to performance mode you locked the CPU at its Max value which will annihilate your battery if you leave it like that. What that means is that the voltage of your CPU was too low at the bottom end and it was making the phone reboot. If your min before was 192, bump it to 384. If it was 384, bump it to 432.
Sent from my ADR6425LVW using xda app-developers app
I had asurion replace my incredible when I broke it once. Shortly after the CPU would over heat all the time and reboot. They covered it under warranty even though it was used. They might cover it under warranty if it hasn't been too long.
Sent from my ADR6425LVW using xda app-developers app
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.