My mom has my old Verizon V10. Since hers updated to VS99023A, her camera force closes. Tried wiping app data, system cache, etc and still not working. Also tried 3rd party cameras.
Before I back it up and factory reset, I was wondering if there is a way to download the OTA file and manually reflash it to see if that will fix it? Not rooted
I figured it out... can download the Verizon LG software update (either from the phone or LG's site) and it will refresh the phone.
I did that but it didn't fix my situation so the phone was returned to Verizon under warranty.
Related
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
botzen67 said:
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
Click to expand...
Click to collapse
If you have Titaniumbackup Pro then just freeze the update/updater apk. If not, I would suggest getting it, it is well worth the cost.
Great suggestion. I have TiBu Pro and have frozen the two Update apps I found in the list along with "VZW Package Installer 1.0" and "Field Test 2.1-update1" and "Field Trial 2.2.1", having done the last three just now. It did try to do yet another update a few hours ago, so we'll have to see if the last three do the trick.
Anybody got any other suggestions for Apps I should freeze to prevent OTA updates?
Update: None of the items I've frozen seems to have made a difference. Still looking for other ideas.
I'm thinking it was DM.apk or something similiar that controlled ota updates. I don't have a stock rom running atm so i can't be sure. When you find the correct one you won't be able to get to the update phone screen from settings any longer. Wish i could be more help but i just can't remember.
Sent from my HTC ThunderBolt using Tapatalk
I was having that same problem and I just broke down and applied the update. I used clockwork rom manager and a rooted/deodexed update file that I found on the forums (linked from androidpolice, i think). Flashed the update, without wiping the current setup, then flashed the radio from the bootloader. Worked like a charm. I've got the update, it's not searching for more, and it reinstalled all the bloatware that I deleted instead of freezing when I got the phone. I went back through and freezed all the bloat junk, and my TB is running better than ever. Oh, and I'm just running a rooted stock rom.
I too suffered the same problem. I just ended up installing a custom rom to get rid of it for good. Best decision I ever made, I really like the Synergy build.
Ok I just got my S3, straight out of the box I booted into odin and successfully followed these instructions to get root http://forum.xda-developers.com/showthread.php?t=1756885 rebooted and started setting up my phone. It automatically started restoring all my apps then I went on and used titanium to restore my k9 mail and a few other apps (no system data or sms app data or anything like that). After I rebooted a messaged appeared " Unfortunately, Messaging has stopped" cleared the cache, fixed permissions, cleared cache and data of the messaging app. Nothing worked. Reset factory. As soon as the phone booted to the setup screen the messaging app error was already there. Back to Odin and reloaded the rooted tar file (I'm using the full stock, rooted version) and I still get the error when I turn the phone on! How can that be?
Exact same problem
jasondhsd said:
Ok I just got my S3, straight out of the box I booted into odin and successfully followed these instructions to get root http://forum.xda-developers.com/showthread.php?t=1756885 rebooted and started setting up my phone. It automatically started restoring all my apps then I went on and used titanium to restore my k9 mail and a few other apps (no system data or sms app data or anything like that). After I rebooted a messaged appeared " Unfortunately, Messaging has stopped" cleared the cache, fixed permissions, cleared cache and data of the messaging app. Nothing worked. Reset factory. As soon as the phone booted to the setup screen the messaging app error was already there. Back to Odin and reloaded the rooted tar file (I'm using the full stock, rooted version) and I still get the error when I turn the phone on! How can that be?
Click to expand...
Click to collapse
My SIII is doing the exact same thing. Verizon 32 gb rooted stock I am returning and they are shipping me a new one on the 14 day no worry guarantee.
Mine SIII also get a busy signal when trying to make a call an phone wont call out or receive calls I am reading where this is happening to a lot of them.
TheSurgeon said:
My SIII is doing the exact same thing. Verizon 32 gb rooted stock I am returning and they are shipping me a new one on the 14 day no worry guarantee.
Mine SIII also get a busy signal when trying to make a call an phone wont call out or receive calls I am reading where this is happening to a lot of them.
Click to expand...
Click to collapse
Hi I found another thread that had a solution, didn't think it would work but it did. I can't find the thread or I'd give him credit.
Basically, boot into odin and flash this (verizon stock unrooted) h**p://samsung-updates.com/get/2114/Samsung_Firmware_SCH-I535_VZW_I535VRALF2_Android_4_0_4.html after its done let it boot and then restart and go back into odin and reflash the rooted image. It's odd but it worked and all my apps and data remained(but backup just in case).
Factory reset guys. You are writing system files over existing system files. Factory reset. Factory reset. Factory reset
Sent from my SCH-I535 using xda app-developers app
das7982 said:
Factory reset guys. You are writing system files over existing system files. Factory reset. Factory reset. Factory reset
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Factory reset didn't work, first thing I tried...did it twice, nor did reflashing the rooted image, fixing permissions, clearing caches, etc. After the factory reset and reloading the rooted image, the error would appear on the language selection screen when first being setup. Reloading the stock non-rooted image and then reflashing the rooted image was the only thing that fixed it.
jasondhsd said:
Hi I found another thread that had a solution, didn't think it would work but it did. I can't find the thread or I'd give him credit.
Basically, boot into odin and flash this (verizon stock unrooted) h**p://samsung-updates.com/get/2114/Samsung_Firmware_SCH-I535_VZW_I535VRALF2_Android_4_0_4.html after its done let it boot and then restart and go back into odin and reflash the rooted image. It's odd but it worked and all my apps and data remained(but backup just in case).
Click to expand...
Click to collapse
Your my hero! This worked perfect. Now everything is as I want it. Once you validate you should make a new topic in development with the subject being the error message and Samsung Galaxy SIII this way all the people with this problem can easily impliment the solution.
Also you were correct. None of my data was lost.
:good::good:
I know there have been a lot of issues for those attempting to pull an update.zip and the entire file becoming corrupted.
I would venture a guess that this is some type of "security" attempt either from Google or Samsung to stop those from doing so.
(Lollipop brings added security features like an activation lock)
I attempted to pull this zip myself and that data was corrupted. But wait! There's more.
Not sure if anyone else has experienced this.
I cleared the cache upon updating to the new software. No issues
Used CF Auto Root to root my device and worked fine. Albiet with normal bugs.
Cleared cache in recovery and device crashed upon booting up.
Hard reset and cleared all and device works fine.
Now to test I cleared the cache after reinstalling NK4, and downloaded the update again.
Cleared cache and everything was fine.
Rooted phone via CF AutoRoot again. Phone working fine.
Cleared cache... Same exact issue again.
So... anyone else see the same issue? Or have any insight on the added security issues.
(I fix phones at said carrier. Internal memo warned us of security issue with activation lock from Google.)
supercholo said:
I know there have been a lot of issues for those attempting to pull an update.zip and the entire file becoming corrupted.
I would venture a guess that this is some type of "security" attempt either from Google or Samsung to stop those from doing so.
(Lollipop brings added security features like an activation lock)
I attempted to pull this zip myself and that data was corrupted. But wait! There's more.
Not sure if anyone else has experienced this.
I cleared the cache upon updating to the new software. No issues
Used CF Auto Root to root my device and worked fine. Albiet with normal bugs.
Cleared cache in recovery and device crashed upon booting up.
Hard reset and cleared all and device works fine.
Now to test I cleared the cache after reinstalling NK4, and downloaded the update again.
Cleared cache and everything was fine.
Rooted phone via CF AutoRoot again. Phone working fine.
Cleared cache... Same exact issue again.
So... anyone else see the same issue? Or have any insight on the added security issues.
(I fix phones at said carrier. Internal memo warned us of security issue with activation lock from Google.)
Click to expand...
Click to collapse
Instead of using cf, just odin twrp and flash supersu. No problems going that route.
Sent from my SM-N900P using XDA Free mobile app
Definitely a good way to go. I only wonder if the added security in Lollipop is causing a lot of these issues.
Sent from my SM-N900P using XDA Free mobile app
I updated my T-Mobile Note-8 to Oreo (CRC2) via OTA update. Ever since my "camera keeps stopping" after taking a pic.. Anybody else here with similar experience?
Things I already tried:
1. Cleared system cache, did NOT work.
2. Cleared camera app cache/data, did NOT work.
3. Cleared gallery app cache/data, did NOT work.
4. Changed to internal/phone memory storage (in the camera settings), did NOT work.
5. Tried safe mode & camera still crashed, did NOT work.
Quick google search says many other people are facing this issue (different devices). I'm surprised there is NO posts here asking about this...
My only option at this point is to do a complete factory reset. But I hate doing that because of all the setup steps involved in making it behave correctly (as I like it).
Any help appreciated.
maxie.maverick said:
I updated my T-Mobile Note-8 to Oreo (CRC2) via OTA update. Ever since my "camera keeps stopping" after taking a pic.. Anybody else here with similar experience?
Things I already tried:
1. Cleared system cache, did NOT work.
2. Cleared camera app cache/data, did NOT work.
3. Cleared gallery app cache/data, did NOT work.
4. Changed to internal/phone memory storage (in the camera settings), did NOT work.
5. Tried safe mode & camera still crashed, did NOT work.
Quick google search says many other people are facing this issue (different devices). I'm surprised there is NO posts here asking about this...
My only option at this point is to do a complete factory reset. But I hate doing that because of all the setup steps involved in making it behave correctly (as I like it).
Any help appreciated.
Click to expand...
Click to collapse
I had Samsung Experience Home keep FCing on me. Had to do a reset. Sucked. 1 other thing you might want to try is to go into Recovery mode and clear the cache there...and see if it helps you. (didn't work for me).
SiNJiN76 said:
I had Samsung Experience Home keep FCing on me. Had to do a reset. Sucked. 1 other thing you might want to try is to go into Recovery mode and clear the cache there...and see if it helps you. (didn't work for me).
Click to expand...
Click to collapse
Yeah, that's what I did in step 1. Didn't make any difference, camera still crashes...
I guess factory reset and setting up the device from scratch is my only option at this point.
Can anyone please post a working version of the stock Samsung Camera APK that works on Oreo (CRC2)?
Help appreciated... Thanks
maxie.maverick said:
I updated my T-Mobile Note-8 to Oreo (CRC2) via OTA update. Ever since my "camera keeps stopping" after taking a pic.. Anybody else here with similar experience?
Things I already tried:
1. Cleared system cache, did NOT work.
2. Cleared camera app cache/data, did NOT work.
3. Cleared gallery app cache/data, did NOT work.
4. Changed to internal/phone memory storage (in the camera settings), did NOT work.
5. Tried safe mode & camera still crashed, did NOT work.
Quick google search says many other people are facing this issue (different devices). I'm surprised there is NO posts here asking about this...
My only option at this point is to do a complete factory reset. But I hate doing that because of all the setup steps involved in making it behave correctly (as I like it).
Any help appreciated.
Click to expand...
Click to collapse
From JaguarXT inn another thread. Maybe this is why:
" Just be aware that there are problems with the current Oreo version for the Note 8. That is the reason why T-Mobile stopped sending out that version of Oreo Android to Note 8 devices right now. The last I heard of is that Samsung went to Google for help on the problems. So both Google and Samsung engineers are working on this.
You might want to wait until they send a version of Oreo Android for Note 8 that has the problems fixed."
I took the Oreo update the day it was pushed. I immediately factory reset and everything, including the camera, works perfectly. For the other Note 8 variants that recieved Oreo, and had problems; a factory reset fixed 99.9% of the issues.
rile1564 said:
I took the Oreo update the day it was pushed. I immediately factory reset and everything, including the camera, works perfectly. For the other Note 8 variants that recieved Oreo, and had problems; a factory reset fixed 99.9% of the issues.
Click to expand...
Click to collapse
Factory Data Reset is where my problems began. That end up Samsung telling this information and wanting to flash me back to Nugget until they fix this issue.
I was on OTA CRC2 Samsung stock Oreo.
rile1564 said:
I took the Oreo update the day it was pushed. I immediately factory reset and everything, including the camera, works perfectly. For the other Note 8 variants that recieved Oreo, and had problems; a factory reset fixed 99.9% of the issues.
Click to expand...
Click to collapse
Yeah, I had to factory reset as well... I used SmartSwitch to backup the phone on to my external SD card and then factory reset, wiped clean & installed CRC2 using Odin and then restored using Smart Switch app.
It sucked to do things all over again, but the phone seems reasonably behaved again!
I was on the beta on S906U. It upgraded today to the release OTA. S906USQU2BVJA is my version. Amazon Shopping, Gmail, Virgin Pulse (used for work fitness stuff) and Lose It Calorie counter all instantly close when I try to use them.
Any ideas on troubleshooting? Clearing cache, Clearing data and reinstalling the apps didn't change a thing. Tried play services, but it's up to date.
Samsung says to hit a repair center and re-flash the phone in a downgrade.
Clean install my friend
butchieboy said:
Clean install my friend
Click to expand...
Click to collapse
Just Factory Data Reset? Should I try a backup using SmartSwitch and restore or would you advise against that?
I never use Smartswitch, some do. Others use other backup methods. I just move what I want to external storage. I don't care about app data and choose to factory reset for best results. When I restored app data once I got official Android 13 Ota, things just didn't run smoothly. Some apps would freeze. For me and this is my preference, a clean install is always best
There is no need to go to a repair center
Factory reset and things appear to be normal. Lesson learned: Just do the reset and don't call Samsung support. They're relatively useless.
Anybody has had success flashing TMO files on AT&T 906U? Is the available firmware a Multi CSC firmware?
gamerchris360 said:
I was on the beta on S906U. It upgraded today to the release OTA. S906USQU2BVJA is my version. Amazon Shopping, Gmail, Virgin Pulse (used for work fitness stuff) and Lose It Calorie counter all instantly close when I try to use them.
Any ideas on troubleshooting? Clearing cache, Clearing data and reinstalling the apps didn't change a thing. Tried play services, but it's up to date.
Samsung says to hit a repair center and re-flash the phone in a downgrade.
Click to expand...
Click to collapse
Did you try factory reset ?