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.

Help: Dont laugh - Bricked my phone

Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance

SysAdmNj said:
Ok so this morning my alarm wakes me up and I noticed I had to unlock my phone to make it snooze, something didnt seem right as my alarm app usually comes up to the front and I can snooze without unlocking my screen. So what do I decide to do half asleep? I decide to reinstall the rom. Here are my steps, and I suggest you dont follow them.
1. Format system
2. Format data
3. Format cache
4. Mount system
5. Reboot phone (Swear this was an accident, as I was trying to navigate to the "install zip from sd card" option)
So my question is ,whats the quickest way to unbrick my phone. It just stays on the "M" boot logo. I found a couple of threads on different sites but want to make sure I"m using the latest method and for the Droid X. Thanks in advance
Click to expand...
Click to collapse
Looks like an SBF is in your very near future.
Go to the Development subforum and search there.
If you have not applied the OTA 2.2 update, you will need the instructions to SBF back to 2.1 and then apply the 2.2 leak, and load your ROM from there.
If you have already done OTA 2.2, there is also an SBF that will restore /system only. It Might save you.
BE ABSOLUTELY SURE YOU DO NOT FLASH the 2.1SBF if you were on OTA 2.2. If you do, it will be game over.
Let us know how you fair.

One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.

SysAdmNj said:
One of the first things I did was the 2.2 ota when I got my phone.
Thanks, I will search there and report back.
Click to expand...
Click to collapse
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.

MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that

MrDanger said:
Can you not get back into Clockwork if you pull your battery?? And they do have a 2.2 sbf that restores your system files.
Click to expand...
Click to collapse
Zaphod-Beeblebrox said:
if you hose /system you won't be able to get back into recovery. Recovery depends on the logwrapper in /system/bin. If it's gone, no recovery boot.
I'm guessing Format System pretty much took care of that
Click to expand...
Click to collapse
Correct, I cannot get back into clockwork recovery.
I can get into android recovery but I cant do much from there.

Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html

SysAdmNj said:
Guys, is the ota 2.2 sbf I need SHADO_X6_2.3.13_SYSTEM-ONLY.zip
found here?
http://rootzwiki.com/index.php/Main-Page/Team-Black-Hat-does-it-again.html
Click to expand...
Click to collapse
Yes. I think that is your only hope at this point. If it doesn't work, I think you are SOL.

I did something very similar to this, flashing the 2.2 System SBF fixed it

I'm back up and running. Thanks people.

good for you man. seriously. just read a couple threads like this. makes me real nervous about flashing roms.

Not nervous since I have insurance
Seriously I caused my issue with a silly mistake. Usually its smooth sailing.

[Q] Updating after I removed bloatware...

Recently I finally got around to rooting my X to get rid of some of the bloatware that is on the phone. I realized about 30 seconds after removing them that I might not should have done that for fear of future updates not installing correctly.
Now today the update has come out and this morning I tried to install it. I thought everything was going fine, the phone rebooted and I got a popup stating that the update had failed.
Can someone please let me know what should be done so that I can get the update? I can't seem to find anywhere what I should do... I don't use any custom ROMs or anything, just the plain system the X came with (well now except for the missing bloatware)
Thanks in advance!

just put the bloatware back and update again

I've currently having the same issue. Is there a way to get the Verizon apps back from the market?

emerica243 said:
just put the bloatware back and update again
Click to expand...
Click to collapse
Well... I haven't been able to find all the individual files for what I deleted... to be honest I don't even remember what all was on there before it was deleted.

I tried doing a restore to factory and that did not work.

The Team Black Hat app has stock images available. Rom Manager's free edition might as well, but I'm not sure off the top of my head.

back up?
did you back up prior to deleting the bloatware? maybe run that back up and then update?

milan616 said:
The Team Black Hat app has stock images available. Rom Manager's free edition might as well, but I'm not sure off the top of my head.
Click to expand...
Click to collapse
How do you use rom manager? I selected the droid x recovery mod but what do i do after that?

I just tried booting into recovery mode and even thats not working. I get the droid with the exclamation mark.

jcha22 said:
did you back up prior to deleting the bloatware? maybe run that back up and then update?
Click to expand...
Click to collapse
Sadly I did not

Look around for the 2.2 sbf and instructions for rsd and booting into the bootloader and not recovery. That should get you back to stock. Or look around for the 2.2.1 (340) sbf that will give you the update. I applied 2.2.1 without reloading the bloatware.

