Hi all,
I just flashed: update-cm-7-20120226-NIGHTLY-galaxys2att-signed.zip. I seem to be having some issues with the com.android.systemui not working. I get an error message on startup saying that "the application Status Bar" has stopped.
My previous mod before applying this one was the cm7 nightly.
Anyone else having similar issues with update-cm-7-20120226-NIGHTLY-galaxys2att-signed.zip ?
i don't used mui but i think you flash rom other, because this rom not complete
Try a clean install, do a factory reset in CWM and reflash the rom. Should solve the problem.
Still same issue even with clean install.
Yes, I am too. I'm going to try replacing the systemUI.apk with a different build version and see if it does anything. I'll post an edit if it works, and the steps to do so.
EDIT: Nope, it didn't work. I'm still having the com.android.systemui crashes for the status bar.
Related
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Foster Basic said:
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Click to expand...
Click to collapse
Hi,
Managed to solve this issue by reinstalling the previous gapps and then reinstalling the firmware. Hope this info helps.
gapps-jb-20121128-signed.zip - I also had problem with this update
Foster Basic said:
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Click to expand...
Click to collapse
I also had problem with this update!!!!!!!
Problem with 28 Nov. GooManager received update for Jandycane 1.8
(updates jandycane 20121020 and gapps 20121011 done on 09/11/12)
........................
On 28 November GooManager automatically downloaded the following: gapps-jb-20121128-signed.zip
On the 29 November I flashed this on my first gen. Kindle Fire
As follows:
first did a Backup then wiped Cache and Dalvik and then started update - gapps-jb-20121128-signed.zip
after starting update got a Dalvik cache Directories wipe complete message (then)
Verifying Filesystem....
Verifying partition sizes...
Install ........ gapps-jb-20121128-signed.zip
Finding update package
installing
......
......
(and finally)
Installation Complete!
(then once again under this the texts)
Verifying Filesystem....
Verifying partition sizes...
But there it seems to have stopped (completed?)
And under in TWRP I have the options: Wipe Cache/Dalvik - Home - Reboot System
I decided to choose Reboot system
The following happened:
I got a message "upgrading Android apps"
then it started in the normal ("turning mirror bits") loading window
then the usual password window
but the keyboard wouldn’t open!!! I couldn’t get past the password window
also I notice that the WLAN was no longer on/active (it had been on during the process)
I tried several reboots – still the same
I eventually decide to do a restore of Backup – this was successful!
I have no idea what is or went wrong
Is there something wrong with this gapps-jb-20121128-signed.zip it certainly seems like it?????????
Any other experiences?
I've had the exact problems you both describe running a clean flash of nightly with CM10 on a Nook Color. Everything is great until gapps-jb-20121128-signed.zip is loaded, then keyboard is disabled, crashes, etc.
http://goo.im/gapps/gapps-jb-20121128-signed.zip appears to have been removed from goo.im
gyrfalcon said:
I've had the exact problems you both describe running a clean flash of nightly with CM10 on a Nook Color. Everything is great until gapps-jb-20121128-signed.zip is loaded, then keyboard is disabled, crashes, etc.
http://goo.im/gapps/gapps-jb-20121128-signed.zip appears to have been removed from goo.im
Click to expand...
Click to collapse
Hi, and thanks for replying - now I know for sure it wasn't me that screwed up, wasn't sure!
Glad to hear that it has been removed - but that's really bad - sending out a really bad update like that - lucky we didn't end up with Bricked devices - really frustrating and not a nice thought at all - I'm really grateful for whoever it is that does all this work...but...putting something like that out ... that is scary ........ don't know if I will now trust the next download(s)!!!!!!!!
who is it that does these gapps anyway?
Total Noob, not sure what I did.
Long story short, rooted my Galaxy Tab 10.1 wifi (p7510) tonight.
Saw a video on how to flash 4.1 onto my tab here: http://www.youtube.com/watch?v=KRjl7zh551w
followed the instructions from the video, it linked to http://forum.xda-developers.com/showthread.php?t=1787399
downloaded the latest nightly from http://get.cm/?device=p4wifi
(cm-10.1-20130124-NIGHTLY-p4wifi.zip )
and the gapps from mirror 1 at http://forum.xda-developers.com/showthread.php?t=1787399
(gapps-jb-20120729.zip)
There was probably my mistake
In any case, i wiped everything, flashed the CM10 and gapps.
On reboot I got 2 error messages,
"Unfortunately, the process com.google.process.gapps has stopped." ok
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Now I have no idea how to recover from this point.
I tried to re-wipe and re-flash my old functioning ICS root and it still reboots into CM loading screen and setup wizard loop
Also, if i attempt to install zip from sdcard my options are:
0/
legacy/
obb/
legacy and obb contain no files and I have to navigate down a couple of layers of 0/ to reach my original root.
Probably screwed myself royally, but I guess that's how you learn. Any advice on how to salvage my tab?
Update*
Restore finds no files to restore
used odin for TWRP instead of CM, still no luck at restoring.
Won't mount USB, so I don't know how to transfer over a different gapps to see if that would solve the problem.
Revert to stock 4.0.4 through odin and start over. Probably be the easiest. I've had to a few times and yes it's how you/we all learn...
Firmware Here
nighthorns said:
Total Noob, not sure what I did.
Long story short, rooted my Galaxy Tab 10.1 wifi (p7510) tonight.
Saw a video on how to flash 4.1 onto my tab here: http://www.youtube.com/watch?v=KRjl7zh551w
followed the instructions from the video, it linked to http://forum.xda-developers.com/showthread.php?t=1787399
downloaded the latest nightly from http://get.cm/?device=p4wifi
(cm-10.1-20130124-NIGHTLY-p4wifi.zip )
and the gapps from mirror 1 at http://forum.xda-developers.com/showthread.php?t=1787399
(gapps-jb-20120729.zip)
There was probably my mistake
In any case, i wiped everything, flashed the CM10 and gapps.
On reboot I got 2 error messages,
"Unfortunately, the process com.google.process.gapps has stopped." ok
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Now I have no idea how to recover from this point.
I tried to re-wipe and re-flash my old functioning ICS root and it still reboots into CM loading screen and setup wizard loop
Also, if i attempt to install zip from sdcard my options are:
0/
legacy/
obb/
legacy and obb contain no files and I have to navigate down a couple of layers of 0/ to reach my original root.
Probably screwed myself royally, but I guess that's how you learn. Any advice on how to salvage my tab?
Update*
Restore finds no files to restore
used odin for TWRP instead of CM, still no luck at restoring.
Won't mount USB, so I don't know how to transfer over a different gapps to see if that would solve the problem.
Click to expand...
Click to collapse
I am in exactly the same situation as you, same build same gapps, same problem.
To help you out, in recovery (CWM) you can mount /data, then using adb on you computer you can push stuff to the "sdcard" via the command "adb push C:\Some\Local\File.zip /data/media/0/File.zip"
Same problem for me. I installed CM10.1 without gapps and it worked without problems. I also tried with different versions of gapps and give all the mentioned problem.
"Unfortunately, the process com.google.process.gapps has stopped." OK
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Does anyone have a solution to this problem.
Thx
Help required if possible!
Hello all, joined just to post here.
I'm having the same issues as detailed in the first post.
A lot of the solutions that I've seen recommend going into settings and turning syncing off but the error messages block me from accessing anything. It eventually just seems to crash itself and turn off anyway, which is probably due to being bombarded with error message popups.
Is there a simple way to fix this without doing a full reset back to 4.0.4 or is that my only choice?
If so then I'm in trouble because I followed the link that mrhiab provided but I can't see which firmware there is the one I need (wifi only galaxy tab 10.1 P7510 uk).
Is the cause of this problem that the version of gapps I installed is broken and causes errors as it worked fine without gapps?
If anyone can answer any of those questions then I'd really appreciate it. I've semi broken my girlfriends tab and she's not too happy lol!
UPDATE/SOLVED:
Just thought I'd comment back and say that I've solved the problem.
I simply reflashed the CM by putting the tab into install mode again but didn't add gapps. After rebooting I noticed that it worked okay so I tried to find another release of gapps and tried that...it worked perfectly - no errors no nothing!
Sorry for the initial noob-post!
same problem as you
sir ... i also have the same problem as you ... i've been searching on almost all sites ... still i can't see any issues that can solve my problem.1st was "unfortunately, google.com.pro ..." then next was "unfortunately, setup wizard has stopped." this results everytime i reboot my galaxytab 2 10.1 .. im on JB 4.1.1 .. and i just followed the guide of sir codeworkx. please lend me a solution.
BTW midgard .. how did you flash CM again w/o the gapps ? because when i go to install zip from sd card ... there's nothing in there .. just obb and stuffs said by the thread maker.
I will appreciate suggestions ... Thanks in advance
I hope some suggestions may come up eventually
I found a way on installing cyanogenmod 10 on my Galaxy tab 2 10.1 by not installing gapps at the same time while installing the CM10 .. but eventually, i found out i don't have any google playstore .. and that's when i googled on how to have one. I found a video saying i could have it by just going to there website via my tablet goo-apps .. then download the existing gapss for my JB 4.1.1 .. and then flash it .. but then again ... the error of the Unfortunately, setup wizard stopped came up again ... help
and thanks midgard !!!
Can I get help
midgar777 said:
Hello all, joined just to post here.
I'm having the same issues as detailed in the first post.
A lot of the solutions that I've seen recommend going into settings and turning syncing off but the error messages block me from accessing anything. It eventually just seems to crash itself and turn off anyway, which is probably due to being bombarded with error message popups.
Is there a simple way to fix this without doing a full reset back to 4.0.4 or is that my only choice?
If so then I'm in trouble because I followed the link that mrhiab provided but I can't see which firmware there is the one I need (wifi only galaxy tab 10.1 P7510 uk).
Is the cause of this problem that the version of gapps I installed is broken and causes errors as it worked fine without gapps?
If anyone can answer any of those questions then I'd really appreciate it. I've semi broken my girlfriends tab and she's not too happy lol!
UPDATE/SOLVED:
Just thought I'd comment back and say that I've solved the problem.
I simply reflashed the CM by putting the tab into install mode again but didn't add gapps. After rebooting I noticed that it worked okay so I tried to find another release of gapps and tried that...it worked perfectly - no errors no nothing!
Sorry for the initial noob-post!
Click to expand...
Click to collapse
I still have that "Unfortunately, Setup Wizard has stopped" loop-message, can somebody help me please!
I have just flashed my phone and been trying to get GAPPS installed. No matter what version I try to flash it does not appear in the system.
Seems to be no issue during the flash through TW, and no errors come up. But when I go into apps area of the phone I only see "Play Magazine" added.
Anyone have an idea?
Doug
Try...
daowen said:
I have just flashed my phone and been trying to get GAPPS installed. No matter what version I try to flash it does not appear in the system.
Seems to be no issue during the flash through TW, and no errors come up. But when I go into apps area of the phone I only see "Play Magazine" added.
Anyone have an idea?
Doug
Click to expand...
Click to collapse
I had the same problem thing that i did was reset my phone to regular Gingerbread 2.3.6 and redid the process first installing the firmware than the GAPPS. The other posibility is you have a corrupted GAPPS files and or files...
*The first method only works with zip files.
Hello all,
I have searched the forums and the thread specific to this rom and I can't find an answer to my problem.
I flashed the Avatar rom and I keep running into two problems.
1. The AOSP keyboard continually crashes when I load the newest GAPPS. I can work around this by loading an older version of GAPPS, install swype, reinstall the new version, and disable the AOSP keyboard.
2. When I go in to change themes, I get an error "An error has occurred, please check the internet connection
I have tried reflashing the rom, both doing just a factory reset, and deleting system. I have tried this rom with and without updating the kernel. I have tried both the AJK and STI kernel.
I am hoping someone can tell me what I am doing wrong. Any and all help on this is greatly appreciated.
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.