yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] codelover:
BSSSU - Bluestacks State Saver & Backup Utility for Windows (Beta)

Let me introduce you to my little simple yet useful tool - BlueStacks State Saver Utility written as Windows Batch Script.

What It Does

What It Does Not

Known Limitation

Files Description

How To Use

Disclaimer & Terms of Use

Please do let me know if you found any bug in the mini program, Thanks!
[Android Software/Hacking General [Developers Only]] codelover:
Some note to users especially those who build & upload Root.fs for others, the su v3.2 that works with Auto Response is actually the one inside Superuser-3.2-RC3-x86-signed.zip, the other one that can be downloaded directly does not work, sorry for any inconvenience caused, already updated my previous post.

I tried just now and yes it does have the problem as you said, what i did was click on BS [Setting] button on right,

[Change Keyboard Settings] -> [Psysical Keyboard Layout setting] and click the American Standard keyboard again,

and the problem seems to be fixed and i still can zoom over and over again while the the left click still working good.
[Android Software/Hacking General [Developers Only]] rocketero:
how come that now that I went back and use the su from superuser3.2x86 apk now root is kind of mess up. when I open terminal ide and type su it goes back to the $ prompt and not asking for root access. I did set up prior to this, the superuser4bs to 'allow' instead of prompt.

all apps that work with root don't work now, like root explorer says 'could not managed to obtain root access' but before that there is the message " application failure, try again', I guess this message comes from 'superuser4bs apk'.

update: all works fine only if I set the superuser4bs to 'PROMPT' instead of ALLOW.

but is kinda defeat the whole purpose as once you have set the apps that need root with 'prompt', one should be able to then set 'allow' so one doesn't have to answer every single time that these root apps are launched.

by the way, th Root.fs I placed in the .rar for download has the su from superuser3.2x86 apk so it's good to go.

And about the Angry birds I still have same issue, after changing the keyboard layout. I do have a crappy mouse so I don't know if the root of the problem is due to this.
[Android Software/Hacking General [Developers Only]] codelover:
Argh...at last i know what was the problem, i messed-up with my Superuser version. The one i have always works because i am using the same version of su & Superuser, but when i wrote the guide i linked the wrong superuser version, that's why some people faced problem using the guilde. :silly:

The matter of fact, the one i am using is Superuser-3.2-RC3-x86-signed.zip as the file has last modified date (Sun, 19 Aug 2012 01:01), later than Superuser-3.2-x86-signed.zip (Sun, 8 Jul 2012 00:44), and guess what, they are using different su version! My Superuser4BS.apk is modded againts v3.2RC3 so you'll have to use su that comes with v3.2RC3. Again, sorry for any inconvenience caused.

For the game, i changed the Settings when i was playing the game and the mouse failed to work, and it's back functioning right after i changed, didn't close the game at all.

Try to play with other keyboard settings.

To @mohazia, just noticed you have my guide in your post, it's no longer valid as i have already edited the guide.
[Android Software/Hacking General [Developers Only]] mohazia:
I already start rooting using official "Superuser-3.2-RC3-x86-signed.zip", but now I swap superuser.apk with yours, and rar it with official su.X86-3.2.

Guide was updated.

[Q1] If I use BS, install apps, register accounts, sync gmail, facebook. I change my root.fs with other root.fs, should I got prob due to miss sync between /system & /data (as installed apps)?

[Q2] in BS I have full root permission, but via adb root -> "restarting adbd as root" & devices disconnected.
[Android Software/Hacking General [Developers Only]] codelover:
Remember to use su from 3.2 RC3 x86 and update the guide.

A1) Yes and No, apps never get installed in system unless you manually place them there, and no apps setting being saved in Root.fs. So it's ok as long as no apps conflict. Eg: /data/app/ & /system/app/ have the same apps, version mismatch, missing apps, etc.

A2) The default adbd does not run as root, alternative you can run > adb su -c "command" as suggested by @Rocketero
[Android Software/Hacking General [Developers Only]] mohazia:
Ahaaa goood, thaks boss

what guide do u refer to be updated? I already use official su binary "Superuser-3.2-RC3-x86-signed.zip" but I finally I did not used official superuser, I used urs.

your guide of updating su and superuser via adb? I took it from here
[Android Software/Hacking General [Developers Only]] rocketero:
I think that the important think is that you finally nailed it. Now with this RC3 su is working as it should. No more popups asking for root access after the first popup.