brianf21 said:
Look around for the 2.2 sbf and instructions for rsd and booting into the bootloader and not recovery. That should get you back to stock. Or look around for the 2.2.1 (340) sbf that will give you the update. I applied 2.2.1 without reloading the bloatware.
Click to expand...
Click to collapse
Cool thanks for the idea... so if I can load the 2.2.1 sbf that will put the phone back to the latest version with stock settings again?
EDIT: This method worked and I was able to update. Thanks a bunch!

Does anyone have the City ID bloatware APK that they can post?

andrewsayshello said:
Cool thanks for the idea... so if I can load the 2.2.1 sbf that will put the phone back to the latest version with stock settings again?
EDIT: This method worked and I was able to update. Thanks a bunch!
Click to expand...
Click to collapse
Hi Andrew,
I am in the same position as you and need to get my apps back to stock to enable me to update. Can you tell me if the SBF will actually delete my data and applications, or is it just for the system only?
Also - is it difficult to apply? Finally - where did you get the SBF file from?
Thanks for your help

Android Central...how to reinstall bloatware....sorry I'm unable to submit the link here.It lists all apps.

Android central has a list of all apk's for all apps that came with 2.2. I googled reinsralling bloatware. Sorry I can't post the link, not allowed.

cassiusover said:
Hi Andrew,
I am in the same position as you and need to get my apps back to stock to enable me to update. Can you tell me if the SBF will actually delete my data and applications, or is it just for the system only?
Also - is it difficult to apply? Finally - where did you get the SBF file from?
Thanks for your help
Click to expand...
Click to collapse
It was just the system only. After i completed it all of my data was still there. It was fairly easy i just found some directions on how to flash it via youtube.
Sent from my DROIDX using XDA App

Update zip for 2.3.340

Hey guys, just sharing this with everyone. Maderschramm over at droidforums and droidxforums has packaged an update zip for 2.3.340. It can be used as an alternative to SBFing or to update you if you haven't already.
Install- Make a backup first
1. Download zip
2. Boot into clockwork recovery
3. Install zip from sd
4. Reboot
5. Activate phone
IMPORTANT
BE SURE TO REBOOT AFTER INSTALLING ZIP. DO NOT DO ANYTHING ELSE IN CLOCKWORK RECOVERY PRIOR TO REBOOT. YOU WILL BRICK.
You will lose root, but you will also still have all apps and contacts.
Read this thread prior to doing the install. There's some helpful tips from Maderschramm.
http://www.droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
Mirror 1
http://ubuntuone.com/p/XAk/
Mirror 2
http://www.megaupload.com/?d=4AO672L1

good find. I am going to download and store away for a rainy day ota update. I hate sbf and rsdlite. And although I appreciate all that the black hat does - having to do like 20 (exaggeration) installs in clock work makes me a little nervous.
so good on ya mate.

that's why after i SBF 2.3.320 i always go straight into Android recovery before booting up and Factory Reset there, then boot up. But i guess everybody has there own way of doing things.

Ya, this is an easy alternative to get everyone to a clean 2.3.340. If you're on 2.3.15, 2.3.320, or 2.3.340 this will definetly come in handy.

Wonderful. I just left a stock rom literally today and realized I lost corporate email access with Gummy. That is a deal-breaker and obviously I didn't research it well enough before doing it. I NEED to get back to stock regardless of how painful it is. So this will unroot me, just Z4 again afterwards I take it?

Correct it will unroot and remove bootstrap. So after rebooting then use z4 and grab bootstrap again.

Very nice, thank you! Hopefully I never need to use it!
Sent from my DROIDX using XDA App

Hopefully we wont need to use it, but at least we will feel better about doing this rather than an SBF.

Droid-Xer said:
Ya, this is an easy alternative to get everyone to a clean 2.3.340. If you're on 2.3.15, 2.3.320, or 2.3.340 this will definetly come in handy.
Click to expand...
Click to collapse
I don't know about 2.3.15 When I did it on that, I bricked and ended up having
to SBF to .320 and using the patches to get to .340

forever29 said:
I don't know about 2.3.15 When I did it on that, I bricked and ended up having
to SBF to .320 and using the patches to get to .340
Click to expand...
Click to collapse
Reasons for bricking:
Installing zip as an update.zip
Doing anything else in bootstrap after installing zip
Soft brick (factory reset will bring it back)

Thanks This has saved me more than once while working on cracking the bootloader

Hrmm I ran this directly from having Apex and it didnt like it. Seemed to not fully wipe the phone at all. Im guessing I didnt read something all the way. I simply went to clockwork and loaded the file and rebooted. When it came back my system was still intact, but everything was force closing.

