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
Related
im on stock dxlp7 via kies. last time it was working was when i switch on the wifi and got stuck (known issue). because i can't wait, i rebooted it by holding the power button and use feature there.
during boot-up, i saw the upgrading OS as if it was a new upgrade to 4.0.3. then there all apps started to force close. only few apps work and mostly are those that come preinstalled.
im doing backup as of this writing and saw one thread that wiping the cache fixes it. i hope wiping the cache really fixes this. created thread because the other was was on 2.3.x. this one is on ICS.
what went wrong with my phone? is this a known issue? i can't find that much info on this.
Do a factory reset.
i first tried to wipe the cache. didn't work.
i did factory reset so far its working fine. no other apps yet except preinstalled.
what went wrong there?
Honestly, that's really hard to say. Something has obviously corrupted some system apps/files by the sound of what you're describing.
Important thing is you seem to have fixed it. See how you go as you start reinstalling your apps.
Flash05 said:
i first tried to wipe the cache. didn't work.
i did factory reset so far its working fine. no other apps yet except preinstalled.
what went wrong there?
Click to expand...
Click to collapse
so far nothing weird happening. installing the apps is ok. configuring one by one sucks.
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 are many forums addressing this problem but mines is a bit different, I know the common solution is App Info > Clear Data but this doesn't help. Neither does a force stop, reset or a clearing of settings cache.
I resolved to needing to do a data wipe, however I received this message, "failed to stat /data/date/com.android.defcontainer/cache" and nothing wiped. I started the phone to the exact same home screen and apps, but I had lost wifi settings and such, and can't open settings to set up wifi yet again.
I contemplated reflashing CM through the installer but wasn't sure if the failed to stat problem would interfere and potentially brick.
Any help would be much appreciated, cheers.
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
boomboomer said:
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
Click to expand...
Click to collapse
I read online that downgrading from 4.4 (CM) to Stock 4.3 would hard brick the device, is there any merit to this?
No, if you use the right firmware and do it properly there is no more risk than with a normal flash.
Problems with all roms SM-T210
Hi!
This problem is driving me crazy!
I have a similar problem!
I have Samsung Galaxy Tab SM-T210
For a long time I used RocketTab rom. I decided to try out new Android 4.4.2 Rom.
I started to get an error "Unfortunately settings has stopped" when I tried to open settings. I also got another application errors.
Now, it does not matter what rom I install, i get application has stopped error.
Even the RocketTab rom.
I flashed original stock rom via Odin, same problem.
I tried CWM and TWRP recovery.
I wiped dalvik cache, system, cache, Data, internal storage.
After flashing a new rom via odin or recovery, same problem.
I don't understand how it's possible that after deleting everything, I still get the same error.
Sometimes when I open settings, instead of getting an error, tablet restarts.
Tablet was 100% working before flashing Android 4.2.2
Any ideas?
Thanks guys
Why are you asking in the i9300 forum?
boomboomer said:
Why are you asking in the i9300 forum?
Click to expand...
Click to collapse
Because the problem seems to be very similar.
Point taken!
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
gilbnx said:
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
Click to expand...
Click to collapse
This happened to me. I had to do a factory reset.
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
elesbb said:
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
Click to expand...
Click to collapse
Thanks elesbb, I saw your message just now but I have my phone working already since few hours ago after a 2nd stock reflashing. If I have the same issues as before - I will use chainfire's update SU.
What I did find is that once I enable accessibility (to apps like Tasker, and an LG bluetooth headphone I have (so it could announce notifications) the phone becomes unstable; it just went through 2 boot loops but eventually recovered... Hopefully it will stay stable.
Gil.
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!