Database Users

process com.android.vending has stopped unexpectedly

Im getting this error and force close on one of my Heros when I try installing any of my apps on any of the 2.1 roms. Im coming from Fresh 1.1 and following the same procedure I used on my other Hero on which the market is fully functional. Ive wiped everything over and over and cleared data on anything that looked like it at to do with the market. I also tried fix apk mismatches from recovery. Short of RUU which Id like to avoid if at all possible Ive tried everything else I can think of. In searching I have come across this error code on other android phones, but nothing on the hero and nothing specific to trying to install apps. So has anyone else seen this? And would RUU do anything a full data wipe didnt already?

Reading instructions has its benefits grasshopper...
Download the latest recovery and throw it onto your SD Card, boot into the old version of recovery and flash the new recovery as a .zip update, reboot into recovery again and then wipe your phone again, then install android 2.1, don't reboot yet, make sure your rom either has it's own custom kernal or download one for 2.1 and flash it, open up adb and clear dalvik cache and boot cache, then reboot your phone and you should load without any problems.

Thanks. But I did that from the get go. Aside from flashing a kernal, but Im running Darchtrev2 on the fully functional Hero that I mentioned and thats got a custum kernal built into the rom. So thats what I started with on the second one using the exact same process without success. Does wiping from adb do more than wiping from recovery? Thats one other thing I didnt do after the initial install.... But do understand you correctly that you have seen this specific error before?

Just bumpin the tread in hopes of finding a solution. I dont even mind gettin flamed for asking a stupid question if I could get linked up with a fix! lol I see its getting views, just no ideas I guess... It sucks cuz everything else works fine except the market. I get the list of my downloads, when I tap on one to install I the download button instead of the install button, so Ill tap on it and I get get the progress bar saying its downloading. When it gets to 100% I get the error and force close... Anyone?

I would try wiping again then flashing fresh 1.1 see if that boots and everything works ok then I would redownload the recovery and flash that still running fresh then reboot make sure everyhting is cool, then redownload whatever 2.1 rom you want and wipe and flash.
doing this serves 2 purposes
1. make sure that somewhere along the line none of the files corupted
2. if you still have the same problem then it will let you know where the problem is coming from.
just process of elimination
if you still have problems after that then I would say RUU, yes it is different than just wiping from recovery as it restores a completely stock image and gets rid of everything else. all a data wipe really does is get rid of user data.
just my opinion.
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.

Thanks for the reply and for giving me something different to try. I hadnt thought about trying that. Frustration I guess! It makes sense though. Ill give it shot. Thanks!

Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).

Yeah, Ive been thinking about RUU'n too just to see if making a fresh start would make any difference, but after all the time I spent getting the one Hero working like I want on 2.1 and the troubles Ive had with the second and what Ive read about people bricking trying to RUU or flash recovery Ive been kinda hesitant....

willy900wonka said:
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Click to expand...
Click to collapse
Thanks. I dont know that Im quite that knowledgable though. Im sure I could read a logcat... understanding what the hell I would be reading is something else again. Saving the url though in case I need to dig deeper. Thanks for the reply.

wtphoto said:
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Click to expand...
Click to collapse
Sometimes it's just fun to RUU and do everything again

Alright if you're still having problems then just follow these steps:
Boot into recovery and make a nandroid back up just in case something goes wrong.
Download the latest version of your current 2.1 rom and reflash it from Recovery.
Open up adb and mount the /data directory (adb shell, mount /data)
Enter the following two commands in adb: rm -r /data/boot-cache , rm -r /data/dalvik-cache
Go Back to ADB and type the following commands: cd /data/data/com.android.vending , rm -R cache
Fix UID Mismatches using the tool in Recovery and then reboot your phone

regaw_leinad said:
Sometimes it's just fun to RUU and do everything again
Click to expand...
Click to collapse
or NOT!

Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.

HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
You should have updated to the latest ruu...

wcgbmd said:
You should have updated to the latest ruu...
Click to expand...
Click to collapse
The latest RUU? I used the 1.56..... I did get it working tho. Flashed the mms. fix zip. Just wasn't expecting to have to as I didn't with my other hero. Don't know what the difference is between the two devices. Both are google branded, but the second one fought me every step of the way.

HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
First, sorry for the bump.
I just started getting this error and wanted to know if you figured out exactly what it was so I didn't have to go through that whole RUUing process. Thanks.

don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.

boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
You're the bomb. That worked like a charm.

boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
Cant believe nobody wrote this first

boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
I was having the same problem on DC a couple days ago and that fixed it for me. I was reading this thread wondering why no one had mentioned it yet.

RyanZA's OCLF post JI6

I'm contemplating using RyanZA's OCLF app to root. My Vibrant has some issues that I'm hoping to correct with root access.
Anyways, does this app (from the market) still work post JI6? I've read that the lag fix doesn't seem to do much anymore, is this correct?
Also, When I run the rooting part of the app, is does it's thing and says reboot to the download mode or whatever, I get into that no problem, but then what do I do?? Volume up and down to move, power to select, but which option do I choose? Everything walk through I've found skips right over this tidbit.
If I remember right, one says reinstall packages, another is erase user data, etc.
Just a little guidance and assurance that this app still works would be great.
Thanks.

atvman29 said:
I'm contemplating using RyanZA's OCLF app to root. My Vibrant has some issues that I'm hoping to correct with root access.
Anyways, does this app (from the market) still work post JI6? I've read that the lag fix doesn't seem to do much anymore, is this correct?
Also, When I run the rooting part of the app, is does it's thing and says reboot to the download mode or whatever, I get into that no problem, but then what do I do?? Volume up and down to move, power to select, but which option do I choose? Everything walk through I've found skips right over this tidbit.
If I remember right, one says reinstall packages, another is erase user data, etc.
Just a little guidance and assurance that this app still works would be great.
Thanks.
Click to expand...
Click to collapse
If you are rooted, have superuser, busy box installed & clockwork mod installed. then you should be able to select reinstall packages and that should take you rite into clockwork recovery menu.

chichu_9 said:
If you are rooted, have superuser, busy box installed & clockwork mod installed. then you should be able to select reinstall packages and that should take you rite into clockwork recovery menu.
Click to expand...
Click to collapse
But I'm not rooted, that's what I'm trying to figure out.

atvman29 said:
I'm contemplating using RyanZA's OCLF app to root. My Vibrant has some issues that I'm hoping to correct with root access.
Anyways, does this app (from the market) still work post JI6? I've read that the lag fix doesn't seem to do much anymore, is this correct?
Also, When I run the rooting part of the app, is does it's thing and says reboot to the download mode or whatever, I get into that no problem, but then what do I do?? Volume up and down to move, power to select, but which option do I choose? Everything walk through I've found skips right over this tidbit.
If I remember right, one says reinstall packages, another is erase user data, etc.
Just a little guidance and assurance that this app still works would be great.
Thanks.
Click to expand...
Click to collapse
It worked on my Vibrant.
When in recovery, the selection to choose is the reinstall packages.
I didn't immediately apply the lagfix after JI6, as stock did have some performances gains. But after a few weeks, I was noticing some of the old lag issues again. At that point, I installed the lag fix again, (I had it installed before JI6) and saw some good results, not as drastic as before, but the problem wasn't as severe as it was right after launch.

Thegreatheed said:
It worked on my Vibrant.
When in recovery, the selection to choose is the reinstall packages.
I didn't immediately apply the lagfix after JI6, as stock did have some performances gains. But after a few weeks, I was noticing some of the old lag issues again. At that point, I installed the lag fix again, (I had it installed before JI6) and saw some good results, not as drastic as before, but the problem wasn't as severe as it was right after launch.
Click to expand...
Click to collapse
So after I click reinstall packages, I just let it do its thing? Once i reboot, I will be rooted?

atvman29 said:
So after I click reinstall packages, I just let it do its thing? Once i reboot, I will be rooted?
Click to expand...
Click to collapse
yes, use OCLF to root....there is no danger in it, then reboot into stock recovery and choose reinstall packages....then reboot and you are rooted....HOWEVER, after you reboot your phone, mount your sd card to your PC, and move "update.zip" from your internal SD to your EXTERNAL SD...this will make way for ClockwordMod's update.zip
^^If youre going to root it was 100% recommended that you flash ClockworkMod's recovery, find it here: http://forum.xda-developers.com/showthread.php?t=734164

