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!
Related
I used a few versions of Lite-ning ROM successfully without problems... on one occasion I unfortunately neglected to put it on USB debugging mode and went ahead and flashed via Odin as normal...
At the time, I started to get force closed in so many applications (stock email was the worst)... I flashed it again correctly but still had lots of them
I have since tried other ROMs which has reduced the frequency but not entirely... as a last resort have now done a full factory wipe/reset followed by using Exynos 3.0 however I still seem to be getting quite a few force closes... it mostly seems to be when filling in a form or typing message etc, if I move the cursor and hit backspace it just force closes which ever app i am in...
How can I resolve this permanently? Do I need to wipe and flash an official firmware version? Would XXKG3 be ok even though its beta? Cheers
Would XXKG3 be ok even though its beta Who says ???
Use recovery wipe cache factory reset wipe Dalvik . Mounts and storage format system data etc .
Use Odin to flash a stock rom should clear up problems .
I never use USB debugging mode with ODIN 500+ flashes .
jje
Thanks for the advice... Lite-ning ROM instructions state to put it in debugging mode, I assumed having skipped that step it might be the cause?
The site I found the offical KG3 firmware on stated it was beta and might be bugs...
Will try what you advise anyway, thanks for your help!
I get "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable" error message consistently even after reboots. Running rooted, with stock ROM. I get multiple FC's which I have to acknowledge before using the phone. Not sure what's happening with my phone. Please help.
what was the last thing you installed before the problem started, it may have damaged the software that is on the phone.
Only thing you might try is doing a factory reset and see if that clears the problem.
sabesh said:
I get "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable" error message consistently even after reboots. Running rooted, with stock ROM. I get multiple FC's which I have to acknowledge before using the phone. Not sure what's happening with my phone. Please help.
Click to expand...
Click to collapse
I would flash another rom tbh ...
This will solve all your problems ..
Don't know why you would want to run stock anyway
Solved: I booted into recovery, then did a data wipe to fix. I then used Titanium Backup to restore everything. All good now. Thx guys!
Probably the cleanest solution HERE
Hi,
I do not have enough posts to post in the cyanogenmod nightlies thread to get a definitive answer, hence why this subforum. I guess my question may be rom independent anyway.
I 'upgraded' from an M release of cyanogenmod to a nightly and buggered my phone. I was forced to flash the stock firmware and then reflash the nightly to fix everything. Except my camera shows a black screen (behind the onscreen focus and options) and force closes nearly all the time. I thought it was just the nightly, but 2 months and 20+ new nightlies later, I still have the issue. In the nightles dev thread, people say the camera is fine. I know the hardware is fine, because 1 in 40 tries the camera randomly works.
I tried a factory wipe, which I now know just wipes user data. So In CWM, under 'mounts and storage' I formatted everything I could and did another factory reset, cache etc. No fix.
I guess this issue is with the rom itself, if the camera is force closing? So I'll have to use Odin or such to flash a stock rom again and flash another cyanogenmod version? But I want to check this is correct before continuing, and how I can completely wipe any trace of the current rom before flashing the stock and another nightly - so I don't get this issue again.
Thanks
So I finally found the issue, after battling with heimdall on ubuntu 14.04 for hours. Its a hardware problem.
I'm just going to leave my experience here in case someone else has the same issue, since anything to do with all the issue I am about to describe don't seem to be documented anywhere on the web clearly.
Firstly, I battled with heimdall 1.3.2 to recognise my phone on ubuntu. I kept getting;
Code:
ERROR: Failed to receive response!
After a number of threads talking about installing usblibx drivers I found one about which libs to install from terminal;
Code:
sudo apt-get install libXXXX
Code:
libusb-ocaml
libdevice-usb-perl
libhpmud0 (not sure if it's essential)
libusb-0.1-4
libusb-1.0-0
libusb-1.0-0-dev
libusb-dev
libusbprog-dev
libusb++-0.1-4c2
libusb++-dev
libusbtc08-1
libusbmuxd-dev
libusbprog0
libusbmuxd1
I installed all but couldn't find libusbmuxd1, restarted anyway, to the same error. I purged heimdall 1.3.2 and instead installed it from the Ubuntu software centre, which using
Code:
sudo apt-cache policy heimdall
showed that I had version 1.4 installed. Then I managed to find
Code:
libusbx-1.0.14_1.0.14-1_amd64.deb
floating somewhere on the internet, which finally installed the proper libusb stuff and allowed heimdall to continue without the error message.
I made a .pit file from my phone. I recommend this first. After hours searching for a stock rom (samsung has removed most of its firmware downloads? and asked links to be removed on other sites!?) came across this site
(I can't post links as a new user) - google [TUTORIAL] Flashing i9000, i9100 or i9300 with Heimdall
Which explains how to flash using heimdall. After a successful flash, my phone didn't get farther than the boot animation. I booted into stock recovery with vol up-home-power to factory reset, but noticed a dead droid and red writting. Rather than continue, I wanted to fix this, so I followed the tutorial again, but this time checked repartition under the pit path, and hoped for the best. The phone stalled at the boot anim again, but this time in recovery, all was good.
I did a data wipe / factory reset, cache wipe etc, but nothing. So I stuck the stock rom zip onto the micro sd and installed it from recovery, factory reset, and rebooted. (which is odd, having to install the rom from recovery - because doesn't that kinda defeat the point of using the same image on heimdall in the first place?!?)
The phone booted! So after all that, (Having data/factory reset, wiped the cache, (wiped the dalvik cache when i had CWM before and formatted all I could in mounts and storage) flashed the stock ROM AND repartitioned the phone) i thought that would eliminate any software issues. I thought the camera would work.
Nope.
As usual, the front camera worked, but the back, now, after a pause would give the samsung error:
Code:
unknown error by errorcallback
Now, after googling this (Cyanogenmod gave a different error with no related answers on google) and being annoyed at my time lost, I took the tongue and cheek advice from some random forum commenter, to tap the camera hard.
It worked.
Apparently, the entire time the camera was suffering from a hardware issue. Something about a 'sticky shutter'. Anyways, i'm going to leave the stock ROM and take it into a shop to get it fixed. Just leaving this trail of breadcrumbs in the hope it helps someone else.
Perhaps this could be marked as 'solved'.
Same problem
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
JCNouel said:
FINALLY; first time I see the problem I have (I'm not feeling good about you having the problem, btw). I've had this problem for a lot of time and I haven't had found it elsewhere.
I have the same issue, but without the error that says "unknown error by errorcallback". Mine just says "Unfortunately, Camera has stopped working". I didn't really understand if it had appeared to you after you did all that, or if it was from the beginning... anyways, just "tapping hard" the camera will make it work? And, did it fix it permanently?
Sorry for any typo.
Edit: I've "tapped" the camera really hard, and no signs of anything. Any advice? (I've done practically everything you have done but flashing the stock rom)
Click to expand...
Click to collapse
Try flashing stock rom and see if this fixes your problem.
gsstudios said:
Try flashing stock rom and see if this fixes your problem.
Click to expand...
Click to collapse
It fixed it, but then I flashed back the AICP ROM, which is KK, and it malfunctioned again. I'm going to try with a JB Custom ROM.
Update: I flashed a JB Custom Rom (Fusion Rom) and it's working good so far.
I'm helping a friend with her S3 i9300. It was running very sluggishly and starting in the last couple months she's been having a sleep of death issue.
It works fine (albeit slowly) while she's using it but when it sleeps for more than 10 minutes it doesn't turn back on without a lot of trouble or a holding down the power button and hard resetting. Every once in a while it only boots if I go indirectly through download mode.
I've confirmed with the play store app that she does NOT have the "insane chip" involved in the SDS issue. I've also factory resetted, rooted, tried flashing a custom kernel, a custom TW ROM (S5 sensation) and now an AOSP ROM (resurrection remix) and the problem persists.
Looking at other users' suggestions I took it apart and cleaned/played with the power button, even replacing it with the one from my old t999. Still the same.
I'm at a loss at this point. Has anyone run into this issue and found a fix I'm missing? Thanks for the help.
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
TENN3R said:
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
Click to expand...
Click to collapse
Thanks for the reply. Before flashing any ROMs I've always made sure to do a factory reset and then individually wipe System, Data, Cache, and Davlik Cache even though I know I'm duplicating some of the wiping. Unfortunately that did not work in this case.
I'll give the MEGA/SUPER wipe a try and report back.
Thanks again.
Looks like MEGA wipe didn't do the trick either. The phone is on NA8; is there a newer baseband I can try? Not sure what else to try.
At this point I'm thinking it might just be a hardware issue.
Flash the latest stock firmware from sammobile then factory reset, remove sd card and sim then test with a different battery.
If still the same then it is a hardware fault, motherboard/cpu.
Hey guys
I need some guru help here :/
I've flashed cyanogenmod 13 with android 6.0.1 on my i9300 along with some gapps (stock version). Everything works well, besides the cell reception.
I've been able to see other networks around but couldn't connect to neither of them. (i'm on roaming, in germany, while my sim card and the phone are from poland)
I have applied no signal fix from here which didn't change anything.
Then I've flashed this (the one with "Poland" next to it), but that only made things worse, as the whole "cellular network" menu in settings is greyed out.
What I've figured out is that when typing *#06# the phone app makes some noise and hangs, and in the settings there is no IMEI number.
This leads me to the conclusion that EFS (seems empty in the TWRP file browser) is broken/cleared.
I've seen many instructions on bringing it back to life, non of them are clear to me, and all use Windows. Is there a way to do that on Mac OS, or.. basically is it THE way to go for?
I would appreciate all the help as I need that phone in the next days :/ thanks!
@krecio4:
1. Look for efs-backup. Some kernels create this. Or as part of TWRP-backup. Restore it.
2. Flash latest firmware with Odin. If IMEI is still gone afterwards, try KIES repair function.
3. Let it repair in service center.
rp158 said:
@krecio4:
1. Look for efs-backup. Some kernels create this. Or as part of TWRP-backup. Restore it.
2. Flash latest firmware with Odin. If IMEI is still gone afterwards, try KIES repair function.
3. Let it repair in service center.
Click to expand...
Click to collapse
thanks a lot @rp158!
I've tried searching for an efs backup but no luck :/ any idea where do they create it? restore option only has those files that I've backed up.
latest firmware you mean the official one, right? Is there a way to do it on mac os?
cheers
@krecio4: TWRP backup contains efs-partition, if you chose/ticked it. Kernels (Boeffla, Agni) store it in sdcard0, but if you never flashed a special kernel, it's over.
Firmware means Samsung's stock 4.3 from sammobile.com. Look there, if they offer Odin and KIES for Mac. Otherwise lean a Windows pc. It's useless to make it more complicated by struggling software.
@krecio4: read this. That's not the solution, but if that all caused by actual CM13-nightly, there comes perhaps any...
I have the same problem with latest nightly. This work fine: "cm-13.0-20160523-NIGHTLY-i9300.zip".
@krecio4 I think that you have to first flash latest firmware then root your phone and then you have to use z3x box, hope it will fix :good:
thanks for your sugestions guys
What I did is to get the latest firmware from sammobile, restored it with Odin, phone was working, I was receiving calls and texts.
So I installed TWRP, backed up EFS, System, Data, and one more thing that was marked.
Then i did a factory reset and installed latest CM13 + gapps in one run (as a batch of files, selected the CM13 first, than the gapps in the que)
rebooted
Again - CM13 works well, but it says "please insert SIM card" :/
No IMEI, IMEI SV (Unknown)
Cellular networks in settings are off, and greyed out inside, "preferred network type" is "Invalid Network Mode (-1). Ignore"
Do you think there is any hope?
I noticed that EFS is empty, after restoring it from backup, and rebooting, it's empty again.
so tired of everything, I went back to the original software using this method (even easier than Odin) http://forum.xda-developers.com/galaxy-s3/general/how-to-factory-installed-firmware-sgs3-t1838480
If you come up with some solution, I'd love to try Cynanogenmod for longer and.. for real
1. Be happy, that your efs-data are ok. Make in TWRP a backup of this partition only, for worst cases.
2. Try @mexit's advice.
Can I with no problem have a custom recovery installed while using original firmware?
So you are saying that it might be with the last 3 nightlies that they are messing up with backed up EFS? If so, I'll try installing the one you've mentioned, but now I've list 2-3 days for the whole crap so I will wait until I have too much time But thank you very much for your support!
BTW, I found this as well: http://forum.xda-developers.com/galaxy-s3/general/tool-backup-restore-efs-imei-sgsiii-t1901098
Posting for anybody, as I digged the whole internet for any answers
Install this: https://download.cyanogenmod.org/get/jenkins/162926/cm-13.0-20160524-NIGHTLY-i9300.zip
http://forum.xda-developers.com/showpost.php?p=67034195&postcount=5968
Click to expand...
Click to collapse
ok, as I don't give up easily, as you can see, I did another approach. Backup, backp EFS only.
Installed the edition from 23rd of mai. All good! But during the "installing apps" during the initial boot, close to the end, the battery died (after the screen flickering). but reboot and it all seems to work well Any issues that could appear after an unexpected reboot during the first boot? Do you suggest to do factory reset and flash CM13 + gapps again?
If I understand well, battery died during compiling Dalvik/ART. Should be happen again after cleaning both caches. But to avoid any mess, I would clean flash the ROM again.
So you suggest to do the factory reset, install CM13, install gapps, reboot ?
No.
Wipe system, data, cache, Dalvik cache.
Flash CM13. Wipe cache, Dalvik cache.
and gapps installation shouold be along the CM13 in a que right?
@krecio4: flash GApps afterwards. Read the last posts of CM-thread: your problem was probably caused by a modem-bug in CM, should be gone now.
after the wipe cache & Dalvik?
so CM13, wipe, gapps, reboot?
Ok, very precisely:
flash cm13, wipe 2 cashes, reboot
if net and wifi ok, make a backup of this state
flash GApps, wipe 2 cashes, reboot
case closed