Database Users

Uninstalled app causing problems

I recently installed an application called vBar, http://vieka.com/, on my wizard. I decided to uninstall it and now on every start up I get an error telling me that vBar.exe is missing. I reinstalled vBar and uninstalled it, but I'm still getting the same message. Is there a way to remove it from the auto executes?

I don't know the particular app, but you might try checking in your Windows\StartUp directory and see if there is a .lnk file for that app in there. Probably called VBar.lnk or similar. If there is, move it somehwere else and soft reset ... if the error message stops happening then you can delete it. if not it must belong to something else and you should probably put it back.

Thanks. I didn't know it was that easy to change startups. Works great now.

Problem with re-signing cyanmod and dwang

I am a supernewb, this is pretty much my first post; so i apologize if it isn't in the right spot. I am still getting used to the organization!
at any rate, I rooted a few weeks back (love it btw) and i started with cyanmod. used terminal to get rid of amazon and apps i don't use. read somewhere to go in and take them out of the zip, which was a great idea. except i couldn't sign them. then i found the androidmodsign and made an automated terminal command to run it.
eventually i ran into dwang and switched; good stuff also. love the google nav. repacked the zip and signed it.
each time i install my OWN repacked zips, i get the com.process.google.gapps error over and over again. signing it is no problem, everything gets accepted, reboots and works; but i get the gapps error and then on occasion some of my apps give errors.
i used backup for root to get all my apps onto SD. took all those apps and put them in the dwang and cyan zips, and even tried just removing the apps from the zip and installing the backup root apps after install. i ALWAYS get the gapps error.
i've searched for days and days, and just needed to humble myself and ask any ideas?
about me...
TMOBILE
MT3G
using a MAC PRO, but have access to XP
currently have DWANG v1.12, cyan recovery

You could just use a file explorer like root explorer (it is a paid app but worth it) and go into the system folder, hit remount and go into the apps folder and remove them also and save yourself the headache

thanks, i am going to give that a shot.
I'd still like to know, if anyone can help. I tried to put the cyan boot.img with the dwang zip and it hung up at boot. i'd just like to tailor one to what i want, if anyone knows what i am doing wrong.

ok, so i followed 'that guys' advice and paid $2 for root explorer; an excellent investment. backup for root is also great... and free.
anyway, i was going through deleting the apps i didn't want one by one; turns out, the IMProvider.apk was causing my com.process.google.gapps error! needless to say that will be the last app i delete that has Provider in it.
anyone want to let me in on how i can edit that process (google apps process i assume) to rid myself of future problems like this? and or get rid of the IM? also, why can't i change the boot.img with another boot.img?
and thanks 'that guy', not only did i get a program i like but i figured out the problem!

ok, so i followed 'that guys' advice and paid $2 for root explorer; an excellent investment. backup for root is also great... and free.
anyway, i was going through deleting the apps i didn't want one by one; turns out, the IMProvider.apk was causing my com.process.google.gapps error! needless to say that will be the last app i delete that has Provider in it.
anyone want to let me in on how i can edit that process (google apps process i assume) to rid myself of future problems like this? and or get rid of the IM? also, why can't i change the boot.img with another boot.img?
any ideas how i can get inside a widget to make some changes? if its as simple as downloading the SDK and eclipse, i've done that but am having difficulty figuring out how to open them... any help is appreciated.
and thanks 'that guy', not only did i get a program i like but i figured out the problem!

Android Market: instant 'Download unsuccessful' message

Hi everyone,
I'm positing because I have a peculiar issue. I cannot download from the Android Market....and I have tried the solutions on the internet from clearing data/cache to trying to sync my google account in different ways...
Here is the background:
- Bought used Vibrant on craigslist
- rooted, unlocked, then unrooted, then hard reset
- no external SD card
After every hard reset, in two instances now, I have been able to download from Android market SUCCESFULLY for about a ~30 min window. After this time window, any download from Market does NOT work, and after clicking 'Install' immediately goes to the red triangle status 'Download unsuccessful.'
At all times, my internet still works fine, both on 2G/3G/wifi.
Android market website does NOT show my device (is this because the device only works with the very first sync when the phone was purchased??)
Something is locking me out from downloading. It's come to such a stupid workaround that since I know Market WILL work after a hard reset, I do a mass download of my app essentials in the ~30 minutes that I have.
Thanks for any help in advance!

