Disclaimer: This is for testing purposes only. I do not condone breaking company policy, or breaking any laws. I am not responsible for you getting fired as a result of you making these modifications. You should always read and abide by company policies and any laws pertaining to such modifications. Use of this tutorial is at your own risk.
Preface: I have tested the new method on multiple devices and it has been flawless so far.
UPDATE: I have found a new method that so far has been flawless across multiple devices so far for me. With this new method you won't even have MobileIron installed when you're done! I have tested this on my Galaxy Nexus, My Nexus 7 and my Galaxy Note II and believe it should work regardless of device. Your company may have different security policies than mine so it's possible this may not work for you.
The easiest way to do this is with one of mskip's toolkits, but it can also be done manually with adb (must have the latest sdk).
Toolkit Method
0. Make sure you have MobileIron and Touchdown installed, configured and syncing. Your phone does NOT have to be rooted to do this.
1. Download mskip's Toolkit Here and install.
2. Make sure you have the adb drivers for your phone installed on your computer and android debugging is turned on in the developer settings on your phone.
3. Open the toolkit and connect your phone to your computer
4. It shouldn't matter what model phone you choose for the purpose of what we're doing, and the options may be slightly different based on which toolkit you download
5. Choose the option backup and restore your device
6. Choose backup all installed apps
7. Choose do NOT include system apps in the backup
8. Choose backup apk's AND respective app data
9. Choose do NOT back up internal storage data in backup
10. Wake your phone and it will ask you to start the backup, choose to do so
Once it is finished you will need to wipe your phone. It may work without wiping and just uninstalling touchdown and Mobileiron before proceeding to the next section, but I haven't tested this.
11. Connect your phone to your computer and enable android debugging
12. Browse to C:\Galaxy Nexus Toolkit (or whatever the name of your toolkit is under c:\)
13. Open the folder backups and rename the backup file to backup.bak. (if you don't see the file extension just name it backup)
14. Open the toolkit and choose a model
15. Choose Backup and Restore
16. Choose Restore apps from a backup file
17. type backup.bak and press enter
18. Wake your phone and choose to begin the restore
19. When it's finished, uninstall mobileiron, open touchdown and see if it's syncs!
ADB Method
adb backup -all -system -shared -apk
recovery> backup, wipe, flash rom, flash gapps, reboot
adb restore backup.ab
Requirements For ICS:
1. Rooted Android Phone running ICS based ROM
2. Titanium Backup (app installed)
3. Hide my Root (app installed)
4. Mobileiron (app installed but never run)
5. Touchdown (app installed but never run)
Instructions for ICS:
0. Make a Nandroid backup
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable. (Its at the bottom when disabled)
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
14. Profit
Now restore your nandroid backup before you get in trouble.
**Update** for Jelly Bean
It seems the builds out there for Jelly Bean use a new version of SuperUser that as of yet isn't compatible with Hide My Root. I wrote the developer of Hide My Root and he is looking into this but currently doesn't have a device running Jelly Bean to test on, so I took it upon myself to figure this out once again. I tested this and it does work. Again this was tested on a VZW Galaxy Nexus only.
Instructions for Jelly Bean:
0. Make a Nandroid backup!
1. Download MobileIron (App installed but never run)
2. Download Touchdown (or any apps that depend on MobileIron and do not launch them)
3. Download Titanium Backup (You may need the premium version to freeze apps)
4. Download SuperSU flashable zip from HERE and place on your SDcard.
5. From the app drawer launch SuperSU (that app already installed, not the zip you just downloaded)
7. Swipe 2 screens to the right to Settings
8. Choose Full unroot.
9. Install and configure MobileIron and dependent apps and let them fully sync.
10. Enable Airplane Mode
11. Reboot to recovery and flash the SuperSU zip you downloaded
12. Boot into Android, open Titanium Backup and freeze MobileIron
13. Turn off Airplane Mode
14. Profit
Now restore your nandroid backup before you get in trouble.
After a reboot all of the lockscreen options will reappear allowing you to have an insecure lockscreen.
This is great
You just saved me hours of frustration.
Thanks!
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
SoCalNewb said:
Thanks - this is a huge help!!
Question: does this work only with Touchdown, or any Android email client? (I prefer the app Enhanced Email).
Click to expand...
Click to collapse
I have only tested this as posted. Make a nandroid backup and play around with it
How to re-enable superuser?
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
bhilgeman said:
1. Open Hide my Root
2. Choose hide SU binary
3. Press home
4. Menu, settings, apps, all apps
5. Choose Superuser.apk
6. Choose disable
7. Now open mobileiron and configure the settings per your company's instruction.
8. Set up your email in the Touchdown application and let it sync everything.
9. Open Hide my Root and choose restore SU Binary
10. Go back to menu, settings, apps, superser.apk and choose enable.
11. Open Titanium Backup
12. Choose backup/restore from the top
13. Scroll to Mobileiron and tap it and choose freeze.
Click to expand...
Click to collapse
SoCalNewb said:
Made a nandroid backup. Followed instructions below. Works great, now I can synch email with MobileIron fortified corp server AND change the PIN lock requirement that MobileIron required! Thank you
Only one issue: I couldn't complete step 10 ("Go back to menu, settings, apps, superser.apk and choose enable"). Superuser was no longer in the "All" list under menu, settings, apps. As a result, I seem to have lost the ability to grant root access to new applications.
QUESTION: How do I re-enable superuser?
Notes:
- ADB: I can connect to device via ADB, but if I type "adb shell", and then type "su" at the "sh-3.2#" promot, no $ access is granted).
- Terminal Emulator: TE cannot get root (I type "su" at the "sh-3.2$" command, and TE says "Permission denied")
- Root Access - Old Apps: Any apps that previously had root privileges still do (Root Explorer can navigate to "/" and enable "Mount R/W", Wifi Tether still works, etc).
- Root Access - New Apps: New apps requiring root are not able to get root (no superuser prompt comes up)
- Re-Installing Superuser.apk: I tried using root installer to re-install superuser.apk (in the "/system/app" directory). It said it installed successfully, but still no superuser in the "All" list under menu, settings, apps.
- Re-Rooting: I tried re-rooting (using mskip's exceelend GNEX toolkit HERE), to no avail (process completes, but no superuser access).
If anyone can help me troubleshoot I would be extremely appreciative. I've tried to not be a helpless newb and to try a few fixes (above), but I would be ecstatic if one of XDA's Android ninjas could tell me how to re-enable superuser. Hoping to avoid comments of "restore nandroid backup and give up"
Click to expand...
Click to collapse
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
bhilgeman said:
When you disable superuser.apk in the apps list it moves it from the alphabetical order to the bottom of the apps list. Look there and see if its at the bottom of your apps list.
Click to expand...
Click to collapse
YOU ARE THE MAN.
That was so simple, but I spent an hour trying stuff and still missed it
My Android experience is back to awesome despite Mobile Iron - THANK YOU!!!!
Thanks for that. Great idea.
I followed your instructions but I had to switch 9 and 10 because Hide my root cannot restore a deactivated app.
But my TouchDown says "Synchronization Error" --> access denied (update your password). Maybe too strong policies?
And by the way: you have to use tintanium backup PRO to enable or disable apps
---------------------
Edit: I made a system application of "Hide my root" with TI Backup - works. I had to uninstall TI Backup now - currently TouchDown is syncing again. We will see if it works, next: I try to use LBE Privacy Guard... will report. Disabling "MobileIron" seems not working for me...
Hey, is not possible solve it on 2.X version of Andriod? Thanks...
OP Updated to reflect Changes for those running JellyBean. Long live the Android experience!
bhilgeman said:
The SU change needed for JellyBean makes this previous method unusable. I did however figure out how to still get to the same result if you're running JellyBean.
I will so an update to the OP soon to reflect this.
Click to expand...
Click to collapse
Looking forward to the instructions for making this work on JB
SoCalNewb said:
Looking forward to the instructions for making this work on JB
Click to expand...
Click to collapse
OP updated for JB instructions.
Sorry, I haven't tested this on a 2.x build so I'm not sure. If I get time I'll try to test this for you, I'm just super slammed with projects right now...
Will we appear "normal" on the Server that the app links us to our Corp acct??
Yes, you will appear as a non rooted phone. I just updated the JB instructions again. Realized I left out a step.
Anyone test this for Airwatch yet?
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
makelegs said:
FWIW.....my experience has shown this to be merely a temporary solution, by itself. Yes...following the JB instructions will allow you to sync up just fine. But.....when mobileiron does not report back as device administrator, the red flags go up. My solution, thus far, has been to suspend root access on the phone, after reactivating mobileiron. In my case, after re-activating mobileiron, the app, itself, now FC's, which may be helping me out....not sure. At this point I seem to be able to continue remaining synced, without root access. As long as I use airplane mode before enabling root access to do root-type stuff, I seem to be fine. Word of caution, though....disabling root, seems screw up TB when I re-enable root. Specificaly...even though I have TB pro, it does not register after re-enabling root, so freezing and unfreezing mobileiron at will has not been possible. Could just be my system though.I recommend using airplane mode liberally if there is any doubt regarding your recognized root/non-root status. This definitely changes how I use the device, though, for sure.
Click to expand...
Click to collapse
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
bhilgeman said:
I run your CM10 build on my nex7 and love it. Great to have navbar mods.
On my nex7 it took me a few tries to get it to stick but I finally got it. I hadn't updated a nightly for a couple weeks and when I did Mobileiron got me. I decided I don't care about getting work email on my tablet as much as I do my phone so no big deal. I freaking hate Mobileiron and touchdown nearly as bad.
On my galaxy nexus (running fitsnugly cm10) I don't have any issues. I flash the nightlies every day and I've gone a couple months without Mobileiron flagging me.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Skanklove!
I was completely under the radar, due to some corporate user configs, until I screwed up and raised the red flag. Then I had to encrypt, and install mobileiron. I was perfectly happy with touchdown until mobileiron got involved. I don't want work email on any device other than my work phone (toro). I can still run email without mobileiron, but no activesync and no email attachments......meh
Steps on ICS
Hello,
I am new to using mobileiron, as my corporation just started to use this program. Can I use your steps on ICS and keep my root undetected or will I eventually have issues. Last question, why is it necessary to restore your nandroid backup at the end?
* 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.