Database Info

[Q]APK Backup

i need an app on Android 1.5 which can Backup System apps as APKs.I need to back up the Google apps(Market,gmail etc). Please tell me of an app that can do this and tell me if i need to root my device.
Thanks

You need to root your phone then you can use either SU file manager $1.97 or Root explorer(file manager)$4.00
You need to root it because generally you need super user permissions to manipulate system/app files.
It may be worth it to try a free app that is used for file managing (it will be a related app to the above stated) To attempt to copy the apk file to another location.
Hope that helps
EDIT >> not sure of whether or not those apps are on andriod 1.5 marketplace.

If you don't want to shell out the cash, I believe the free Root Uninstaller (which als requires root permissions) can backup any installed application as an apk or configured to perform backups automatically anytime an app is installed or updated.

[APP] Get your Old Android Market Back

You know what distinguishes a good the from the from a bad on? The good one spend his time is helping others, while the bed one spend his is time consolidation power
There are no stupid question, every question is a quest for knowledge..Knowledge flows freely here at XDA! ask and ye shall b answered.
ThaNx to all the member that TEAM AD with the various tips and trick for this post I walk away, but my knowledge increased by the experiences shared with is wonderful group people. Long Live Android!
Installation:
1. Download files below, do not rename them! Transfer to SD Card.
2.* Use any file explorer and mount system as RW and delete file name (Root Explorer works nicely)‘Vending.APK’ and ‘MarketUpdater.apk’ from /system/app/. You can also delete folders com.android.vending and com.android.vending.updater in /data/data.
*Do a reboot.
* Open File explorer/ Root Explorer and Mount your file system as RW and copy ‘updater.apk’ from SD Card to /system/app/ and do a reboot.
* Now, mount your file system as RW from explorer and copy ‘market.apk’ from SD Card to /system/app/ and Reboot phone.
Edit: I feel retarded.. forgot to mention that this method is iffy on my rooted stock ROM, but it works great on my rooted custom rom.
[B said:
acolwill[/B];16952837]What functionality? All I see is fancy graphics designed for children and iRetards, there's no discernible change in how apps are grouped or searched for since version 2.12.
I have 5 android devices ranging from the HTC Hero up to the Samsung Galaxy Tab and the new market looks **** on every one. Application presentation is marred with oversized text and incessant scrolling, making it slower to actually see information pertinent to what you are looking at. Emphasis should be on the applications contained within the market, not the market application itself.
Other than that, the obfuscated way that application permissions are presented to a user in the newer versions makes it far too easy for the layman to install things with less than honourable permission requests. At least in version 2.12 you HAD to move your fingers around to accept permissions, since then all it takes is two jabs with a finger with little or no perceived consequence.
The fault lies with Google for forcing the new market style on users, no choices outside of root&destroy.
So thanks for actually taking the time for making the Google apps look nice, just let those whom want the 'clean' version have their say.
--
The attached Vending.apk is the "old" market. In order to install it, you must be rooted and you need either a little knowledge of ADB or Root Explorer from the market.
Using ADB;
Reboot into recovery and plug into pc, mount /system using your recovery
From your preferred ADB console:
adb push Vending.apk /system/app
adb shell rm /system/app/MarketUpdater.apk
adb shell chmod 644 /system/app/Vending.apk
adb shell chown root.root /system/app/Vending.apk
Reboot.
Using Root Explorer;
Download apk to sdcard
mount /system rw
browse to /system/app
remove MarketUpdater.apk
remove Vending.apk
browse back to sdcard and copy the Vending.apk to /data/local/tmp
copy the Vending.apk from /data/local/tmp to /system/app
using permissions action, set permissions on Vending.apk [Owner: Read Write. Group: Read. Others: Read]
using set owner action, set owner to 0 - root, group to 0 - root.
Close and reboot.
The Root Explorer method may not work for all phones, and will not work on HTC phones which do not have s-off. The ADB method should work on any rooted device which previously had market access.
Click to expand...
Click to collapse
[B said:
here.david[/B];16956089]Thanks that worked BTW, on the Vibrant (MiUi) here is the command I used to mount without going into CWM....
From your preferred ADB console:
adb shell mount -o rw,remount -t ext4 /dev/block/stl9 /system
adb push Vending.apk /system/app
adb shell rm /system/app/MarketUpdater.apk
adb shell chmod 644 /system/app/Vending.apk
adb shell chown root.root /system/app/Vending.apk
Reboot.
Click to expand...
Click to collapse
[B said:
nygmam[/B];16959137]I use a simple method, which works very well, and so far has not had a down side:
1) Using Titanium Backup (Or another app that lets you do this) either Freeze (Paid app) or Backup, then delete Market Update (Free App)
2) Go to Settings, Applications, Manage Applications, and scroll down to market, and select
3) Uninstall updates from Market
This is very easy to do, and you may be able to use other freeze or backup apps to achieve the same result. Also note, no reboot required.
Click to expand...
Click to collapse

I use a simple method, which works very well, and so far has not had a down side:
1) Using Titanium Backup (Or another app that lets you do this) either Freeze (Paid app) or Backup, then delete Market Update (Free App)
2) Go to Settings, Applications, Manage Applications, and scroll down to market, and select
3) Uninstall updates from Market
This is very easy to do, and you may be able to use other freeze or backup apps to achieve the same result. Also note, no reboot required.

Why would anyone want to do that? To put it in a different way: What are the advantages of the old market?

Thanks man, the new market sucks...

For some people the new market lags a lot especially on lower end phones, the last version was terrible for me so I had to use the old one but this latest update is a huge improvement, so i'll stick with it.
Sent from my HTC Wildfire using XDA Premium App

If you change the density of your phone's display, you wont't be able to download many apps(shazam free for example). It says that your device is incompatible, that's why I reverted back to the old market.
Sent from my HTC Desire

new market sucks..it lags on older phone

Agreed. Installed it, and soon had to restore old version from backup!

Any chance this will work without root? My wife hates the new market.
Sent from my ADR6350 using Tapatalk

QBall45 said:
Any chance this will work without root? My wife hates the new market.
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
Have you given a brief look at the benefits of root vs stock? Well worth it.. Just a little research about rooting your particular phone and you can do it quite simply

i just downloaded the old market apk again and replaced it over the new one , and it worked , i have samsung galaxy s2 ,but still the new market is slow

I use a simple method, which works very well, and so far has not had a down side:
1) Using Titanium Backup (Or another app that lets you do this) either Freeze (Paid app) or Backup, then delete Market Update (Free App)
2) Go to Settings, Applications, Manage Applications, and scroll down to market, and select
3) Uninstall updates from Market
This is very easy to do, and you may be able to use other freeze or backup apps to achieve the same result. Also note, no reboot required.

shadows of yesterday said:
i just downloaded the old market apk again and replaced it over the new one , and it worked , i have samsung galaxy s2 ,but still the new market is slow
Click to expand...
Click to collapse
If you don't delete or disable Market Updater, new market will return... Maybe not right away, but it will be back. Also no need to reinstall old market, it is still on your phone. Just see my post above on how to uninstall the updates to market (Step 2 and 3), just uninstall updates, and go back to market, accept teh T&C and you will be back using old market again.

This worked for me ONLY after following the steps in OP and:
1. Changing the permissions of both files to rw-r-r
2. Renaming market.apk to Market.apk
3. Renaming updater.apk to Updater.apk

I think you'd need to 'chown root.root' on both files too...

GRRemlin said:
This worked for me ONLY after following the steps in OP and:
1. Changing the permissions of both files to rw-r-r
2. Renaming market.apk to Market.apk
3. Renaming updater.apk to Updater.apk
Click to expand...
Click to collapse
Maybe the mods can add this bit of info to the first post. Thank you!

You can edit it (or should be able to)