r3dlined said:
Hrmm I ran this directly from having Apex and it didnt like it. Seemed to not fully wipe the phone at all. Im guessing I didnt read something all the way. I simply went to clockwork and loaded the file and rebooted. When it came back my system was still intact, but everything was force closing.
Click to expand...
Click to collapse
Doing a factory reset seemed to put it back to normal

It will update or bring you back to clean 2.3.340. You will lose root and bootstrap, but you will keep all apps and setup.

does anyone have any alternate DL links? it keeps hanging no matter which link I use.

Got it going. Honestly though, who uses Megaupload anymore?
Sent from my DROIDX using XDA App

i won't try to install until file size matches

r3dlined said:
Hrmm I ran this directly from having Apex and it didnt like it. Seemed to not fully wipe the phone at all. Im guessing I didnt read something all the way. I simply went to clockwork and loaded the file and rebooted. When it came back my system was still intact, but everything was force closing.
Click to expand...
Click to collapse
You didn't wipe cache and factory reset before install
Sent from my DROIDX using XDA App

If you don't wipe data/cache prior to install then you will have the same setup and apps, only you will have lost root and bootstrap. If you want a clean start then wipe data/cache then install zip.

WOW Droid X saver
Man this saved my Droid X from sure bricking, thankyou very much uploader

[Q] Stuck on 4.1.2.6--Can Somebody throw me a bone?

Just as a precursor and in advance--I apologize if I missed a thread on this topic here. I searched a number of different times and ways but didn't find any so hopefully I am speaking for others with the same problem with this newly generated one!
So I got a brand new Atrix about 2 days ago and just like every Android I get, I came straight to XDA right after initial boot and a little play-around with it to get the rooting process started . I downloaded the Gingerbreak .apk (I believe it was v 1.0) and rooted with no problem. However, later on while checking the phone out a little more, I stumbled upon the "System updates" section under the "About phone" category in the settings and out of curiosity (and not knowing anything about software updates etc.) thought I'd check it. Well it detected that the 1.57 update was available as the phone obviously came stock with the 1.26 to begin with. So I went and ahead, downloaded it and then attempted an install.
It would get about...oh, I'd say 40% of the way through the install process and then fail (I'm guessing this was the case anyway as the arrow coming out of the package pointing to the android suddenly just turned into the dreaded "!". So I just pulled the battery and rebooted and thought, "Hmm, well it's probably because I've got it rooted--must be something in the system files that's preventing it from pushing the update through successfully."
Next, I figured I'd try a different route and push the update through RSD Lite 5.0. Followed all instructions to a T and just about the same thing happened during install THAT way (i.e. Process failed about 40% or so of the way through).
Following that, I searched to see what unrooting methods were available following the previously botched attempt at a solution. I found a thread mentioning that v 2.0 of Gingerbreak had an unroot option>followed instructions>unrooted (no detected problems there)>attempted to push OTA update again and no dice. Same issue again. I'm both beginning to run out of solutions and am exhausting myself as I usually only have time to do this late at night when I should probably be sleeping (pssh, who needs that, right? )
Anyway, if someone who has experienced similar issues or knows what is going on here could point me in the right direction it would be GREATLY appreciated as I feel like I've got a phone that's not working to it's full potential (after having read what all the updates do)! Thanks a TON in advance for any help!

Save yourself some frustration..
Backup your stuff using titanium backup
Download the stock 1.2.6 SBF
-flash it using RSD lite
-root your phone using gladroot
-update to .57 from your phone (system updates)
-run afterupdate.bat
-update to .83 from system updates again
-run afterupdate.bat
Done.
Restore from titanium backup (batch restore is your friend..)
Sent from my MB860 using XDA App

FYI - you don't need to run afterupdate between 157 and 183 upgrades. Worked fine for me twice.
Sent from my MB860 using XDA App

nsaia said:
FYI - you don't need to run afterupdate between 157 and 183 upgrades. Worked fine for me twice.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I figured that from the part of the script that asks if you intend to update. I did it anyway, it was reassuring to see I still had root before the upgrade lol. Good to know for next time though
Sent from my MB860 using XDA App

Save yourself some frustration..
Backup your stuff using titanium backup
Download the stock 1.2.6 SBF
-flash it using RSD lite
-root your phone using gladroot
-update to .57 from your phone (system updates)
-run afterupdate.bat
-update to .83 from system updates again
-run afterupdate.bat
Done.
Restore from titanium backup (batch restore is your friend..)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thank you kindly sirs (knlgSeeker and nsaia) for the help. Cool. Sounds like a plan. I've already got a backup w/ Titanium on my phone actually (it's always something I keep a copy of on the trusty ext SD) so that should be good to go. Do you by chance have the links for the SBF's you were referring to? I think I might already have the 1.57 one (as I had mentioned in the original post) but I'm sure it wouldn't hurt to post it again. Thanks again in advance!