Clear market cache
also, setting proper permissions on /data/ and /data/app might help (with a program like root explorer)

Do you use titanium backup? Restoring any setting? I got similar problem when I freeze "media container" in titanium backup.

Had this problem when z4mod was setting incorrect permissions on /system partition

All,
To avoid the issues with any roms/rooting, I unrooted the phone, as stated in the first post.
I basically got the phone back to 'stock' settings, and I have this issue. Any additional help would be great...this is my first experience with Android and it has only been headaches....
getting nostalgic with my old E71. haha

So, did you use odin to go to jfd?
I'm really interested and willing to help, just santo make sure I understand everything that you've done.
How did you root?
Why no external?

Rooting My TMo Vibrant Using Super Oneclick (A Full Guide)

And every other step you need to transform and gain control of your stock ROM!
Given the fact that T-Mobile and Samsung have made it clear that the Galaxy S Vibrant will not receive Gingerbread, Honeycomb, ICS, or any other functionality update, I made the decision that it was finally time to root my beloved phone.
I didn't want to root for the purpose of trying a ROM for any of the above OS's. I merely figured that since there are not going to be any future updates to my phone, I'm basically on my own. And if I'm on my own then I can and should get rid of the TMo crap software that came pre-installed on my phone (and which can't be uninstalled by any normal means).
Hopefully this process might also help make my phone operate a little faster and cleaner. And in general, the rooting process would give me full control over my own phone. But if you have ever rooted a device the experience can sometimes be challenging, even for tech-savvy folks like me.
There are lots of sites for advice and how-to’s on rooting your Android device, but most of these sites run you through the process in a way that assumes all will work perfectly the first time. There aren't a lot that take you through the root process with at-hand solutions to many of the commonly reported errors.
I've just finished rooting my stock TMo Vibrant, fixing signature/Multi-CSC issues from the root process, installing and using Titanium Backup (TB) PRO to handle bloatware, and finally installing ROM Manager for the purpose of installing ClockworkMod Recovery (for creating and restoring backups of my current ROM). WHEW! And while it's all fresh in my mind, I'm writing it all down to share the process with you so that it's all in one convenient place.
Let’s Start With Rooting The Phone By Using Super Oneclick
After doing some reading in the XDA forums and a few other places, I wanted to try rooting with a one click option. There are many out there that are available for use. But the very first issue that plagued my rooting process was the incompatibility of many of these root installers with my home Win7 64bit pc.
I tried downloading and extracting various recommended solutions that use the "one click" functionality (Super Oneclick--various versions with and without drivers, Galaxy S One Click Root, and Vibrant One Click Root). I also downloaded and installed AIO Vibrant Toolbox, a program which also features a “one click” method for rooting a Vibrant once it has been installed on your pc.
What many posts on rooting never really mention with these methodologies is that you might have issues running the programs on a Win7 machine, which was my issue. Not all Win7 machines, but some. I downloaded the zip file for each with generally with no issue. * But once I tried to run the exe (best done via "Run As Administrator"), I got the following error message on virtually all of them:
"CLR Error: 80004005 The program will now terminate"
AIO Vibrant Toolbox wasn’t any better even though it was an installed program. It terminated as well.
(*NOTE: Anti-virus programs will mistake parts of the root zip files for Trojans, usually quarantining them after download. You are then left with the uncomfortable choice of turning off your anti-virus and taking that chance, or looking for another zip solution. I opted for the latter. Never take a chance with a Trojan!)
These errors messages did not show up on my work pc which is also Win7 64-bit. But that was no comfort as most of my root work was going to be done at home. After much searching on the internet, I read a random post that mentioned two helpful suggestions:
Use a rear or powered USB port, not a front port (because they often can’t power the root install sufficiently)
Use Super Oneclick v1.7 as opposed to any newer versions. The newer versions can cause problems with this particular Galaxy S root.
Two simple suggestions that made a world of difference! The root process worked smoothly afterward, and was finally a "success".
Reminder - Remember to put your phone into USB Debugging mode for the root process, and don’t mount the external SD card when attached.
Along the way to “rooting” you might be confronted with messages about your Samsung drivers for your phone. You may see messages like these:
Device drivers not found
Samsung android USB composite device failed
A quick search on these forums will yield updated drivers for your phone. The successful install of these drivers can also be a function of using the proper USB ports, as in the situation above. The installation of Samsung drivers failed on the front USB ports of my Dell. Success was again found using the rear ports. The main point here: use the rear ports (or powered USB ports) no matter how much of a pain it is maneuvering under your desk and behind your pc!
You’re Almost There…Kinda!
You can check to see if you are successfully rooted by checking to see if Superuser is installed in your apps. It was there… whew. The next step was to install Titanium Backup so that I could have root control over my apps, allowing me to delete bloatware that was slowing my phone. I downloaded TB from the Market, opened it, tried to give it Superuser permissions, and was notified with an error message that permissions were unsuccessful because the phone was not rooted. WHAT???
More online research revealed that I had achieved a “soft root”, whereby you have successfully rooted your phone but you don’t have all root permissions because the install wasn’t complete. The solution? Basically you just have to keep doing it more than once. All steps of this process seem like they will take the first time if you do what you are supposed to do. But more often than not, you have to repeat your steps over and over to make sure that it takes. After two more Super Oneclick rooting attempts, TB finally gave me the thumbs up for root.
Some may say it’s not necessary, but I upgraded to TB PRO. It allows for more options and better functionality with the apps and system data on the phone. And really, at about 6 dollars it is more than worth the price. Heck, two Starbucks lattes will run you more than 8 or 9 bucks. So if I can get piece of mind with respect to app management on my newly-rooted phone, 6 bucks is more than worth it.
I immediately wanted to learn how to remove bloatware -- and it’s amazingly difficult to find clear directions on doing so. After my backup of all apps and data, I went to the backup/restore tab and found the programs I wanted to get rid of. Many online users recommend “freezing” an app first to make sure that removing it won’t make your phone all wonky. So after “freezing” the offending apps (by pressing the menu button, selection batch, and then scrolling down to the appropriate section on freezing apps), I long-pressed the desired app and only saw one option for uninstalling via an exploit. I selected it and long story short, it failed. As the phone boots to stock recovery, this message popped up:
E:failed to verify whole-file signature
E:signature verification failed
Applying Multi-CSC Installing
Multi-CSC Installation Aborted​
In simple terms, the rooting tool (Super Oneclick) doesn’t contain all of the necessary items for a complete root. A fix is needed for the invalid signature problem that will help you get to a full root state. Fortunately there are fixes out there you can find for this particular fix.
Here are some helpful links:
http://androidforums.com/galaxy-s-a...iled-installation-aborted-one-click-root.html
http://forum.xda-developers.com/showthread.php?t=1052991
Read the instructions for the fix on the first page, but get the correct file from the second page as the link for the fix from Dropbox is a little messed up in the first URL. The second URL has the correct link. Use the automatic method so that you don’t have to use the terminal emulator. If you are like me, this process has already given you more gray hairs than you would really like to admit. So take the easy route.
Run the install.bat file and you will be fine. When you reach stock recovery again remember to reinstall all packages. This will make sure that the fix is installed properly. I didn’t know that was needed and was wondering why the fix wasn’t taking initially. So I’m sharing this with you to head off your frustrations at the pass. ;-)
Getting Rid Of The Bloat
Check to make sure that you are fully rooted by opening TB. It will automatically take Superuser permissions from the first time you allowed it IF you are rooted. If not, it will tell you. And by now you should be rooted. Heading back to the bloatware, I was able to figure out that the “long press method” was not the correct one for uninstalling apps.
Once again, press the menu button (bottom left) and select batch. Scroll down and you will see a section for uninstalling apps. Select uninstall user and system apps, and make sure to DESELECT ALL before you do anything else. From there you can pick and choose the apps to uninstall, then “run the batch operation” to complete the task. Bye bye bloatware!
The last crucial step to complete now that your phone is rooted is to make sure that you have a backup of your current ROM and configuration. The backup you created using TB is only for apps and data. It is not a backup of your current stock ROM.
Nandroid backup works best for the purpose of backing up and restoring ROMs. And if you have done any previous rooting on an Android device, you will recognize that Nandroid is a function of ClockworkMod Recovery. Sigh. I know... frustration starts to set in as you realize that there is yet another necessary install needed for a totally successful root process ON TOP OF and AFTER everything else you have had to do. So what is the next step?
ROM Manager To The Rescue
Install the free ROM Manager from the Market and you will be good to go. This app allows you to flash CWM Recovery as well as mount various ROMs on your phone. After installing the app (and declining the various offers that pop up), press “Flash ClockworkMod Recovery” at the top of the menu. It will cause the phone to reboot. And CWM will be downloaded…but not installed. To install after reboot, open ROM Manager and now select Reboot into Recovery. It will challenge you with a question on whether you really want to do this or not. Say Yes.
Important: This is another one of those places where it’s not intuitively obvious what to do for CWM Recovery.
When I first rebooted into recovery I didn’t see any changes from my stock recovery menu…because there were none. What I needed to do (which I found in yet another forum posting) was again to select Reinstall all packages. CWM had been downloaded and was ready to install… this would do so.
Happily, the phone went into Clockwork recovery*immediately after "Reinstall all packages" . If it wasn't clear earlier, use the volume buttons toggle up (or down) to select backup/restore. *You can then implement your selection by pressing the power button on the right side of the phone. On the next screen select backup, and then let it do its’ thing. It may take a while to complete, but will be well worth the time and effort if you have any future problems.
The Entire Process Is Finally Complete
So there you have it. In a nutshell, here were my steps:
1. Samsung drivers
2. Super Oneclick v 1.7
3. E. Signature fix
4. Titanium Backup PRO
5. ROM Manager (free version)​
Use the rear USB ports or powered USB ports for the phone connection. Phone should be in USB debugging mode, and external SD card should not be mounted. For each process, it may take up to 2 or 3 attempts for successful completion. So keep trying after the first FAIL message. When applicable, “Reinstall All Packages” to make sure that downloaded files are actually installed.
And lastly, if absolutely nothing works correctly for you, PLEASE PLEASE PLEASE use Google for help. Many others have successfully worked through all of the problems you might encounter that aren’t listed here. Actively use Google to help find solutions to any problems, using the exact error messages shown and adding in your phone type. You will be amazed by the depth of experience out there that can help you.
Above all else, keep up a good attitude. Rooting might be a pain in the ass while you are doing it, but it’s for a greater purpose. My four days of rooting have now given me a phone that is FREE from all the bloatware that bugged me for the past two years. And soon I’m sure I will experiment with a different ROM. But for now I’m just happy that I have my phone, my way. After all, if they (TMo and Samsung) aren’t going to make our phones better, we can do so for ourselves.
Good luck, and I hope this complete set of instructions from my own past 4 days of experience will help someone else!

