Related
[Q] ls980zv7_01_to_zv8_13 update
My phone keeps telling me to install ls980zv7_01_to_zv8_13. Whenever I say yes, it reboots, but as far as I can tell the update doesn't install and after a few days the update notification pops up again.
my device rooted,
and im still not recieve Kitkat update on my device,
anyone please help :crying:
im use LG g2 sprint, im buy in canada, but my location now in Asia and use local Provider
Anyone help please
Same problem
I'm having the exact same issue, and my phone is rooted too. I've done the update profile that it tells you do to prior to install, but it doesn't install. Phone reboots, upgrade animation starts then quickly just goes to the home screen and still running 4.2.2.
I haven't found any fix yet...
wolvyne said:
I'm having the exact same issue, and my phone is rooted too. I've done the update profile that it tells you do to prior to install, but it doesn't install. Phone reboots, upgrade animation starts then quickly just goes to the home screen and still running 4.2.2.
I haven't found any fix yet...
Click to expand...
Click to collapse
and still not solved your problem??
ohhh this make me confused :crying:
and you not reciev kitkat update on your G2??
vrythree said:
and still not solved your problem??
ohhh this make me confused :crying:
and you not reciev kitkat update on your G2??
Click to expand...
Click to collapse
Still nothing. I even tried unrooting my phone to see if it was a root issue breaking the update. Even with everything back to stock the upgrade fails.... Frustrating! I'm starting to look at custom roms to get to 4.4.2 at this point as I can't find any fix.
You might have to revert to stock to lose root before the update can apply. Do you have a custom recovery installed?
InsanePostman said:
You might have to revert to stock to lose root before the update can apply. Do you have a custom recovery installed?
Click to expand...
Click to collapse
No custom recovery. All I did was root it, I tried unrooting with no success. I may try doing a full factory reset, but not sure if I want to go through the pain of resetting it up again... :good:
If I get bored and try it sometime I'll post my results.
InsanePostman said:
You might have to revert to stock to lose root before the update can apply. Do you have a custom recovery installed?
Click to expand...
Click to collapse
how can i have custom recovery ??
i still using JB
and now my phone got bootloop :crying:
wolvyne said:
No custom recovery. All I did was root it, I tried unrooting with no success. I may try doing a full factory reset, but not sure if I want to go through the pain of resetting it up again... :good:
If I get bored and try it sometime I'll post my results.
Click to expand...
Click to collapse
my phone its working now and update Kitkat,
i use this thread : http://forum.xda-developers.com/showthread.php?t=2432476
But my phone need unlock sim and im tried this : http://forum.xda-developers.com/showthread.php?t=2655133
my problem is APNs its not working but my signal working good for SMS and phone.
vrythree said:
my phone its working now and update Kitkat,
i use this thread : http://forum.xda-developers.com/showthread.php?t=2432476
But my phone need unlock sim and im tried this : http://forum.xda-developers.com/showthread.php?t=2655133
my problem is APNs its not working but my signal working good for SMS and phone.
Click to expand...
Click to collapse
and now my phone working very well...
until update kitkat my antutu decrease than JB
vrythree said:
my phone its working now and update Kitkat,
i use this thread : http://forum.xda-developers.com/showthread.php?t=2432476
But my phone need unlock sim and im tried this : http://forum.xda-developers.com/showthread.php?t=2655133
my problem is APNs its not working but my signal working good for SMS and phone.
Click to expand...
Click to collapse
Brilliant! Took almost an hour to go from flashing the firmware, to applying all the granular updates (3 of them) to get to 4.4.2, but it did work. :good:
Doing a restore from backup & restore does not fix the issue just as a fyi to anyone else having this issue.
Hello frnds!
I am using Samsung S3 NEO with Stock ROM and without ROOT but from the last 3 days, I am unable to use the device! Every 5 seconds this error pops up - Process.com android not responding!
I am simply unable to use the device! Can't even call someone!
I tried a factory reset but of no use! This error still prevails but the occurence duration has been reduced! But, still m unable to use the fon as it just hangs up in between anything and everything!
Pls. help me with it's solution asap! What should I do? Pls...
UPDATE - It asked for updating and I updated my device to 4.4.4 (Stock).
But still, the phone still hangs a lot but the error has changed! Earlier, it showed - Process com android not responding!
But now, it shows - Google Play, Google TV, Google Calendar has stopped working!
These types of errors are being displayed and m still unable to use my device! Pls. let me know it's solution!
techie_vintage said:
Hello frnds!
I am using Samsung S3 NEO with Stock ROM and without ROOT but from the last 3 days, I am unable to use the device! Every 5 seconds this error pops up - Process.com android not responding!
I am simply unable to use the device! Can't even call someone!
I tried a factory reset but of no use! This error still prevails but the occurence duration has been reduced! But, still m unable to use the fon as it just hangs up in between anything and everything!
Pls. help me with it's solution asap! What should I do? Pls...
UPDATE - It asked for updating and I updated my device to 4.4.4 (Stock).
But still, the phone still hangs a lot but the error has changed! Earlier, it showed - Process com android not responding!
But now, it shows - Google Play, Google TV, Google Calendar has stopped working!
These types of errors are being displayed and m still unable to use my device! Pls. let me know it's solution!
Click to expand...
Click to collapse
Try to flash the stock firmware via odin. You can download it on sammobile's firmware section
koroveshi said:
Try to flash the stock firmware via odin. You can download it on sammobile's firmware section
Click to expand...
Click to collapse
Have tried this also! Didn't work! The fon simply doesn't respond at all! M unable to use it!!
Any other solution pls??
Thanks to the bad gplay updates, the software is pretty bugged. Just download the stock firmware and check checksums before flash. Or flash custom rom from the section down below.
Dont know if you already tried but did you do a factory reset after the 4.4.4 update. I know OTA updates shouldn't mess stuff but sometimes they do.
koroveshi said:
Try to flash the stock firmware via odin. You can download it on sammobile's firmware section
Click to expand...
Click to collapse
I have tried this but of no help!
mandzo said:
Dont know if you already tried but did you do a factory reset after the 4.4.4 update. I know OTA updates shouldn't mess stuff but sometimes they do.
Click to expand...
Click to collapse
I even did a factory reset but of no use!
MoHuToP said:
Thanks to the bad gplay updates, the software is pretty bugged. Just download the stock firmware and check checksums before flash. Or flash custom rom from the section down below.
Click to expand...
Click to collapse
I had flashed CM12 (5.1.1). It all went well - the flashing & all! But, i cudn't make any calls!
I have installed this ROM on my S3 Neo! But, m unable to make any call (From the SIM 1. Haven't used SIM 2 coz of the Audio prob being faced in the SIM 2 as mentioned in the thread). Whenever I make a call (sim 1), it gives an error - PROCESS SYSTEM ISN"T RESPONDING! Do u want to close it?
Even if i Click WAIT, nothing happens, there;s just a green screen being continuously displayed for about 30 seconds and then automatically, it gets back to the HOME SCREEN~!
I am unable to receive any incoming call also! The fon automatically reboots if a call comes and once it restarts, it shows the log in MISSED CALL!
Pls. Help! How to solve this out?
UPDATE :- I flashed CM11 after this problem thinking it might solve the problem but of no use again! Even, after installing CM11, I am unable to make any calls! The screen just goes blank! And then automatically gets back to the home screen! It's not showing the error of PROCESS SYSTEM NOT RESPONDING as it used to show up in CM12!
Now, pls. some one tell me it's solution at the earliest!! Pls..
techie_vintage said:
I have tried this but of no help!
I even did a factory reset but of no use!
I had flashed CM12 (5.1.1). It all went well - the flashing & all! But, i cudn't make any calls!
I have installed this ROM on my S3 Neo! But, m unable to make any call (From the SIM 1. Haven't used SIM 2 coz of the Audio prob being faced in the SIM 2 as mentioned in the thread). Whenever I make a call (sim 1), it gives an error - PROCESS SYSTEM ISN"T RESPONDING! Do u want to close it?
Even if i Click WAIT, nothing happens, there;s just a green screen being continuously displayed for about 30 seconds and then automatically, it gets back to the HOME SCREEN~!
I am unable to receive any incoming call also! The fon automatically reboots if a call comes and once it restarts, it shows the log in MISSED CALL!
Pls. Help! How to solve this out?
UPDATE :- I flashed CM11 after this problem thinking it might solve the problem but of no use again! Even, after installing CM11, I am unable to make any calls! The screen just goes blank! And then automatically gets back to the home screen! It's not showing the error of PROCESS SYSTEM NOT RESPONDING as it used to show up in CM12!
Now, pls. some one tell me it's solution at the earliest!! Pls..
Click to expand...
Click to collapse
Maybe an EFS error, restore EFS partition and see if permissions are set correctly
sev3n1985 said:
Maybe an EFS error, restore EFS partition and see if permissions are set correctly
Click to expand...
Click to collapse
I have a query! Is EFS only meant for IMEI related probs? Just asking becoz my fon is showing the IMEI Number and i am able to send and receive sms but problem is only with the calling! Can't make or receive any call!!
techie_vintage said:
I have a query! Is EFS only meant for IMEI related probs? Just asking becoz my fon is showing the IMEI Number and i am able to send and receive sms but problem is only with the calling! Can't make or receive any call!!
Click to expand...
Click to collapse
Try with a complete wipe of cache, system, data, dalvik, and internal memory, after that reinstall cm11 rom
sev3n1985 said:
Try with a complete wipe of cache, system, data, dalvik, and internal memory, after that reinstall cm11 rom
Click to expand...
Click to collapse
I just tried this too but the problem still exists!! I am unable to call!!! What should I do now?
I have followed the guide to flash the unlocked firmware and root my S7 Edge (http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145) and all has been working well this weekend. This morning my phone gives me a persistent popup notification about a service provider update and "my device will restart to configure features supported by new sim card." The only option is to press ok and allow it to reboot. I cannot use my phone while this notification is active, and I am unable to kill it in any way. When the phone reboots to recovery, the configuration fails with "dm-verity verification failed". I then reboot system or power off and the endless cycle continues.
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
I wasn't getting any notifications however i did have some strange behavior going on and rebooted only to get the dm-verity verification failed and was no longer able to boot it would just sit at the Samsung splash screen I then had to factory reset re-post and re-setup everything, hopefully your experience won't need that since you are still able to boot!
Sent from my SM-G935U using Tapatalk
Thank you for the response, it's always nice to know someone has had similar problems. Looks like I will have to try reflashing the firmware. After your re-setup, did you do anything to prevent the issue from reoccurring?
Everything is again in working order. If anyone finds this and has the same problem, after flashing the Verizon fixes the phone is identified (in the about device setting) as the SM-G935V version again and is set to download updates automatically. I unchecked this option and I hope this should prevent it from happening again.
Not really wasn't sure exactly what happened the first time but thankfully (knock on wood) ??? it hasn't happened again.
Sent from my SM-G935V using Tapatalk
mine did it too. had to reinstall the whole thing.
drmatthews1 said:
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
Click to expand...
Click to collapse
shawnten said:
mine did it too. had to reinstall the whole thing.
Click to expand...
Click to collapse
I encountered this issue today and found a solution:
http://forum.xda-developers.com/galaxy-s7/help/whats-package-service-provider-update-t3425169
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Dameon87 said:
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Click to expand...
Click to collapse
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
thedrizzle said:
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
Click to expand...
Click to collapse
This has been my experience, as well as a few others. I'm not 100% sure it's that setting in particular, but I am 100% sure that it is caused by a setting in xTouchWiz. I had the issue once before, and it was a clean install save for xTouchwiz and me running through all the options. Since then, I've limited the choices in xTouchwiz and have not experienced the issue since. When I have some time I'll run through it and see if I can replicate the behavior again, since I'm working on a ROM.
There is a simple fix...
I agree, XtouchWiz drops a bomb when installed and it will cripple your phone. I never played with DVFS, I personally though it was the disable TIMA that set it off. An easy fix for anyone who stumbled on this. Power off your phone, remove the sim card, power up your phone, freeze a service called AutoPreconfig, power down and insert sim, good to go.
More info http://forum.xda-developers.com/gal...ge-service-provider-update-t3425169?nocache=1
Shout out to Wired4Fun for this easy fix.
My PH-1 worked just fine. I did use it for about two months with the official Oreo-beta build. Now, before selling it, I flashed the latest Nougat-build, went through the setup process and installed the latest update. I missed checking for the audio. Now, it seems the audio in calls does not work at all. The caller can not hear the participant and vice versa.
Any suggestions?
/* solution: (thank you WickedDaemon)
Download and flash older NMJ32F Firmware and update from there.
*/
Return to stock and check if u have the same problem.
hypnz said:
Return to stock and check if u have the same problem.
Click to expand...
Click to collapse
Thanks for your reply.
But that is exactly what I did. Nougat = latest stock from https://www.essential.com/developer/current-builds
What u mean i missed checking the audio?
I missed checking if calls work. Now you can call or accept a call, but audio won't work. You don't hear the participant and he doesn't hear you.
Same boat here. Flashed with Essential Stock ROM, and everything seemed fine until someone called me. Anyway, I've been banging on this for a couple days. A few things I've tried:
- Tried the VoIP application for my job. No joy..
- Uninstalled/reinstalled Phone app. No joy.
- Installed some other Phone app from Play. No joy.
- Hangouts Dialer seemed to work for a second, but has all sorts of other issues. No joy.
- Reset all data, restored from Google. No joy.
- Reset all data, setup as new phone. No joy.
- Disable OK Google. No joy.
A new clue; the baby monitor app errors out with something about the microphone being in use. But I'm having trouble figuring out which one is locking the mic. Anyone have a trick for this?
dzendeh said:
My PH-1 worked just fine. I did use it for about two months with the official Oreo-beta build. Now, before selling it, I flashed the latest Nougat-build, went through the setup process and installed the latest update. I missed checking for the audio. Now, it seems the audio in calls does not work at all. The caller can not hear the participant and vice versa.
Any suggestions?
Click to expand...
Click to collapse
It could be a setting in the mobile network for better audio during calls or something like that. Disable that and it will work fine. Happened to me when I went back to stock once.
Turbojugend said:
It could be a setting in the mobile network for better audio during calls or something like that. Disable that and it will work fine. Happened to me when I went back to stock once.
Click to expand...
Click to collapse
Are you referring to 'Enhanced 4G LTE Mode'? I just disabled that and tested. No joy.
Side note: After many reboots, reinstalls, and general button pushing, my VoIP app now has sound but still no mic. I removed Microphone permissions on almost everything and started adding them back one by one. Still no joy.
I think something changed within the firmware during the 8 upgrade, then didn't get reverted back during the 7 downgrade. Is there a particular image or partition that needs to be flashed again?
WickedDaemon said:
Are you referring to 'Enhanced 4G LTE Mode'? I just disabled that and tested. No joy.
Side note: After many reboots, reinstalls, and general button pushing, my VoIP app now has sound but still no mic. I removed Microphone permissions on almost everything and started adding them back one by one. Still no joy.
I think something changed within the firmware during the 8 upgrade, then didn't get reverted back during the 7 downgrade. Is there a particular image or partition that needs to be flashed again?
Click to expand...
Click to collapse
All I do when I switch back and forth is always fastboot -w before I flash and after I flash. May be overkill, but it always works
Older Firmware
dzendeh said:
My PH-1 worked just fine. I did use it for about two months with the official Oreo-beta build. Now, before selling it, I flashed the latest Nougat-build, went through the setup process and installed the latest update. I missed checking for the audio. Now, it seems the audio in calls does not work at all. The caller can not hear the participant and vice versa.
Any suggestions?
Click to expand...
Click to collapse
I've downloaded and flashed the older NMJ32F firmware and it appears to be working. Going to try the OTA update to NMJ51B and see where that goes.
WickedDaemon said:
I've downloaded and flashed the older NMJ32F firmware and it appears to be working. Going to try the OTA update to NMJ51B and see where that goes.
Click to expand...
Click to collapse
OK, I'll give it a try.
WickedDaemon said:
I've downloaded and flashed the older NMJ32F firmware and it appears to be working. Going to try the OTA update to NMJ51B and see where that goes.
Click to expand...
Click to collapse
Aaaand THANK YOU! That worked
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
SashaNT86 said:
Hello all,
I am running the XT1768 variant, Qualcomm version, rooted with Resurrection Remix version 5.8.5 unofficial. I have twrp as my recovery.
Everything was going smoothly until mms blew up. I can't send or receive pictures/files at all.
Here's what I've done so far:
I've checked the apn settings at least a dozen times and they are correct as per my carrier's website.
Tried different messaging apps and the problem persists through all of them.
I've reached out to my carrier and my favorite texting app developers and they have no clue.
I got a momentary reprieve when I force stopped the messaging service and rebooted the phone, but that trick is no longer working somehow. I tried it three times before coming here.
Everything else is working perfectly, including humongous texts. I am so confused right now.
Click to expand...
Click to collapse
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
If that fails try returning to stock to see if the problem persists. Occationally mms dysfunction can be upstream and require carrier involvement.
madbat99 said:
Try a clean install of your rom. Or even a dirty flash first to see if you borked something.
Click to expand...
Click to collapse
A dirty flash seems to have done the trick,though I will say I used a different download for the flash. Loving it so far.
Thank you for the help!
Davey216, I will keep that in mind if it comes back. Stock is kinda icky but I need my mms. Thank you for the reply!