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.

himem rooted users seems to be unable to flash froyo?

Ok i've found few guys here to have the same problem like me and they all seem to have rooted with the himem option
we all get that when trying to apply the update.zip
"
assert failed: apply_patch_check("/system/lib/modules/bcm4329.ko" . "e594389935893859358938")
E:error in /sdcard/update.zip
(status 7)
Installation aborted.
"
im with stock rom, update1
hopefully someone will be able to guide us through

i was rooted with hi-mem. froyo went without a hitch.
i wiped everything except my sd:ext partition though

timothydonohue said:
i was rooted with hi-mem. froyo went without a hitch.
i wiped everything except my sd:ext partition though
Click to expand...
Click to collapse
I did the same exact thing and everything also went perfectly fine for me.

hm i tried only without wipe, i guess ill wipe now... uh

I had himem and rooted and did a full wipe before installing. no problems

r34p3rex said:
I had himem and rooted and did a full wipe before installing. no problems
Click to expand...
Click to collapse
did you get any error before trying with wipe?

I tried updating without a wipe and the phone was unusable, I couldn't even get passed the lock screen, did a full wipe and reinstalled update and it works fine now. I still went back to cm though cuz I'm waiting for theming and some of the other apps I use aren't updated to work yet.

Fking1 said:
did you get any error before trying with wipe?
Click to expand...
Click to collapse
just wipe it. what's the problem? it takes about 2minutes to do

need help
Newb here to Nexus one... what do you mean specifically by "wipe"

ok im about to wipe it, but cause im android new let me just make sure
that titanium backup program, i ran, it makes full backup on the sd card right?
and after the wipe and update, i just reinstall titanium and import the backup from the sd card right?
and it will recover all apps+their data+ system/settings data?

drworsley said:
Newb here to Nexus one... what do you mean specifically by "wipe"
Click to expand...
Click to collapse
you will need amon_ra's recovery program. if you don't know what i'm talking about, you probably don't need to worry about it, because you probably aren't rooted, or more likely, even that you even have an unlocked bootloader(which will prohibit you from even installing). read up in the dev section before you even start messing around with this and waste your time, and possibly brick your phone.
Fking1 said:
ok im about to wipe it, but cause im android new let me just make sure
that titanium backup program, i ran, it makes full backup on the sd card right?
and after the wipe and update, i just reinstall titanium and import the backup from the sd card right?
and it will recover all apps+their data+ system/settings data?
Click to expand...
Click to collapse
theoretically, except i believe that froyo won't see your ext partition if you were using apps2sd before. i'm not positive. i've only put on the very basic apps i absolutely need, because i'll be putting enom's froyo version as soon as it lands and i don't want to waste my time. so, i didn't use titanium backup.

did anyone got a file signature error when trying to flash without a wipe?

I wiped and flashed, restored and flashed without a wipe. All installs ok, but I can't install anything, it all hangs at "installing". Seen others say this is a bug, but it is never there.

I was able to load it right over CM version I was using and have had only one problem, which was it couldn't find my location so I'm doing a wipe and flash as I type this.

Fking1 said:
did anyone got a file signature error when trying to flash without a wipe?
Click to expand...
Click to collapse
if you were rooted, use paul o'brien's (modaco) zip, if not, use cyanogen's and follow his instructions. paul's is signed. if you're getting an error, check the md5 hash and make sure your download wasn't corrupted

seems that the problem is that the default recovery tool only works with google signed updates
and if you are rooted you have to use developer update, so you gotta use another recovery tool as well, like amon-ra
gotta flash this one now

NO froyo builds are stable on my nexus one.

I'm serious. It's slow everything force closes and I figured now that cyanogen had his new build of Froyo....I could give the kang o rama a try. but everything is still force closing and I have no idea how to fix it and I'm about ready to just give up :/
What do I do?

Are you completely wiping everything before you install a rom?

Give yourself a wipe, or at least a cache partition wipe
Sent from my Nexus One using XDA App

if its slow then something is using a large amount of cpu power.
I just caught Flickie doing it (thanks to CPUStatusLED)....but it stopped before i got to uninstalling it.
Backup your apps, wipe everything data, ext, cache..then install a ROM.
My phone was freezing/rebooting 3-10 times a day before I did the above and now its quite stable.

EVERYTHING has been wiped. Dalvik, cache, Factory reset, everything I could do without doing anything to the SD card.
I'm seriously at a loss for words.
Currently on kang o rama's 2.2 cyanogen build A2 btw is what I'm trying to work with. Though it has been no different for other roms. I Mean it's so unresponsive and always force closes everything

2.1 works ok ?
2.2 doesn't you say? after all wipes and a clean install of Cyanogen and other ROMs? How about stock Froyo FRF91?
It may be a hardware error if the stock one doesn't work. So even if you got an unlocked phone, Google/HTC should replace it because it's hardware. If you're installing it wrong SOMEhow.. then that's another story.

EDIT: NVM believe I found it

