yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] kianty99:
thanks for answer

i've used ccleaner, then i've clean the registry and cancelled all folder but it say always that there is a latest version already installed (but is false)

maybe there is a corrupted file somewhere?

i've used version 0.7.2.751, it download the program but he say me this error.

there is a software to search and clean the system from update version or i must use this?

p.s. wich are the right procedure to root? the first three pages are much confusion, and in followes pages there is various mode to do---- i've used the reg file two times and it crash bluestacks with only agent open

pc with Windows Vista sp2 x64

sorry for bad english but i'm not speak english very well
[Android Software/Hacking General [Developers Only]] tenet420:
Don't say sorry - I wouldn't even be able to write one sentence of whatever your native language is :)

Did you delete the bluestacks folders in C:\ProgramData and C:\Users\YOURUSERNAME\AppData (in Local or LocalLow, can't remember which)? ProgramData and AppData are "hidden" folders so they are not able to be found using default Windows folder options.
[Android Software/Hacking General [Developers Only]] mohazia:
if you are sure that you deleted all files:

%programfiles%\bluestacks

%programdata%\bluestacks

%programdata%\BlueStacksSetup

then clean all regedit records, (I'm using Windows 7 Manager - Registry Tools v1.1, it's one of win7 manager utilities), then don't forget to restart.

for rooting, the first posts are not working now. I concluded members efforts in rooting Bluestacks at this thread, you can take a look.
[Android Software/Hacking General [Developers Only]] rocketero:
They do work, I just upgraded my BS0752700 to 077813 and applied the Root.fs and Initrd.img I was using and still it's rooted

But just for fun, and now that I still have fresh memory on how I rooted it, I have created a Root.fs rooted and with system.img resized to 500MB that is working fine with BS07.7.813.

you can download it here: https://www.dropbox.com/s/rdf35z9cupl5xnb/Root-fs_and_Initrd-img-bs077813.rar

the md5sum has changed: FFA77658EF35AACDDA06B379CBF52CB8

it contains Root.fs and Initrd.img, to install these 2 files, one can follow the FIRST METHOD explained here bay mohazia:

A few notes:

- system partition resized to 500MB

- su version 3.2 x86-RC3-signed was added not only to /system/xbin but also to /system/bin as well as busybox to keep a fallback when updating the su binary.

- binary /system/bin/ls was symlinked to busybox instead of toolbox to get nice color file listings in a terminal

- superuser4BS.apk (moded by @codelover) was added to /system/app
[Android Software/Hacking General [Developers Only]] sga999:
Rocketero, I just followed Mohazia's FIRST METHOD, along with your Root.fs and Initrd.img.. Everything went smoothly. However, I installed Titanium Backup, and it says that I am NOT rooted. Are there subsequent steps (after Mohazia's instructions) necessary to acquire root? I hope I'm not overlooking something obvious.

I did have an old version of Bluestacks from June installed, but I am sure (as much as I can be!) that it was completely deleted, registry cleaned, etc., before doing this new 077813 install.

Thanks very much.
[Android Software/Hacking General [Developers Only]] rocketero:
I'll have to look for a post here that I explained how to install T.B. get back to you with the link when I find it.

Edit: it's here on post # 493: http://xdaforums.com/showthread.php?t=1571308&page=50
[Android Software/Hacking General [Developers Only]] sga999:
That would be great. But I also tried to see about whether I was rooted in another way. Terminal Emulator, su command, still showed $ prompt, not a #. So that' makes me think that even if I get a better way to install T.B., I still won't be rooted. I think I followed the steps very closely, so this is baffling.
[Android Software/Hacking General [Developers Only]] rocketero:
open your supersuser apk and see if it shows v.3.1.3 and su v 3.2. if you don't see a popup asking for root access when you first type 'su' at a terminal then something didn't work the way it should. Also there is an app at google store called 'root checker' that will show if you are rooted.

Titanium backup doesn't work unless you use the lucky patcher and it works only with T.B v.5.4.2.1
[Android Software/Hacking General [Developers Only]] sga999:
I'll look at superuser soon. In the meantime, I tried to get your package.zip as per your instructions for getting T.B. and lucky patcher. I get the following when the download completes. I'm running Windows 7.:

"package.zip is not commonly downloaded and could be dangerous"