I guess I'll have to create another Root.fs for others to download, but my question is, should I also replace the superuser I placed in /system/app (superuser.apk v3.1.3) for the modded one you posted on 668 (superuser4BS), and renamed it superuser.apk when placed back into /system/app ?
[Android Software/Hacking General [Developers Only]] mohazia:
this one is 3.2 not 3.1.3, I integrate it in my root, and now it's 3.2

edit it----------------------------------

sorry for miss understood, yes, just replace
[Android Software/Hacking General [Developers Only]] J94w:
When trying to run registry fie, i keep getting an error telling me that its not a registry script
[Android Software/Hacking General [Developers Only]] tenet421:
Working Registry File

Thanks again @j94w

New .zip file 'a' here

Sorry, had to get some stuff submitted elsewhere and was rushed; forgot to enter the first line Windows Registry Edito...blah,blah. My bad ;)

---------- Post added at 11:36 PM ---------- Previous post was at 11:28 PM ----------

@j9w4

all the modified files (initrd-betahack.img. ramdisk.img, and system.img) are to be placed in "C:\ProgramData\BlueStacks\Android\"
[Android Software/Hacking General [Developers Only]] nagar.xda:
thank you dear,

I Replaced Files and changed GUID but once i start bluestacks close automatically before starting, Plz Help, and how to get adb.

Tnaks
[Android Software/Hacking General [Developers Only]] tenet421:
After changing the guid did you run the .reg file?

There are guides around for setting up adb on a Windows machine. Google that then try running BlueStacks then #adb connect 127.0.0.1:5555

EDIT: also, which system.img are you using?
[Android Software/Hacking General [Developers Only]] dewobedil:
how to extract the system.img file? do you mean system.sfs and then renamed to system.img ?

thanks

---------- EDIT ----------

i am finally able to extract system.img from the system.sfs file. just had to download squashfstool and extract the file :D

Thanks for the great tutorial!

mine has been rooted now :D
[Android Software/Hacking General [Developers Only]] J94w:
Hey, thats the point of being a tester lol, making sure that everything works, and thanks!! that got me kind of stumped both the registry and the placing the files haha..

And its no problem, adds more suspense with waiting, also gives time to pick though the files haha

Another thing you can add for newbie's in the tutorial is that they have to go though reg edit to find the GUID, I was lost on how to find the GUID, until I re-readx and was messing around with the reg file trying to make it work.
[Android Software/Hacking General [Developers Only]] tenet421:
System resized!!!!!

Sorry if my posts are not clear enough for you all :)

Been putting in some work here... I resized system.img and I have 50 MB free!!!!

Not possible for a tutorial really but if xRepinsSporsx will pm me his email I will give him the resized .img
[Android Software/Hacking General [Developers Only]] DEAD41:
Can somebody explain How to get system.img file
[Android Software/Hacking General [Developers Only]] tenet420:
EDIT: To get a fresh system.img

1. Use 7zip to extract Root.fs

2. Download unsquashfs.exe

3. Right click system.sfs (extracted from Root.fs) and choose to open with unsquashsfs.exe

4. Move system.img (unsquashed from system.sfs) to \programdata\BlueStacks\Android\
[Android Software/Hacking General [Developers Only]] DEAD41:
7zip keep saying cannot open file as archive
[Android Software/Hacking General [Developers Only]] nitin1978:
Thanks, m trying this now
[Android Software/Hacking General [Developers Only]] tenet421:
Extracting system.img

Update:

To extract system.img from Root.fs you are going to need 3 tools-

osfmount

Ext2fsd

and

unsquashfs.exe

First, install osfmount and Ext2fsd.

Next, run Ext2fsd (Ext2 Volume Manager)

-Select the tools menu

-In 'service startup mode' select "SERVICE_DEMAND_START"

-Near 'Service Status' is a button that reads "Start" >press it, apply, accept 'yes' at the warning prompt

-Minimize Ext2 Volume Manager

Then, run Osfmount

-Select 'Mount New'

-Leave all settings at defaults

-Under 'Image File' click the box to browse for where Root.fs is located and select it

-Select 'Ok"

***At this point you should see the osfmount windows showing a drive letter and the path to Root.fs. The drive is 'mounted'***

-Right click the drive in Osfmount and select 'Open'

-An explorer window should pop up with the contents of Root.fs -two folders named /android and /lost+found

-Open the /android folder and two files are in there - ramdisk.img and system.sfs

-Right click system.sfs, select copy, then paste the system.sfs file in a directory you can work in -like your desktop