hello.
i'm using an xperia x10 mini E10i, and just did those steps. My market dissapeard, and now i don't know how to install it back( i didn't make a backup of the apks i deleted =( ). Can you please tell me what should i do?
I also tried GRRemlin's version and still doesn't work.
Thanks in advance.

li9ht said:
new market sucks..it lags on older phone
Click to expand...
Click to collapse
after themeing the market for the last five versions i would have to say the new market adds fuctionality over the old.
sounds like your blaming google for having a slow outdated phone.
still a good post though for those that like the look of the old market

Try restoring your apps and following the directions posted in post 2 it really is easier, and you don't have to mess with chmod and renaming and rebooting.
Sent from my ACA Gingerbread HTC HD2 using XDA App

Good for Enterprise (GFE) [03-7-2014] root workaround

This IS working for 4.3+ using xposed module.
http://forum.xda-developers.com/showpost.php?p=49878296&postcount=679
All credit goes to Phantasm4489. I am only adding the the OP so people can find it.
Below can be used for anything below 4.2 but I still think the xposed module above is better.
Standard Disclaimer:
**************************************************************************************************************
I AM NOT RESPONSIBLE FOR YOU BEING FIRED BY CIRCUMVENTING THE POLICY YOUR IT STAFF HAS PUT IN PLACE. I AM NOT RESPONSIBLE FOR BRICKING YOUR PHONE (ALTHOUGH SERIOUSLY DOUBT IT COULD POSSIBLY DO THAT). I AM NOT RESPONSIBLE FOR ANY DAMAGE WHAT SO EVER. THIS IS FOR EDUCATIONAL PURPOSES ONLY!!
**************************************************************************************************************​
Click to expand...
Click to collapse
First off:
THANKS to sparky for the 'su' binary I use in my newer scripts.
THANKS to chainfire for the 'su' binary I use in my older scripts.
THANKS to Fallon for helping fine tuning the directions.
This thread is dedicated to using GFE on rooted devices. My intent is to understand root detection schemes for my own personal education. If the information here is beneficial to others, then that is a plus.
I came up with a process that satisfies both GFE and its use on rooted (technically temp unrooted) devices. Basically unrooting and rerooting the phone so that the GFE app functions and I comply with not running GFE on a rooted phone. .
Tested on CM9 and CM10 for the Epic 4 Touch and the Galaxy S3. I've seen success on other ROMS as well. If you run into issues, i'd be happy to help and improve the process.
What GOOD(GFE) detects and what it doesn't care about
Some key notes about what GFE seems to detect:
Detects 'su' anyplace on the phone /system partition (usually located in /system/bin/su or /system/xbin/su).
Detects the superuser apk and supersu apk
Detects if you have su'd in adb or shell while it is running. Close adb and log out of and shells before launch!
If you use a root tool like titanium, reboot before launching good! Titanium will sometimes leave open rooted processes running.
In pre-JB, it could use the READ_LOGS android permission to comb the system logs and find 'root like 'activity'. In JB, that 'security hole' is closed and that permission is locked down by android.
It detects if /system is RW.
The software is setup to never be shutdown. Once its started, it runs no matter what. Preventing it from starting is a good thing IMHO.
Seems that for some unknown reason, if es explorer was run in root mode at any point before running good, it detects root. Even if I manually kill all the back ground processes before unfreezing/launching Good.
Sometimes I get a compliance failed when I was working in ADB prior to running good. Typically if I was in ADB doing root work, i'll reboot the ROM before enabling good.
Turn off 'automatic update' for super user app from market
What GFE does not seem to care about:
busybox
CWM
locked/unlocked bootloaders
Here is how to make root and GFE play as nice as possible. This isn't perfect but it works pretty good. I still get the 'compliance failed' once in a while when i do something dumb. I am lucky in that I can clear data on the GFE app and reuse the prior key or request a new key from our IT system on demand. If you cannot do this easily, then this may be cumbersome. As we further progress this, we should get less and less lockouts.
SCRIPTED PROCESS
Downloads:
Something to run the scripts One of these will do:
- Connectbot or any shell execution program from play store. connectbot has widgets. I use connectbot.... ​- Script Manager found here: http://db.tt/Vonx78NI . Or playstore.​
(required for PRE-JB roms only). Install Permissions Denied from the Market
The latest cwm/twrp flashable zip attached to this OP.
An installation of busybox. Typically comes with CM and lots of other ROMs but just making the point here that it is required.
Setup app and dependencies:
Flash the gfe_workaround_setup zip attached to this OP in CWM. This will create four scripts and a "backdoor" su binary. They are as follows:
/system/xbin/dger
/system/xbin/egdr
/system/xbin/fu. (The sparkysu binary is insecure so be careful out there! Just a disclaimer)
/system/xbin/r_dger
/system/xbin/r_egdr
Install Good Application
If pre-JB (NOT REQUIRED ON JB+), open Permissions Denied and disable the READ_LOGS permission for the Good Application. Immediately after disabling that permission reboot the device from within the Permissions Denied app (in the menu). It must be done from within the application immediately after toggling the permissions to denied.
Optional but recommended: use "autostarts app" (or similar) from market to turn off all autostarting flags for Good app. This is incase you forget to disable root before you reboot and dont want it to start after again after flashing a rom which would restore root..
Use Connectbot or old script manager to execute the enable/disable scripts.
HOW TO Use the scripts and run the Good.
These scripts will basically temp unroot your phone and disable the superuser user whenever you want to run good. It will reverse the operation whenever you want to return root and lockup good.
I typically leave good disabled unless I am using it but that is up to you.
Whenever you want to 'run good'. You will run the script egdr.
Whenever you want to disable good and return root to your phone run dger (prior to reboot for example or flashing roms or whatever)
DO NOT FORGET TO run the DGER script before flashing a rom since that rom will repush superuser and su and if good was enabled when you shutdown to reflash the rom, good will detect root and deactivate the handheld. Also since I disable the superuser user entirely when you flash the new rom, you will lose root and will need to enable the superuser user and reflash the rom to fix things... You can always just fix it with adb but renabling superuser... But that is a pain.
(pre-JB only) Permissions Denied takes FOREVER to startup, several minutes at least & you repeatidly see it getting root permissions, at first I thought it was having issues but that is how it works.
No need to "Lock Permissions" within the Permissions Denied app from what I've seen but ymmv
Under the ROM Developer Options "Root access" is irrelevant, GFE is working just fine with it set to "Apps and ADB right now"
GFE will work fine by wiping app data & initilizing it with a new PIN if you get things cleaned up after a policy violation
No need to get an unlock code from your sysadmins after a policy violation, just wipe app data for GFE & get a new PIN (assuming you have access to a website to request a new PIN
A mini-how to for connectbot:
I prefer this because connectbot is a simple tool and I like to keep it simple. But you may prefer the script manager interface instead.
With connectbot, you can create 2 'local' connections. One for each of the enable/disable scripts appropriately named. You can edit each of the local connections and setup 'post-login automation'. In the post-login automation you add the following (Note that <enter> means to put a line feed... i.e. hit enter ):
Code:
/system/xbin/dger;exit
<enter>
Code:
/system/xbin/egdr;exit
<enter>
You can either open connectbot each time and run the enable or disable scripts or you can add connectbot shortcuts to each local connection on your launcher's desktop. Its under 'add shortcut' you will see connectbot.
If you, like me, get annoyed by the notification icon from connectbot, you can optionally do these steps to execute it.
In the connectbot options, disable persistence. Also you can replace the ';exit' in the post automation commands with ';kill $PPID' and that will get you very close a self closing command. That will terminate the shell session you are in. When disabling GFE you'll still have to hit the back button but when enabling GFE it wont stay in your notification bar.
Example:
Code:
/system/xbin/dger;kill $PPID
<enter>
The negative is that if there was an issue, you wont see the log. I may add logging support in the scripts so that we can go back and look easier anyway at what failed if we get a lock out. If you ever needed to debug though just remove that temporarily and you'll see the log again.
If you wanted a few seconds to review the log, you could do something like this also:
Code:
/system/xbin/dger;[COLOR="Red"]sleep 5[/COLOR];kill $PPID
<enter>
A mini-how to for script manager:
In script manager you will add the scripts into script manager and execute them via the app or it's widgets. The scripts should NOT be setup to run as superuser but they still will prompt for super user when the disable one is actually executed and you should respond GRANT to that request. You will use the app to find the scripts in /system/xbin chosing the following:
Code:
/system/xbin/dger
Code:
/system/xbin/egdr
FAQ
Q: If I am going to dirty flash a new rom (no data wipe), What do I need to do to keep GOOD in compliance?
A: IT'S LIKE DANCING AROUND A LAND MINE! You will want to follow this process before and after flashing dirty:
Run dger to return root to your device and disable GOOD
Reboot into cwm
Flash rom and do any other rom specific instructions including any reboots or whatever the rom maintainer wants you to do.
Reflash the gfe_workaround zip from the op since flashing the rom overwrites it.
Boot into the rom and set it up as you like with root...
Run disable good enable root.sh to make sure things are well after rom flash.
reboot one last time
use scripts as normal
Q: If I am going to clean flash a new rom (wipe data), What do I need to do to keep GOOD in compliance?
A: Clean Flashing will require you to restore the good app or jsut reactivate it. You can likely avoid reactivation by following this. YMMV
Run dger to return root to your device and disable GOOD
Use Titanium Backup (or similar like carbon) to backup the GOOD app and data.
Reboot into cwm
Flash rom and do any other rom specific instructions including any reboots, wiping data/system or whatever\ the rom maintener wants you to do.
Reflash the gfe_workaround zip from the op since flashing the rom overwrites it.
Boot into the rom and set it up as you like with root...
Restore GOOD with Titanium. You may need to also restore your android ID with titanium as I am not sure if it hashes that ID with activation credentials.
Immediately run dger BEFORE REBOOTING to make sure things are well after rom flash.
Ensure you redisable any permissions denied things and autostarts.
reboot one last time
use scripts as normal
DEBUGGING PROCESS
So you've experienced a policy break/lockout? Now what?? This is how you can debug and give me what I need to help you if required:
flash newest scripts in OP and boot up and let it settle.
run the disable good script.
run enable good script.
run disable good script again.
That will create log files in /sdcard/ with the same names as the scripts. You can review those or submit them to me in this thread and I can look. I will also need the following. I review these files to see if there are any 'other' superuser or supersu apks that my scripts have missed. I will need the /sdcard/gfe.txt after you run the below to assist posted in the thread.
Run the following commands in a connectbot shell after above:
Code:
Code:
su
find /system/app /data/app /system/bin /system/xbin|sort > /sdcard/gfe.txt
pm list packages >> /sdcard/gfe.txt
Then give me these following logs:
/sdcard/gfe.txt
/sdcard/egdr.......log
/sdcard/dger.......log
Some of the most common reasons for lockouts are because of the running of certain root apps prior to enabling good. Certain root apps still retain root access after you close them. Notably es explorer and titanium. I'm sure there are others but this is two that I know of. If you use those tools either disable root access in them if applicable or reboot before running good after using them.
Change log
04-20-2013 (v16):
Renamed scripts and binary
04-03-2013 (v16):
Added "script complete" messages to output.
04-02-2013 (v15):
Added command line option to turn off auto-launch of GFE. The default will remain to auto-launch it.
04-01-2013 (v14):
Went back to sparky su as other su is causing too many anomolies.
FAQ added to OP.
02-26-2013 (v13):
Removed execution speed enhancement introduced in v11 as it caused some issues.
02-22-2013 (v12):
Further improved Logging to sdcards
Added some enhancements and termination of some root apps(titanium)
02-14-2013 (v11):
Improved script execution speed by parallelizing some operations
Added logging to /sdcard if available
02-04-2013 (v10):
Changed the way I handled superuser apps (or multiples) stored in data and system.
Added ability to handle chainfire's nonag apk in addition to regular supersu.
Started using supersu's su for a more secure setup.
Revamped directions and cleared up some errors in the OP.
01-29-2013 (v9):
added new mask for apk
added error handling for mounts incase.
01-25-2013 (v8):
reversed order of hiding apks between system/data to resolve
issue of supersu/superuser "forgetting" settings when rerooting.
12-18-2012 (v6):
added supersu support
fixed left over apks from super app upgrades
12-14-2012 (v3):
Added clean exit commands.
12-13-2012 (v2):
- Discovery that new script manager may cause compliance issues and doesn't work after temp unrooting!
12-12-2012 (v1):
- Fixed bugs
- Automated variables
- Created flashable setup script
- Simplified the install process
12-10-2012 ():
- Initial design

The 'manual' process may not work anymore. I believe supersu apks are getting picked up for compliance. There are a few more manual ways listed in this thread that may or may not work for you but you are welcome to try them.
MANUAL PROCESS
If the script process is too complicated for you and you want to do things manually, you can do this as well. It is a pain though and more prone to getting the handheld disabled by good because of user error (forgetting to do something).
The key to this way is that gfe doesnt appear to detect supersu apk and does detect superuser apk. Not sure how long this will last! ymmv
You can install supersu, open it and let it authorize. Then rename /system/app/Superuser.apk to super_user.rob since its not needed anymore and let supersu do the authorizations.
Then install "app quarantine" from the market or titanium backup. These apps let you freeze and unfreeze the gfe app so you can bounce between a rooted and unrooted phone. (hint: there are widgets for this in titanium and app quarantine that are much more convenient)
If pre_JB, Install "permissions denied" (in app store) to remove the some of the permissions from the app. specifically you must remove
READ_LOGS
The process is as follows once the above is complete and gfe is installed and you want to use gfe:
FROST GFE(reroot)
open gfe and go into preferences and select "disconnect" and then select shutdown good. VERY IMPORTANT TO DISCONNECT AND SHUTDOWN from within the GOOD app. Do NOT just hit the 'HOME' button and reroot. It WILL detect that it has been frosted and unfrosted if you do not follow this advice
immediately open supersu app and go to settings and select "enable supersu" to reenable root.
open app quarantine (or titanium) and freeze good so it won't autostart.
You can now use the rooted phone like normal.
when you want to use gfe, temp unroot as follows:
UNFROST GFE(temp unroot)
using titanium or app quarantine defrost gfe.
immediately open supersu and go to settings and uncheck "enable supersu". the will hide the su binary and temp unroot.
open gfe and use it like normal.
once done using gfe, refrost it like above
this works very well but ymmv. The scripted method works much better.

Finally had success getting GFE running a recent CM10 nightly on my AT&T SGS3 thanks to calisro. Thanks for figuring out a good work around to enable GFE! It looks like my issues this go around were with Permissions Denied & me doing some uninstall-re-install of GFE.
My process (tweaks to calisro's stuff mostly):
Uninstalled ES explorer (just to make sure it is not causing issues for now)
Installed GFE
Installed Script Manager (I've since upgraded to Script Manager-SManager(NoAds), always a good idea to support the devs)
Installed Permissions Denied
Installed su as /sdcard/rob_su
Opened Permissions Denied and disabled the following permission for the Good Application: READ_LOGS and RECEIVE_BOOT_COMPLETED
Rebooted from within Permissions Denied, checked & verified Good had the 2 permissions in question denied
Created the 3 scripts using the updated versions recently posted
setup_rootdoor.sh
enable_good_disable_root.sh (complete with the missing final line noted above)
disable_good_enable_root.sh
With Script Manager, ran setup_rootdoor.sh
Deleted all data for GFE through app manager
With Script Manager, ran enable_good_disable_root.sh
Activated GFE
Working GFE
Notes:
Permissions Denied takes FOREVER to startup, several minutes at least & you repeatedly see it getting root permissions, at first I thought it was having issues, but I guess that's normal behavior
No need to "Lock Permissions" within the Permissions Denied app from what I've seen
Under Developer Options "Root access" is irrelevant, GFE is working just fine with it set to "Apps and ADB right now"
GFE seems to be sucessfully cleaned up by deleting app data from within app manager
GFE will work fine by wiping app data & initializing it with a new PIN if you get things cleaned up after a policy violation
No need to get an unlock code from your sysadmins after a policy violation, just wipe app data for GFE & get a new PIN (assuming you have access to a website to request a new PIN
Logs & thoughts from of my previous failures & troubleshooting steps http://forum.xda-developers.com/showpost.php?p=33025295&postcount=5

Fallon said:
Finally had success getting GFE running a recent CM10 nightly on my AT&T SGS3 thanks to calisro. Thanks for figuring out a good work around to enable GFE! It looks like my issues this go around were with Permissions Denied & me doing some uninstall-re-install of GFE.
My process (tweaks to calisro's stuff mostly):
Uninstalled ES explorer (just to make sure it is not causing issues for now)
Installed GFE
Installed Script Manager (I've since upgraded to Script Manager-SManager(NoAds), always a good idea to support the devs)
Installed Permissions Denied
Installed su as /sdcard/rob_su
Opened Permissions Denied and disabled the following permission for the Good Application: READ_LOGS and RECEIVE_BOOT_COMPLETED
Rebooted from within Permissions Denied, checked & verified Good had the 2 permissions in question denied
Created the 3 scripts using the updated versions recently posted
setup_rootdoor.sh
enable_good_disable_root.sh (complete with the missing final line noted above)
disable_good_enable_root.sh
With Script Manager, ran setup_rootdoor.sh
Deleted all data for GFE through app manager
With Script Manager, ran enable_good_disable_root.sh
Activated GFE
Working GFE
Notes:
Permissions Denied takes FOREVER to startup, several minutes at least & you repeatedly see it getting root permissions, at first I thought it was having issues, but I guess that's normal behavior
No need to "Lock Permissions" within the Permissions Denied app from what I've seen
Under Developer Options "Root access" is irrelevant, GFE is working just fine with it set to "Apps and ADB right now"
GFE seems to be sucessfully cleaned up by deleting app data from within app manager
GFE will work fine by wiping app data & initializing it with a new PIN if you get things cleaned up after a policy violation
No need to get an unlock code from your sysadmins after a policy violation, just wipe app data for GFE & get a new PIN (assuming you have access to a website to request a new PIN
Logs & thoughts from of my previous failures & troubleshooting steps http://forum.xda-developers.com/showpost.php?p=33025295&postcount=5
Click to expand...
Click to collapse
FYI, I simplified the install with a flashable zip and some modifications to the scripts so that the work they do is dynamic rather than hard coded.

Discovered that the new Script Manager is potentially causing policy compliance issues. See the op for alternative or older version of script manager.

calisro said:
Discovered that the new Script Manager is causing policy compliance issues. See the op for alternative or older version of script manager.
Click to expand...
Click to collapse
Does it only trip when you use it? I think I saw Script Manager update a couple days ago, but haven't had any problems yet. Then again I haven't needed to mess with SM at all since then or even engage root for anything since I got GFE working on CM10 a week or so ago.

I'm having it fail compliance by simply having it installed. I've gone through and upgraded, tested, downgraded, tested, etc for a number of times to be sure and it keeps tripping as soon as it is used once. I've even installed it,denied superuser for the app, then used connectbot to actually run the script and it still failed. As soon as I go back to older version it works flawlessly again.
I'll be interested if yours' trips when toggle root and good once again.

De easiest way to perform tasks that require root is to use chainfire's exynos exploit apk to acquire root and when you're done use supersu to unroot.
Make sure you stop de GFE service before rooting! I just did this and GFE really stops working as I rooted, cleaned up my new polish Note 2 4.1.2. rom, unrooted, booted and used GFE like before, no policy violations.
Whatever you do, do not boot before you unrooted.

blackspp said:
De easiest way to perform tasks that require root is to use chainfire's exynos exploit apk to acquire root and when you're done use supersu to unroot.
Make sure you stop de GFE service before rooting! I just did this and GFE really stops working as I rooted, cleaned up my new polish Note 2 4.1.2. rom, unrooted, booted and used GFE like before, no policy violations.
Whatever you do, do not boot before you unrooted.
Click to expand...
Click to collapse
I wouldn't call that the easiest but to each their own.
While that may work for some people for a short time, it doesn't address a lot of things:
1) Doesn't work with superuser since Good detects the superuser apk and doesn't detect supersu yet. Detection of supersu will be added to Good at some point since its use is being coming more prevalent.
2) That exploit will be addressed soon since it affects millions of hand sets. Samsung will close the exploit and AOSP/AOKP will also address the exploit. So it will be useful for a short time only.
3) It only works for Samsung exynos based handsets only. My method is generic.
4) Requires reboots to bounce back and forth between root and unroot. Would be tiresome to do this many times a day.
5) if you reboot while your rooted, you'll get policy breaks.

v6 works great. the new method of CWM installation of scripts makes it very easy. i used the free autorun app "autorun manager" to disable the receiver flags of GFE.
the only annoyance that really is not bad is that when GFE is disabled, the shortcuts/widgets i have are removed since the app is hidden. a very acceptable price to pay considering my company has the "root" compliance turned on. this at least gives me access to email w/o rebooting when needed.
Thanks for all the work!

Do you have to use CWM recovery to flash the zip or can I use the team win recovery. I'm on Verizon note 2 with jelly beans v4 rom.
Thanks, Will
Sent from my SCH-I605 using xda app-developers app

wc4482 said:
Do you have to use CWM recovery to flash the zip or can I use the team win recovery. I'm on Verizon note 2 with jelly beans v4 rom.
Thanks, Will
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I have not tried twrp but it should work fine.

calisro said:
I have not tried twrp but it should work fine.
Click to expand...
Click to collapse
Just wanted to say thank you for your scripts. Installation worked perfectly on TWRP and to be safe I froze ES file Explorer in titanium since it came with my ROM.
I think my favorite part of the re root script is killing Good and not being bothered by work emails unless I want to be.
Sent from my SCH-I605 using xda app-developers app

glad they are working for you. what rom and phone are you on?

calisro said:
glad they are working for you. what rom and phone are you on?
Click to expand...
Click to collapse
Jelly Beans v4 ROM for Verizon Galaxy Note 2
Sent from my SCH-I605 using xda app-developers app

Good unrooted
Hi,
I've tried lots of different options, being a complete noob at this unrooting malarkey.
Having had a nightmare rooting, I finally managed it, only for Good to then not work because it was rooted.
I finally managed it thus: Downloaded the paid for version of SuperSU. Selected the 'clean up for complete unroot option', downloaded GFE, and self served a new pin, installed Good, went through the setup steps, et voila!
Have rebooted a couple of times and it's still working. Fingers crossed.
Galaxy S3 i9300 with a nightly build of CyanogenMod 10.1 Jelly Bean 4.2.
Not sure if it'll keep working, but I really hope so!

Bestbaldmanever said:
Hi,
I've tried lots of different options, being a complete noob at this unrooting malarkey.
Having had a nightmare rooting, I finally managed it, only for Good to then not work because it was rooted.
I finally managed it thus: Downloaded the paid for version of SuperSU. Selected the 'clean up for complete unroot option', downloaded GFE, and self served a new pin, installed Good, went through the setup steps, et voila!
Have rebooted a couple of times and it's still working. Fingers crossed.
Galaxy S3 i9300 with a nightly build of CyanogenMod 10.1 Jelly Bean 4.2.
Not sure if it'll keep working, but I really hope so!
Click to expand...
Click to collapse
If you completely unrooted it should be fine but now you don't have root unless you reflash. The point here was to offer a way to temp unroot.

calisro said:
If you completely unrooted it should be fine but now you don't have root unless you reflash. The point here was to offer a way to temp unroot.
Click to expand...
Click to collapse
*hangs head in shame for being a dumbass*
That said, it's no biggie to reflash with CF Root whenever I need Root. Which won't be very often I can't imagine... I've had the phone six months and only flashed it cos I got so frustrated with TouchWiz and the horrendous lag I was getting.
The SGS3 is my work phone; I'm an iOS boy for all my personal stuff (sorry!), so I'm quite used to operating without Root access!

Bestbaldmanever said:
*hangs head in shame for being a dumbass*
That said, it's no biggie to reflash with CF Root whenever I need Root. Which won't be very often I can't imagine... I've had the phone six months and only flashed it cos I got so frustrated with TouchWiz and the horrendous lag I was getting.
The SGS3 is my work phone; I'm an iOS boy for all my personal stuff (sorry!), so I'm quite used to operating without Root access!
Click to expand...
Click to collapse
But the scripts in the OP didn't work for you? What problems did you have?
I understand if it ain't broken don't fix it, but I'm also a noob and was able to get this working- the best of both worlds now!
Sent from my SCH-I605 using xda app-developers app

wc4482 said:
But the scripts in the OP didn't work for you? What problems did you get have?
I understand if it ain't broken don't fix it, but I'm also a noob and got the best of both worlds now!
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Truth be told, i'm not sure what happened. Flashed the ROM, installed connectbot, ran the scripts; nothing happened. Searched for the scripts in system/xbin but couldn't find them.
This was at the end of two days of battling with connection problems with Odin, phone getting stuck in Download mode, SD card not being recognised with the nightly build of CM 10.1 I was using, and a few other things.
I could probably have made it work, but being as my primary goal was to get rid of TouchWiz and all the Vodafone clag on the phone, that has been achieved.
At some point in the future, i might have another go. But as I'm someone who loves technology but isn't a techie, the instructions on most of these blogs are a bit difficult for my small brain to follow.
That's obviously my problem, not anyone else's, but it takes me a while to penetrate the language and understand what people mean. So, unless I really, really need to be switching back and forth between root and no root, I'll probably leave well alone for a while now.
Thanks, though, to everyone who is clearly a lot, lot cleverer and more persisten than I am for making all this wonderful stuff available.

[TOOL/ROOT][WIN] BlueStacks MultiTool v1.21r1 (Auto Rooter, Xposed, De-bloater, etc)

* This page is for BlueStacks App Player's users, if you have no idea what is BlueStacks, please visit this page.
* If you are using BlueStacks for Mac and looking for root, please try the pre-rooted image instead.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, you can have your BlueStacks for Windows rooted automatically in less than 2 minutes!
Follow the instructions below to get started, any suggestions/comments are welcome.
Private message requesting for support will NOT be entertained, please try other rooting method if this tool doesn't work for you.
WARNING: TRY AT YOUR OWN RISK. I am not responsible for any brick or data loss caused by this tool.
FEATURES OVERVIEW
BlueStacks Auto Rooter / Unlocker
Full Unroot (Helper for BS)
De-bloater (Auto Mode - Disable Only)
De-bloater (Auto Mode - Delete Permanently)
De-bloater (Manual Mode - Disable, Delete, Skip or Re-Enable)
Superuser / SuperSU Installer & Updater (Helper for BS)
Xposed Framework Installer & Updater (Helper for BS)
Apk Installer (Wrapper)
Multi / Mass Apks Installer (Wrapper)
Hosts File Updater / Injector
Build.prop Updater / Injector
Auto Updates Disabler
Dirty Uninstaller
Full Factory Reset
Click to expand...
Click to collapse
BASIC REQUIREMENTS
* BlueStacks App Player Beta for Windows 0.7.4.x - 0.8.11.x only.
* Your BlueStacks MUST be able to run smoothly on the system running this tool. (Especially self-rooting)
* And of cause, some free space on your harddisk for temporary storage and backups.
* For detailed requirements of each task / feature, please refer to the requirement section under it's own topic.
Click to expand...
Click to collapse
TESTED VERSIONS
Personally tested on the following versions:
BlueStacks Beta v0.8.11.3116 on Win 7 x32
BlueStacks Beta v0.8.10.3096 on Win 7 x32
BlueStacks Beta v0.8.9.3088 on Win 7 x32
BlueStacks Beta v0.8.8.8006 on Win 7 x32
BlueStacks Beta v0.8.7.3066 on Win 7 x32
BlueStacks Beta v0.8.6.3059 on Win 7 x32
BlueStacks Beta v0.8.5.3042 on Win 7 x32 & x64
BlueStacks Beta v0.8.4.3036 on Win 7 x32 & x64
BlueStacks Beta v0.8.3.3026 on Win 7 x32 & x64
BlueStacks Beta v0.8.1.3011 on Win 7 x32
BlueStacks Beta v0.7.13.899 on Win 7 x32
BlueStacks Beta v0.7.6.802 on Win 7 x32
BlueStacks Beta v0.7.4.788 on Win 7 x32
Users Reported Working Versions :
BlueStacks Beta v0.8.9.3088 on Windows 7, 8.1 x64
BlueStacks Beta v0.8.7.3069 on Windows 7, 8 x64
BlueStacks Beta v0.8.6.3059 on Windows 7 x64
BlueStacks Beta v0.8.4.3036 on Windows 8.1 x32 & x64
BlueStacks Beta v0.8.3.3026 on Windows 8.1 x32 & x64
BlueStacks Beta v0.8.3.3026 on Windows XP x32
BlueStacks Beta v0.7.11.885 on Windows 7 x32
* Feel free to report your working configuration so that i can add to this list.
Click to expand...
Click to collapse
DOWNLOADS & CHANGELOG
2013/12/12, BSAutoRooter v1.03 - First public preview version.
2013/12/15, BSAutoRooter v1.04 - Major bug fix & improvement!
2013/12/18, BSAutoRooter v1.04r2 - Added SuperSU installer/updater & unroot helper function.
2013/12/19, BSAutoRooter v1.04r3 - Now ChainsDD Superuser can be used too; Win XP is now supported.
2013/12/29, BSAutoRooter v1.04r5 - Raised time limit to support slower machine; Support BS up to version 0.8.4.
2014/01/14, BS MultiTool v1.05 - Complete overhaul. Now support Xposed, De-bloater, and many more features.
2014/01/19, BS MultiTool v1.05r2 - Added 'Restore Backup' and manual Debloat mode.
2014/01/21, BS MultiTool v1.05r3 - Added Xposed & Superuser Installer/Updater to main menu; Minor bug fix.
2014/01/28, BS MultiTool v1.05r4 - Added 0.8.5 support.
2014/02/08, BS MultiTool v1.05r5 - Added Superuser X support. (Posible fix for AMD Athlon users)
2014/02/09, BS MultiTool v1.05r6 - Fixed a bug in Xposed Installer Helper function, now should works with arm libs too.
2014/02/09, BS MultiTool v1.05r7 - Fixed broken Xposed Installer Helper function since previous release.
2014/02/27, BS MultiTool v1.06 - Added support for non-standard UserData's path; Minor bug fix.
2014/03/12, BS MultiTool v1.06r1 - Added 0.8.7 support.
2014/04/22, BS MultiTool v1.07 - Major release. Added hosts/build.prop updater.
2014/05/09, BS MultiTool v1.20 - Now with express rooting engine; Support up to BS 0.8.9.
2014/05/21, BS MultiTool v1.20r1 - Improved rooting engine; Fixed bug in debloater.
2014/05/24, BS MultiTool v1.20r2 - Added 0.8.10 support; Minor bug fix.
2014/06/29, BS MultiTool v1.21 - Major release. Added few new features. Support BS 0.8.11.
2014/07/03, BS MultiTool v1.21r1 - Bugfix release.
Chainfire SuperSU, Latest (Recommended; Link to official thread)
ChainsDD Superuser v3.2a (Optional; Modded, for BS only; AMD processor users MUST use this)
BlueStacks Offline Installer MSI (Could be useful if you have slow internet connection)
Google Apps Installer for BlueStacks (Installer apk; Can be used to add gapps to your BS)
SkipGraphicsDriverCheck.zip (Self explained: Disable graphic driver check during FE start-up)
BlueStacks 0.8.11.3116.msi - BSMT last supported BS version (141.05 MB) (Mirror #2: d-h.st)
* Note: Official download link for 0.8.11 is gone, above are mirrors; check downloaded file's size before you run it.
BlueStacks Net Blocker v1.03 - Added systray support.
BlueStacks Tweaker v1.5 / BlueStacks Tweaker v3.12 by @AJacobs (Changelog)
WARNING: Direct linking / sharing this rooter program on other forum / file host is NOT permitted.
Click to expand...
Click to collapse
COMMONS FAQ (IMPORTANT INFO, PLEASE READ!)
Q: Why this tool? Why should i use this tool instead of other available method to get root for BlueStacks?
A: Well, this tool is a time saver! With this tool, you no longer have to spend minutes to hours DIY rooting or downloading hundreds MB of the pre-rooted images.
Q: How did you come up with this tool?
A: Well, let's just say i got a thought in my head since years ago, wondering "Why would you need another linux to root BS while you already have one that can do the same job? The BlueStacks itself!".
Q: How long it takes to get rooted with this tool?
A: The actual rooting process should take less than 2 minutes to complete, however on slower machine it could takes longer..
Q: I can see Root.fs being resized, and why 320 MB?
A: 320 MB for /system is more than enough for normal users, prior to BS ICS version it give ~167 MB free space! and for ICS you get ~48 MB..
Q: 320 MB for /system is not enough for me, i need to install lots of system apps!
A: Once unlocked, you can use tool like TopoResize to resize Root.fs
Q: I feel that my BS is running slower after rooted using this tool, can i undo or return to stock BS give me?
A: Yes, If you got rooted using this tool, you can use the newly added feature 'Restore Backup' in MultiTool to restore back to stock image.
A: Alternatively, you can also rename the backup file 'Root.fs.BAK' back to 'Root.fs', you can find the backup in one of following folder:
%ProgramData%\BlueStacks\Android\ (Vista+)
C:\Documents and Settings\All Users\Application Data\BlueStacks\Android\ (XP)
C:\Documents and Settings\{USER}\Application Data\BlueStacks\Android\ (XP)
Q: I would like to use SuperSU instead of the older Superuser, but the tool keep choosing the later one??!
A: The tool auto select the last 'UPDATE-Super*' zip found in the tool folder based on filename sorting.
A: Alternatively, once unlocked with this tool you can simply drag & drop to install your desire superuser app at any time.
Q: My SuperSU stops working properly after it got updated from Google Play Store??!!!
A: DO NOT update Superuser app directly, you are adviced to disable 'Auto Update Apps' feature under Google Play settings menu.
A: Some apps like SuperSU and Xposed cannot be updated using the usual way on BS, use my tool to update instead.
Q: I got an error 'BlueStacks is missing necessary files / features, what should i do?
A: First, make sure your BS is installed and running properly, second, check your security/antivirus software that might block access to file.
Q: I got an error 'Unable to communicate with BlueStacks', what should i do?
A: Certain firewall software such as Comodo, BitDefender will block local connection too, so you must add this tool to it's white-list.
Q: I got an error 'This SuperSU is not compatible with your system' -or- 'No su binary found'! what should i do?
A: Please try to use ChainsDD Superuser provided by this thread (Under downloads section).
Q: I got an error 'Could not complete rooting task #...', 'Timed out while...', what should i do?
A: 1) You are adviced to disconnect from internet temporary prior to running this tool. (Stops apps from (up|down)loading...)
A: 2) Try to remove or kill all unnecessary apps prior to running this tool. (Free some resources)
Q: The tool said rooting was successful, but non of the root apps is working! SuperSU shows 'No SU binary installed' error!
A: At the moment only ChainsDD Superuser has been found working with your APU. (UPDATE-Superuser-v3.2a.zip)
Q: After i ran 'Auto Debloater', my BS shows nothing except black screen, what should i do?
A: Please Install a custom launcher prior to debloating, otherwise you have no launcher when default one get disabled.
A: My personal recommendation is Holo Launcher HD, which seems to works well with BS.
Q: There is no gapps (Google Apps: PlayStore, G+, etc) in my BS after i got rooted with this tool?
A: Please follow THIS instructions to install gapps on your BS.
Click to expand...
Click to collapse
TODO IN COMING UPDATES
Add option to resize /system according to user input. CANCELLED
Add option to update hosts file directly using drag & drop. DONE!
Add 'ROM Customizer' function, something like binary-updater.
Maybe this too - Multi-Users mode, if there is enough free time. (But i think BS team is going to release this feature anytime soon.)
Click to expand...
Click to collapse
CREDITS
Chainfire - SuperSU
ChainsDD - Superuser
bitcubate / Robert N. - Superuser X
rovo89 - Xposed Framework
Click to expand...
Click to collapse
WARNING: DO NOT hotlinking or upload these files to other file host / forum. Thank you.

Main Features
Feature: #1) BlueStacks Auto Rooter / Unlocker
REQUIREMENTS
Untouched system image 'Root.fs' (NOT using any other pre-rooted files.)
Must have over 360 MB free space left on your /data partition.
WHAT IT DOES
Create a new rewritable /system (Default: Read-only for /system)
Resize /system to 320MB (Default: 300MB, but pointless because of the read-only FS)
Add Superuser apk & binary of your choice. (Default: limited su binary only)
HOW TO USE
UPDATE: AMD users, skip instructions for step 1 below and download UPDATE-Superuser-v3.2a.zip instead.
1) Download this tool under 'Download' section below and also Chainfire's latest SuperSU.
Choose the 'CWM / TWRP / MobileODIN installable ZIP' version.
Extract this program and add the downloaded 'UPDATE-SuperSU-*.zip' to the program folder.
NOTE: The attached Superuser in this thread is to be used as a fallback only, download SuperSU instead.
2) (Re)Start BlueStacks, wait until it is fully loaded, then run MultiTool and press 1.
WARNING: DO NOT stop this tool in the middle of the rooting process.
Follow the instructions on the screen carefully.
Run this tool as Administrator if your current user account is restricted.
Your BlueStacks will be restarted several times to accomplished the tasks, do not close or stop it.
For older versions of BlueStacks, press 'Yes' immediately when prompted if you want to Quit.
EXPECTED OUTPUT:
Click to expand...
Click to collapse
Feature: #2) Full Unroot Helper for BS
REQUIREMENTS
Unlocked/Rooted 'Root.fs' (Prefer Root.fs rooted with this tool, although other pre-rooted should work too)
PURPOSE:
This function helps you to further clean your system by removing root related leftover files on system.
Could be useful if you need to run apps that check & block your device if your device is rooted.
HOW TO USE
1) Execute 'Unroot / Full Unroot' provided by your Superuser app. (If it is currently installed)
2) Run BS MultiTool, press '2' on main screen and follow the on screen instructions.
You may also need remove root related app, just in case the the above mentioned app detects root apps as well.
You can verify root status by using app like 'Root Checker', it should shows all RED to indicates root is not available.
EXPECTED OUTPUT:
Click to expand...
Click to collapse
Feature: #3,4,5) De-bloater (Bundled Apps Remover)
REQUIREMENTS
Unlocked/Rooted 'Root.fs' (If you want to use 'Delete' mode)
IMPORTANT: Custom launcher MUST be installed first if you plan to disable/delete default launcher.
AVAILABLE MODES
3) Fully Automated, DISABLE all pre-defined bloat apps.
4) Fully Automated, DELETE all pre-defined bloat apps.
5) Manual Mode - You decide: DELETE, SKIP / ESC, ENABLE, Any other key = DISABLE
NOTES
Run this first if you have timed-out problem while rooting, especially for those who running BS on slow & old machine.
TIPS: Option '#3) Debloat (Disable Only)' can be executed on stock BS even you have not unlocked/rooted.
INFO: Currently there are around 15 pre-defined apps that will be processed by this tool.
This list is mostly apps that i don't need or don't use it, and more close to stock feel once custom launcher installed.
NOTE: DO NOT use Auto debloat mode if you use/need any of the bundled apps that come with BS.
EXPECTED OUTPUT (AUTO MODE):
EXPECTED OUTPUT (MANUAL MODE):
New in BSMT 1.21: Re-enable disabled bloat app with 'E'.
Click to expand...
Click to collapse
Feature: #6) Superuser Installer / Updater for BS
REQUIREMENTS
Unlocked/Rooted 'Root.fs' (Prefer Root.fs rooted with this tool, although other pre-rooted should work too)
Must have at least 1 MB free space left on your /system partition.
Superuser apk of your choice. ('UPDATE-SuperSU-*.zip' or 'UPDATE-Superuser-*.zip')
WHAT IT DOES
Allow you to install new Superuser app. (Eg: From ChainsDD's Superuser to Chainfire's SuperSU, and vice versa)
Update your existing Superuser app to latest version. (DO NOT update directly through PlayStore!)
For ChainsDD superuser, a clean (re)installation will be used, and only the one attached in this thread can be used.
For SuperSU, existing installation will be updated, thus your authorized apps database should remains after the update.
For a completely clean install, use the 'Full Unroot' feature under SuperSU settings to remove it, then reinstall using this tool.
HOW TO USE
Simply drag & drop the latest 'UPDATE-Super*.zip' to this tool & follow the on screen instructions.
TIPS: There is no need to run this tool first, simple drag & drop the zip file to program icon in folder.
NOTE: If drag & drop is not working properly please use option 'S' under main menu.
EXPECTED OUTPUT:
Click to expand...
Click to collapse
Feature: #7) Xposed Framework Installer Helper for BS
REQUIREMENTS
Unlocked/Rooted 'Root.fs' (Prefer Root.fs rooted with this tool, although other pre-rooted should work too)
Must have at least 1 MB free space left on your /system partition.
Xposed Framework Installer apk ('de.robv.android.xposed.installer_*.apk')
HOW TO USE
1) Download rovo89's Xposed Framework Installer APK under it's download section.
latest.apk should be renamed automatically by server when you click the link to download.
Place downloaded 'de.robv.android.xposed.installer_*.apk' under the same folder with MultiTool.
2) Simply DRAG & DROP 'de.robv.android.xposed.installer_*.apk' to the MultiTool.
NOTE: If drag & drop is not working properly please use option 'X' under main menu.
You are adviced to disconnect from the internet temporary before running this step.
Follow instructions on the screen carefully.
3) Validate Install. (Success or Fail)
Once installed, open 'Xposed Installer' to check whether Xposed Framework is working properly.
If working your Xposed main page should looks like below. (Without the red warning message under Framework)
If failed, your Xposed will looks like below. (Red warning message)
If you see this you MUST uninstall the framework or else you won't be able to boot again after BS restart.
NOTE: Even app_process & XposedBridge.jar show active versions you MUST uninstall too.
Sorry to tell you the Xposed version used will not work for you, ignore step 4 and 5 below.
4) Disable Updates.
If successful, open "Xposed Installer" and go to it's [Settings] and UNcheck the [Enable downloads]
You are also adviced to disable updates for apps installed on BS under PlayStore settings menu.
Warning: DO NOT update or reinstall the framework or else your BS might not be able to start normally again.
5) Install & Activate the Modules.
Activate the newly installed modules by ticking the checkbox under [Modules] page.
Some modules might need a restart before changes take effect / function properly.
Sample: Module "XhaloFloatingWindow" by @zst123
For more information about Xposed Framework, please visit their respective thread. Modules repo can be found HERE.
Please check whether the module support ICS first before install, module like GravityBox that needs JB+ won't work.
Click to expand...
Click to collapse
Feature: #8) Apk Installer (Wrapper)
HOW TO USE
Simply DRAG & DROP ' an .apk to BS MultiTool.
NOTE: This function is ONLY needed if your .apk does not get associated with BS properly.
TIPS: There is no need to run this tool first, simply drag & drop the apk file to program icon in folder.
Click to expand...
Click to collapse
Feature: #9) Multi / Mass Apk Installer (Wrapper)
HOW TO USE
Simply DRAG & DROP ' a folder containing .apk files to BS MultiTool.
To those who think the Apk Installer in this tool is useless because you can simply double click the apk to install, now what do you think?
TIPS: There is no need to run this tool first, simply drag & drop any dir containing apk files to program icon in folder.
NOTE: Only top dir under the dropped dir will be scanned for apk files, files in sub dirs are ignored.
Click to expand...
Click to collapse
Feature: #10) Hosts File Updater / Injector
REQUIREMENTS
Unlocked/Rooted 'Root.fs' (Prefer Root.fs rooted with this tool, although other pre-rooted should work too)
PURPOSE:
This function help you to update/inject your edited hosts file directly to your BS.
Could be useful if you need to add custom domain names to resolver or to block ads (Eg: using MoaAB).
HOW TO USE
1) Place your updated 'hosts' file under the same directory with MultiTool.
TIPS: To grab a copy of 'hosts' file currently in use by system, create and use an empty 'hosts' file instead.
TIPS: You can create multiple hosts profiles by naming it as hosts1, hosts2, hosts3.txt, etc.
TIPS: You can easily edit 'hosts' file with any text tool that support unix line ending like Notepad++, etc.
2) Simply drag & drop the 'hosts' file to MultiTool or enter 'H' on main menu.
Retrieving (BlueStacks -> Computer)
Updating (Computer -> BlueStacks)
Click to expand...
Click to collapse
Feature: #11) Build.prop Updater / Injector
REQUIREMENTS
Unlocked/Rooted 'Root.fs' (Prefer Root.fs rooted with this tool, although other pre-rooted should work too)
PURPOSE:
This function help you to update/inject your edited build.prop file directly to your BS.
Could be useful if you need to add/change new setting, eg: Change device brand, model, or to add 'ro.sf.lcd_density', etc.
HOW TO USE
WARNING: Use with caution. Wrong edit / invalid build.prop could make your BS unbootable. Use at your own risk.
1) Place your updated 'build.prop' under the same directory with MultiTool.
TIPS: To grab a copy of 'build.prop' currently in use by system, create and use an empty 'build.prop' instead.
TIPS: You can create multiple build.prop profiles by naming it as build1.prop, build2.prop, etc.
TIPS: You can easily edit 'build.prop' file with any text tool that support unix line ending like Notepad++ etc.
2) Simply drag & drop the 'build.prop' file to MultiTool or enter 'B' on main menu.
3) Please do a FULL restart on BlueStacks for the changes to take effect.
To do that simply right click BS tray icon and choose [Restart].
Retrieving (BlueStacks -> Computer)
Updating (Computer -> BlueStacks)
Click to expand...
Click to collapse
Feature: #12) Auto Updates Disabler
REQUIREMENTS
Administrator's right *might* be needed if your current user account is restricted.
PURPOSE:
Disable BS auto updater - Keep your current version without update enforcement/notification.
Disable Graphic Card driver check - Stop nagging about outdated graphic drivers.
TIPS: Updating GPU driver is not a bad idea, but make sure you use latest stable and not beta driver.
OUTPUT:
Click to expand...
Click to collapse
Feature: #13) Dirty Uninstaller
REQUIREMENTS
Administrator's right *might* be needed if your current user account is restricted.
WARNING: DO NOT use this if you have any Non-BS program that has the word 'Notification Center' in it's name.
PURPOSE:
ONLY needed if you have problem reinstalling BlueStacks, not for failed installation, eg: system not supported, compatible issues etc.
Fix reinstallation issues by removing ALL registry entries leftover by BlueStacks & Notification Center after uninstallation.
Eg: error 'Uh oh - BlueStacks cannot be installed on this PC because you already have this version installed.'
Why 'dirty'? Oh well, because this tool has nothing to do with uninstalling the actual program, or removing the files, indeed,
...it stimulate uninstalled effect by tricking the setup program to *think* the program is not installed, even though it's installed.
HOW TO USE:
WARNING: Experimental feature. For expert user only, use with caution and try at your own risk.
1) Run your BlueStacks Built-In uninstaller from Control Panel.
NOTE: You will also need to uninstall 'Notification Center' which is also a BS program.
TIPS: You can also use your favorite helper program such as Revo Uninstaller, CCleaner, etc to uninstall.
2) Start BSMT and press '7' to start Dirty Uninstaller.
You will be given an option to continue or abort. To abort you can simply close the program window.
If you choose to continue, the cleaning will begin.
NOTE: The tool will try to create a registry backup for entries that will be removed. (RegistryBackup.reg)
TIPS: The backup can be found under the same dir with BSMT, double click the registry file and answer YES to restore.
3) Once completed, restart your computer and delete any left over files found in:
%TEMP%\bst*
%ProgramFiles%\BlueStacks\*
%ProgramFiles(x86)%\BlueStacks\*
%ProgramData%\BlueStacks\*
-OR- your customized installation/data path.
4) You may now retry to install BlueStacks, using offline installer is preferable & recommended.
Click to expand...
Click to collapse
Feature: #14) Full Factory Reset
REQUIREMENTS
Administrator's right *might* be needed if your current user account is restricted.
PURPOSE:
If you tried the 'Factory Reset' in your running BS you should have know that it didn't work as expected.
With this tool you can stimulate a factory reset effect similar to clearing your data/sdcard partitions.
HOW TO USE:
WARNING: Experimental feature. For expert user only, use with caution and try at your own risk.
1) Backup your apps & data, sync your contacts, messages, settings, etc.
NOTE: All apps that were installed after BS first start will be deleted, including it's shortcut on Windows.
2) Prepare needed apk files to be reinstalled, eg: custom launcher, GApps Installer, etc.
I recommend Holo Launcher HD, works well with both BS 0.7 & 0.8. (Need some customization to make it looks nice)
TIPS: Link to download gapps installer (Play Store, Play Services) can be found in first post.
3) Start BSMT and press 'F' to start Full Factory Reset.
You will be given an option to continue or abort. To abort you can simply close the program window.
Next, you will be given an option whether to backup existing data or not, please decide wisely!
INFO: If your data/sdcard are full the backup could takes 16GB!! Make sure you have enough space!
Once you have chosen the backup option the actual reset will begin.
Default unrooted state will be restored for BS v0.8.11 and above, for other versions, root will be kept.
TIPS: If you ran debloater before and deleted default BS launcher, you might get black screen on first boot,
... to solve that, simply drop your custom launcher apk file to BSMT to install and get back your HOME screen.
If you have chosen to create backup, the backup path will be given when the reset job done, please copy it down.
TIPS: You can copy & paste the path in your address bar to navigate to the backup dir.
Please delete any backup that is no longer needed to save some space.
4) Once completed, you may start your BlueStacks.
INFO: The first boot after reset will take much longer than usual to boot as files need to be copied.
If first boot failed, please restart your computer and try to start BS again.
If somehow the reset did not work and your BS could not be started, please restore from backup manually.
Click to expand...
Click to collapse
--

