yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mohazia:
aha, thanks.

The image u just share didn't had google account, right.

I had now data.fs and sdcard.fs, which I extracted from BS 0.7.2... and already integrated into my BS 0.7.7.813, the advantages of .fs that I can resize it very easy. Do u advice me to share it? :confused:

actually, rooting and make some customization, was attractive, now joy was solved, it's boring :rolleyes:

I can't even play where's my water? on BS, is for me only or with all?
[Android Software/Hacking General [Developers Only]] rocketero:
I do have a sdcard.fs of 8GB working with v0.7.7.813, but even that I have not much in it the size would be huge to share it which makes it almost impossible to upload to any file-sharing site like dropox or box.net. I saw in an old post a shared sdcard 2GB in size but that's the default size when installing BS older than 0.7.3.x I believe. The Data.fs it has been always 2GB in size.

The good thing from updating BS from older versions to the new ones is that it will carry out the old Data.fs and Sdcard.fs and it will incorporate them into Data.sparsefs and SDcard.sparcefs

About the apps/games that run in BS it's just trial an error, sometimes very disappointing that it doesn't run the one's preferred apps.
[Android Software/Hacking General [Developers Only]] tichs:
It says that "Blue stack player app download in progress" and says its "already installed", error. idk what happens
[Android Software/Hacking General [Developers Only]] rocketero:
You'll get more responses if you post on the official BS thread here: http://xdaforums.com/showthread.php?p=33701742#post33701742
[Android Software/Hacking General [Developers Only]] kianty99:
11- Open Superuser -> Settings -> Automatic Response -> Allow
Now your BlueStacks have root permission and google apps.

you mean that now i don't need anymore google play store because the Google apps are integrated in my bluestacks market?

thanks
[Android Software/Hacking General [Developers Only]] mohazia:
no what I actually meant is that ur system now have google permission, you can now install google play and it will works.

OK, when I did this guide, I did not differentiate between apps that set on /system/app and /data/app.

I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
[Android Software/Hacking General [Developers Only]] kianty99:
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install

excuse me... i have search for google play apk on first post but i don't found it... where is it?

thanks
[Android Software/Hacking General [Developers Only]] mohazia:
I'm review now the method from scrash
[Android Software/Hacking General [Developers Only]] kianty99:
i've installed the two apk you mentioned and say me an error:

apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
[Android Software/Hacking General [Developers Only]] mohazia:
OK, I just remove BS, for re-install it, to start from scrach, I will update soon
[Android Software/Hacking General [Developers Only]] tichs:
AMD Appzone its better than bluestacks? I read that they have some unique technology that uses the gpu to accelerate everything, is that available to normal blue stacks builds?
[Android Software/Hacking General [Developers Only]] mohazia:
no, bs is a no gpu accelerator. Even youtube not work
[Android Software/Hacking General [Developers Only]] mohazia:
1- Now delete ur root.fs & data.s* from %programdata%\bluestacks

2- Extract data.s* from the archeive @ %programdata%\bluestackssetup on %programdata%\bluestacks

3- Follow new guide (exactly) with excluding steps 1 and 3 (just skip and contiune in same sequance)
[Android Software/Hacking General [Developers Only]] tichs:
so they are the same thing right just different name?
[Android Software/Hacking General [Developers Only]] Almighty2:
Instructions on what to do with the files?
[Android Software/Hacking General [Developers Only]] FalcionX:
CHECK
[Android Software/Hacking General [Developers Only]] Almighty2:
Thanks, have a question. Why is the initrd.img and Root.fs smaller than the stock version? Was something taken out?
[Android Software/Hacking General [Developers Only]] FalcionX:
Read/Write for /system added repacked with FLATE compression so it can be smaller

Defragmented and compacted file system + shrink for smaller file
[Android Software/Hacking General [Developers Only]] Almighty2:
Thanks!

Am I correct that only replacing initrd.img and Root.fs will give root already? If I use all the files in the repack, will the existing installed apps still be there?

Also, anyone managed to get SuperSU installed on a already rooted bluestacks?
[Android Software/Hacking General [Developers Only]] FalcionX:
Simple....

Root.fs = Important System files !

Data.sparsefs = There some data files for system files too !!

initrd.img = mount points system config at boot time etc...

