Hi,
I did a factory reset on my e4 which I have owned for about a year.
Got me a new phone and was setting the E4 up for my wife, so did a reset & a couple of things have stopped working like they did before reset.
With data on when trying to send photos by text it just keeps showing as sending & they never go through. I even tried sending a very small image file & it would just be stuck on sending.
This was never a problem before I did the reset.
It is running Android 7.11 and being the wife's phone this is critical for me to fix it
This is a puzzler to me.
Any suggestions will be greatly appreciated.
Mark
snoozer854 said:
Hi,
I did a factory reset on my e4 which I have owned for about a year.
Got me a new phone and was setting the E4 up for my wife, so did a reset & a couple of things have stopped working like they did before reset.
With data on when trying to send photos by text it just keeps showing as sending & they never go through. I even tried sending a very small image file & it would just be stuck on sending.
This was never a problem before I did the reset.
It is running Android 7.11 and being the wife's phone this is critical for me to fix it
This is a puzzler to me.
Any suggestions will be greatly appreciated.
Mark
Click to expand...
Click to collapse
Which e4 do you have? Which carrier? Did you have it rooted? It may need to be provisioned. For CDMA it would be a prl or profile update. Did you disable any stock system apps?
You could try wiping it again and paying special attention to carrier specific parts of setup. Beyond that, it sounds like a carrier/provisioning issue. The stock messaging app is a modified version of Android messages. You may need to go into settings of it and see what is selected (like advanced, rcs messaging).
madbat99 said:
Which e4 do you have? Which carrier? Did you have it rooted? It may need to be provisioned. For CDMA it would be a prl or profile update. Did you disable any stock system apps?
You could try wiping it again and paying special attention to carrier specific parts of setup. Beyond that, it sounds like a carrier/provisioning issue. The stock messaging app is a modified version of Android messages. You may need to go into settings of it and see what is selected (like advanced, rcs messaging).
Click to expand...
Click to collapse
It's an unlocked phone. One of Amazon phones. Never been rooted. It's not CDMA.
No stock apps are disabled.
What is provisioned?
To the best of my knowledge everything is set just like it was before resetting it.
Everything worked fine before that.
Thank you for the reply
Sent from my Moto G (5) Plus using Tapatalk
snoozer854 said:
It's an unlocked phone. One of Amazon phones. Never been rooted. It's not CDMA.
No stock apps are disabled.
What is provisioned?
To the best of my knowledge everything is set just like it was before resetting it.
Everything worked fine before that.
Thank you for the reply
Click to expand...
Click to collapse
Reference material: https://forum.xda-developers.com/moto-e4/help/sprint-sim-unlock-t3744955/post77097366
Davey126 said:
Reference material: https://forum.xda-developers.com/moto-e4/help/sprint-sim-unlock-t3744955/post77097366
Click to expand...
Click to collapse
Thanks for the reply.
When I bought the phone new from Amazon, it was one of the Prime phones it was unlocked to use with any provider.
I just put in Sim card from my carrier and everything thing worked no changes needed to be made.
I figured it was going to be the same after doing a factory reset.
I may just do a reset again and see what happens.
Sent from my Moto G (5) Plus using Tapatalk
Problem solved.
I did another factory reset, but this time I removed the sim card & the ext sd card.
After doing the reset installed the sim card & everything is working like it used to.
It appears doing a reset with sim card in might be a big no-no
Related
After upgrading to 2.26.60, the phone resets every 15-30 minutes.
Unlocked using GSM.
Didn't install any other apps.
Didn't root.
Any solution/suggestion?
My only guess would be to try a factory reset which might solve your problems
My phone went into something close to a death loop where it would reboot toward the end of the startup phase. It seemed like it was caused by some combination of wifi and GPS because the reboot would happen shortly after the GPS system fired up. The solution for me was to delete the Tasker app data through Settings - Applications and that seemed to correct the problem. Hope this helps.
Hmmm, I am having the same problem after the 2.26.60 update.
I also use it on GSM/UMTS mode with a SIM card. The phone works perfectly well, but every three calls placed or received it will either badly distort the sound, or reboot itself. I have an original, non-rooted phone.
Factory resetting it did not help either.
Anyone know of a way of rolling back this update? It definitely did not happen before.
Thanks!
hk9090 said:
Hmmm, I am having the same problem after the 2.26.60 update.
I also use it on GSM/UMTS mode with a SIM card. The phone works perfectly well, but every three calls placed or received it will either badly distort the sound, or reboot itself. I have an original, non-rooted phone.
Factory resetting it did not help either.
Anyone know of a way of rolling back this update? It definitely did not happen before.
Thanks!
Click to expand...
Click to collapse
You can go back simply by flashing the 2.26.20 SBF. You'll find a link for it somewhere on the forums.
Droid flashed back to 2.26.2. Working perfectly now.
Apparently there is a bug with the latest update and using sim gsm networks. It is a shame though not being able to update the software; especially with a brand new, original, unrooted, unmodified phone.
Sent from my DROID PRO using XDA App
http://forum.xda-developers.com/showthread.php?t=923552
Hello everyone. I've owned my 6p since it was first released and have used T-Mobile this whole time. Recently I noticed that no one was texting me so I decided to test it out and text myself and I was right . I wasn't receiving any messages. At the time I thought it might have been something to do with me running a custom ROM so I unrooted and went back to stock and still the same thing was happening. I can send messages but nothing comes back to me. I talked to T-Mobile for a few hours. Literally troubleshooting everything on their end and everything was fine. Full service and all. Now I've been looking all over online and have yet to find anything. The frustration is really getting to me. Has anyone else experienced anything like this before? Are there any setting in my 6p that I might need to check out? Please help me guys.
Again. I have full service bars with activated service. I can make calls browse the web and send messages. I'm just not receiving anything. Also I am using stock google messenge
Of the top of my mind, clear google msn cache and data, from configuration> apps> google messenger... also check in hangouts if u have it if the google messenger is the default app for sms..
Once a long time ago, the rom tool box was the default app for sms and instalation of apps, dunno why this happend.. hope it helps, also u can use a third party app for sms and check, or even the hangouts.
good luck.
Could you provide a screen shot of your selected APN?
V6iNSPIRE said:
Could you provide a screen shot of your selected APN?
Click to expand...
Click to collapse
This. Check your apn against T-Mobile's settings.
V6iNSPIRE said:
Could you provide a screen shot of your selected APN?
Click to expand...
Click to collapse
I contacted T-Mobile and they went through all that with me and my apn was all correct. It's the same apn I've been using the whole time. Also to the guy who said clear cache I fully factory reset the whole phone and re installed every app. I would assume that would clear the cache? It's so frustrating cause everything seems to be working. It's like my phone wants to be stubborn and not receive messages lol
Can you try your SIM card with another phone?
Ok I fixed it. Very weird. I switched to 2g and all texts came through then went back to LTE and continued working
Hey I have the same issue with my OnePlus 3. Stopped receiving sms 3 days ago. I can send sms just fine.
Like note3userr I had rooted my phone, so un-rooted it and did a factory reset, but the issue still persists.
I'm also on Tmobile, my selected APN is T-Mobile US (epc.tmobile.com)
Switched to 2G and back to 4G, as noteuserr suggested. The trick worked for me!
Weird as **** though...
RomboyJ said:
Hey I have the same issue with my OnePlus 3. Stopped receiving sms 3 days ago. I can send sms just fine.
Like note3userr I had rooted my phone, so un-rooted it and did a factory reset, but the issue still persists.
I'm also on Tmobile, my selected APN is T-Mobile US (epc.tmobile.com)
Switched to 2G and back to 4G, as noteuserr suggested. The trick worked for me!
Weird as **** though...
Click to expand...
Click to collapse
Glad I can help man. Seems like it might be a T-Mobile thing. Very frustrating to deal with
I'm running Clark stock 6.0 build MPH24.49-18/unlocked/rooted/xposed on Verizon. Build is fine, was fastboot installed direct from Moto's firmware package back in September and has been running flawlessly. All of a sudden I'm not able to receive any MMS messages. My primary SMS app is Signal so I tried Google Messenger and the stock messenger app and all of them are failing to download any MMS. This just started happening a couple weeks ago. I'm not convinced that this is a rom or any customization that I may have done issue, I think it's purely something with Verizon or maybe an APN issue? It's just weird that this just started happening out of the blue. Before I contact Verizon I figured I'd ask here if anyone has come across this.
I'm on Verizon n no problems.
annoyingduck said:
I'm running Clark stock 6.0 build MPH24.49-18/unlocked/rooted/xposed on Verizon. Build is fine, was fastboot installed direct from Moto's firmware package back in September and has been running flawlessly. All of a sudden I'm not able to receive any MMS messages. My primary SMS app is Signal so I tried Google Messenger and the stock messenger app and all of them are failing to download any MMS. This just started happening a couple weeks ago. I'm not convinced that this is a rom or any customization that I may have done issue, I think it's purely something with Verizon or maybe an APN issue? It's just weird that this just started happening out of the blue. Before I contact Verizon I figured I'd ask here if anyone has come across this.
Click to expand...
Click to collapse
Had this happen once about a year ago on the stock rom too. I hadn't made any major changes and the phone stopped receiving MMS. It had been working fine for at least a month prior. On AT&Ts network for me.
Restoring a nandroid backup fixed it, but I never did actually figure out what went wrong.
jason2678 said:
Had this happen once about a year ago on the stock rom too. I hadn't made any major changes and the phone stopped receiving MMS. It had been working fine for at least a month prior. On AT&Ts network for me.
Restoring a nandroid backup fixed it, but I never did actually figure out what went wrong.
Click to expand...
Click to collapse
So the backup restore fixed it...? So strange. Now I must figure out what is causing this.
Sent from my XT1575 using Tapatalk
annoyingduck said:
So the backup restore fixed it...? So strange. Now I must figure out what is causing this.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I was rooted with a custom kernel, but had been for weeks with no problems. Then mms just quit working.
Didn't do much troubleshooting, sorry. Restoring the backup fixed it and it's never happened again. Could be a coincidence, but sounds just like what you described.
I've had this happen a few times, a power off reboot usually fixes it. Verizon, true pure x. I've been to stubborn to reload to see if it fixes it permanently.
SOLVED
The issue is with the APN settings. 2 Lines were incorrect:
-MMS Port was set to "not set", it needed to be "80"
-APN Type was set to "default,dun,supl", it needed to be "default,dun,supl,mms"
Very strange that these configurations magically changed themselves. What's even funnier is that Verizon customer service told me that the issue is that it's a non-Verizon phone and the only thing they could recommend was a factory reset and/or a new sim card. They also would not give me the correct APN's, they said some nonsense about that information being unavailable to them. So Google fixed this issue for me. FU Verizon.
I have had mixed luck with different APN settings. The above worked for me for a while, and then inexplicably stopped. I tried a bunch of different configurations before sticking with the settings in the attached screenshot. These settings worked for me on Marshmallow and continue to work on Nougat (7.1.1). These are also the settings that appear after resetting my network settings from the Mobile Networks menu. I hope this can help someone out.
Have searched extensively and found no working solution to this issue. Return would be a last and unwanted resort. Here's the deal. Mobile Hotspot performs strangely no matter what android version I run. In marshmallow it would turn off during use. In nougat it would just crash and need to be restarted. It most reliably occurs when playing lan minecraft over 2 comps on the hotspot but will still have the issue randomly even when only 1 device is connected. Many calls to various companies have all resulted in "send it back in". This is infuriating as this feels like a software issue not a hardware issue, I just can't see how it can be any other way. I have tried everything I could think of and had no luck, here's the list of what i've tried so far:
Restart phone
Factory reset
update to latest firmware
downgrade back to original marshmallow firmware
there is no access to advanced settings for hotspot so timeout is non-existant
reset network settings
edit: also tried ElementX kernel still have the same problem
tried flash-all to stock Marshmallow firmware without restoring apps or settings
RMA TWICE
etc. (any others I've forgotten that I did I will edit and add if ppl suggest it)
Nothing works, before I downgraded back to MM I did capture a bug report when the crash happened on latest nougat. I have no idea if I caught relevant info but will include the zip here anyway. Any help is massively appreciated.
Flash the correct factory images using google flash-all method (backup data first or remove -w in the script!). Upon startup do NOT restore settings apps etc.. and test.
If it doesn't work post a bug report on google website.
rchtk said:
Flash the correct factory images using google flash-all method (backup data first or remove -w in the script!). Upon startup do NOT restore settings apps etc.. and test.
If it doesn't work post a bug report on google website.
Click to expand...
Click to collapse
if it wasn't clear in my post I was at factory default and the problem occurred and have restored and erased a few times. If the method you're describing is different form having out of the box stock please elaborate, I only flashed a kernel recently as a further last resort.
By not restoring settings are you referring to not allowing google backups to restore? and finally if you can provide a link to where exactly I am to post this bug report I would appreciate it, I have posted in what I thought was official channels with a bug report and was told to call in, which is stupid, considering if I leave a bug report why not read it and get back to me?
Anyways thanks for reply and any further info you give
rchtk said:
Flash the correct factory images using google flash-all method (backup data first or remove -w in the script!). Upon startup do NOT restore settings apps etc.. and test.
If it doesn't work post a bug report on google website.
Click to expand...
Click to collapse
Finally got back from vacation and had time to try your request. used flash-all method and did not restore any apps or settings and hotspot still did not work. any other info or at least a link to where I should post a bug report to google as I have used the report function through the device and have posted on nexus help forums and not received answers. I really don't want to have to do an rma as I hate the thought of receiving a refurb phone when I wanted a brand new one and they sent me a broken one
well all is officially lost as I am in the process of doing an RMA. Multiple phone calls between carrier and manufacturer see each company blaming the other with no solution in sight. Fingers crossed hard enough to bleed that somehow a new phone or any "repairs" done to mine will fix the issue. Come back in a few weeks for an update. :crying:
I would confirm with T-Mobile that your line is provisioned with Tethering. When testing an AT&T SIM from a friends UDP (no tethering) account, this is what would happen. My T-Mobile and Verizon accounts both allow it, so it just works.
SpookyTunes said:
I would confirm with T-Mobile that your line is provisioned with Tethering. When testing an AT&T SIM from a friends UDP (no tethering) account, this is what would happen. My T-Mobile and Verizon accounts both allow it, so it just works.
Click to expand...
Click to collapse
I have tethering on my account and have had it for 2 years. worked flawlessly on other devices before switching to this one. It also doesn't explain why it could work for hours at a time before failing. Or why it would consistently fail within minutes when playing LAN minecraft.
Well Huaweii has been an absolute joke, after 3 weeks of terrible communication and no transparency I finally received my phone in the mail (no email notification on if it is a replacement device or not) and the issue still persists. I'm at a loss for what to do.
Hello guys. I have an a Verizon S7 currently being used on Metro PCS. I'm still running 6.0.1 Marshmallow and hoping I wouldn't have to do any software updates until a few days ago. I suddenly began getting a "sim card error" when I tried dialing out. I took out sim card, popped it back in and same issue. I even checked the sim and tray for any damage and there is none. Also, the phone has never been exposed to any liquid at all. I tried a soft reset, still same issue. Tried clearing cache in recovery, same issue still. Finally did a full wipe, set up as a new phone without doing the 7.0 update. That hasn't cleared the issue. I still can't dial out, HOWEVER people can still call me and the calls go through normally. I can also send texts. This isn't happening only in low signal areas as I initially thought. I'll have full bars in some places and not be able to call out. I don't really want the 7.0 update since I like the way my phone is now on MM. Are there any other options for me at this point? I did some research and it looks like people are relating this to a software issue which would mean I'd have to take the plunge into Nougat...
Unless anyone here can offer an alternative? :fingers-crossed:
As an added bonus, does anyone know if my mobile network settings (GSM/CDMA, GSM, UTS, etc) have something to do with this? Thank you for any suggestions!
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Dirtydcs said:
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Click to expand...
Click to collapse
Sorry for late reply. What's AP?
Dirtydcs said:
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Click to expand...
Click to collapse
By the way I ended up taking my sim card out and put it back in. It worked fine. Just yesterday it did the sim error again so it reminded me of this thread
Try going into b recovery mode and wipe cache. I did that &it fixed my calling.