hi there,
very interested in this project since I'm running macro on a game everyday.
when i tried to use your tool to root, it says "ERROR: Could not comlete rooting task #1" in red words
i'm using 0.8.3.3026, win7 x64 already used adminiatrator right.
hopefully this can be resolved
much thanks!

pakudaboy said:
hi there,
very interested in this project since I'm running macro on a game everyday.
when i tried to use your tool to root, it says "ERROR: Could not comlete rooting task #1" in red words
i'm using 0.8.3.3026, win7 x64 already used adminiatrator right.
hopefully this can be resolved
much thanks!
Click to expand...
Click to collapse
Same here. Windows 8.1 x64. Ran as admin.

New Update
Hey guys, sorry if you tried the first version but it didn't work for you.
There was a big mistake in the earlier release which i believe has caused ALL version to fail during the root process.
It wasn't my code didn't work but the bug was caused by the optimization engine & configuration i used, apologize for that.
With the 1.04 release the problem should have been fixed, also tested on Windows 7 x64, it should work just fine even without Administrator right.
But as i said the program is still under early beta stage so please feel free to report any bug, if you get error message when rooting, please let me know the last message before the error message so i can do follow up.
Also appreaciate if you can report your successful rooted version.
Thank you.

codelover said:
Hey guys, sorry if you tried the first version but it didn't work for you.
There was a big mistake in the earlier release which i believe has caused ALL version to fail during the root process.
It wasn't my code didn't work but the bug was caused by the optimization engine & configuration i used, apologize for that.
With the 1.04 release the problem should have been fixed, also tested on Windows 7 x64, it should work just fine even without Administrator right.
But as i said the program is still under early beta stage so please feel free to report any bug, if you get error message when rooting, please let me know the last message before the error message so i can do follow up.
Also appreaciate if you can report your successful rooted version.
Thank you.
Click to expand...
Click to collapse
Thanks for creating this little tool. Will test the new version now and report back. Your work is really appreciated
EDIT: Amazing! v1.04 rooted my BlueStacks v0.8.3 successfully on Windows 8.1 x64. Thanks a million!