A good read. A few things though with the Titanium part.
First I whole-heartedly agree to kick down the $ for the Pro. It really ups the functionality of the app and what all it can do.
The part about "freezing". This part is tricky b/c you need to make sure he apps that you are freezing are indeed bloat and not something that is needed for something else (i.e. did you know that GTalk directly effects the market on some ROMS). I don't use Gtalk but I still have it installed and frozen so I can defrost at will. This is the reason for Freeze. It lets you know of any adverse effects on your ROM, other apps,...then you have the option to defrost if need be. I also always avoid doing anything in "Batches" on TBPro, as it can sometimes be a little wonky, especially when restoring batches, causes reboot and freezes resulting in batterty pull.
I freeze for at least a week on new ROMs so that I get the full experience with daily life to make my determination on uninstall, defrost or wait longer.
Another way to do it is once you know the apps that are frozen do not effect any other parts of your ROM, you can back them up with TBpro for later use and uninstall or you can do it this way. Since you have root, go into /system/app or and pull the APK out and put it in a folder or something like that on your SD card. You would do this to some of the /system apps that TB shows as only haveing a checkmark next to and not the yellow/orange circle with the M in it. If you uninstall these with the checkmark you will not be able to restore them b/c part of the executable portion of the APK is not able to be backed up. This is the reason to pull the app out of /system/app and put it on your SD card. Hit menu, more, Clean up Dalvik cache and viola!! you have some free space on /system and the offending APK's dex will be deleted too.
Sidenote: I have never been able to get SuperOneClick to work on any phone I have ever tried. Maybe I'll unroot and try again but the SU exploit is a flashable zip located here. Option A. Put it on your SD card, boot into recovery and Bam!!! you are rooted
Nice work though.