If I allow it rather than discarding it, then unzip, I get x80004005: unspecified error.

Is there another place to look for package.zip?

---------- Post added at 11:19 PM ---------- Previous post was at 11:15 PM ----------

Version for superuser is 3.0.7. So...how did I get an older version than I should have?
[Android Software/Hacking General [Developers Only]] rocketero:
you have to use 7zip to unzipp it, I don't think I placed that note there.

if you get a message about being dangerous is probably becouse of lucky-patcher but it should be ok. I'm going to create another package zip with wizip so that doesn't show that error 80004005

Edit:the above link has been edited on post # 493, the package.zip (rar) now should unzip with winrar/winzip/7zip.

Just remember, you should get that popup asking for root access when you open the app usually the first time, thou home apps keep asking everytime you opened them but that's also OK.

About the version 3.0.7 I don't know where you get it from. revise the Root.fs and Initrd.img to make sure are the ones I uploaded, you should see the su file in both folders: /system/bin and /system/xbin. you can updated manually if you want, first replace the one in /system/xbin so you still have root access when replacing the one in /system/bin.
[Android Software/Hacking General [Developers Only]] sga999:
I've used 7zip to unzip package.zip. But it seems like the main problem is that my superuser version is old...3.0.7 (I made a new post earlier, but it included it as an edit to another one).

So I updated superuser from the play store to get the 3.1.3 version. But now it won't seem to let me click on the menu so that I see if Automatic Response/Allow was correct! Maybe I did the wrong thing by just updating superuser. I guess the question is why did I have the older version? Did it somehow come from an old June install of Bluestacks? I don't think I had any of that old system left hanging around.
[Android Software/Hacking General [Developers Only]] rocketero:
The su that I placed on Root.fs (/system/bin and /system/xbin) is su-3.2-x86-RC3-signed . the size is 173,034 bytes and the md5sum is CF88AC4F28EFB50671207A46A43DFCE9
[Android Software/Hacking General [Developers Only]] sga999:
Thanks, Rocketero, I won't bother you any more tonight. I'm going to download your Root.fs and initrd.img again, and I'll try this all again. I really appreciate all of your help! I'll update you tomorrow on the status.
[Android Software/Hacking General [Developers Only]] rocketero:
Not a problem, I'm getting the md5sum for that root.fs and initrd.img to make sure you got the right file. they are:

MD5: 958FB2C4701811CD68946111C8F78FD2