Awesome! Rooted on BS 8.3 on windows 8.1 x32 bit! Thank you much for doing this!

Ok, this might sound like a strange request but... is there a way to fully unroot BlueStacks? The reason I ask is because in order to check my companies corporate email I have to use a third party app called AirWatch and even with a stock/clean BlueStacks install it detects it as being rooted as do other root checking apps like "Root Checker" by joeykrim for example. Anyways a way to do the opposite of what this currently does would be amazeballs for me.

voluptuary said:
Ok, this might sound like a strange request but... is there a way to fully unroot BlueStacks? The reason I ask is because in order to check my companies corporate email I have to use a third party app called AirWatch and even with a stock/clean BlueStacks install it detects it as being rooted as do other root checking apps like "Root Checker" by joeykrim for example. Anyways a way to do the opposite of what this currently does would be amazeballs for me.
Click to expand...
Click to collapse
Surprisingly joeykrim's Root Checker is one of the root checker that correctly detects BS as a 'rooted' device.
The fact is BS does come pre-rooted even since the GB versions of it, only that you have limited access due to read-only /system.
While doing a FULL unroot is very easy once you get fully rooted with unlocked /system, the problem still lies on the AirWatch app itself.
It's unknown how the 'compromised' detection works, there could be an emulator detection as well, who knows.
Perhaps i can try to include a full unroot function when i convert this tool to multi-functions utility.
But as a reminder, doing so might against their/your companies rules. (Either faking device rooted status or running in emulator)