soooo... mixing that files is not recommended ! can give you errors in some apps or no... you're warned :D
[Android Software/Hacking General [Developers Only]] Almighty2:
Interesting, I read about replacing Root.fs and initrd.img to root bluestacks but never knew about Data.sparsefs as I only replaced the former two and it seems to work. Is /data in any of those 3 files?
[Android Software/Hacking General [Developers Only]] FalcionX:
/data is in Data.sparsefs unfortunately
[Android Software/Hacking General [Developers Only]] Almighty2:
I tried replacing data.sparsefs and all the /data stuff is gone... So right now I'm just using Root.fs and initrd.img and it seems fine so far... Thanks for taking the time to answering questions!
[Android Software/Hacking General [Developers Only]] sto1911:
I'd like to copy files from PC to Bluestack. How can I do that? - OK, I've managed to find the shared folders :)

However if I press the settings button nothing happens...
[Android Software/Hacking General [Developers Only]] rocketero:
If you're using the [MENTION=5006850]FalcionX[/MENTION] .zip file, uncompress it with 7zip, then go to c:\programdata (this is a hidden folder, need to setup windows explorer to see hidden folders) and first make a backup of c:\programdata\bluestacks folder, then replace all the files and folders with those in the extracted .zip to that location.

regards.
[Android Software/Hacking General [Developers Only]] sto1911:
I've done the same and it booted up fine. However I cannot access Bluestack settings (gear icon on the overlay) to change my app sizes to tablet.

I've just tested it what happens if I copy over only the root fs and initrd img and it seems to work fine. Root browser has asked for permissions and seems to work fine along with the settings button.

Next step is to create a cfg for Pinball Arcade :)
[Android Software/Hacking General [Developers Only]] Almighty2:
What is meant by "No Google Play Account"?
[Android Software/Hacking General [Developers Only]] FalcionX:
you will have to create them yourself :p (Play Store is included)
[Android Software/Hacking General [Developers Only]] Almighty2:
I thought that was supposed to be standard procedure anyways since it'll be funny to include a google account that everyone will be using.. LOL
[Android Software/Hacking General [Developers Only]] seancojr:
If we allow BlueStacks to update itself will that break root functionality?
[Android Software/Hacking General [Developers Only]] ughoji:
dude they have been no update since 0.8.0.2997 so your question is pointless

plss can u mod xposed installer into it am quite tired of gamevil games telling me am violating their terms cause i am trying to modify datas
[Android Software/Hacking General [Developers Only]] codelover:
Bluestacks Multi-users mode

Since Bluestacks v0.8.x running ICS just went public not long ago, do expect frequent updates as they fixing bugs.

Meanwhile, i spotted some cool (hidden?) feature in BS, guess what? The multi-users mode!

I'm not sure if this feature is completed, perhaps they are still working on it, that's why it has not been enabled by default.

Note that the files required has not been included in the setup as well.

But with my little imagination & some tweaking + coding i managed to get it working.

Imagine you can check multiple WhatsApp account on the same BS installation in the future!. :D
[Android Software/Hacking General [Developers Only]] Nephatiu:
Dunno if anybody's interested, but here are my Root.fs and initrd.img of 0.8.1.3003 -> rooted, with market, su and busybox. ;)

Links removed, newer Root.fs further down. ;)

You'll need to rename the last one to initrd.img of course. (I have the read-only original one in the same download-dir, hence the added '_rw' in the name of the download. ;p)

Anyway, enjoy! ;)

Grtz,

~ Nephatiu
[Android Software/Hacking General [Developers Only]] duphafral:
Hello!

I installed the latest version of bluestacks and the I Installed the 0.8.0 root installer for bluestacks posted by FalcionX

Rootchecker says i have root, but in ESExplorer I cant activate the root functions. Also I cant change the build.prop file.

I also tried to do this with bluestacks version 0.8.0.2997.

Any idea what I'm doing wrong?

Thanks
[Android Software/Hacking General [Developers Only]] Nephatiu:
Besides of a rooted Root.fs, you also need an initrd.img which loads /system read-write.. To do this you can follow the instructions of the OP, or download my img 2 posts up.

Just rename it to initrd.img and replace your initrd.img in the same folder as where the Root.fs file is.

P.S.: Don't forget to backup your original in case something goes wrong. ;)

Grtz,

~ Nephatiu
[Android Software/Hacking General [Developers Only]] duphafral:
Thanks a lot Nephatiu

The exe made by FalcionX was puting those files in Programs folder, not on Programdata.