Also there is one Note about superuser.apk. If you try to update the su binary from there it will fail. In order to fix that, download this fie (sutools(x86) and place it in /data/data/com.noshufou.android.su/files ..... if you don't see the folder files there in that location, just created and copy the sutools there: https://www.dropbox.com/s/yzhzqs1s6j825q7/sutools

then try to update su binary from the superuser apk and it should work.
[Android Software/Hacking General [Developers Only]] sga999:
Rocketero, I'm new at this, so even getting the checksum was something I had to google. I ran md5.exe and that compare worked fine. I didn't check anything with the SHA-1 value. Let me know if I need to do that one too, but I'm sure I have the right file. And I'm sure I have extracted with 7zip into root.fs, etc.

I did it again, and it's still the older version of superuser. I haven't tried the "Note" that you put in the last post. I really wanted to get this to work exactly as it is written. So I'd rather just figure out why I'm not getting the correct superuser version. I cannot see how I'm managing to get a 3.0.7 version if you are putting the 3.1.3 version into your root.fs. I'm really missing something! Is there any way to "disassemble" your root.fs and see exactly what version of superuser is there? If it's the wrong version inside there, then obviously I'm still messing something up!

---------- Post added at 01:40 AM ---------- Previous post was at 01:26 AM ----------

Gee, I have NOTHING under data at all. And I tried to create a folder structure under it with ES File Explorer as you described, but it won't allow it. What app do you use to create the folder? Then, once I get that done, I'm not clear on the next steps. Do I unzip the sutools that you pointed me to? Into .../files or into /files/sutools? And then do I run something from within that folder? Sorry for so many questions. I had said I'd wait until tomorrow, but it's bugging me!
[Android Software/Hacking General [Developers Only]] tenet420:
I am running the 0.7.7.813 build - I used the installer from the Bluestacks website. I then rooted Bluestacks using only the "Root.rar" file that contains both the modified Root.fs and the modified initrd. Google Play installed fine, Root Checker returned a positive for root, and Titanium Backup installed straight from the market. Nice work.

I would like to offer a "theme" for people who think that the Bluestacks boot animation and user interface are dated looking. The "theme" is a combination of icons, a new splash screen at boot time, the new ADW home launcher for an ICS look, and the app PicSpeed Wallpapers to enable non-stretched non-blurry wallpapers. The instructions are included in a readme text inside the included zip and are simple.

Please feel free to learn by example and make your own theme by replacing the included files with some of your own colors, styles, backgrounds, etc.

Enjoy, and smash that thanks button if you're feeling friendly...

EDIT: just so people understand - you don't need root to make these changes, most of it is on the Windows side.

Also, there is a method for increasing RAM for Bluestacks to 1GB (or more) through the Windows registry for those who haven't read the entire thread :)
[Android Software/Hacking General [Developers Only]] mohazia:
Don't over guess, yes the integrated superuser.apk is old, just update it via google play. but make sure you select automatic response is allow.

it should works, I just try it.
[Android Software/Hacking General [Developers Only]] sga999:
I did update superuser to 3.1.3 through the Play Store, but it won't let me click "settings" so that I can change automatic response. Sorry, I'm not trying to over guess....I'm trying to use the procedure as given. Rocketero said the root.fs would have the 3.1.3 version already in it. I think you're saying that is not so.

If I update superuser, I get the problem where I can't click settings for that app. I can then go back and uninstall, it reverts to 3.0.7, and then I am able to click settings. What do I need to do to get the settings to show for me?
[Android Software/Hacking General [Developers Only]] tenet420:
Before updating superuser from the play store you need to open superuser>settings and first update the binary. After that succeeds, update the superuser app in the market.
[Android Software/Hacking General [Developers Only]] mohazia:
OK, I know that's seem to be crazy, the same file works her and there, but not working for u. OK, I think you can download this and reply plz
[Android Software/Hacking General [Developers Only]] sga999:
tenet420, if you mean update the su binary, it says it is already up to date.

mohazia, same result with the .rar file you just gave me. It still shows superuser 3.0.7. So as tenet420 suggested, I tried to update the su binary. That failed because it said it was already up to date (3.2). Then I went to the Play Store and updated superuser to 3.1.3. And now I cannot click on the "settings"! Actually, in Bluestacks, it is the "Show Menu" button to the right of the back button at the bottom left corner, right? I can click that on the 3.0.7 version, and I can change the automatic response, but after I update it to 3.1.3, I can no longer click that.

---------- Post added at 02:46 AM ---------- Previous post was at 02:30 AM ----------

Okay....it appears that superuser changed between version 3.0.7 and 3.1.3 about how to change the settings or preferences. For 3.0.7, the "Show menu" button brings up Go Elite!, Clear log, and Preferences at the bottom of the screen. Then Preferences contained the automatic response setting. For 3.1.3, that same "Show menu" button no longer works for me, but there is a wrench at the top right corner of the superuser app screen, and when I click that, there are MANY options, one of which is the automatic response. I changed it to "allow". I do not see any choice for updating the su binary on this "wrench screen" like I did before on the "preferences screen".

Result is still...I am not rooted. I am using terminal emulator or root checker to check if rooted. I'll use Titanium Backup to check it later, but I don't really need it yet..

Goodnight, guys. Thanks for all your help. I'll try again tomorrow.
[Android Software/Hacking General [Developers Only]] rocketero:
just for kickers I updated the root.fs with su v.3.2 (x86) ( I had su 3.1.3 before in system.img), it's in /system/bin and also in /system/xbin.

it's the same link as I posted before, thanks to Dropbox that let you update a file with the same name and the link stays the same.

just the md5 changed and the new is:

MD5: 958FB2C4701811CD68946111C8F78FD2 (for the file Root-fs_and_Initrd-img-bs077813.rar)

if you want to check the su file in /system/bin, the size now is 173,034 bytes, and its md5sum is: FFA77658EF35AACDDA06B379CBF52CB8

to check md5 in bluestack it's simple, change directory to where su is and then use the command: md5sum followed by the name of the file.

cd /system/bin (or cd /system/xbin)
md5sum su

also you can check that /system partition is now resized by using the command:

df -h /system

Do also as tenet420 wrote, check the settings of superuser and update su if necesary, then update superuser. the version 3.0.7 you were talking about was not of su, I think you were referring to the version of superuser which can easily updated from Google store.

And lastly the sutools is a file, and it should be placed in /data/data/com.noshufou.android.su/files, then you can update the su binary using superuser apk.

By the way, @tenet420, that's a nice looking theme for BS, I'm sure will be using it from now on, same as the splash logo.

Regards.
[Android Software/Hacking General [Developers Only]] codelover:
About the su v3.2 & Superuser v3.1.3 pair, actually the perfect match would be su 3.2 & Superuser 3.2 RC3 apk.

It's just the red warning message problem, but as you tried before you can swap the arm version of sutools with x86 and it will work, tested.

One can use the official su v3.2 inside this zip and my modded Superuser4BS.apk v3.2 RC3 that contents both x86 version of sutools.

For those who already have their old version Superuser.apk installed, the trick is to remove the /system/app/Superuser.apk manually, then reinstall:

01) adb root
02) adb connect 127.0.0.1 # If 'adb device' return empty result
03) adb shell su -c "rm /system/app/Superuser.apk" # or lowercase 'superuser.apk'
04) adb uninstall com.noshufou.android.su
05) adb install Superuser4BS.apk