codelover said:
Surprisingly joeykrim's Root Checker is one of the root checker that correctly detects BS as a 'rooted' device.
The fact is BS does come pre-rooted even since the GB versions of it, only that you have limited access due to read-only /system.
While doing a FULL unroot is very easy once you get fully rooted with unlocked /system, the problem still lies on the AirWatch app itself.
It's unknown how the 'compromised' detection works, there could be an emulator detection as well, who knows.
Perhaps i can try to include a full unroot function when i convert this tool to multi-functions utility.
But as a reminder, doing so might against their/your companies rules. (Either faking device rooted status or running in emulator)
Click to expand...
Click to collapse
I don't think there is any emulator detection since I doubt the AirWatch folks bothered to code that in for the 0.000001% of us trying to run this draconian crap within Windows so we can avoid having our personal devices/privacy totally invaded simply because we need to check our company email. If it was a company issued phone/tablet then sure do whatever but it's not so... yea that's getting off topic a bit. As for the 'compromised" issue it specifically states that it is compromised because of being rooted. Company policy isn't restricting what devices are used it just mandates that they be Android 3.0 or later and not rooted.
Anyways, thanks first for the root tool, which is very helpful, and second for taking the time to respond and consider my request.

New Update - BlueStacks Auto Rooter v1.04 revision 2
I am glad to announce that BS Auto Rooter has reach another milestone, v1.04r2 will brings below new functionality:
+ SuperSU Installer / Updater
+ Full Unroot Helper
Refer post #2 for more info.
@voluptuary , if that doesn't work you're probably out of luck. :X

