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
Related
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I dont use ROM manager to flash it in, I flash everything in through recovery.
McLabia said:
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I flash everything in through recovery.
Click to expand...
Click to collapse
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
devindpotts said:
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
Click to expand...
Click to collapse
The ROM Ive been on hasnt mattered. Ive jumped through BAMF, the new Cubed Rom, the Deodexed stock debloat and Virus' Airborne(which is my daily driver). Ive done the different radios. I was on the v2 leaked for a while, then I switched to the new 3g and old 4g to see if its worked but it hasnt. I may have to try out the original one and see if that works, but I havent had wifi since before I flashed in the leaked radio when it came out.
isdnmatt said:
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Gotcha. Trying this now. I will make sure to make a nandroid this time if it works. lol.
@isdnmatt: Thanks, that got rid of my recovery problem
Still having wifi issue though. 100% out of the box stock and I get the "Unable to scan for networks
**** me, I should have read that before I did it. Now I have to reroot. Goddamnit.
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
ILMF said:
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thats a separate issue than what Im having. Im not having issues with it forgetting my networks. I cant scan for networks.
I am thinking of downgrading the radio.
EDIT: after LOTS of research here, I upgraded to MR2 and Gingervitis. All of my WiFi issues are gone.
Sent from my TBolt using XDA Premium App
Search, nothing relating to CM 7.1.
Anyone kow if there is an issue when *228 or *22899 both fail for me.
Thanks in advance for any thoughts.
THey fail for me too :/
I had it glitch twice on my little brothers phone and my gf's.It would end up breaking my service until I rebooted the phone.
And I could not get my gmail accounts to sync because I didn't flash the google add-ons lol...( I haven't rooted or flashed for a long while now)
Yeah, *228 never worked for me on CM7 either. I even flashed a new modem with an EFS wipe
I have read somewhere on here before that it does work just reports on the phone it failed. I just did it to test and the system voice advised it was successful but phone advised failed and try again.
That's exactly what happened, sfobrien. Thanks again for the info. I thought it was funny that one said successful, and the other said not...
Either way, it works, and the ROM is rather nice. I flashed it for my wife who had previously been running a rooted stock. It had updates waiting, but I wasn't even about to let the OTA run.
So far, it's been perfect for her. I'm running the same on my incredible flawlessly.
Thanks!
sfobrien said:
I have read somewhere on here before that it does work just reports on the phone it failed. I just did it to test and the system voice advised it was successful but phone advised failed and try again.
Click to expand...
Click to collapse
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
*READ BELOW FOR A GUIDE TO FIX*
I've had my note for over a year now and i have had it rooted pretty much the entire time. Never any problems with it up until recently it started doing this thing where it would keep restarting. It would boot up and less than a minute later just restart. Off and on for a few days it was doing this. I was still running 2.3.6 at that point. So i decided to push 4.0.4 via odin since kies didnt support the firmware. Everything was working fine for a few hours then all of the sudden "the ring of death" showing me no service. Went through the phone and noticed it was saying there is no sim inserted. Tested sim on another phone. Works fine. Since then ive figured out via kies i can recovery and update firmware. Tried that. No Bueno. Now im to the point where im on 4.0.4 with no service. I've scoured through forums trying all kinds of different things, pushing different roms and modems via odin and cwm. Still no bueno.
Baseband version
Unknown
Kernel Version
3.0.8
Build Number
IMM76D.UCLF6
If anyone can give me ideas im willing to try them out.
Thanks.
I got it working so heres a direction for anyone else who has this issue!
Replaced Sim&SD card reader-No fix
After flashing all kinds of roms & modems still same issue saying no sim inserted.
Do a hard reset through your settings.
Flash cwm and put the radio from this link on your sd card. Use cwm to flash the radio.
Flash rom http://forum.xda-developers.com/showthread.php?t=2261598 via odin.
The first try i got an error during flash and got stuck on the software download error screen.
Reflashed the JB rom.
After its flashed flash clockwork recovery.
Enter cwm and do a factory reset. Clear cache. Clear dalvik cache. Reboot system.
If you get service, turn off phone. enter cwm and do a backup.
Reboot system.
It should be working.
If not restart and make sure to do a factory reset through your settings in the phone before reflashing rom.
Got the Phone up and running for about 30 mins.
After battery removed it reverted back to no sim card inserted.
Kept reflashing rom until it worked again.
Flashed cwm.(ClockworK recovery mod)
Deleted cache, dalvik cache
Backed up via cwm
If it reverts back to no sim after that restore using the cwm backup.-it worked for me
Now for the tricky part, my phone was getting crappy service...
So heres what i did to fix it.
Settings-more settings-mobile networks-access point names-click on the apn.
Name-
ATT Phone
APN-
Phone
Proxy-
Not set
Port
Not set
User Name-
Not set
Password-
Not set
Server-
Not set
MMSC-
http://mmsc.mobile.att.net
MMS Proxy-
proxy.mobile.att.net
MMS Port-
80
MCC-
310
MNC-
410
Authentication type-
None
APN type-
default,admin,fota,mms,supl,hipri,internet
APN protocol-
IPv4
Enable/disable APN-
(check mark)
Bearer-
Unspecified
Hope this helps anyone else having this issue.
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
440bro said:
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
Click to expand...
Click to collapse
I Started from scratch via "kies emergency recovery".
No luck.
dweeezy said:
I Started from scratch via "kies emergency recovery".
No luck.
Click to expand...
Click to collapse
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Stuck power button. Your pants are too tight.
Theoriginalgiga said:
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Click to expand...
Click to collapse
i ordered a new sim port to see if that works. what is gb?
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
dweeezy said:
i ordered a new sim port to see if that works. what is gb?
Click to expand...
Click to collapse
GB stands for Gingerbread which was the first version of the OS that came with the phone. I believe the number was 2.3.6 (you can take a look in the about section in the settings and it'll tell you what you're currently running). ICS is Ice Cream Sandwhich which for our phone was 4.0.4 i believe. Jelly bean just came out today which you can use Kies to upgrade to and that I believe is 4.1.2. The numbers don't really mean a think, just the classification of what the OS is so if your phone reads something else (say 2.3.4) assume your phone is right and I'm wrong. I can't remember OS versions to save my life haha.
But you can use Kies to do an emergency recovery and I THINK it'll install Gingerbread. that's where I'd start, then test it, and then move to ICS and test, and then move to JB and test. I know long tedious process, but sometimes it's necessary. Imagine how fun I am to talk to on the phone while troubleshooting a computer :laugh:
redman9 said:
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
Click to expand...
Click to collapse
what I use to migrate, and I between roms at least once a week with a full wipe because I rely on my phone being stable.
SMS and call logs: SMS Backup + (saves your call logs and sms to your gmail account. Makes a label for it and everything, pretty sweet. You can also restore from it. it takes about an hour for me to restore at 7000+ text messages).
pictures/media: stored on SD card
apps: if rooted and rommed I use titanium backup and run 2 sets. those which I want to keep my data like sms backup + to make restore easier and those I don't care about the data like google voice. If you're stock, just remember to check the little box in the beginning saying backup this phone to google (or something like that) and the next time you have to restore tick the box that says restore from google (or something like that) and it'll reinstall your apps. Mind you not the info, but it'll give you a head start.
As with your issue with installing roms. If you're using CWM i highly recommend switching to TWRP, not saying it's better in fact I like CWM better, but TWRP is the best for our roms and phone. If you have no clue what I mean by CWM or TWRP, read the all info sticky about how to rom thy phone.
I hope that helps.
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
redman9 said:
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
Click to expand...
Click to collapse
No problem always happy to help. since you're used to this sorta thing you don't need to use odin again and reroot. What you can do is either install TWRP through CWM using this file here:
http://goo.im/devs/OpenRecovery/sgh-i717/openrecovery-twrp-2.5.0.0-quincyatt.zip
Or you can install Goo manager, click settings and select Install OpenRecoveryScript (though that's only 2.4.4.0 the link above is 2.5.0.0)
That should change you over to TWRP. and like always do a nandroid backup and then flash to your heart's content!
fixed!
dweeezy said:
fixed!
Click to expand...
Click to collapse
How ?
galinha said:
How ?
Click to expand...
Click to collapse
i have the same issue.....i kn0w its n0t an hardware issue....my ph0ne is fairly new never dr0pped and this started happening 3 days after i p0rted black star jb alpha
I have this same issues ive tried flashing everything ive tried a new sim and replaced the card reader.
What works consistently for me if to flash the latest modem everytime i have to reboot or boot the note. Its my daughters phone now and she drains the battery regularly if it boots after charging or it needs to be rebooted for whatever reason it will come up with the no sim card error. If i flash the modem thru recovery it will work for that boot but only as long as I dont reboot or shut the phone off, then i will have to flash the modem again.
Not fixed
All. This is not fixed. I am having the same issue and if you follow the guide, it works for a day maybe regardless of what rom is loaded or what modems. Has anyone found a real solution to this yet??
i717 running stock GB or ICS or JB roms...
Thanks!
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Kraize said:
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Click to expand...
Click to collapse
I'm having the same problem. There seems to be no set way to get it back to working. Basically any reboot of the phone produces a no sim card error. I have tried flashing the modem through recovery as it was mentioned that will fix the problem. That did not work for me. What does work, sometimes, is one of the following:
1. Full wipe and reinstall
2. Restore backup from Recovery
3. Fix permissions
I just keep doing one of the above listed and eventually it works. However if the phone reboots then it's back to the carousel of trying these options to get it back to working.
I'm running Padawan JB V2
I honestly have no idea what's causing it. I haven't tried to fix permissions before to fix this issue, but if I go into recovery and install the modem again and reboot, it works fine for a while (and by a while, I mean like a few hours at max).
Just started having this issue, myself...after flashing Tmo_SGH-T989_VKL1_radio_ATTNOTE.zip modem on my phone...restoring from a prior backup...
Restoring a backup will not change your modem.
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
This is my fist post, have visited many times. Here we go.
As a LG V20 owner, I recommended the V30+ to two people at work. In a matter of 24 hours, both units stopped sending and receiving emails. I have taken the sims out and tested these in other phones, not a sim issue. I then moved my sim (Telstra Aus) into the V30 and only in the Messaging app, it came up with the message No SIM. This I thought might be a sim slot issue, moved it into the other slot closest to the outside. This worked for about an hour. Then the same issue occurred again. It has to be software, an update or a network change that has caused this. I did a network setting reset, have cleared cache for messaging app. SAFE MODE etc. Very strange.
yanni_pap said:
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
Click to expand...
Click to collapse
Yes I used Messenger app for SMS and this failed. It sounds network setting related but still testing.
I had the same problem on my V30, suddenly SMS has stopped working. (I'm using Textra app)
I checked the sim card on the other phone and it was ok.
I found on the internet that other V30 are also affected.
The solution was to install the Message app from Google and run it.
Now SMS is working on Textra and also on the stock app.
Whoa, didn't see this before I posted in another thread. Same problem here, but I already had Messages installed! Wonder if it's just this phone for some reason?? My partner is also on VZ (S7) and can send SMS
edit: apparently it's something Google broke. Temp fix is to disable Carrier Services!
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
gimpy1 said:
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
Click to expand...
Click to collapse
See my solution directly above your question. It's not "rooting" that caused it, it's "Google" that caused it. Uninstalling or freezing Carrier Services will fix it. Did for me.
Check the litany of * reviews from today alone:
https://play.google.com/store/apps/details?id=com.google.android.ims&showAllReviews=true
Also, both the standard and debloat ROMs for VS99630c from their respective threads and androidilehost are downloading fine for me.
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
As an edit. My phone has also started giving me problems with my fingerprint recognition and my phone dialed has suddenly changed looks forcing me to constantly press and swipe an unlock button to keep the dial pad open if I hesitate too long in punching in numbers or trying to change to speakerphone from there.
I don’t know if it is something I have done/installed (wrong modem perhaps?).
And having the new XDA transition at the same time certainly didn’t help .
gimpy1 said:
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
Click to expand...
Click to collapse
I don't know what to tell you about the downloads, confirmed they work.
You don't need to freeze CS, you can literally just uninstall it from the Play store. It's just an enhancement for the Google MEssages app they broke. if you don't use Messages, you surely don't need it. I don't know what you meant about CS showing up in the "non installed portion of the apps". It's either installed and frozen or thawed, or it's not. Maybe you had a backup there for reasons? Regardless, you certainly need to reboot after changing CS, not sure if you did that.
You have alot of other issues coming from RR, then flashing a modem, then trying to dirty flash VS996. Since you have TB already, you should definitely backup your apps, then Maybe clean flash VS99630c once you've followed the WTF thread. You should probably wipe your system after the other ROMs and just start over.
That certainly was a quick answer. In TiBu, under “backup/restore”, I have all the apps that are currently on my phone—a very long list. This list can be frozen, etc., and is bolded and colored fonts. Scrolling down that list, it ends and a list starts that is not bolded and has lines thru it. I guess these are apps, etc. that I have, at one time, had on the phone and can be re installed via TiBu.
I was trying to “start over” by downloading the vs99630c rom and try it. Where were you thinking I need to start over at? I wish to work only on “zips” via twrp, as I don't have much luck/knowledge with kdz and computers.
Thx, again.
Again, I'm the furthest thing from the expert here, but he's on travel! Check the WTF thread, because I'm not sure what happens when you wipe with the flashes you've made. But you'd probably start from 6.7. MORE TWRP ACTIONS here:
https://forum.xda-developers.com/t/...ar-instructions.3790500/page-10#post-76584629
I would reboot to TWRP and do a complete system backup in case this goes tits up you can restore that from TWRP. Then I would boot to OS and back up everything in TB, then delete all uninstalled backups through the batch actions. Then reboot to TWRP again, wipe, install the VS99630c ROM, install MAgisk, reboot. Make sure your install works then restore your apps through TB.
Ok, thx. I wish to install the vs99630c rom zip now (not the debloated) and am unable to download it from JohnFawkes LG V30 vs 996-30c thread from here on xda. I have tried via my phone about a dozen times now and it stops now generally after the 10 to 20% zip has downloaded. I even tried it a couple of times downloading onto a laptop. Can you possibly point me to a different link that I can try? I need to be on Verizon’s vs 996 and not on the 998 rom, I think? Sorry for the big bother.
Well, I did finally find a download mirror on here from chazzmatts thread using his mirror. It is downloaded now. I will try this installation before going thru the wtf steps you referred me to. If this doesn’t work, then i will try it.
thx, again for your help.
As an update, I did a clean wipe and installed this zip. So far, it seems to have settled things down for. I was able to text (2) and make a phone call. Both worked. I did agree to everything they asked (I normally refuse things such as location, etc.). I’m happy for now. Later, I may try to reinstall the debloated zip.
Ideveraux, thx for all your help on here. I really appreciate it.
Make sure you backup TWRP and TB. Just saying!
And to the OP, I’m sorry I hijacked your thread. I hope you got yours solved, too.
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Lozv said:
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Click to expand...
Click to collapse
I tried that initially and that's not the accepted fix at all. Read above.