Where can we still get Super Oneclick v 1.7?

http://forum.xda-developers.com/showthread.php?t=739300 make sure you have ADB turned on and use the USB ports from the back not front

too lengthy.

Just got vibrant
Sent from my SGH-T769 using xda app-developers app

Sent from my SAMSUNG-SGH-I317 using Tapatalk
Delete..

[Q] 9 more attempts before device gets wiped issue

A co-worker and I both have a Verizon Note 3. They both are running Bajarom. We both followed the same steps to root and install it. The only thing I can find that is different about the phones is that I have the Galaxy Gear and it does the auto-lock thing on my phone when the gear is out of range. And we may have some different xposed modules/configs enabled.
However, my device gives the warning about wiping all the data when I enter the unlock pattern wrong. My co-worker's phone does not. I would really like to get rid of this because there is to much of a possibility of my young daughter of playing with the lock screen and wiping my phone.
Can anyone tell me how to get rid of this scary thing? What I have tried so far (all without effect):
1)Tried with android device manager as device administrator and without. Currently not set as device administrator.
2)Switched lock screen to swipe instead of auto-lock.
3)Created a Tasker task to take picture when >1 unlock attempt is made (using secure setting module for profile).
Thanks.

Am I the only one? I can't find much info about this anywhere. All I find are unhelpful posts such as this one: http://forum.xda-developers.com/showpost.php?p=48590347&postcount=23
I can't seem to get rid of this thing.

iherbivore said:
Am I the only one? I can't find much info about this anywhere. All I find are unhelpful posts such as this one: http://forum.xda-developers.com/showpost.php?p=48590347&postcount=23
I can't seem to get rid of this thing.
Click to expand...
Click to collapse
I don't know if you can get rid of that or not. Kinda weird that one phone has it and the other doesn't. Since you're running Baja you could always PM him directly and see if he knows what's going on. He's pretty down to earth and doesn't have a Dev God Complex. In the meantime do you use Titanium Backup? I would just use this, make a Titanium folder on your external sd card, TIBU will install inital backup folder on your internal. Got into preferences and point Tibu to your external sd card folder. Make a batch backup of your user apps, not system apps. Go through and backup anything it might not have manually, for example if you have bookmarks in chrome batch won't back that up you have to do it manually. Then if your phone gets wiped by accident everything is still on your sd card and just restore with tibu. Honestly anyone flashing roms should have this app, it's priceless. Hope this helps for now.