-Right click on the system.sfs file that you placed in a working directory (desktop, etc.) and choose 'open with'

-Use 'Browse' to locate unsquashfs.exe and select it to open system.sfs

-unsquashfs.exe will extract the contents of system.sfs to the folder/location it is in (wait for command windows to close on its own)

-Open the folder containing the system.img file

-Copy/paste system.img to \%programdata%\BlueStacks\Android

*Hope this helps
[Android Software/Hacking General [Developers Only]] AndroidFileHost:
I am uploaded the system.img so users wont have to.

http://www.androidfilehost.com/main/Misc/Bluestack/Rooting BlueStacks Beta/

let me know if that works :)
[Android Software/Hacking General [Developers Only]] tenet421:
@Repins

Thanks, it works.

However - Gmail still fails.

Please check pm.
[Android Software/Hacking General [Developers Only]] borce_razor:
How to increase the size of system.img ? It says "not enough memory (~5.2MB)"
[Android Software/Hacking General [Developers Only]] tenet421:
To resize system.img you need a Linux build and command line.

Can I ask, what are you trying to place in system? GAPPS requirements?
[Android Software/Hacking General [Developers Only]] AndroidFileHost:
I sent you pm with ftp info. If you want to replace the system.img with your custom one.

Thanks
[Android Software/Hacking General [Developers Only]] tenet420:
Ok thanks!
[Android Software/Hacking General [Developers Only]] J94w:
Deleted Post
[Android Software/Hacking General [Developers Only]] borce_razor:
I just extracted clean system.img from root.fs, changed registry settings in order to properly run the bluestacks, successfully rooted it + google play install with adb push to /data/bst, but when I try to install any apk, I get "not enough system memory" error. In titanium backup it shows only 5,3MB free memory in system partition (system.img)
[Android Software/Hacking General [Developers Only]] codelover:
Yeap you have to use Superuser 3.2 RC3 so that all features work properly, especially the Auto Response, i guess i was wrong about it before - the fact that each Superuser must use their own unique version of su to function properly. yes, rename to superuser.apk if you use mine.
[Android Software/Hacking General [Developers Only]] rocketero:
but does this superuser-3.2-RC3 has the sutools.x86 ? the one you provided in post668 has a different md5sum that this 3.2-RC3 from download.android.su website.
[Android Software/Hacking General [Developers Only]] mohazia:
[Q] you got official Superuser-3.2-RC3-x86-signed.zip, ok -> extract ->

1- su -> take it to place it in /system/bin & /system/xbin

2- Superuser.apk -> open with 7-zip -> extract sutool-x68 -> rename it into "sutools-armeabi" then replace "sutools-armeabi"-> and why busybox is larger that offical pack? did u update it?
[Android Software/Hacking General [Developers Only]] codelover:
The Superuser4BS.apk is modded againts official Superuser.apk 3.2 RC3, as the one i have since day one is v3.2 RC3, never use the july v3.2 version, just when i wrote the guide accidently linked the wrong one, thought they were same, which is not the case.

---------- Post added at 06:03 PM ---------- Previous post was at 05:49 PM ----------

Yeap, replaced with the smallest dumpy x86 busybox version i could find, it doesn't even have the functions needed by Superuser, but it doesn't matter as those functions are only required for temp unroot which you will never needed for BS. And when i named it Superuser4BS it's really mean for BS only.
[Android Software/Hacking General [Developers Only]] mohazia:
if I got that , am I OK, or also I can get the same result with the wrong susperuser.apk
[Android Software/Hacking General [Developers Only]] rocketero:
when you say 'moded' you mean you extracted the sutools-armeabi and renamed it sutools-x86 ?

so I should use the superuser.apk that has md5sum; AD16DCFB26B8A3A3F50CDB7F5D5803A2 ?
[Android Software/Hacking General [Developers Only]] codelover:
If you got that your Superuser is ok. You mean you can get that with official Superuser 3.2? Really? The problem we face is that when you install Superuser it has sutools arm version installed by default because the app detects system as an arm processor, i don't know about latest version of BS cause i haven't update my BS to latest. Can you double confirm by uninstalling Superuser properly and then install the official Superuser.apk 3.2, not delete the folder and apk directly. need to know, curious...

---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------

