Develop Bugs

[Q] Working Market for CM7 or CM7 Build 1/2?

So thanks to CWMR 3.005 a lot of old zips don't work.
old_market.zip won't install.
New Market V2.2.11 won't install.
Vending_2_2_11.apk installs but FC's.
gapps-gb-20110120-signed.zip installs and FC's.

Why are you flashing different versions of the market? Why didn't you just flash the official Gapps from the CM7 nightly or CM7 RC1 threads?
Also, do you have the latest CWM3.0.0.5? The newest version that supports 2.2 and 2.3 that is flashed from ROM manager, not the one downloaded and installed manually. I've been flashing the stock launcher (.zip) for several builds now with this CWM Recovery.
Edit: looks like the Gapps page is down for a few. There are people posting dropbox links to it though.

martonikaj said:
Why are you flashing different versions of the market? Why didn't you just flash the official Gapps from the CM7 nightly or CM7 RC1 threads?
Click to expand...
Click to collapse
Because the official Gapps installs but the market FC's, as said above.
martonikaj said:
Also, do you have the latest CWM3.0.0.5? The newest version that supports 2.2 and 2.3.
Click to expand...
Click to collapse
As said above, yes.

What's CM7 build 1/2? You might try flashing a full rom not half of one
Just kidding, though I still don't what you're talking about in reference to build 1/2.
Anyway, do a wipe and reflash it twice in recovery to make sure everything sticks. Then just use the market to load gapps. I think the market is past 2.2.11 now but I'll check for you and post the .apk if you want. Lastly, I'd run a fix permissions if for some reason it still fc's on you, then reboot.

adrienspawn said:
Because the official Gapps installs but the market FC's, as said above.
As said above, yes.
Click to expand...
Click to collapse
Well I just wanted to double check. There was the pre-stable release of CWM 3.0.0.5 that only supported 2.3 and maybe this was the one you had causing issues.
I'd just try to reflash with a clean Gapps install and see what you can do about it. Also try simply wiping your market cache with something like Titanium Backup if you have tried flashing around all these different markets.

Question about gapps/updating to a later AOSP-based ROM

I've never used an AOSP ROM before, but now I am currently on AOKP. When I want to update to a newer version, do I still need to flash gapps after flashing the update? I assume I have to reflash the kernel as well if I use one different than the one included with the ROM?

You need to flash GApps straight away after if you are wiping your device. You also need to reflash the kernel of choice after. Good luck.

jd1001 said:
You need to flash GApps straight away after if you are wiping your device. You also need to reflash the kernel of choice after. Good luck.
Click to expand...
Click to collapse
Only wiping I would do would be cache and dalvik since I am merely upgrading the ROM version, eg nightly 19 to nightly 20. Would that still involve flashing gapps?

edgeicator said:
Only wiping I would do would be cache and dalvik since I am merely upgrading the ROM version, eg nightly 19 to nightly 20. Would that still involve flashing gapps?
Click to expand...
Click to collapse
Yes
10char.

You shouldn't have to reflash GAPPS if you are just updating..

2 separate answers. Anyone else want to chime in?

You have to ref lash the kernel because flashing a rom flashes the from kernel. I've never had to flash gapps on any device if going from an old build of a rom to a new one unless specifically stated.
Sent from my Galaxy Nexus using xda premium

edgeicator said:
2 separate answers. Anyone else want to chime in?
Click to expand...
Click to collapse
Just think about it. It depends on how you flash and if you flash an update.zip if that zip wipes existing data or just adds to it.
For a sure answer you would need to say what method is used and how the update edify script in the zip looks like.
Now for someone how knows the rom you're talking about in detail and what files are provided there might be a clearer answer, but not every poster does know such details^^

The answer is no, if you just update a rom without wipe, you dont need to flash gapps. This type of rom update keeps all your data in tact anyway so of course no need to flash extra.

[Q] CM10 Stable - Completely Unstable and Broken

Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.

Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip

Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium

Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.

dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?

Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.

You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.

i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset

If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...

goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.

BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.

Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).

goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.

Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works

wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.

Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end

wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?

Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.

[Q] CM and Gapps version

Hello! I have managed to root my phone, but I got the set up wizard message and the gapps error. After a google search it told me I had the wrong version of gapps. However, when I go to the official gapps page, the download for cm 10.1 only works with 4.2.2 and not 4.1.2. The one for cm 10.0 is for 4.1.2, but on the hercules downloads page, the 10.1 stable release is already out (that's the one I used!). Does this mean I have to run 10.1 without gapps, or downgrade to 10.0 if I want gapps?
Trust me, I have searched for this. Any help would be appreciated.

if you are on 10.1 grab the first one on the page http://goo.im/gapps also double check make sure you have no market installed if you do then you dont need any gapps install everything from the market

Alright
Ok, I'm gonna try that. +1 thanks for you. Man, I'm such a noob. :crying: :crying:

Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Roulette
krazierokz said:
Bro all good we (I) was all there gotta start some where :thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
It's circling now...it's been at it for about 5 minutes now...the wait is unbearable!

Circling
It appears to have no end to the blue circling boot screen. I tried clearing cache and factory reset using CWM, no cigar still. Any fixes for this?
The CM version is the 10.1 stable release for hercules.
The gapps version is the 20130301 version.

which link did you flash for the CM what thread point in the right direction where you flashed from ? if you booted up the first flash and gapps were incorrect it shouldnt matter when you update the gapps it wipes the old files just make sure to wipe dalvik/cache and reboot

My Idiocy
I am retarded. I decided to go and unroot the phone and flash a stock rom and try again. I then flashed twrp via odin (which I prefer now) with no problems. But for some reason, no matter how many times I clear everything and try different kernels, the device will just not root. I have tried the superuser zips from the official site, I have tried the superuser from CWM's site, nothing works. Gah. Now what? Am I stuck stock forever?

Babbalabba said:
? Am I stuck stock forever?
Click to expand...
Click to collapse
Just use TWRP to flash whatever (Hercules) ROM you want. Make sure you wipe dalvik, cache, system and data.

Alright, I will try a wipe again, and then flash a custom ROM. If it doesn't root me I will report back with the situation. Thank you for all your help!

Um, just another question before I proceed with wipe and rom...if the ROM is based off of JB 4.2.2, such as Cyanogen mod, will my phone just run 4.2.2 as part of the rom, or will it be incompatible?
EDIT: Never mind...

I love you all forever. It works, and I have gapps running and root access. Thank you so much...I really don't know what to say.

[Q] CM 9.1 crashes continiously

Dear Community,
this is my first post on XDA-devloppers.
I ask you for help as y have a serious promlem with CM 9.1 on my xperia arc.
I flashed CM on my phone using the latest stable rom downloaded from the official cyanogenmod website (cm-9.1.0-anzu.zip)
Everything worked perfectly and i was delightet.
Unfortunately, after two days my phone crashed.
By crashed i mean that it first reacted very slow then froze. After this, the screen went black (backlight on) an then dark.
no button could get me back to lockscreen.
then suddenly the phone rebootet.
this happened every time about one minute after booting my phone.
As the problem didn't seem to get away i decided to reflash it:
wipe SD
delete davlik cache
reseting to factory
and then istalling the same rom and gapps from zip
everything worked fine again, but after one day i got the same problem again.
what can I do to fix this?
I would appreciate any kind of help
and excuse me if this isn't the right forum (search also, didn't help)
sincerly,
PraetorAce

You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた

popthosegaskets said:
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
Click to expand...
Click to collapse
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)

PraetorAce said:
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
Click to expand...
Click to collapse
You can try the nightly versions if the stable doesn't work for you.
Take out the boot.img inside the ROM zip and flash with fastboot. Then put ROM zip onto SD card and flash with CWM.
僕のLT18iから送られてきた

I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx

PraetorAce said:
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
Click to expand...
Click to collapse
Odin is for Samsung devices only. If CM9.1 doesn't work for you then you might want to try CM10.
僕のLT18iから送られてきた