TopShelf10 said:
yes, use OCLF to root....there is no danger in it, then reboot into stock recovery and choose reinstall packages....then reboot and you are rooted....HOWEVER, after you reboot your phone, mount your sd card to your PC, and move "update.zip" from your internal SD to your EXTERNAL SD...this will make way for ClockwordMod's update.zip
^^If youre going to root it was 100% recommended that you flash ClockworkMod's recovery, find it here: http://forum.xda-developers.com/showthread.php?t=734164
Click to expand...
Click to collapse
Do I install the clockwork app before or after root? Is that just for bailing you out of a bad situation essentially?

atvman29 said:
Do I install the clockwork app before or after root? Is that just for bailing you out of a bad situation essentially?
Click to expand...
Click to collapse
thats one thing its for, but it serves many functions....backup/restore, flashing roms/kernels/mods, wiping, etc.

TopShelf10 said:
thats one thing its for, but it serves many functions....backup/restore, flashing roms/kernels/mods, wiping, etc.
Click to expand...
Click to collapse
So install it immediately following root?

I installed RyanZA's OCLF straight from the Market on JI6, and so far I have to say the user experience is much more responsive. The JI6 update made things noticeably better in terms of responsiveness, but the OCLF has made this thing almost "snappy".
I haven't installed Clockwork recovery (yet) as I'm still puzzling over exactly what to do (what to copy and where) now that the OCLF rooting and lag fixes are installed.

Rooted Samsung Vibrant, Kernel 2.6.29 JI6
Ryan I installed your lagfix, but Quadrant Score almost identical than before lagfix install. I know many thumb their nose at these benchmark scores, but I was expecting a big change. Anything I could have done wrong?
thanks in advance for any help!!

****update*****
I knew something could be done to better this so I messed around a little. I originally installed OCLF V1+ ...... and the V1+ Quadrant score was the same as pre-OCLF around 835 ... uninstalled that and went to OCLF V2+ ....... OMG this is insane!!!
After going to OCLF V2+ - Quadrant score exploded to 2118 ..... wicked. I tried to swamp this thing but that's just not happening.
Thank you RyanZA

[q] someone with a brain help me please!!

i rooted using adb like 2 days after the phone came out.. i still have the original dh12 radio. everyone told me not to use OTA updates after rooting and removing bloatware. and i want to use the new froyo leak.. but i guess you need d105 or 09 i have now clue how to unroot because i used adb.. what should i do??? please help me.. im stupid when it comes to this stuff

ace5198 said:
i rooted using adb like 2 days after the phone came out.. i still have the original dh12 radio. everyone told me not to use OTA updates after rooting and removing bloatware. and i want to use the new froyo leak.. but i guess you need d105 or 09 i have now clue how to unroot because i used adb.. what should i do??? please help me.. im stupid when it comes to this stuff
Click to expand...
Click to collapse
find the DL09 Verizon official odin package http://forum.xda-developers.com/showthread.php?t=908451 . it will update EVERYTHING including radio to DL09. Then re root using ADB again. get CWM using CWM install thread here on XDA, then flash this rom. done.
make sure you flash DL09 in "PDA" NOT "phone" using ODIN.

so please dont mind my ignorant qquestions.. but im not familier with odin ive read a bit about it.. but do i need to unroot before i do that.. or not.. and cant i just say f adb and use a one click at that point?

Before you install the complete stock DL09 package posted above (which is resistant to one-click rooting, by the way), consider this option:
1. Download the DL09 modem by itself here: http://adrynalyne.us/files/roms/DL09modem.tar
2. Download Odin here:
http://dl.dropbox.com/u/458252/Odin Files/Odin3 v1.3.exe
3. Pull battery from device
4. Launch Odin
5. Hold volume down button and plug device into computer
-This will place the device into download mode
6. Verify device shows up in odin
7. Click "PDA" button in odin
8. Select "DL09modem.tar" from where you downloaded it
9. Click "Start"
10. Congratulations - you now have the DL09 modem installed. Now you're ready to install your froyo build using Clockwork recovery. Might I suggest this (http://www.mediafire.com/?f282mms2jb2ra2q) one?