Er....the other way, sutools-x86->sutools-armeabi. It's up to you but @mohazia said he can get rid of the red warning message with the official 3.2 apk which i could not confirm, maybe you can help me have a look, if that is true then you don't need my Superuser4BS anymore, yeap i reconized that md5, it's mine.
[Android Software/Hacking General [Developers Only]] rocketero:
I'm running BS 077813.

I unintalled the superuser4BS (com.noshufou.android.su) through adb

installed through adb the superuser 3.2.x86 RC3 from download.android.su/superuser.

then opened superuser in BS and it shows the red path not green. Also in /data/data/com.noshufou.android.su/files the sutools is not the x86, is the armeabi (size 92Kb)

Edit: Also before proceeding to uninstall superuser4BS, I noticed that in /system/app there was not longer the superuser.apk after it was rm on step 04 from the process in post 668.

I also tested the 'busybox' that is placed on '/data/data/com.noshufou.android.su/files/ and that version does not work with BS, it comes with error message: not executable magic 7F45, as it's armeabi not x86.
[Android Software/Hacking General [Developers Only]] codelover:
See, the default one will always install the arm one in BS, not sure how @mohazia managed to get rid without fixing it manually, maybe his PC+BS make the app thinks it's still running x86.

---------- Post added at 06:52 PM ---------- Previous post was at 06:48 PM ----------

You know why there exists post #668? because i know you cannot uninstall any app that is installed in /system/app/ without manually removing the apk first. :P
[Android Software/Hacking General [Developers Only]] mohazia:
No, I'm now using ur superuser, but I want to confirm method of modding to add it to guide. I write the guide u can found it at the botton of the full guide.
[Android Software/Hacking General [Developers Only]] rocketero:
so if we use the moded superuser4bs,apk that you posted on #668 ( which is working fine in BS 077813 bundled with the su from superuser-3.2.x86-signed from download.android.su website), and place it in /system/app (as superuser.apk) when creating the rooted Root.fs, would it work afterwards? I am not quite sure as the normal installation of BS wouldn't have a /data/data/com.noshufou.android.su folder (or app) there. So how is going this superuser.apk in /system/app would get installed after one place the rooted Root.fs in ../android folder ??
[Android Software/Hacking General [Developers Only]] mohazia:
Did you get busybox x86 from HERE

---------- Post added at 02:22 PM ---------- Previous post was at 02:12 PM ----------

Acualy my mistake at the beginig was replacing my official /system/app/superuser.apk with your /system/app/superuser.apk and delete /data/data/com.noshufou.android.su, when I excute BS, no superuser app.

Then I tried your adb command to remove old superuser.apk and uninstall com.noshufou.android.su, but can't inspit that I have root permission inside BS.

That why, I remove BS, and start from scrach and offical /data don't have /data/data/com.noshufou.android.su, so I add your /system/app/superuser and sure add official su to /system/bin and /system/xbin with fixing permission. And now it's working.
[Android Software/Hacking General [Developers Only]] rocketero:
I'm going to test it, creating a new rooted Root.fs with the superuser4bs.apk in /system/app and su.3.2x86 RC3 in /system/bin and /system/xbin, to see afterwards it installs in /data/data/ as com.noshufou.android.su . .. so for that I will rm with adb the com.noshu.... I have right now and see if it works after the new Root.fs is placed in ..../android.

Edit: Success!, now the new rooted Root.fs with su-3.2-x86-RC3 and modded Superuser(4bs) in /system/app works and sutools is the right one.

I'll be uploading it to my dropbox in a lil while.
[Android Software/Hacking General [Developers Only]] codelover:
su v3.2 RC3 is inside Superuser-3.2-RC3-x86-signed.zip NOT Superuser-3.2-x86-signed.zip. Then it should works perfectly. It's will install automatically when booted as long as there isn't any other Superuser installed in the system, where the apk is in /data/app/ and the app folder already exists in /data/data/com.noshufou...
[Android Software/Hacking General [Developers Only]] rocketero:
this is what I did:

- First I uninstalled through adb com.noshufou.android.su to make sure there was nothing in /data/data

- Edited the system.img from Root.fs and place the su from superuser-3.2-RC3-x86-signed into /system/bin & /system/xbin, chmod 06755

- placed Superuser4BS.apk in /system/app as Superuser.apk

- repacked the new rooted Root.fs

After placing it in .../android and restarting BS, there was already a superuser icon in the drower, I launched it and it shows all in green in the path. I checked the sutools file and it was the right size for the x86 (172Kb)