I just went through this.
Just download the PASSIMG.ZIP from the latest Eclair build and put it on the root of your SD card. Go into bootloader and it will automatically pick it up.
In a minute you'll be at stock Eclair. By the time you can get into the Settings menu, you'll have the majority of FRF91 downloaded. Let it do its thing and probably within 5 minutes you'll be sitting pretty on a stock FRF91 Froyo build.
http://lmgtfy.com/?q=passimg+eclair
First link

If you've used the Froyo App2SD function, then you might need to delete your .AndroidSecure folder on your SD card after a flash.
I never touched that folder and the last few times I flashed a ROM I was getting weird problems where I couldn't install things, it would hang, I would get FCs, etc. I deleted that folder, rebooted, and everything was cleared up for me.
...Of course you'll have to install those apps again.

mudrock1000 said:
I'm serious. It's slow everything force closes and I figured now that cyanogen had his new build of Froyo....I could give the kang o rama a try. but everything is still force closing and I have no idea how to fix it and I'm about ready to just give up :/
What do I do?
Click to expand...
Click to collapse
Have you installed the latest radio image? Even if you have give it another flash. I had the same problem on my Hero

mindfrost82 said:
If you've used the Froyo App2SD function, then you might need to delete your .AndroidSecure folder on your SD card after a flash.
I never touched that folder and the last few times I flashed a ROM I was getting weird problems where I couldn't install things, it would hang, I would get FCs, etc. I deleted that folder, rebooted, and everything was cleared up for me.
...Of course you'll have to install those apps again.
Click to expand...
Click to collapse
Yea thats a good idea. The short time I've been on Android, it seems like A LOT of CRAP gets brought into new builds. Everytime I flash a new rom, the Market downloads all the crap from before. lol.
While I can see it as being a nice feature, it can get troublesome. When my replacement Nexus comes tomorrow, I'm going to backup my APK files and format my SD card. Start completely from scratch on Froyo 2.2

Usually I have NO problem hunting for things myself...but I DO NOT AT ALL...see this "Passimg" in that thread.
ANYWAYS I'm gonna try reflashing the radio to see if that helps

This is why I just use stock stuff, I want my phone to just work

khaytsus said:
This is why I just use stock stuff, I want my phone to just work
Click to expand...
Click to collapse
Foo Stock dun work .
Anyways good news...I've gone more then a few minutes without it crashing. . I think the radio think might actually have worked.
Wait market crashed. I'm hoping it's just a thing and I'm gonna reboot and try again.

Nope just more Force Closes
Tell me about this passimg.

mudrock1000 said:
Foo Stock dun work .
Anyways good news...I've gone more then a few minutes without it crashing. . I think the radio think might actually have worked.
Wait market crashed. I'm hoping it's just a thing and I'm gonna reboot and try again.
Click to expand...
Click to collapse
And you're sure your N1 isn't defective?

Other then the occasional data connection failure...yea Eclair worked perfectly.
And sriously...guys I need the effing stock rom image I wanna try something else BUT I don't have it.
Oh yea. AND NOW I'm trying to reinstall the apps but it says out of space...and I can clearly see I have 111 mbs of internal storage. I think it's installing it on the SD card. IDK HOW TO MAKE IT STOP and I'm so frustrated I'm about ready to dump my n1. I've been screwing with this forever and I was excited. The first build of Cyanogen and nothing works...

mudrock1000 said:
Other then the occasional data connection failure...yea Eclair worked perfectly.
And sriously...guys I need the effing stock rom image I wanna try something else BUT I don't have it.
Oh yea. AND NOW I'm trying to reinstall the apps but it says out of space...and I can clearly see I have 111 mbs of internal storage. I think it's installing it on the SD card. IDK HOW TO MAKE IT STOP and I'm so frustrated I'm about ready to dump my n1. I've been screwing with this forever and I was excited. The first build of Cyanogen and nothing works...
Click to expand...
Click to collapse
Wipe, install rom, reboot and hold volume down to load the bootloader, power off in bootloade, pull battery, remove microsd, replace battery, boot and set it up. See what happens.

you might just have a faulty hardware (bad ram or something)

norazi said:
you might just have a faulty hardware (bad ram or something)
Click to expand...
Click to collapse
I'm betting it has something to do with data saved on the sd. . .

Apps Keep Appearing After Flash ... But I'm Not Connected.

I have been moving my Hero from Sense -> Vanilla.
But, after wiping, flashing, rebooting, there are some apps, like ASTRO, MyBackup, aNetShare, and Springpad, for example, that are already there after first boot.
And before anybody says that Android is backing them up, I'm not connected to any account!
How can this be?

It may already be installed in the ROM you flashed

I've found the same thing whilst benchmarking. I'll wipe everything flash a new rom to benchmark and the benchmark apps will install themselves on first boot. Something I'm as yet unable to explain. Having said that i've experienced no issues with this the two times it has happened (out of at least 10 different rom wipes) and all the apps have worked as they should.

sebxd said:
It may already be installed in the ROM you flashed
Click to expand...
Click to collapse
Is CMH 1.4.1 ROM. I do not think CMH has Springpad, and much less MyBackup Pro, does it?

