This is my first post on this forum and I am nowhere near as tech savvy as most people on here, so I apologise in advance if anything I post sounds daft or if I have broken any forum rules which I have tried to follow.
I have a Galaxy S2 GT-I9100 which was on Android 4.1.2 and which I am trying to flash to Kitkat with limited success using Slim Sabre.
If I unzip Slim Sabre by itself the phone "works" - I can make calls use internet, text etc, but when I install gapps all I get is messages stating "the android process (name of process) has stopped" - the processes include keyboard, location, calendar and a couple of others. I've tried flashing different versions of gapps, as well as Slimkat but keep getting the same thing.
I would really appreciate it if someone can point me in the right direction as to what I need to do to get kitkat working on my phone.
Again, my apologies if I have forgotten to include information or breached any rules, and thanks in anticipation for any assistance.
The following is currently what I have on "about phone"
Android version: 4.4.2
Kernel version: 3.0.80+ [email protected] #1
Slim version: Slim-4.2.2.build.5-OFFICIAL-4068
Build number : slim_i9100-userdebug 4.4.2 KVT49L 4068 test-keys
Update
Just to update, after switching my phone off and on again, the only message now appearing is "android keyboard (AOSP) has stopped". I am not getting any of the other messages for some reason.
I've tried clearing data from Keyboard app as well as dictionary and also tried clearing the cache on both. The cache for the dictionary was at 12 kb and when I pressed the clear cache button nothing happened (though I did get haptic feedback so I know it was pressed).
I've also tried installing LatinIME.APK but it fails to install (I have allowed unknown sources).
Also tried fixin permissions.
I would really appeciate any help and guidance on this - I am very new to all this flashing and rom business as you might guess!
Many thanks
rk001 said:
Just to update, after switching my phone off and on again, the only message now appearing is "android keyboard (AOSP) has stopped". I am not getting any of the other messages for some reason.
I've tried clearing data from Keyboard app as well as dictionary and also tried clearing the cache on both. The cache for the dictionary was at 12 kb and when I pressed the clear cache button nothing happened (though I did get haptic feedback so I know it was pressed).
I've also tried installing LatinIME.APK but it fails to install (I have allowed unknown sources).
Also tried fixin permissions.
I would really appeciate any help and guidance on this - I am very new to all this flashing and rom business as you might guess!
Many thanks
Click to expand...
Click to collapse
Reboot to recovery and then Simply reflash the rom zip file once again without any wipe and see
Thanks for responding. Ive done as you said but still get the same thing.
Boot into recovery - wipe/factory reset.
Still no joy. Ive read that another cause is flashing the wrong version of android. Does the info ive put in my first post suggest this?
Really do appreciate the help being provided.
Just tried iWnn IME but get the same problem if that sheds any light
Umm... Gone quiet on here! Will it be worthwhile trying a new rom, kernel etc and see if that works or is the problem indicative that nothing will work?
Turns out I was using wrong version of gapps. Got the correct one now and all seems to be running OK. However Play is now telling me that Candy Crush is not compatible with my device but it was before. Any ideas what that is all about? I need it to keep me sane at work!!
Related
I get this message when I boot up.
I cannot access settings so I cannot perform a factory reset.
Is there any way to factory reset when you cannot access "Settings" because of constant force closes.
I am running stock but with lots of side-loaded apps.
I can access the file explorer. That is the only thing I can open that will remain open even though I get constant force close popups like "android.process.acore has stopped... android.process.media has stopped unexpectedly...
Is my gtab toast? Can it be saved or should I return it?
I get this all the time, with all the mods I do. Don't worry, your system is fixable.
For me, I use clockworkmod recovery .08. There's a "fix permissions" option and this always fixes the problem for me. It also allows a data wipe within recovery.
If you are 100% stock, you could try one of the stock ROM's here as well - that might get you working. You have a few options, here. Check out the FAQ in my signature. I'm actually posting up the new stock update that I pulled from TnT, today.
EDIT: Direct link the the stock ROM updates -- http://forum.xda-developers.com/showthread.php?t=842000. You'd need to understand how to actually run these, which I mention in the FAQ section.
thx Roebeet, I was able to update to the new stock rom.
But I still have the same problem. Is there any other way to wipe my data. Can it be done while connected by usb or do i have to root it?
Is there any hardware button method to do a factory reset?
I still cannot open settings... it gets canceled by the force closes.
I am ready to give upon my G-Tab which I was enjoying so much.
Does anyone know how to wipe the date if you cannot open settings???
Try clockworkmod - it really is a great tool. You can find it in the Tnt Lite dev section as I have a link for .08.
For UID issues, "fix permissions" will correct it. And you can wipe data via clockworkmod as well. You can even remove it by flashing back to stock -- the latest stock firmware works as I've done it myself, the other day.
Btw, there are so many threads here that I sometimes miss replying. I dont ignore, I just might miss a post. Always feel free to PM me if you have a question.
I had a similar issue where something got corrupted in my user data and I was completely unable to start the settings or open the keyboard. I had to flash back to the full vanilla ROM because it contained clockworkmod, which was the only option available to accomplish a factory reset. That wasn't a fun day.
Think I figured out a key reason for sudden UID issues
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Again, the Tap UI team and who hired them and approved it on the Gtablet should be fired, rehired for a minute and then fired for good. Word.
This sounds kind of "preachy," but don't give up.
There is a learning curve to the G-Tablet, and it takes a good bit of reading on this site and assimilating the info.
I will testify that I had a hugely bad malfunction and and even worse fix on my tablet.
Using suggestions from helpful folk -- and carefully researching what I needed to do -- I was able to get my tablet back working just fine. To be sure, it's not stock any more!!! But I actually believe that with all I learned about flashing, mods, etc., I now could go back and make it stock again if I wanted to.
Don't give up. Just keep reading and researching the learning.
Rev
rushless said:
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Click to expand...
Click to collapse
Not true for me, I installed the new Gmail from the Market with no problems. I am on TNTLite 2.2.1.
Google Voice has always been a hack for a tablet, since it is not actually phone. You might want to pull it out and see if your issues are solved.
I am back up and running thanks to clockwordmod. Thanks again!
ninjaprofessor said:
I am back up and running thanks to clockwordmod. Thanks again!
Click to expand...
Click to collapse
Good to hear and thanks for the update!
I am currently having this problem. I am hoping to sell my 10" Android 2.2 Tablet PC on Craigslist... I need to fix this Error... I've only used it 10 times to play Angry Birds. The forum with the links I am confused as to what one to use... I am younger I must say. I am not a 21 year old "computer whiz"/.NET/OS maker... I do make websites. Besides that... I do not know how to "Wipe my system partition" as my Error message says to. Especially due to the fact I cannot open Settings. PLEASE HELP. I may have repeated things said above in his problems but I would like a "NOOB" walk through... (Because I am one). Please help. Thanks in advance. -Sophomoric
Hey, I had a same after my phone battery was empty and it turned off. I kept it off and recharged it, then I had the feeling "I'm feeling Lucky" -.-' so nice from google. xD
Had to wipe everything then full reinstall... such a pain.
Probably the cleanest solution HERE
Hey everyone,
I need serious help, I've been trying to fix this problem for a couple of days but I have had no luck at all. I have searched the X10 forum for countless hours but haven't found any solid solution. I realize that many people are having problems with the 2.1 market and I tried following the advices on those forums but none of them worked.
When I try to download something from the market, it would take forever to download and the process would add to the queue on the notification bar (see screenshot). Every time I access the market, it adds another process to the notification bar. Now I'm up to 50 ongoing process, and I have no idea why it's doing this.
So far, I've tried clearing the data and cache on the market, flashing the phone to a newer firmware (now I'm on Build number: 2.1.B.0.1, Baseband: 2.1.67), factory resetting the phone, opening Google Talk (some how its suppose to work) and even uninstalling the market from phone. The funny thing is even when the market is uninstalled, the downloading process still shows on the notification bar. I'm a noob when it comes to programming but I don't think the problem is from the market itself cuz even when I factory reset my phone and uninstalled the market, the process is still ongoing and displays on the notification bar.
Does anyone know how I can fix this? Maybe I'm suppose to delete a file or kill a command or something? Any help is greatly appreciated, I'm really desperate to get my X10 fixed. Everything works perfectly besides the market so I can't download or update any of my existing apps. Thanks in advance!
Find a new vending.zip and install with recovery. Have seen it posted plenty on the forums.
Sent from my X10i using XDA App
I've tried wiping the cache on the market and installing a new market via Root Explorer and the market still doesn't work. I can't find vending.zip anywhere so I can't flash my phone, any idea where i can find the vending.zip??
Try this through recovery
http://db.tt/sZkKRMo
Sent from my X10i using XDA App
I tried flashing the NewMarket.zip through XRecovery 0.3 and it didn't work either it uninstalled my existing market and I can't install the market through Root Explorer either. It says "There is a problem parsing the package". Do I need a newer version of XRecovery?
I installed that version through recovery v.03 .
Sorry cant be of more help.
Which rom r u running
Sent from my X10i using XDA App
I'm running EWJET LauncherProEx V001ex ROM but when I flashed to the generic 2.1.B.0.1, the market still doesn't work. I'm thinking of flashing it back to 1.6 then to 2.1 again? Thanks for the help so far, really appreciate it but I seem to have no luck with this at all
Have u tried to format everything, and install the rom once again over the existing rom?
Yep, I've factory reset the phone, reset through XRecovery before installing the new ROM and the market still won't work
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 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!
I have been flashing the nightly CM12 ROMS and am very pleased overall, apart from one issue. Sometimes on startup I see the message "Android is upgrading...starting apps". This message displays just before the lock screen appears. I have tried the following to solve the problem, all to no avail:
* Full wipe using CWM Recovery and TWRP (inc. data, system, caches etc)
* Removing apps one by one
*Wiping cache and dalvik cache
* Fix permissions
I even flashed back to CM11, all OK. The problem is not present on this ROM. Therefore, could it just be an issue with CM12? After all, the ROM is still in the early stages of development.
I know it's not a major problem, but I would like to solve the issue if possible. Any help would be appreciated.
its not an issue its just verbose output showing up telling what its doing
If you are familiar with android since its beginning you might have seen this quite a few times. Otherwise get use to it
Many thanks for the reply. So, no need to worry? Do you see it often on your Z Ultra? And why is this happening randomly on reboot and not everytime? Thanks again.
pretty pixel said:
Many thanks for the reply. So, no need to worry? Do you see it often on your Z Ultra? And why is this happening randomly on reboot and not everytime? Thanks again.
Click to expand...
Click to collapse
nothing to worry about, it happens now and then...for example if you moved an app to system directory or installed something which uses a lot of storage
Thank you again for your advice