I red the previous posts and found out that the exe was doing it worng, probably just in my machine, so I used the files you provided and put them in the right folder, and now it is really rooted :)

But my first problem still persists. Bluestacks is still identified as an emulator. I edited build.prop (in system folder) but it is still identified as an emulator. Do you, or anyone else can tell me what i have to do to correct this situation?

Thanks a lot
[Android Software/Hacking General [Developers Only]] Nephatiu:
Identified as an emulator where? What are you trying to do? Can't seem to find your first problem mentioned. ;)

Grtz,

~ Nephatiu
[Android Software/Hacking General [Developers Only]] Almighty2:
Seems like the installer is now installing 0.8.1.3051, any chance you have a root.fs and initrd.img for that version? Thanks!
[Android Software/Hacking General [Developers Only]] Almighty2:
I tried doing this except for steps #4 and #5, what file am I supposed to extract those files from?

F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES I got it from codelover's MOD superuser4BS.apk

Quote:

1- Download last version of Superuser for x86 from HERE

2- Download 7-Zip & install it from HERE (if you didn't have it)

3- Download latest version of "busybox-i686" from HERE to "C:\pubuntu" (take attention it should be small letter) and rename the downloaded file into "busybox"

4- Extract "\system\bin\su" to "C:\pubuntu" we need it to copy it to "/system/bin" & "/system/xbin"

5- Extract "\system\app\Superuser.apk" to "C:\pubuntu"

6- Close 7-zip

7- Open "Superuser.apk" via "7-zip" -> extract "assets\sutools-x86" -> rename it into "sutools-armeabi" -> drag it back in 7-zip to replace existed "sutools-armeabi".

8- Make copy of "busybox" and rename this copy to "busybox-armeabi" -> drag it again in 7-zip to replace existed "busybox-armeabi"

8- Close 7-zip and now, you have latest files MOD Superuser,apk, extracted "su" binary and busybox files
[Android Software/Hacking General [Developers Only]] duphafral:
Nephatiu

I'm trying to create an account in Tapporo

When I try t says something like:

we are sorry, creating an account usin emulator is not allowed, please use a real device
[Android Software/Hacking General [Developers Only]] Nephatiu:
Just rooted 0.8.1.3051 myself, here are links to them. ;p

[URL="http://bit.ly/1aed7mT"]Rooted Root.fs 0.8.1.3051[/URL]

[URL="http://bit.ly/1avRVrI"]Write-Enabled initrd.img 0.8.1.3051[/URL]

;)

Oh, and Almighty2:

You get them from the flashable superuser-zip you just downloaded in nr 1. ;)

Inside the zip it's:

"/system/app/Superuser.apk" and "/system/bin/su" ;)

Grtz,

~ Nephatiu
[Android Software/Hacking General [Developers Only]] Almighty2:
Thanks Nephatiu for the answer and files provided! I think the problem was the instructions doesn't say what to do with the file downloaded in #1 and then the next thing it says is extract so wanted to be sure I was extracting from the correct source... ;) Has anyone gotten SuperSU to work and does Google Play Services now install?
[Android Software/Hacking General [Developers Only]] Nephatiu:
No problem. ;) I don't see why SuperSU shouldn't work.

Install SuperSU
Move it from '/data/app' to '/system/app'
Reboot BlueStacks
Open SuperSU
Install SuperSU's su libraries, giving it root permissions with the other one.
When that's finished succesfully, you can remove the old one from '/system/app'
Reboot BlueStacks

That should do the trick. :p

And I don't know about you guys, but Google Play Store comes installed automatically with my BlueStacks installation in data. BlueStacks just wants you to enable their app sync and add your Google account before it will open. Should I add the play store and services in the Root.fs next update? Cause it seems to work fine from data on this end. :)

Oh, and btw, I've opened a new thread for this which I will try to keep updated. It'll be easier to oversee. It's right here.

Grtz,

~ Nephatiu
[Android Software/Hacking General [Developers Only]] Almighty2:
The problem is that SuperSU isn't able to install the su binary as it will prompt to update the su binary which is really what determines which root program to use except I think maybe the reason is because su on bluestacks is in two locations while on a regular Android device, it's only in one location. Google Play Store does come with BlueStacks but I'm still not sure if Google Play Services will work or not until after I install some things that requires it.

