I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
The last link you put up is a theme, not a Rom. Which ROM are you currently using?
Be sure when changing roms to wipe data and cache. Not doing so will cause a boot loop, which you described above. Also, if you have to reactivate your phone and can't get a dial pad, long press the menu button to bring up the keyboard and use the keyboard numbers.
Sent from my ultra fast Liberated Droid 2
boxfuk said:
I recently went ahead and unrooted my eris so I could call and get a new one sent to me since I'm still under warrantee, and on the other phone I never seemed to have a problem with rooting it and installing the roms. But now for some infuriating reason, every rom I've tried has given me issues within the starting point of loading them. http://forum.xda-developers.com/showthread.php?t=677097 <- That one loaded perfectly fine, but then my internet would just refuse to work.
I also tried one called Pure Eris I think it was called, but that one would just stay stuck on the loading screen, go black, then go back to the loading screen, not sure how I had the patience to sit through that for an hour assuming it was perhaps just going to take a while. I used this thread as a help to see if I was perhaps doing something wrong http://forum.xda-developers.com/showthread.php?t=835758 I did everything it said to do, and then went ahead and found another rom I thought I'd enjoy, but then all of a sudden I'm required to re-activate my phone. When I call to activate, the keypad refuses to show, and I need to press 1 to activate. Hah. It's just been a hair-ripping experience today.
Now I'm attempting to install http://forum.xda-developers.com/showthread.php?t=769624 and HOPING I won't have yet again anymore issues.
Anyone have an idea of what I may be doing wrong even after following those instructions? I'm still new to this so to say, since I've only rooted the eris once before this, and I didn't have a problem until now. Rooted it just the same, and each theme seems to make a new problem arise. Haaaaaalp?
Click to expand...
Click to collapse
I don't know what all roms you have tried that won't boot but there was one person who's phones could not boot my cfsv6 through cfsv8 kernels. I fixed the issue in cfsv9 kernel so check to see if the roms you have tried are using those kernels. I know the one you said booted was an older rom and was not using my kernel. CELBFroyo is using the v9 kernel if you want to test that. If that is your issue you can just download the cfsv9 kernel and flash it after flashing the rom of your choice. It was something to do with the hardware in a small percentage of eris's that the kernel would not work with. Maybe you have the same hardware as that case...
Related
Hello folks of XDA,
I came here because I have not heard any response on the MIUI forums and UI guess is because the community over there is not as big.
Anywayas, I flashed 1.8.5 MIUI, and I suddenly could not see the screen after I dialed a phone number. Then I also noticed that I could not see the answer screen when someone called me.
Everything else worked like a charm, so I thought to myself, well, maybe I have not been back on JFD for a while, so I went ahead and restored the phone back to stock, follow even the MIUI procedure for the massive JFD restore, and it does not matter.... Any Rom from stock to MIUI or CM7.1 all give me the same problem or an app force close, of phone freeze. I can hear the person on the other side if I call, but there is no human way I can answer the phone.
I believe the phone.apk might be the problem, but after trying to do all kinds of factory reset and format, I am still in the same place.
So my first question is, is there a way to fully format the phone and put it with stock apps. Like out of the box? using CWM gives you the option to format the mount points, but I am afraid to format everything and then have a true bricked phone.
Any comments suggestions, questions, please let me know. I been working on this for 2 days now with no avail.
Bump. I have no phone, so it is very frustrating
So I called tech support and see if they had any idea of what could it be. in the end I am back on stock, so what more harm can I do to it right? Well the tech said something that really leave me thinking. He said that the proximity sensor could be damaged. Now that makes a lot of sense, in the end the phone is already somewhat old and I have had my mishaps dropping it from time to time, but luckly no scuffs on it. What do you guys think?
This though is gonna mean that I have to go get me a new phone today ....
I have searched and searched, but can not find what seems to be an applicable fix, so here goes.
Ok here is my best description. Equipment: Rooted vibrant. The plot: Rooted. Ran fine for months. Yesterday purchased Rom Manager premium. Installed one of the premium roms. Can't remember the name of the rom. After install everything worked fine except I kept getting the error, "com.google.process.gapps has stopped unexpectedly" so I tried everything I could find related to that problem to fix it, but nothing worked. As a symptom the market, gmail, etc wouldn't work. Anyway I figured I'd just recover the last rom that I backed up and start over. So I did, but now the phone boots, goes to the "draw pattern to unlock screen" and won't recognize the fact that I'm actually drawing the pattern to unlock the screen. The "buttons" on the bottom of the screen recognize my touch (menu, home, search, back) as they darken when touching them.
So there the phone sits on the unlock screen. After a minute or two the screen goes blank, the phone vibrates once, and the unlock screen comes back and won't accept any input.
Is this fix applicable, or would it work in bringing my phone back to me?
http://forum.xda-developers.com/showthread.php?t=848737
I want to make sure as I don't want to further exacerbate the uselessness of my phone. I feel like I've lost a limb with it gone.
Thanks for any help.
Sorry to hear you found the worst gremlin of all. I'll get that from time to time when my phone feels like being stupid. Lucky for me, I can just reboot the phone, and she's back to normal.
As far your situation is concerned, I would probably try to use Odin and flash your phone back to stock so you can build it back up to whatever ROM you're on. This usually happens when you bounce back and forth between a froyo and GB ROM; or a ROM from a different dev that's used a different framework to make all his stuff work.
Jump into the link in my sig, and see if you can find the files you need. Otherwise, shoot me a message so I can link you to the files I use to go back to stock pre-rooted.
Lol, did you try this?
http://forum.xda-developers.com/showthread.php?t=749605
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
younix258 said:
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
OK. The sticky worked. I admit I panicked, but IT WORKS NOW!! I'm just ecstatic! You guys rule.
I guess I was just gun shy. I bricked the snot out of my my-touch a year ago (still doesn't work).
Anyway, on to hacking.
Thanks again!
Awesome! Glad you got it werkin
Next time just try a simple Google search of the error itself.
*EDIT*
If you still have the mytouch I'd be interested in it. PM me if so
Yeah I tried to google the problem, but I was still stuck. None of the fixes seemed to work. Until google led me here.
I do still have the my touch. Mint condition, minus the fact it doesn't work! I'd like to get it working again if possible. Is there a way to odin the my touch? I tried and tried last year when I bricked it, but I never got it to work again. Is there a my touch forum here somewhere named something other than "my touch"?
Sent from my SGH-T959 using XDA App
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
kdub2000 said:
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
Click to expand...
Click to collapse
My guess is that something is screwing up kernal wise or your flashing. If your phone was fine stock then something got dicked during the flash.
Is there anything I can do to a clean wipe and start fresh again? Or should I try to figure out why the Superwipe isnt working? Or do I have to flash all the stock back on and turn the s-on and get a new phone? I think the digitizer is causing these issues.
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
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.