This Info may be wrong. Please correct it, if its wrong
codelover said:
For older versions of BlueStacks, press 'Yes' immediately when prompted if you want to Quit.
Click to expand...
Click to collapse
I think here we should press 'No', instead of 'Yes'
Because I got Error #2 while rooting Bluestacks and pressing 'Yes' Button.
I got Bluestacks rooted when i denied to quit Bluestacks with 'No' Button both time.
Whatever Thanks for this amazing tool

New Update: BS Auto Rooter v1.04 revision 3
Updated to allow rooting/installation using the old ChainsDD Superuser in case SuperSU did not work or not compatible on your system.
If you already rooted with my tool simply drag & drop the UPDATE-Superuser4BS-v3.2.zip provided in OP to my tool.
gdjindal said:
I think here we should press 'No', instead of 'Yes'
Because I got Error #2 while rooting Bluestacks and pressing 'Yes' Button.
I got Bluestacks rooted when i denied to quit Bluestacks with 'No' Button both time.
Click to expand...
Click to collapse
It was a bug instead, which happen after i done some modification to better handling the quiting process for newer versions.
As i said the new version has not been tested on older BS, anyway, thanks for reporting, fixed now. Users should click YES instead.
Btw why you have not updated to ICS? if i remember correctly the confirmation dialog only exists for versions prior to v0.7.1x, correct?
I might need to withdraw support for older version in the future...