If you are on windows just use Odin. It is very easy and you are okay if rooted. Just make sure you read instructions. There is one button that can be painful if you don't know what you are doing.

gbmitchell said:
If you are on windows just use Odin. It is very easy and you are okay if rooted. Just make sure you read instructions. There is one button that can be painful if you don't know what you are doing.
Click to expand...
Click to collapse
Do you know who created Odin?
Maybe we can request him/her to release another version of the app without the "phone" button.

jmcintire said:
Before you install the complete stock DL09 package posted above (which is resistant to one-click rooting, by the way), consider this option:
1. Download the DL09 modem by itself here: http://adrynalyne.us/files/roms/DL09modem.tar
2. Download Odin here:
http://dl.dropbox.com/u/458252/Odin Files/Odin3 v1.3.exe
3. Pull battery from device
4. Launch Odin
5. Hold volume down button and plug device into computer
-This will place the device into download mode
6. Verify device shows up in odin
7. Click "PDA" button in odin
8. Select "DL09modem.tar" from where you downloaded it
9. Click "Start"
10. Congratulations - you now have the DL09 modem installed. Now you're ready to install your froyo build using Clockwork recovery. Might I suggest this (http://www.mediafire.com/?f282mms2jb2ra2q) one?
Click to expand...
Click to collapse
would this be the easiest way to go about it.. this all makes sense to me??

ok i cant dl odin.. i started an account on dropbox because everytime i click the link it says 404 page not found.. and it still says the same thing???

mailaliasgar said:
Do you know who created Odin?
Maybe we can request him/her to release another version of the app without the "phone" button.
Click to expand...
Click to collapse
I always assumed it was a Samsung designed product but I don't know. I also hypothesized that it is not just for Android and that the phone button is for feature phones but I really have no idea and have not cared enough to research it.

ace5198 said:
ok i cant dl odin.. i started an account on dropbox because everytime i click the link it says 404 page not found.. and it still says the same thing???
Click to expand...
Click to collapse
sorry... try this one:
http://adrynalyne.us/files/odin/Odin3v1.3.exe

ace5198 said:
would this be the easiest way to go about it.. this all makes sense to me??
Click to expand...
Click to collapse
Granted, it seems like an involved process, but most advice posts group most of these steps into one, like saying "Flash DL09 modem in Odin" without actually explaining how to do so, since there are other posts that can be found in this forum with these more detailed instructions.
Believe me, if you flash the entire DL09 stock package, rooting will be much harder to do. If you flash this package, you probably will have to root using adb again, since as far as I know no one-click root method has worked consistently on the stock DL09 ROM.

and i need to root again b4 flashing 2.2 i have rom manager and titainium backup.. .so to save all of my paid apps.. i just back them up using ti backup right???

and one more thing.. the link you posted for 2.2 theres no info on it.. what makes it so special