Forgot to ask but is ADW the stock launcher with the newer BlueStacks as I upgraded mines and was using GoLauncher so not sure if it came that way or if you included it in your root hack. :)
[Android Software/Hacking General [Developers Only]] Nephatiu:
First of all, u made me curious and I'm going to test it out right now. :D

Second, in the worst case scenario, u just check which one got replaced (by checking time of creation or modification of both files before and after) and then you just cp it to the other dir,... I suppose... :p

Anyway, I'm trying right now! :D

Well, Ingress does not work, I can tell you that. ;D

I added it, and removed BS's stock launcher apps. ;) It had to have a launcher, and the BS own launcher never shows SuperUser apps, so it doesn't seem fully rooted until the launcher has been replaced.;p

Grtz,

~ Nephatiu ;)
[Android Software/Hacking General [Developers Only]] Almighty2:
The second idea wouldn't work because SuperSU will ask to update the su binary as I've tried that before on both a tablet and phone thinking it would work when the su binary won't update from another device that has the correct su binary. Do you have a copy of BS's stock launcher app's apk somewhere? So Root.fs is really the entire /system tree.
[Android Software/Hacking General [Developers Only]] Nephatiu:
It actually didn't work, which I find weird, because I've replaced it with other Superuser apps successfully that way in the past. On phones I've even replaced the custom ROM's su app with SuperSU many times, until su apps began to come integrated into ROMs...

Maybe it has something to do with the way I made the last Root.fs, where I just put one "su" in '/system/xbin' and a symlink to that one in '/system/bin'. So there's no actual second su-file in my root. ;p Didn't seem to break root though, but maybe does break changing superuser app su-libraries. :p New things to consider on my next attempt... ;)

I just deleted it straight away, since I honestly thought it sucked. :D But I'm gonna try if I can't get SuperSU working from a fresh root cycle, and thus reinstalling it again tomorrow, at which time I will copy the (now deleted) launcher files before removing them again and link them here... Hopefully together with a working SuperSU rooted Root.fs. ;)

Root.fs contains both '/system' image and the ramdisk image. ;)

Grtz,

~ Nephatiu
[Android Software/Hacking General [Developers Only]] Almighty2:
I wonder what checks does SuperSU use on the su binary as it's weird on other devices, it will still update the binary even if you copied the correct one. Maybe it has something to do with BS needing two su binaries since on other android devices, there is only one su binary but the instructions seems to indicate one needs the su binary in two different locations.

Actually, it seems like both the stock Root.fs and initrd.img are in C:\ProgramData\BlueStacksSetup\runtimedata_0.8.1.3051.zip so it wouldn't be hard to restore provided I knew how to extract from the Root.fs file to get the launcher and such.
[Android Software/Hacking General [Developers Only]] Nephatiu:
Are you guys even sure about this? My rooted devices all have a 'su' in '/system/xbin' and a 'su' symlink in '/system/bin' to the one in '/system/xbin', which results in about the same thing as 2 'su''s. ;p On phones we usually just create a symlink in 'bin' to the one in 'xbin' to prevent double files. (I actually did that to my Root.fs as well. ;p) As I have known it, 'su' always had to be in both, even on phones and such... And I've always been said to, when I'm using a symlink, always to put the real 'su' file in 'xbin' and symlink from 'bin'. ;)

Grtz,

~ Nephatiu ;)
[Android Software/Hacking General [Developers Only]] Almighty2:
I've been running Android since 2009 with the Motorola Droid 1 which ran Froyo 2.2 and now have both the Motorola XOOM Tablet that started with 3.1 then 3.2 Honeycomb and later 4.0 ICS and now JB 4.1.2 and my Motorola RAZR HD MAXX which started with ICS and later JB 4.1.2, they all have su only in /system/xbin. If you goto terminal, type which su and it will show you exactly which su binary is being used. su as you know came from Unix or rather Linux as Android is based on Linux and there is supposed to be only one su binary in the entire system for security reasons and that's how the hierarchy works. On the HP Zeen C150 Tablet from the eStation Printer, when one uses z4root, it does put

su in /system/bin but when you are in the terminal and type su, it will fail because it's trying to run /system/sbin/su instead so what people do to fix it is:

rm /system/sbin/su ; ln -s /system/bin/su /system/sbin

even though in my case, I basically moved the su to /system/xbin and it works fine.

Here is something that even mentions su being in /system/xbin only...