I tried your latest tool with latest bluestacks
codelover said:
It was a bug instead, which happen after i done some modification to better handling the quiting process for newer versions.
As i said the new version has not been tested on older BS, anyway, thanks for reporting, fixed now. Users should click YES instead.
Btw why you have not updated to ICS? if i remember correctly the confirmation dialog only exists for versions prior to v0.7.1x, correct?
I might need to withdraw support for older version in the future...
Click to expand...
Click to collapse
Thnaks for reply,
I have updated BlueStacks to latest version. When I tried to root it I got following Error:-
if it is working very well with you, then help me what I have did wrong??

gdjindal said:
I have updated BlueStacks to latest version. When I tried to root it I got following Error:-
if it is working very well with you, then help me what I have did wrong??
Click to expand...
Click to collapse
Have you tried the recommendation on FAQ sections?
Error on task #4 indicates the system is running too slow and the task could not be completed within the given time period, hence 80s,
which i think is more than enough since an old core2duo 2.x ghz processor can complete task #4 in less than 20s.
Some users reported to me that they managed to fix the error by temporary stopping some Windows program such as anti-virus when rooting.
Please take note that any program that has massive read/write operations to disk could cause the rooting process #4 to fail, especially on old system.

codelover said:
I am glad to announce that BS Auto Rooter has reach another milestone, v1.04r2 will brings below new functionality:
+ SuperSU Installer / Updater
+ Full Unroot Helper
Refer post #2 for more info.
@voluptuary , if that doesn't work you're probably out of luck. :X
Click to expand...
Click to collapse
Awesome! I'll give it a go sometime this weekend. Thanks for the super quick turnaround. The next $5 amazon credit I earn from bing rewards will be yours (i'll pm you with it) as a little thank you.