If you want to replace/update your existing su, run the following commands:

06) adb push su /sdcard/su3
07) adb shell su -c "cp /sdcard/su3 /system/xbin/"
08) adb shell su -c "chown 0.0 /system/xbin/su3"
09) adb shell su -c "chmod 6755 /system/xbin/su3"
10) adb shell su -c "mv /system/xbin/su3 /system/xbin/su"

The above code assumed that you already have rooted and writable (rw) /system/ and downloaded Superuser4BS.apk, Superuser-3.2-RC3-x86-signed.zip and extracted su and placed them inside adb folder.

Thanks @rocketero for testing.
[Android Software/Hacking General [Developers Only]] rocketero:
@codelover, where did you get your su.3.2.x86? it has the same size (140KB) as mine, but the md5 is different. I got it from http://downloads.androidsu.com/superuser/ extracted from Superuser-3.2-x86-signed in that site.

I'm trying to follow the code you wrote above. when I type 'adb devices' I see the emulator-5554 listed as device, but after using the code: 'adb root' and typing again 'adb devices' nothing is listed. I've done twice and the same, I then have to type 'adb kill-server' and then the emulator-5554 get listed again.

Note: I'm doing this from my Windows 7 64bit PC in an MSDOS window, not inside a BS terminal.

Edit: I got pass the point where the device was not listed by ommitting the command 'adb root' and instead using

adb shell su -c 'rm /system/app/superuser.apk' ([COLOR="Blue"]lowercase s as that's the name I gave it when I rooted it[/COLOR])

But I am still not going through the next command, I'm getting this output:

C:\>adb install superuser.apk
1756 KB/s (843503 bytes in 0.469s)
pkg: /data/local/tmp/superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]

C:\>adb uninstall com.noshufou.android.su
Failure
[Android Software/Hacking General [Developers Only]] codelover:
If you check the above link you should be able to see i linked the su.3.2.x86 from the official source.

As for the adb root problem, thanks for that i think i need to update the code.
[Android Software/Hacking General [Developers Only]] rocketero:
ok I got the su from that link you posted...., now I passed the point and I could now install the superuser.apk, then uninstall com.noshufou.android.su, and then install Superuser4BS.apk.

but the next point doesn't want to go, the 'adb push su-3.2-x86 /system/xbin/' I get:

C:\>C:\>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting adbd as root

C:\>adb devices
List of devices attached

C:\>adb connect 127.0.0.1
connected to 127.0.0.1:5555

C:\>adb devices
List of devices attached
127.0.0.1:5555 device

C:\>adb push su-3.2-x86 /system/xbin
failed to copy 'su-3.2-x86' to '/system/xbin/su-3.2-x86': Permission denied

I did as you posted, adb root, then as there were not devices listed with 'adb devices' I did 'adb connect 127.0.0.1' and after that that's when it failed with the 'permission denied'.

I check in BS I still have root access in a terminal, as I have su in both /system/bin and /system/xbin folders. and I did check in Root_Explorer that / was RW same as /system/xbin is RW