jz4467 said:
Thank you kindly sirs (knlgSeeker and nsaia) for the help. Cool. Sounds like a plan. I've already got a backup w/ Titanium on my phone actually (it's always something I keep a copy of on the trusty ext SD) so that should be good to go. Do you by chance have the links for the SBF's you were referring to? I think I might already have the 1.57 one (as I had mentioned in the original post) but I'm sure it wouldn't hurt to post it again. Thanks again in advance!
Click to expand...
Click to collapse
No problem..here's all the info/ links you should need:
http://forum.xda-developers.com/showthread.php?t=991072
Just remember, 1.26 is the only one you will need to flash from RSD.. Just do an OTA update for .57 & .83
Sent from my MB860 using XDA App

No problem..here's all the info/ links you should need:
http://forum.xda-developers.com/showthread.php?t=991072
Just remember, 1.26 is the only one you will need to flash from RSD.. Just do an OTA update for .57 & .83
Click to expand...
Click to collapse
Cool. I had actually gone ahead last night and eventually found it myself. Was good to come back though and get some reaffirmation as to whether or not the location I had found and instructions were the correct ones. After clicking on the link you provided I found that it was the exact same thread/post that I had used to do it. So thank you again!
I also had some interesting info to pass along as well. I just thought after flashing 1.2.6 again from RSD Lite that I'd go ahead and just do the OTA updates for .57 and .83 to make sure that they worked and they did. Obviously my concern while going ahead and skipping to those steps was whether or not I'd still be able to get root and I'm happy to report that I was still able to get root after doing so. I just sideloaded the Gingerbreak 2.0 app and it rooted no problems at all! Thanks again for your help guys!
Another random question to throw out there (I figured I might as well just post it in here to see if there's an easy fix: I've got ClockworkMod Recovery on here and I was trying to flash the recovery for the Atrix. However, when the "Confirm Phone Model" comes up, I don't see/find an option for the Atrix. Are we supposed to use a different phone model's version of recovery? Thanks again in advance for any help!

jz4467 said:
Cool. I had actually gone ahead last night and eventually found it myself. Was good to come back though and get some reaffirmation as to whether or not the location I had found and instructions were the correct ones. After clicking on the link you provided I found that it was the exact same thread/post that I had used to do it. So thank you again!
I also had some interesting info to pass along as well. I just thought after flashing 1.2.6 again from RSD Lite that I'd go ahead and just do the OTA updates for .57 and .83 to make sure that they worked and they did. Obviously my concern while going ahead and skipping to those steps was whether or not I'd still be able to get root and I'm happy to report that I was still able to get root after doing so. I just sideloaded the Gingerbreak 2.0 app and it rooted no problems at all! Thanks again for your help guys!
Another random question to throw out there (I figured I might as well just post it in here to see if there's an easy fix: I've got ClockworkMod Recovery on here and I was trying to flash the recovery for the Atrix. However, when the "Confirm Phone Model" comes up, I don't see/find an option for the Atrix. Are we supposed to use a different phone model's version of recovery? Thanks again in advance for any help!
Click to expand...
Click to collapse
All's well that ends well! Not sure what exactly you're trying to flash, but I use Tenfar's CWM..
http://forum.xda-developers.com/showthread.php?t=1019143
It's pretty straightforward, you can boot to recovery in 2 steps
Sent from my MB860 using XDA App

All's well that ends well! Not sure what exactly you're trying to flash, but I use Tenfar's CWM..
http://forum.xda-developers.com/show....php?t=1019143
It's pretty straightforward, you can boot to recovery in 2 steps
Click to expand...
Click to collapse
Sweet. I think I had run into that same thread earlier on (and had actually already installed that same app on my Atrix) and had completely forgotten about it. So thank you for refreshing my memory on it and directing me to it again! Thanks for all your guys' help in general as well!
Got another question for ya: How do you delete all the bloatware off of the phone? I've got Root Explorer and what I usually do is just navigate in like fashion: system>app>and then just delete any of the bloatware apps. However, I've found with this phone that there isn't a single one of the at&t apps found inside this "app" folder. I HAVE found them in the following way however: system>preinstall> BUT there's no way to change how the files found within are accessed (i.e. mounting them as r/w rather than r/o) and so as a result there is no way to delete them. The option to mount the files as r/w is simply not there. Any info on this would be great! Thanks in advance again.
By the way, if you have any questions concerning the Samsung Captivate, I'm pretty knowledgeable about that phone--gained quite a bit of knowledge during the time that I owned it which was probably about 6 months.