codelover said:
Superuser Installer & Updater
UPDATE: Now you can use the original ChainsDD Superuser too!
Allow you to install or update your Superuser, as long as your Root.fs or /system is already unlocked.
By default this tool will update your SuperSU, meaning your authorized apps database will remains after the update.
For a clean database, use the 'Full Unroot' feature under SuperSU settings to remove it, then reinstall using this tool.
For ChainsDD, a clean (re)installation will always be used since some user data file need to updated as well.
HOW TO USE: Simply drag & drop the latest 'UPDATE-Super*.zip' to this tool & follow the instructions.
Full Unroot Helper
Could be useful if you need to run apps that check/block for rooted devices.
It can help you to remove some uncommon root related files in the system left by BS.
You also need to run 'Unroot' feature provided by your Superuser app, such as 'Full Unroot' in SuperSU to fully unroot.
Also try to remove root related app such as Root Explorer, etc, just in case the the app detect root app as well.
Root checker app should show all RED after that, if you are lucky maybe you can run the above mentioned app.
HOW TO USE: Simply drag & drop an empty text file 'unroot.txt' to this tool would do the job.
Click to expand...
Click to collapse
Great... Now how to get rid of the BS channels... When it's not connected to the internet, it keeps trying to poll to repopulate the BS-channels. This is a major issue with BS.

robertkjr3d said:
Great... Now how to get rid of the BS channels... When it's not connected to the internet, it keeps trying to poll to repopulate the BS-channels. This is a major issue with BS.
Click to expand...
Click to collapse
Thank you for trying my tool.
If you mean to disable BS-channels only when you are disconnected, i am sorry to tell you that's not possible without disabling the app itself because by design the app needs internet to function properly.
For your information i am currently working on a 'Stock Converter' feature, which by then you should be able to disable ALL apps that come with BS easily and have a closer stock ICS look, but you will also lost all BS functionality that comes with it such as their very own apps drawer.
In the meantime, you can disable related apps by using DISABLE function under [Settings] -> [Apps] -> [ALL] -> <TheApp> -> [DISABLE] whenever the app support it, a start-up manager app would also do the job.
P/S: Please DO NOT quote the whole post, i do not want any outdated information appears in other posts other then my own. Please edit it. TQ.

Has anyone been able to get the xposed framework installed. After I install xposed and reboot, bluestacks will hang at boot up. Anyone have any luck?

t436h05t said:
Has anyone been able to get the xposed framework installed. After I install xposed and reboot, bluestacks will hang at boot up. Anyone have any luck?
Click to expand...
Click to collapse
First of all, this is NOT a BS support thread, for BS related question please use their official support @ https://getsatisfaction.com/bstk/
Second, as a reminder for those who share this program for download on other file hosts (especially those with paid url redirector),
please remove it as i have clearly stated it's PROHIBITED (NOT Allowed) to share this program download on any site other than XDA.
If you disobey the rules you will get your name blacklisted in the program itself for future versions. You have been WARNED.
If you do not like the rules please use other rooting method, there are lots of ways and tutorials available around.
Thank you for cooperation.

File explorers on Android 10?

Just upgraded to Android 10 and when trying to use Solid Explorer, I always get access denied. I have the permissions enabled, but still get access denied. How can we enable file explorers on Android 10?

dustintinsley said:
Just upgraded to Android 10 and when trying to use Solid Explorer, I always get access denied. I have the permissions enabled, but still get access denied. How can we enable file explorers on Android 10?
Click to expand...
Click to collapse
Just installed it there to see and no problems.

Same here, works fine for me. I did do a full wipe to stable, but was also working fine on the beta for me.
Sent from my GM1913 using Tapatalk

dustintinsley said:
Just upgraded to Android 10 and when trying to use Solid Explorer, I always get access denied. I have the permissions enabled, but still get access denied. How can we enable file explorers on Android 10?
Click to expand...
Click to collapse
Go to apps and notifications, click on see all apps. Scroll down to app and then click storage and cache and click force stop then clear storage. Reopen app and you should get Grant and deny root pop up.

Since I use Android 10 (mostly tried with Android 10 custom ROMS) I only can install .APK files with the Android 10 File Explorer itself but not with other File explorers.
I tried with ES File Explorer, Solid Explorer, Root Explorer.
When I try to install an .apk file with them I just get an error saying like "no such app found".
I tried with a MIUI ROM Port (based on Android 10) for my Phone as well and there it was working to install .apk files with Solid Explorer.
Anyone else facing the same issue?
Thanks in advance!

Wishmasterflo said:
Since I use Android 10 (mostly tried with Android 10 custom ROMS) I only can install .APK files with the Android 10 File Explorer itself but not with other File explorers.
I tried with ES File Explorer, Solid Explorer, Root Explorer.
When I try to install an .apk file with them I just get an error saying like "no such app found".
I tried with a MIUI ROM Port (based on Android 10) for my Phone as well and there it was working to install .apk files with Solid Explorer.
Anyone else facing the same issue?
Thanks in advance!
Click to expand...
Click to collapse
Just test that with FX File Explorer and with that it is working without issues on Android 10.

I use ES File Explorer Pro since years... Haven't found a better one yet

No problems with Solid here at all. Dirty flashed stock 10 over 9.5.13

i uninstall the new Q file explorer and install the old pie explorer from apkmirror and my life it's easier now

hallo dare said:
Just installed it there to see and no problems.
Click to expand...
Click to collapse
FX works just fine for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've only used Amaze but it's worked perfectly for me since the upgrade.
Sent from my OnePlus 7 Pro using XDA Labs

I have this same problem after upgrade to Android 10 :/
Cleaning of data from mass storage apps doesn't help me too. I totally don't know what to do to repair it. Solid Explorer is my must have :/

MisiekDP said:
I have this same problem after upgrade to Android 10 :/
Cleaning of data from mass storage apps doesn't help me too. I totally don't know what to do to repair it. Solid Explorer is my must have :/
Click to expand...
Click to collapse
try root explorer download for free from web browser 4 bucks in play store

billyt1 said:
try root explorer download for free from web browser 4 bucks in play store
Click to expand...
Click to collapse
Yes, I know but I really need Solid Explorer (is the best).

MisiekDP said:
Yes, I know but I really need Solid Explorer (is the best).
Click to expand...
Click to collapse
(Was the best) until they update the app

billyt1 said:
(Was the best) until they update the app
Click to expand...
Click to collapse
Why do you think so?

MisiekDP said:
I have this same problem after upgrade to Android 10 :/
Cleaning of data from mass storage apps doesn't help me too. I totally don't know what to do to repair it. Solid Explorer is my must have :/
Click to expand...
Click to collapse
did you manage to solve? can I ask you if you uninstalled the system file manager before the error?

tyrion93 said:
did you manage to solve? can I ask you if you uninstalled the system file manager before the error?
Click to expand...
Click to collapse
No, I didn't uninstall system file manager. But I was able to fix the problem. I just downloaded version 2.6.3. This is the last version that works correctly. The newer application has changes in memory access and I think that's the reason.

MisiekDP said:
No, I didn't uninstall system file manager. But I was able to fix the problem. I just downloaded version 2.6.3. This is the last version that works correctly. The newer application has changes in memory access and I think that's the reason.
Click to expand...
Click to collapse
I think they'll fix it sooner or later

tyrion93 said:
I think they'll fix it sooner or later
Click to expand...
Click to collapse
I don't think so. I wrote to them a long time ago. They did not write back to me and still no corrections. In Nova Launcher I also found bugs, recorded a video and sent. To this day, still silence: /