I then launched terminal ide and just for a second it didn't give me root when I typed 'su' but that's was because the popup for asking for root access took a bit longer to show. but once it showed and replied to it, the su command worked fine. same as with Root Explorer an Titanium backup. all of them got the first popup but after the second launch of those apps there was not more popups and got root acces fine.

Edit: The link to the new rooted Root.fs + Initrd.img.rar file is the same as before, as dropbox allows to change the file with the same name and keeps the same link. Just the md5sum has changed: FFA77658EF35AACDDA06B379CBF52CB8

So if @mohazia wants to consolidate just one link for the Root.fs and Initrd.img in your guide that would be better than placing 2 different versions. O place the same file in another cloud website so there is a fall-back in case one cloud site goes down. Just a thought.
[Android Software/Hacking General [Developers Only]] codelover:
Just in case you don't know, you can leave the name as it and it will still work.
[Android Software/Hacking General [Developers Only]] rocketero:
that's good to know, I didn't know it.

So we have advanced now a great deal, with a well rooted BS07.7.813. What's the next project?
[Android Software/Hacking General [Developers Only]] mohazia:
Right, same as what I did. But the [Q] now how did codelover mod superuser4bs.apk

Correct me if I'm wrong.

1- Download official superuser 3.2 RC3.zip -> extract superuser.apk

2- open it via 7zip -> assets -> extract sutool-x86 -> rename extracted sutool-x86 to sutool-armeabi -> replace sutool-armeabi in side 7zip with renamed extracted file.

3- replace busybox-armeabi with busybox-x86 <from where did you bring this busybox>

I open busybox official site HERE

I download busybox-x86_64 -> rename it to busybox-armeabi and replace same file in superuser.apk (that opened in 7zip) -> remove /system/app/superuser.apk and uninstall /data/data/com.noshufu.android.su via codelover adb commands

I tried to install modded superuser.apk via codelover adb commands but failed

Then, mount root.fs -> mount system.img -> add moded superuser.apk in /system/app -> umount all -> open BS

I have superuser and sutool green :thumbup:

I open Terminal Emulator -> su -> get root prompt -> get root permission :thumbup: -> then write "busybox" :mad: error with excutable permission.

By the way /system/xbin/busybox should also be x86?

I repeat superuser.apk removal then repeat all previous steps with codelove modded superuser(4bs).apk -> run BS -> terminal emulator -> busybox work fine.

So, plz can we have busybox resources for both /system/xbin and modded superuser.apk :banghead:
[Android Software/Hacking General [Developers Only]] rocketero:
you don't need the superuser.apk from superuser.3.2.x86.RC3. just use the @codelover's Superuser4BS.apk, not need to 7zip it, just place it in /system/app. it works.

the only thing you need from superuser-3.2.x86-RC3-signed.zip is the 'su' file in the /system/bin folder (after unzipped).

busybox_x86_64 does not work with BS, I already tested it, it gives error, non executable, magic 745F or something in that order. So far the only busybox that works is v.1.16.2 that comes with original BS. if one of you find a later version that works with BS let me know.
[Android Software/Hacking General [Developers Only]] mohazia:
I used it already, I want to fullfill the guide. For next updates. If we leave BS, next members can do it.

---------- Post added at 03:58 PM ---------- Previous post was at 03:55 PM ----------

The next project should be guide for mod initrd.img, to write the full guide.

I don't know if codelover can help us, or we should ask merrickville
[Android Software/Hacking General [Developers Only]] rocketero:
I just received in the mail an order I had placed 2 months ago from China, it's a Mini Android 4.0 PC (Mk802 device), at that time it cost me $56 plus another $15 dollars that I had to pay for sending back for exchange as it has a problem with the screen going black and never coming back from black. This new device is working great, hope it stays that way. The price has come down dramatically since then, now in Amazon one can get it for $39.00 with free shipping.

it has a slot for a SDcard, USB port where one can place a usb-hub and connect mouse/keyboard/hdd-sticks. a mini hdmi port to connect to an lcd tv/monitor. Not a bad gadget for the work it does. It connected wirelessly to my comcast box and I'm right now using ES file Explorer and Google Store to install apps. Only one Angry bird version so far works, still testing.

---------- Post added at 02:09 PM ---------- Previous post was at 02:03 PM ----------

There is not really much to it with the initrd.img. the difference from the original from BS and the one we are using is in one character, as @codelover pointed me a long ago and many pages back. there is not moded initrd.img, just an edited one, as I said with only one character of difference from the original. What merricville did was something in another direccion as he uses a different approach to root BS.