ace5198 said:
and i need to root again b4 flashing 2.2 i have rom manager and titainium backup.. .so to save all of my paid apps.. i just back them up using ti backup right???
Click to expand...
Click to collapse
If you only installed the DL09 modem using Odin, you shouldn't have to root again... if you installed the entire DL09 package, you will need to re-root.
Regarding Titanium Backup, go ahead and back up your apps, use Clockwork recovery to install your DL30 build, then reinstall Titanium Backup and do a batch restore (I'm assuming you already know how to use Titanium Backup, but I'll be glad to walk you through it if you don't). You should only back up and restore user apps, NOT system data! (choose "backup all user apps" from the batch menu when backing up, and choose either "restore missing apps with data" when restoring - do NOT choose "restore missing apps + all system data"). Restoring system data after making the jump from Eclair to Froyo is almost guaranteed to cause problems.

ur going to get all kinds of thanks ur awesome dude.. ok backup is done.. u said to use clockwork recovery to install dl30.. i just use odin. for d109 and then put the dl30 file on my sd card and install it through clockwork??? right.. n can i backup contacts too??? or will google save them?? and theres no chance of losing pictures or nething else on my sd card is there??

ace5198 said:
ur going to get all kinds of thanks ur awesome dude.. ok backup is done.. u said to use clockwork recovery to install dl30.. i just use odin. for d109 and then put the dl30 file on my sd card and install it through clockwork??? right.. n can i backup contacts too??? or will google save them?? and theres no chance of losing pictures or nething else on my sd card is there??
Click to expand...
Click to collapse
Sorry it took me so long to get back to you... had to take a powernap... you shouldn't lose anything on your sd card... I've flashed countless ROMs, kernels, themes, etc. without losing anything. Contacts should be good, too. Just to be safe, though, you might want to make sure your contacts and calendar appointments are saved and/or synced to your google account and not just stored on your phone.
Released from SAMSUNG-SGH-I897 Captivation using XDA App (my Fascinate is charging)

yes they are.. awesome.. well im gong to give my daughter a bath put her to bed.. and go for it ill def let you know how it goes.. thank you sooooo much

No ADB (shell) when in Recovery?

Does ADB not work when in recovery?
When my N7 is in recovery mode (CWM) my PC (Win7) doesn't see any attached USB devices and "adb shell" obviously tells me "no devices found".
My N7 is rooted, unlock bootloader, has CWM (non touch) installed and when in "regular", normal boot I can perfectly "shell in" via adb, just not in CWM recovery....
Does CWM not support that as of yet, or am I doing something wrong?

Not sure. Adb works fine for me in cwm
Sent from my Nexus 7

Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.

bagofcrap24 said:
Not sure. Adb works fine for me in cwm
Click to expand...
Click to collapse
OK, so it might just be something I'm doing wrong.
TECK said:
Why did you installed CWM into your tablet, instead of loading it ONLY when you need to? That is the proper approach.
Click to expand...
Click to collapse
Counter question: Why not?
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing - also I might need it (or at least it's supposed root adb shell access) everytime I go to recovery, so why keeping the need to have to "fastboot boot" it everytime instead of just booting into it?
Also - as said above - adb and fasboot both work fine, just not in CWM.
I might try another driver, maybe that'll help.

HellcatDroid said:
You don't have to decide what's the proper way to do things for me, I think I know what I'm doing.
Click to expand...
Click to collapse
The proper way is to tempload CWM, not install it. You want to be special and do it your way, feel free to... nobody is stopping you. Since you know what you are doing, then you should not have any issues.
HellcatDroid said:
I might try another driver, maybe that'll help.
Click to expand...
Click to collapse
What's wrong with using the default Google USB drivers? They work properly.

TECK said:
What's wrong with using the default Google USB drivers? They work properly.
Click to expand...
Click to collapse
See first post, not working in CWM for me right now.
Might not be the drivers, if you have any real help to give, feel free to share.

I would not use other drivers, except the Google USB ones provided on their developer site.
Based on my experience, you can have only headaches if you replace stock recovery with CWM. That's the main reason why I always temp load it, instead of physically install it. I know it is convenient to have it installed, but how often do we use it? Very rarely. The less I tweak on the phone, the safer it is. Are you running 6.0.1.0 on your tablet?
First, do you see the Android 1.0 driver marked as invalid in device manager?
If yes, then the fix is easy... Follow the procedure I posted in my signature to properly install the ADB drivers.
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
If not, this is what I would do in this situation: I would install the Google factory image (straight from console, no crazy toolkits) and restore everything back to normal. Then, I would test the stock recovery and see if everything works as expected. After that, I would tempload CWM 6.0.1.0 and see if there are any issues. I know is a ****ty deal, especially if you have lots of customizations on your tablet. The goal is to see if you can run all proper commands while using the stock recovery. If you cannot, that's a different ball game.

It's been the drivers.
i installed the ones from the Android SDK and everything works now (had drivers d/l'ed from the Asus page so far).
TECK said:
Based on my experience, you can have only headaches if you replace stock recovery with CWM.
Click to expand...
Click to collapse
Based on my experience it doesn't really matter - unless you are going to use some special functionality CWM breaks (like the full device encryption on the S2 with GingerBread 2.3.x - and I got even that to work with an own build).
Bottom line: every one does things differently and something perfect for one might be suboptimal for the other.
TECK said:
That's the main reason why I always temp load it, instead of physically install it.
Click to expand...
Click to collapse
I love the option to be able to temp-boot a kernel, my Droids so far (Samsung Galaxy S2 and S3) didn't support that.
Tempbooting a kernel is perfect for testing a new build as you don't have to reflash a working one if the one you tried doesn't work
Though, it'd be just more work for me to tempload CWM everytime I need it, but as said, that's just me.
TECK said:
I know it is convenient to have it installed, but how often do we use it? Very rarely.
Click to expand...
Click to collapse
Negatory, I use it alot.
Mostly for the rooted adb shell access though, yet that's rather often - and also quite often away from my home computer with everything loaded and temploading without the kernel image.... hmm, not really
TECK said:
The less I tweak on the phone, the safer it is.
Click to expand...
Click to collapse
Safety is overrated (disclaimer: that's a joke )
For me it's more like "the more I mod the hell out of it, the more fun it is - and if everything breaks, I restore/reflash factory and start over".
CWM won't stay for too long anyways, eventually I'll smack my own kernel and own recovery-kernel onto it.
Time to check out those sources
TECK said:
Are you running 6.0.1.0 on your tablet?
Click to expand...
Click to collapse
Yeah.
TECK said:
Do you have any "fancy" drivers installed, like Samsung, Unsigned from XDA, etc.? Get rid of all of them, if you do and make sure you ONLY deal with Google drivers.
Click to expand...
Click to collapse
Nothing "fancy" but Samsung drivers, yes.
And getting rid of them is totally out of the question as my S2 and S3 won't work anymore, then.
But everything works now, got the Google SDK drivers for the N7 and the Sammy drivers for the rest and everything looks good
TECK said:
(straight from console, no crazy toolkits)
Click to expand...
Click to collapse
Yeah, that's exately how I do it, adb and fastboot all "by hand".
TECK said:
I know is a ****ty deal, especially if you have lots of customizations on your tablet.
Click to expand...
Click to collapse
All hail to the backups, just restore my data after the wipe :good:
Anyways, thanks for the help, after all it was that link to the tut that got me to install the Google SDK drivers

[Q] Are there any good stable roms for Ideos S7 Fat?

i have an s7 but the fat one not slim.
i was wondering if there were any stable custom roms i could put on it
if some one could point me to a how to or somethign that would be great thank u

Hi, as far as i know, besides stock, only fusion is stable, cm9 and cm10 are not complete stable, lot of thing dont work.
I have a s7-105 and froyofusion is most stable.
Hope it help.
Hal_2000

hal_2000 said:
Hi, as far as i know, besides stock, only fusion is stable, cm9 and cm10 are not complete stable, lot of thing dont work.
I have a s7-105 and froyofusion is most stable.
Hope it help.
Hal_2000
Click to expand...
Click to collapse
could u point me to the tut on how to install the rom?
does it still alow internet access?
are u able to get aps like googlemusic and netflix?

Hi, you must be root, and clockmod recovery must be install, i advice version 6.0.1.
Make a backup of corrent rom, just in case
Copy froyofusion zip file to sdcard, power off, click menu+call(green button)+power on, after reboot in recovery, choose install zip file, again a few minutes and then reboot.
froyo as internet acess, and you can acess the google market, never try to install the programs you said but i have install a lot others with no problem.
Hal_2000

hal_2000 said:
Hi, you must be root, and clockmod recovery must be install, i advice version 6.0.1.
Make a backup of corrent rom, just in case
Copy froyofusion zip file to sdcard, power off, click menu+call(green button)+power on, after reboot in recovery, choose install zip file, again a few minutes and then reboot.
froyo as internet acess, and you can acess the google market, never try to install the programs you said but i have install a lot others with no problem.
Hal_2000
Click to expand...
Click to collapse
would this be the right one?
and when u say clockmod u mean rom manager from clockworkmod?
http://forum.xda-developers.com/showthread.php?t=1099298

imevilbob said:
would this be the right one?
and when u say clockmod u mean rom manager from clockworkmod?
http://forum.xda-developers.com/showthread.php?t=1099298
Click to expand...
Click to collapse
Yep that it , you got it.
Hal_2000

hal_2000 said:
Yep that it , you got it.
Hal_2000
Click to expand...
Click to collapse
where do i get the rom from that thing is really confusing all or most the links dont go anywhere

I also dont know where to get an old version of rom manager
Sent from my SCH-R720 using xda app-developers app