I've been running Cyanogen tazz since v1 and have loved it. I was removing some things with Titanium Backup today, and now i cannot receive sms, but I can still send them. I've tried wiping and re-flashing the rom, flashing a different rom, and a nand restore, and I still have the problem. Any ideas?
I tried searching but couldn't find anything, so please dont kill me if this is something i should have found on my own...
have you figured it out mines doing the same thing?
Related
Hey.. I just flashed a rom to my droid eris and the Rom worked fine and everything was great until i realized that i CANT receive text messages! So i tried resetting everything and flashing some other roms until it worked and it still doesnt work.
HOw can I get it to receive texts again?
httjs said:
Hey.. I just flashed a rom to my droid eris and the Rom worked fine and everything was great until i realized that i CANT receive text messages! So i tried resetting everything and flashing some other roms until it worked and it still doesnt work.
HOw can I get it to receive texts again?
Click to expand...
Click to collapse
Which rom are you using and what have you flashed? First thing I'd suggest trying is to flash a 2.1 rom such as xtrsense. Open market and install the app APN backup/restore. Backup your APN with the app. Flash the rom you want to use, install APN backup/restore and then restore APN. That would be my first suggestion, it's worked for several others that I'm aware of.
+1 what CondemnedSoul said.
I had that problem. I unrooted, then could receive text after that. so rerooted and flashed the rom back and was still able to receive, so that was my fix.
chadw80 said:
I had that problem. I unrooted, then could receive text after that. so rerooted and flashed the rom back and was still able to receive, so that was my fix.
Click to expand...
Click to collapse
Yes... you can' also do it this way but I would only suggest this as a last resort.
i'm actually having the same problem after flashing to GSB 1.2. When i was on 1.2 i couldn't send or receive and now that i'm on 1.4 i can send but not receive. i would have asked in the GSB thread but apparently you don't know anything about anything if you don't have more than 10 posts...
lygris said:
i'm actually having the same problem after flashing to GSB 1.2. When i was on 1.2 i couldn't send or receive and now that i'm on 1.4 i can send but not receive. i would have asked in the GSB thread but apparently you don't know anything about anything if you don't have more than 10 posts...
Click to expand...
Click to collapse
See post 2 above. I still say try that first before unroot and root again.
Sent from my Ginger Tazz using XDA App
I just realized same thing happened to me...
I have the same problem ever since flashing from GSB v1.2 to v1.4. Tried nand restore back to FroShedYo and KaosFroyo...no dice. Gonna try CondemnedSoul's suggestion. Hope it works!
btw My gmail stopped syncing also at the same time, but worked when I went back to Froyo.
[edit] Thanks to CondemnedSoul my eris is rockin GSB v1.6 and EVERYTHING works!!
omik47 said:
I have the same problem ever since flashing from GSB v1.2 to v1.4. Tried nand restore back to FroShedYo and KaosFroyo...no dice. Gonna try CondemnedSoul's suggestion. Hope it works!
btw My gmail stopped syncing also at the same time, but worked when I went back to Froyo.
Click to expand...
Click to collapse
Go with what I suggested for the text problem. As far as gmail... Check your accounts and sync and make sure gmail is enabled to sync.
This has happened to me many times before. Notably, it also happens if I leave WiFi on when I reboot my phone. Here's what I do (in order, usually step one or two works, I've only ever had to unroot once):
1. Turn airplane mode on, reboot the phone, turn airplane mode off
2. If your previous ROM was running the same version of android, restore a Titanium backup of your dialer storage and reboot
3. APN backup/restore, as mentioned before
4. Unroot, reroot, reflash, as mentioned before
To test, remember you can always send your own number text messages
dc9884 said:
This has happened to me many times before. Notably, it also happens if I leave WiFi on when I reboot my phone. Here's what I do (in order, usually step one or two works, I've only ever had to unroot once):
1. Turn airplane mode on, reboot the phone, turn airplane mode off
2. If your previous ROM was running the same version of android, restore a Titanium backup of your dialer storage and reboot
3. APN backup/restore, as mentioned before
4. Unroot, reroot, reflash, as mentioned before
To test, remember you can always send your own number text messages
Click to expand...
Click to collapse
Gotta love Calvin and Hobbes!
Did the fix and everything works and my gmail not being enabled was the problem. Never thought to check that
Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
lilhaiti said:
Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
Click to expand...
Click to collapse
You flash anything or change anything with a2sd etc, before this started happening?
It's not doing it on an older NANDROID (from 4/22).
I flashed Drowning 7-6 ad then noticed it. But since my last restart before that, I've installed a lot of stuff. I will try it for a while on this NANDROID and see if it does it again after updating my apps, too many changes to rebuild from here...
Basically what happened was I flashed the Kernel (7-6) and restarted, things were fine...but then (per Drownings advice) I restarted again, and then all hell broke loose. I recovered my last NANDROID but experienced the same thing with just a restart, so now I am on an earlier NANDROID and tried a restart and all went well..Like I said I will try to update my apps when I get home (damn ATT data caps) and see what happens then...
OK...several restarts after installing updates, and everything seems normal it's definitely got something to do with either drowning 7-5 or 7-6, or n75 and/or n76.
Right now with the NANDROID I am running n42 with drowning 7 with aufs enabled (as was with the newer ROMS)
I also run DT A2SD with apps and dalvic on SD.
I will try to upgrade to n76 and drowning 7-7 in a few and see how that works out...
n76 and Drowning 7-7 has been good so far...I think the problem is solved...there was definitely something wrong with my setup that was common to the later NANDROID...thank god I saved some NANDROIDS
Wasn't there some kind of known issue with 7.6? I don't remember the details, but I seem to recall that there was some reason why I didn't flash it at the time (aside from general laziness).
Did a fresh install of n76 with S2E and Drowning 7-7, all is running smooth again and I have restarted a dozen times with no issue. After flashing over top of ROM's for the last few months there was probably some trash getting in the way, so I decided to clean house.
Hi Guys,
I got my S3 a few weeks back and had one of the Omega JB roms on it (think it was v17) and then com.android.phone just started failing all the time. So I took it back to the Stock backup i had done before installing the Rom and wiped/ factory reset before that reinstall. The Nandroid backup was made using CWM recovery.
The phone has been fine since then for the last week, but today I was trying to go into Call settings in Phone and every time I press the call settings link in the menu in Phone i get the "com.android.phone has stopped" error. I had facebook synced to the phone but only when on the Omega Rom and not since I've been back on the stock Rom.
I searched a few things for this and it always seems to come back to FB sync issues which cause com.android.phone errors, but I can't work out what else could be affecting it. I tried reinstalling the phone.apk by using the no-increase-ringing mod, but this also doesn't sort it either. I'd rather not go through a full stock rom re-flash if i can help it as well, but feel I might have to. I can make and receive calls no problem as well.
Any ideas?
UPDATE: Have reinstalled the stock phone.apk from Omega files (the one with the increasing volume) and the problem is now solved.
Hi there, ive looked all over online and on here for about a week solid now for a solution for this and cannot find one anywhere! My situation is.. im running gingerbread 2.3.3 on my S2 that I got in 2011. As soon as I got it I flashed the Lite'ning ROM to it. It worked fine up until christmas just gone and just all of a sudden started saying this error message when I tried to open anything, such as messages, contacts, google, camera etc..
"sorry the application ..... (process com.android.vending) has stopped unexpectedly. please try again"
So I have just been trying to get the phone back to orignal factory settings by putting a factory ROM on, or install a new custom ROM in the hope that this will solve the problem and get the phone working normally again. I used Odin and installed a custom ROM successfully (so I thought) but when I rebooted the phone I was still stuck on Lite'ning ROM and everything was how it was before. The same happened when I installed a factory ROM. I also tried to install a custom ROM via the SD card, but this failed everytime.
One other thing.. when I restore to factory settings while on the CMW and then reboot the phone.. nothing has gone, its exactly the same, with all my contacts, pictures and apps. I never knew it would be so hard to restore my phone. Im hoping someone here can advise me on what to do... Ive a feeling it might be to do with the fact the phone is gingerbread 2.3.3 and all the custom ROMs now are made for ICS or Jelly Bean? If so how do I get my phone to work with these ROMs. Thanks for reading and I really hope someone can help!
alexandamusic said:
Hi there, ive looked all over online and on here for about a week solid now for a solution for this and cannot find one anywhere! My situation is.. im running gingerbread 2.3.3 on my S2 that I got in 2011. As soon as I got it I flashed the Lite'ning ROM to it. It worked fine up until christmas just gone and just all of a sudden started saying this error message when I tried to open anything, such as messages, contacts, google, camera etc..
"sorry the application ..... (process com.android.vending) has stopped unexpectedly. please try again"
So I have just been trying to get the phone back to orignal factory settings by putting a factory ROM on, or install a new custom ROM in the hope that this will solve the problem and get the phone working normally again. I used Odin and installed a custom ROM successfully (so I thought) but when I rebooted the phone I was still stuck on Lite'ning ROM and everything was how it was before. The same happened when I installed a factory ROM. I also tried to install a custom ROM via the SD card, but this failed everytime.
One other thing.. when I restore to factory settings while on the CMW and then reboot the phone.. nothing has gone, its exactly the same, with all my contacts, pictures and apps. I never knew it would be so hard to restore my phone. Im hoping someone here can advise me on what to do... Ive a feeling it might be to do with the fact the phone is gingerbread 2.3.3 and all the custom ROMs now are made for ICS or Jelly Bean? If so how do I get my phone to work with these ROMs. Thanks for reading and I really hope someone can help!
Click to expand...
Click to collapse
I think you should try a 3-files odin flash rom.
If you search in google for "Odin 3-files i9100" than you will find the rom
Started with stock, then S-off'd, rooted, and flashed a custom AOSP (can't remember the name). Everything went swimmingly for months.
Out of nowhere, I started getting "internal storage" issues. Internal storage was listed at 1GB, and started filling up regardless of if I deleted things. It seemed to cause slight problems, but nothing serious. Shortly after, I stopped receiving texts altogether. Tried flashing a new ROM, went with MIUI V5, it worked, but still no texts. Decided to start from scratch. RUU, re-root, re-flash recovery, etc etc. Ended up flashing MIUI V5 again, but got stuck in a bootloop. Tried 4-5 different hboots/recoveries/every setting imaginable, nothing. Started over again (RUU >>>), flashed MIUI V5 again, and this time it worked. Load it up, ask a friend to text me, BOOM, text received!
Open up the browser... "403 Forbidden". Wat. Nothing to do about it, it seems. I've tried fiddling with all of the relevant settings, I've downgraded/upgraded radio, nothing. I've flashed to a different ROM and back again, nothing. Just crip-crapity-crap.
As of right now, the rest of my night is going to be spent backing up/flashing to sense to do system upgrades/restoring backup and hoping it works. Anyone know what would cause "forbidden" errors, data wise? Calling/texting works both wase (not MMS, obv).
I think you should try a new kernel
Sent from my HTC EVO 3D X515m using xda app-developers app
Problem was solved by backing up my current MIUI build (working minus data), full wipe, then flashing Harmonia 3.17, doing all available System Updates, full wipe, then restoring my MIUI backup. I now have data, send/receive MMS, and calling, + MIUI V5 totally working.
Finally!
Case closed. Thanks!