http://android.stackexchange.com/qu...ary-simply-be-copied-techical-response-please

This one tells one how to root a device and it tells one to put su in /system/xbin:

https://f-droid.org/wiki/page/How_can_I_root_my_Android_device?

Even root checking utilities only check for /system/xbin/su...

http://androidforums.com/optimus-v-all-things-root/731381-lost-root-how-do-i-fox-problem.html

Basically, the device based on the path will check for the command which is a file in the order of the path.

There is always on one su binary on the system in one location since su is to gain superuser access from a user in the root group and if you have it in other locations, you're putting yourself at high security risk. Samsung devices have su in places like /sbin and /system/bin.

From the author of Superuser, read section 3.1 under hardcoded checks where the default location is /system/xbin/su.

http://su.chainfire.eu/
[Android Software/Hacking General [Developers Only]] Nephatiu:
Well, my screenshots come straight from an untainted CyanogenMod (CM10.2) copy on one of my devices, and I really don't know which page ever learned me to root, because it's been almost 5 years as well for me, but I never questioned it, since 1. it seemed to work perfectly and 2. all custom ROMs I've ever installed had the 'su' symlink in 'bin' as well. I did always stay with Samsung when it comes to Android, though, except for the HTC Dream ages ago... And 'su' aside, my first encounter with 'busybox' on android also told me to first install it to 'bin', then to 'xbin', and that's also quite some time ago now. :p

Also, (just looking around just now) pages like these also say to do the symlink, though:

Create your own ROM guide - XDA-Developers

set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");

And this is the update-script of (for example su-2.3.6.1+busybox1.19.zip:

show_progress 0.1 0

show_progress 0.5 0
delete SYSTEM:bin/su
delete SYSTEM:xbin/su
copy_dir PACKAGE:system SYSTEM:
set_perm 0 0 06755 SYSTEM:bin/su
[B]symlink /system/bin/su SYSTEM:xbin/su[/B]
run_program PACKAGE:installbusybox

show_progress 0.1 10

;)

So, yeah,... :p I'll keep on doing it, though, on all my devices, for it has never done any harm and it's installed like this in all major ROMs out there today, too. I suspect that won't be without a reason either... ;)

Yeah, well, root checkers gave me many false positives before too, so... Not saying what you say isn't true, but root checkers are quite untrustworthy. ;) Root checkers even give full root access when you reset the BlueStacks initrd.img to 'ro' (at which point you can't make it 'rw' from within Android, thus you actually have no root at all...) and you ask them if you have root. :p

And docs are always so updated these days,... ;) I think I can find errors in 70% of all linux tutorials online. Including the Android ones. :D

It could also mean that the apk makes the symlink afterwards by itself, if you didn't. ;p

Maybe you should try to keep an open mind, and maybe check some other custom ROMs, like 'AOSP' and 'CM', because they both have the '/system/bin/su' symlink in place on untainted flashes. I don't think they'd do this just for the fun of it. ;)

Grtz,

~ Nephatiu
[Android Software/Hacking General [Developers Only]] Almighty2:
I've actually been using Unix based systems and sys admin them for the last 25 years and all the systems only ever had one su binary as I recompile the entire src code atleast once a week. I'm sure the reason for the symlink is just in case the su wasn't in the path for the system to find. I don't use custom ROMs but I'm just saying that you really only need one su binary and also keep in mind, that most of your examples are from non-Google Experience devices. The Motorola XOOM is a Google Development device and the Droid 1 is what made Android a major player in smartphones. AOSP isn't a custom ROM as AOSP is just the Android Source Code. I already checked on all my devices, they only have /system/xbin/su and not /system/bin/su or even a symlink there so the apk doesn't create a symlink afterwards either.

Besides, you should be the one who needs to be more open minded, just because it's in two places in the ROM doesn't mean it's correct. The best way is to always real world experience, delete the /system/bin/su and if everything works, you know who is correct since either it works or it doesn't. You can put symlinks for su in /system/bin, /system/sbin if you wanted to but the system will only use one su and that's how it works, that was the reason I said to use the "which su" command.

Also, there is a reason you can't trust 99% of Linux tutorials because #1, Linux is not even a Operating System, it is just a kernel. It is packaged by others into a OS which is why there are more flavors of Linux than there is ice cream as the user land is packaged by others. BSD on the other hand is a operating system because the entire kernel and userland comes from the same source.