Today, I changed my normal Moto G first gen to the Google Play edition. From there, I still had service, and everything seemed fine. From there, I updated it to 4.4.4. Still having service, I updated to 5.0 and then to 5.1, where I lost service.
At first the sim card wouldn't register, but then it just showed "No Service". I've already been into the access points and made sure that everything was correct, but I'm still left with the issue. I've already restarted the phone multiple times.
If anyone can help me at least a little, I would be extremely grateful.
Thanks in advance
Did you fix it??
CookooCam said:
Today, I changed my normal Moto G first gen to the Google Play edition. From there, I still had service, and everything seemed fine. From there, I updated it to 4.4.4. Still having service, I updated to 5.0 and then to 5.1, where I lost service.
At first the sim card wouldn't register, but then it just showed "No Service". I've already been into the access points and made sure that everything was correct, but I'm still left with the issue. I've already restarted the phone multiple times.
If anyone can help me at least a little, I would be extremely grateful.
Thanks in advance
Click to expand...
Click to collapse
Did you manage to fix it? i just got the same problem after updating to 6.0.
reras said:
Did you manage to fix it? i just got the same problem after updating to 6.0.
Click to expand...
Click to collapse
Yeah, actually I did. I had to do a factory reset, and it worked fine afterwards. That was on Lollipop, though. Sorry for taking so long to reply. I don't visit the forum very often.
reras said:
Did you manage to fix it? i just got the same problem after updating to 6.0.
Click to expand...
Click to collapse
Is there another way to fix this problem? I already did a factory reset, but it doesn't seem the work..
Related
I used SHIELD RAM to reflash back to stock (was previously rooted on KitKat) which went fine but I can't convince the Shield to get any updates, it just says "Your system is up to date".
I tried doing a factory reset from Recovery Mode but still nothing. I wondered if something had gone wrong so I ran RAM again and did another full restore but am still having the same problem. Help?
I did reset erase all data in options and that appeared to fix the problem for me. What happened was the OTA update wouldn't download
Sent from my iPhone using Tapatalk
Thanks eikast, I've just tried that too but the problem remains. If I go to Settings -> About Shield -> System Updates -> Check Now it simply says "Your system is up to date" even though it's running 4.3 (build no JSS15J.01.00.14422.0068)
Ellipsis_ said:
Thanks eikast, I've just tried that too but the problem remains. If I go to Settings -> About Shield -> System Updates -> Check Now it simply says "Your system is up to date" even though it's running 4.3 (build no JSS15J.01.00.14422.0068)
Click to expand...
Click to collapse
What country are you in? If youre not in the united states it could be why. If you cant get it theres a couple methods to do it manually.
hexitnow said:
What country are you in? If youre not in the united states it could be why. If you cant get it theres a couple methods to do it manually.
Click to expand...
Click to collapse
I'm in the UK. I managed to get some help from Josh at Nvidia and he reset the OTA flag their end and the update popped up instantly. It seems Nvidia add devices which have had the update (or think have had it) to a 'group' which can then prevent those devices seeing it again.
Ellipsis_ said:
I used SHIELD RAM to reflash back to stock (was previously rooted on KitKat) which went fine but I can't convince the Shield to get any updates, it just says "Your system is up to date".
I tried doing a factory reset from Recovery Mode but still nothing. I wondered if something had gone wrong so I ran RAM again and did another full restore but am still having the same problem. Help?
Click to expand...
Click to collapse
This has happened to me quite a few times... simply use it a few days, it will eventually tell you to update. Other than that, I've never gotten it to manually see the update.
Clearing the data for Google services worked for me.
Regards,
John Francis
same problem for me...i live in Italy...i not received the update i still remain on 4.3...can someone help me???
thanks
I've had this really weird problem ever since the update for 4.4.4 got downloaded to my phone automatically as soon as it was released for the Verizon moto g. I'll be using my phone like normal and this black screen will pop up for a second as if it is asking me to do something but nothing is there then it will go away. It happens quickly and doesn't do anything but it is very annoying. I'm wondering if it is because I told the update not to install yet and set a reminder for later? Although it isn't time for that reminder to go off yet and this happens about every 5 minutes or so. I haven't installed any new apps or downloaded anything and I even factory reset my phone and the problem remains.
I'm not rooted and my boot loader is still locked. Running stock android 4.4.2 on Verizon xt1028.
Ideas?
lilrob1213 said:
I've had this really weird problem ever since the update for 4.4.4 got downloaded to my phone automatically as soon as it was released for the Verizon moto g. I'll be using my phone like normal and this black screen will pop up for a second as if it is asking me to do something but nothing is there then it will go away. It happens quickly and doesn't do anything but it is very annoying. I'm wondering if it is because I told the update not to install yet and set a reminder for later? Although it isn't time for that reminder to go off yet and this happens about every 5 minutes or so. I haven't installed any new apps or downloaded anything and I even factory reset my phone and the problem remains.
I'm not rooted and my boot loader is still locked. Running stock android 4.4.2 on Verizon xt1028.
Ideas?
Click to expand...
Click to collapse
It's from the OTA notification service.I have the same issue, coz I'm lazy to disable the update service atm.
To clarify, the problem you get is a quick flash-in/flash-out in black color. Happens quite quick.Right?
liveroy said:
It's from the OTA notification service.I have the same issue, coz I'm lazy to disable the update service atm.
To clarify, the problem you get is a quick flash-in/flash-out in black color. Happens quite quick.Right?
Click to expand...
Click to collapse
Yeah that's exactly what happens! I figured it had to do with the OTA… so how can I stop it from doing that? or should I just update to 4.4.4? Are there any issues?
lilrob1213 said:
Yeah that's exactly what happens! I figured it had to do with the OTA… so how can I stop it from doing that? or should I just update to 4.4.4? Are there any issues?
Click to expand...
Click to collapse
You can disable it if you have root.In case you do, then go to /system/priv-app/ and find motorolaOTA.apk , change its permissions to 0000 and you`re good :>
liveroy said:
You can disable it if you have root.In case you do, then go to /system/priv-app/ and find motorolaOTA.apk , change its permissions to 0000 and you`re good :>
Click to expand...
Click to collapse
Okay… I don't have root… but the verizon moto g can only get temp root without write access… will that still work??
lilrob1213 said:
Okay… I don't have root… but the verizon moto g can only get temp root without write access… will that still work??
Click to expand...
Click to collapse
No idea, just give it a try.
I have recently been sent the update to android 4.4.2 on my note pro however my WiFi will not connect now.
I've tried restarting the device and it keeps saying "network connection unavailable".
has anybody else had a similar experience with this device?
ryz4eva said:
I have recently been sent the update to android 4.4.2 on my note pro however my WiFi will not connect now.
I've tried restarting the device and it keeps saying "network connection unavailable".
has anybody else had a similar experience with this device?
Click to expand...
Click to collapse
Use search, here are couple topics about broken wifi after update. Factory reset should fix it.
ryz4eva said:
I have recently been sent the update to android 4.4.2 on my note pro however my WiFi will not connect now.
I've tried restarting the device and it keeps saying "network connection unavailable".
has anybody else had a similar experience with this device?
Click to expand...
Click to collapse
Hi!
Have you got Passpoint running?
This might be a totally different issue but if a factory reset or reflashing doesn´t help you might try looking here.
Regards
Elo
ryz4eva said:
I have recently been sent the update to android 4.4.2 on my note pro however my WiFi will not connect now.
I've tried restarting the device and it keeps saying "network connection unavailable".
has anybody else had a similar experience with this device?
Click to expand...
Click to collapse
I have the same effect!
A full reset won't fix this problem. I contacted Samsung support and the said that I should send them the tablet.
A reset usually isn't sufficient, you need to reflash the firmware.
I fully reset the tablet about 4 times and it suddenly works.
Hi all!
I have exactly the same issue.... I just updated my Note Pro LTE (unrooted) to the latest firmware and I also do not have access to wifi.
Could you please help me? I read in this thread that by reflashing might solve the issue, but since I am not so experienced with that stuff on Android (hence the reason I never rooted), could you please provide detail instructions what exactly I have to do?
Thanks a lot for your great help!
elessar2014 said:
Hi all!
I have exactly the same issue.... I just updated my Note Pro LTE (unrooted) to the latest firmware and I also do not have access to wifi.
Could you please help me? I read in this thread that by reflashing might solve the issue, but since I am not so experienced with that stuff on Android (hence the reason I never rooted), could you please provide detail instructions what exactly I have to do?
Thanks a lot for your great help!
Click to expand...
Click to collapse
I eventually made a factory reset and after everything was finalized, wifi was running again fine. All my apps from play store were installed again automatically and everything seemed to run properly!
However, when I woke up this morning, unfortunately the same issue was present. No network connectivity and all available wifi networks were marked 'not in range'!!
Thus, it seems that factory reset does not solve the problem... Therefore I searched on google how to reflash my tablet. This is the link that I found:
http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Could you please confirm whether this is the procedure I should follow? If yes, which update should I use? The latest or the previous one, i.e. P905XXUANH3 or P905XXUANC3?
Also, will Knox be tripped if I flash the firmware?
Thanks a lot for your help and I look forward to your responses!
elessar2014 said:
http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Could you please confirm whether this is the procedure I should follow?
Click to expand...
Click to collapse
Yes.
I usually direct people here: http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969 (It's for the S3, but the procedure is the same everywhere. Make sure you get the most recent version of ODIN. The three buttons have different names (Bootloader/PDA/Phone/CSC are now BL/AP/CP/CSC), but the order is the same.)
If yes, which update should I use? The latest or the previous one, i.e. P905XXUANH3 or P905XXUANC3?
Click to expand...
Click to collapse
You can't downgrade, so use either the one you already have or a newer one.
Also, will Knox be tripped if I flash the firmware?
Click to expand...
Click to collapse
If you use the official firmware for a country in your region, No.
Thanks a lot ShadowLea!!
Eventually there is no need to reflash the tablet....
The only thing I just did was to uncheck the Passpoint option, as Polar67 describes above, in the Advanced Settings of wifi and immediately the issue was fixed!
Thank you all for your great help!!
ShadowLea said:
Yes.
I usually direct people here: http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969 (It's for the S3, but the procedure is the same everywhere. Make sure you get the most recent version of ODIN. The three buttons have different names (Bootloader/PDA/Phone/CSC are now BL/AP/CP/CSC), but the order is the same.)
You can't downgrade, so use either the one you already have or a newer one.
If you use the official firmware for a country in your region, No.
Click to expand...
Click to collapse
elessar2014 said:
Thanks a lot ShadowLea!!
Eventually there is no need to reflash the tablet....
The only thing I just did was to uncheck the Passpoint option, as Polar67 describes above, in the Advanced Settings of wifi and immediately the issue was fixed!
Thank you all for your great help!!
Click to expand...
Click to collapse
Interesting.. Let's remember that solution for when someone else runs into it!
Posted in the wrong forum earlier.
1. Rooted phone 2 months ago
2. Factory reset because it kept restarting.
3. After factory reset the phone wouldn't go past the lgsetup.
4. Used the wrong img file and bricked phone.
5. Fixed with the right img file. (Always check md5!)
6. After I got everything working I updated to MM.
7. Since MM update I get the following error "Unfortunately, Google Play Store has stopped." and Mobile ID is stuck on download.
Pretty sure I broke it by updating. Any help is greatly appreciated!
superstimpy said:
Posted in the wrong forum earlier.
1. Rooted phone 2 months ago
2. Factory reset because it kept restarting.
3. After factory reset the phone wouldn't go past the lgsetup.
4. Used the wrong img file and bricked phone.
5. Fixed with the right img file. (Always check md5!)
6. After I got everything working I updated to MM.
7. Since MM update I get the following error "Unfortunately, Google Play Store has stopped." and Mobile ID is stuck on download.
Pretty sure I broke it by updating. Any help is greatly appreciated!
Click to expand...
Click to collapse
That mobileID thing is tiny carrier specific unnecessary app, you just have to disable. The google play store has stopped is either going to have to be factory reset whereas you'll be better off resetting from recovery, OR send it to LG , they'll fix it for free and send you a free postage label, takes like 10 days.
https://www.lg.com/us/support/mylg/product-registration
Are you factory resetting from recovery or from settings?
tube517 said:
Are you factory resetting from recovery or from settings?
Click to expand...
Click to collapse
When I messed it up the first time it was from settings.
superstimpy said:
When I messed it up the first time it was from settings.
Click to expand...
Click to collapse
That's probably what messed you up.
Never factory reset from settings on a rooted phone.
I don't have the Boost version of the Stylo but there is no custom recovery (TWRP) for that model, is there?
Yeah. No custom yet. I was able to fix the lgsetup issue. Now it's just an issue with Google Play store not working now.
I was thinking about trying to do another reset but am worried I'll break it again. And this time there is no good way to unbrick MM.
superstimpy said:
Yeah. No custom yet. I was able to fix the lgsetup issue. Now it's just an issue with Google Play store not working now.
I was thinking about trying to do another reset but am worried I'll break it again. And this time there is no good way to unbrick MM.
Click to expand...
Click to collapse
Reinstall google play services that should fix it.
Thediesel1972 said:
Reinstall google play services that should fix it.
Click to expand...
Click to collapse
Where can I find the apk or file to reinstall?
Thediesel1972 said:
Reinstall google play services that should fix it.
Click to expand...
Click to collapse
Downloaded apk from apkmirror dot com. Still not working.
Any other suggestions?
Took the chance and factory reset from recovery. Works fine now. Woo!
Thanks for all the help!
SM-G900V (PB1) KLTE, Samsung eMMC (CID 15)
When I first was able to install Lineage everything seem to work fine. But when I woke up the next morning I had a notification saying SIM card not found. So I went to go to cellular networks to check the APN and when I clicked it I recieved an error com.android.phone error. Would you like to restart or mute. Neither option worked. So I reflashed the os and still had the same issue. With TWRP I reformatted and wiped all data and tried for a fresh install. Nothing worked. Was wondering if anyone knows of anything. If you took the time to read this I thank you for your interest.
Rismr said:
SM-G900V (PB1) KLTE, Samsung eMMC (CID 15)
When I first was able to install Lineage everything seem to work fine. But when I woke up the next morning I had a notification saying SIM card not found. So I went to go to cellular networks to check the APN and when I clicked it I recieved an error com.android.phone error. Would you like to restart or mute. Neither option worked. So I reflashed the os and still had the same issue. With TWRP I reformatted and wiped all data and tried for a fresh install. Nothing worked. Was wondering if anyone knows of anything. If you took the time to read this I thank you for your interest.
Click to expand...
Click to collapse
Greetings and welcome to assist. This sounds like a rom specific bug, have you tried grabbing a log and posting it in the rom thread ?
Regards
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. This sounds like a rom specific bug, have you tried grabbing a log and posting it in the rom thread ?
Regards
Sawdoctor
Click to expand...
Click to collapse
Thank you for replying. I seem to have fixed the issue. So I flashed the phone back to factory and rerooted and reflashed rom and it seemed to fix the issue. Not sure I understand how. This time I did wait for a little bit after rom booted and it seemed to eventually work.
Rismr said:
Thank you for replying. I seem to have fixed the issue. So I flashed the phone back to factory and rerooted and reflashed rom and it seemed to fix the issue. Not sure I understand how. This time I did wait for a little bit after rom booted and it seemed to eventually work.
Click to expand...
Click to collapse
As long as its all working thats the main thing