btdag said:
I've found the same thing whilst benchmarking. I'll wipe everything flash a new rom to benchmark and the benchmark apps will install themselves on first boot. Something I'm as yet unable to explain. Having said that i've experienced no issues with this the two times it has happened (out of at least 10 different rom wipes) and all the apps have worked as they should.
Click to expand...
Click to collapse
Same here apps work fine. But that is not the point I'm getting crazy understanding where they are.

Did you wipe EXT as well?

wywywywy said:
Did you wipe EXT as well?
Click to expand...
Click to collapse
By EXT you mean Linux partition? Cause if that, i have no linux partitions on the card ... or not that i remember ... would have to check back if that is the case.

kwanbis said:
By EXT you mean Linux partition? Cause if that, i have no linux partitions on the card ... or not that i remember ... would have to check back if that is the case.
Click to expand...
Click to collapse
Should say "Wipe SD:Ext" in recovery. That's where all apps are installed if you use Apps2sd...
Full wipe usually means Data, Dalvik, Sd:Ext.

ante0 said:
Should say "Wipe SD:Ext" in recovery. That's where all apps are installed if you use Apps2sd...
Full wipe usually means Data, Dalvik, Sd:Ext.
Click to expand...
Click to collapse
I did a factory reset, dalvilk reset, but i did not do a SD:Ext, as i do not remember having a partition.
But now that you mention it, it could very well be the case.
I would check as soon as i get the phone home.
Thanks.

Weird sbf?? getting ready for fission..

ok, im confused....i just sbfed to get ready for this rom and once it finally booted back up i still had my old wallpaper on it, still running launcherpro and i get the message saying that dx overclocker was going to app ly the overclock in 90 seconds and so on. it did have the stock status bar and so on. but what i did right away i just did a factory reset and wiped cache in the recovery screen and now i seem to be back to factory..i just checked and dont have root..is this normal operation for sbf?

yeah, the sbf takes you back to factory stock, no root. it is just like it's fresh from motorola's oven

akanealw said:
yeah, the sbf takes you back to factory stock, no root. it is just like it's fresh from motorola's oven
Click to expand...
Click to collapse
But the weird thing is after sbf still had my apps and settings..had to wipe in order to get it all factory fresh.

Are you sure you did a full sbf rather then the system sbf. Full sbf should wipe all data along with system.
Sent from my DROIDX using XDA App

deadlyv2 said:
Are you sure you did a full sbf rather then the system sbf. Full sbf should wipe all data along with system.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
This is the file I used, VRZ_MB810_2.3.15_1FF_01.sbf. It came from rootz wiki in a folder called the gift2. Is it the same thing after I wiped the data and cache or do I need to figure out how to get a full sbf?

jredecop said:
This is the file I used, VRZ_MB810_2.3.15_1FF_01.sbf. It came from rootz wiki in a folder called the gift2. Is it the same thing after I wiped the data and cache or do I need to figure out how to get a full sbf?
Click to expand...
Click to collapse
Hmmm..just did it again. Same thing

jredecop said:
This is the file I used, VRZ_MB810_2.3.15_1FF_01.sbf. It came from rootz wiki in a folder called the gift2. Is it the same thing after I wiped the data and cache or do I need to figure out how to get a full sbf?
Click to expand...
Click to collapse
that is the full sbf. after you've successfully sbf'd, you have to boot into recovery and do a wipe data and cache. that will complete the process of returning it to stock.

akanealw said:
yeah, the sbf takes you back to factory stock, no root. it is just like it's fresh from motorola's oven
Click to expand...
Click to collapse
razorloves said:
that is the full sbf. after you've successfully sbf'd, you have to boot into recovery and do a wipe data and cache. that will complete the process of returning it to stock.
Click to expand...
Click to collapse
Ok all is normal then! Thanks guys

Thanks for taking the time out to do that. I highly suggest that anyone who is having weird problems like slide reboot, battery manager FCs and whatever weird stuff some people have reported to SBF. I know it is a huge pain in the butt. It may help with some of those weird bugs that some users have and if you do want to track down the slide to unlock problem it will help with that too. The slide reboot problem has been something found in the stock ROM and other custom ROMs so it is not unique to this ROM. If we all work together maybe we can find what is causing it.
If you anyone would like to test what could be the final build of 2.0.1 ROM then please join us on IRC... http://webchat.freenode.net/ #teamdefuse & #fissiontest
Thanks!

Angdroid said:
Thanks for taking the time out to do that. I highly suggest that anyone who is having weird problems like slide reboot, battery manager FCs and whatever weird stuff some people have reported to SBF. I know it is a huge pain in the butt. It may help with some of those weird bugs that some users have and if you do want to track down the slide to unlock problem it will help with that too. The slide reboot problem has been something found in the stock ROM and other custom ROMs so it is not unique to this ROM. If we all work together maybe we can find what is causing it.
If you anyone would like to test what could be the final build of 2.0.1 ROM then please join us on IRC... http://webchat.freenode.net/ #teamdefuse & #fissiontest
Thanks!
Click to expand...
Click to collapse
sorry, im a newb, how do i download from here?
edit..neverming..install process same as 1.2.1?