Note: I am just trying to follow the code you wrote, because I can easy bypass it by just going into BS and in a terminal or with Root Explorer rename the su I have there and then copy this new su as having this binary in 2 places that are in the PATH allows to rename/delete one while this new su is copied to it and then do the same with the other one in the other folder.

But I would like to learn why I can not do it from the MSDOS with adb.
[Android Software/Hacking General [Developers Only]] codelover:
How about adb push su-3.2-x86 /system/xbin/ (with / at the back), another possible reason is that your adbd does not run as root, what you get with 'adb shell whoami'?
[Android Software/Hacking General [Developers Only]] rocketero:
with the forward-slash still get permission denied. and adb shell whoami does get 'shell' as result. got not idea why if adb root did executed at the beginning. I did tried again, killed adb server, then did adb root, adb connect 127.0.0.1 and I get again 'shell' as result for 'adb shell whoami'.

But inside BS, in a terminal after typing su, then whoami I get 'root' as result.

about the commands in adb, the only thing different I noticed is that without the adb root, when doing 'adb devices' one get 'emulator-5554' as device, but with connect 127.0.0.1 is another port: 5555. could be this the issue at hand?

As an aside note, I have already replaced the su in /system/xbin and /system/bin with this new one that has md5 122068847AD1DCB2A8F072776E3DA20A by the procedure I mentioned above using first ES File Explorer to copy from PC to BS then using terminal ide apk to copy to system/xbin and .../bin to chmod it. But still curious about the adb method.
[Android Software/Hacking General [Developers Only]] codelover:
Nop, that is not the problem, perhaps my code might not work for all, as i thought 'adb root' supposed to give you run commands as root like real device. For your information there are at least two ways to have adbd be able to run as root:

1) Replace with a modded one that always runs as root

2) Mod init.rc and force adbd to run service as root

But above required more works so the easiest way is still directly replacing the modded files in image files, but since you already have su 3.2 you don't have to replace it because both version work fine even they have a diff checksum.
[Android Software/Hacking General [Developers Only]] rocketero:
I may have not been clear, I did replace the su for the one you posted. there is not need to modify the images files. the reason for that is that as I placed su in both folders: /system/xbin and /system/bin, these 2 folders are in the global environment PATH so if you rename one su in one folder while you copy the new version, you still have root as the other su in the other folder act as fall-back. that way you can do it inside BS without having to bother working again with the images.

regards. and thanks for the code to install the new superuser4BS
[Android Software/Hacking General [Developers Only]] codelover:
I think su can be replaced directly with other version as long as the new one has all the proper ownership & permission set before replacing.

Ofcause it's always a good idea to have Plan B. About the images, i mean the 'images' for other users since you are providing Root.fs to users that prefer simple step to get rooted.
[Android Software/Hacking General [Developers Only]] dari-woka:
Hi!

Does anyone knows how to "redirect" the option icon?

So instead of opening the configuration app of blustacks, open the original android menu

(The one that is on the right at the bottom)
[Android Software/Hacking General [Developers Only]] rocketero:
you don't need that icon if you install a different launcher like ADW or GO Launcher EX HD,... these launchers will make the second icon at the bottom (left) to take you to the 'android menu'.

Also with these launchers and tenet420 new configuration theme you'll have an extra icon on the right to make BS full-screen or windowed. Besides with these launchers you'll have Google Play Store icon in the main screen as you can not get it with the BS regular home launcher.
[Android Software/Hacking General [Developers Only]] lalo3:
****ty BS

I also have the same problem than a user on the previous pages.

Installed the last BS of this topic unnistalled it with CCLeaner, but Only deletes the Installs of BS nothing more.

Any file got deleted, i have deleted programdata/bluestacks and bluestackssetup

And in programandsettings x86 Bluestacks. Also i have checked the Log of the program and it's shows a registry files, showed a lot of this, deleted everyone and nothing ........

I can't install bluestacks cause the system reconigze it like is already installed.

Also ----------

FMF have a new version update yesterday (9.0) that blocks Bluestacks emulator shows This App Doesn't Run on Emulators.

Some people tested it with YouWave, and works good without anyproblem but Youwave isn't good like Bluestacks atm, anyone can do a bypass for this ****ty app?

Thanks you for helping me there, and sorry for my english cuz i'm spanish :P