yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] rocketero:
One Note about the above files.

I forgot to replace the binary ls to be handled by busybox and not by toolbox, so if one wants to have those nice color listings in an Android terminal, like different colors for files, folders, scripts, binaries, etc, all you have to do is this:

Open a terminal window (Terminal IDE or Android Terminal Emulator would do),

then do these commands

su
cd /system/bin
mv ls ls.orig
ln -s busybox ls

Now binary ls is handled by busybox and NOT by toolbox.

Now type ls -la /system/bin (for instance), and you'll see a nice colored listing. This is possible because I placed a copy of busybox in /system/bin aside from the original place in /system/xbin. If you use Android Terminal Emulator, set the background color to black so you can see better the colors than the default blue background.

EDIT: I went an extra mile and re-do the Root.fs to let binary ls be handled by toolbox, so this procedure explained here is not longer needed !
[Android Software/Hacking General [Developers Only]] shinobisoft:
BlueStacks Root Installer has been updated. Changed the way I was handling string resources. Updated it to check for the 'system.fs' before attempting to install. Also added a little more error checking. The installer now checks for 'Root.fs' and 'initrd.img' to be in it's folder and aborts the installation if either of them are not found.

The original post is here. I took down the link in that post for the root package as it was faulty anyways. I can mirror rocketero's package if need be. I have also considered packaging the the root patches package and the installer into a single entity. I'll leave that up to you all.

Thanks again to everyone for all of their efforts.:cool: It really goes to show what can be accomplished when people work together. :highfive:
[Android Software/Hacking General [Developers Only]] codelover:
It's only recommended if you are not going to use windoz command prompt & adb shell to execute commands, otherwise you probably will see some alien codes when you use ls with it.
[Android Software/Hacking General [Developers Only]] codelover:
su-3.2-x86 & Superuser-3.1.3-x86-signed.zip works fine.

As i mentioned earlier, replace sutools in /data/data/com.noshufou.android.su/files/sutools with a x86 version available inside the Superuser 3.1.3.apk itself, it's under the /assets/ folder, if you are too lazy you can use the uploaded version instead, also be reminded you may need restore the default ownership and permission of the file.
[Android Software/Hacking General [Developers Only]] codelover:
I think BlueStacks requires Vista with SP2, are you using SP2? perhaps you can check setup log files in %LocalAppData%\Temp\

---------- Post added at 02:38 PM ---------- Previous post was at 02:08 PM ----------

If i remember correctly /dev/sdd1 is not always got mounted, only when necessary.

Perhaps you can try something like:

#*** check before mount
e2fsck -vy /dev/sda1 > /tmp/fsck_sda1.log
#*** mount statement
#*** mounted
mv /tmp/fsck_sda1.log > /android/system/fsck_sda1.log
#*** it really depends on where & when you want to perform the check

I don't think you can reboot from inside BS, once the BS HD frontend closed you cannot bring it up from inside android, but you can still try and let me know.

As for the PATH, perhaps you are working with the wrong file, for your info initrd is for initial boot state only, once booted it may no longer in use, try ramdisk instead.
[Android Software/Hacking General [Developers Only]] rocketero:
I already changed the Root.fs to include ls be handled by busybox in the download link for Root.fs and iintrd.img link in the previous page link.

But if one wants to use adb commands in your PC, to avoid the alien characters do the following as I explained in another forum:

Also if you don't want the nice colors in your terminal listings in your Bluestacks, you can always get the regular black and white by reversing the ls binary in /system/bin

su
cd /system/bin
mv ls ls.busybox
mv ls.orig ls

---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------

How do I go about and see the contents of ramdisk.img inside Root.fs, to check if I can change the global eniroment PATH?

I try to mount ramdisk.img to a folder in ubuntu OS but it doesn't mount. (with mount -o loop ramdisk.img /b/ramdisk_img/)
[Android Software/Hacking General [Developers Only]] rocketero:
Updating Google Store to Jelly Bean and Titanium Backup Fill

2 great apps for your BS: Google Store Jelly Bean v.3.9.16 and T.B

One is Google Store Jelly Bean version 3.9.16, is un apdate to the one you already have, I believe is 3.8.17 after you install BS v0.7.4xx and up.

(the first installation of Google Store will update automatically to v3.8.17 so you have to open a couple of time the first installed version so it does update automatically).

Once you check that your version of Google Store is the 3.8.17 (or whatever version is at the moment you read this post), then proceed first to do a full backup of your installed apps.

To this install ES File Manager Explorer, then in the options menu select MANAGE, then select APPS MANAGER from that popup menu. .. Once you have the screen with apps, click on the CATEGORY button and select ALL (other wise you won't be backing up Google Store).

Once you backed up all apps, now proceed to install the Google Store JellyBean v3.9.16 inside this package.rar I posted to my Dropbox space.

Ok that takes care of Google Store.

Another app that I included in the package is Titanium Backup v5.4.2.1, this version specifically was with the purpose of getting it to full version using the app LuckyPatcher I included in the zip.

To do this, first install Titanium Backup 5.4.2.1, then at the end of installation DO NOT open it, just select DONE.

Then install Lucky patcher (v2.5.9.2), and give root access to it if you see the superuser popup window.

Once installed, if LuckyPatcher tells you that there is an update, go ahead and install the update.

Now LP will show the list of apps installed, at the top you'll see T.B. in order to apply the patch, LONG PRESS on T.B and a from the LuckyPatcher menu window that pops up, select CUSTOM PATCH.

Now after selecting Custom, you'll see 2 options. Select the one that says: COM.KERMINDAS.TITANIUMBACKUP

and in the next window click the APPLY button.

Now your T.B is good to Go!

---------- Post added at 10:06 PM ---------- Previous post was at 09:22 PM ----------

How to make a Picture fill the whole screen as your wallpaper

For those of you who don't know it, (and if someone knows another method please post it here), you can use a full size picture as wallpaper, for that download Simple Image Wallpaper Free and install. After installation, you won't see anything listed in the drawer or anywhere else. This is because this is a live-wallpaper.

Long Press on an empty spot in your screen, then select wallpapers, then live-wallpapers, select simple image wallpaper free, then select SETTINGS and then SELECT IMAGE. Choose any image you want as wallpaper, then press the back button till you see SET WALLPAPER, press that button, now you have a full sized picture as your background wallpaper.

Did I help you in any way? Hit THANKS button! :good:
[Android Software/Hacking General [Developers Only]] rocketero:
How to resize the BS window from default 800x600 to a bigger size.

By now most of you know how to do this, but for those who don't, do the following:

open the Registry in your PC, STartMenu >>RUN, and in the box type: REGEDT32

go to: HkEY_LOCAL_MACHINE >> SOFTWARE >>BLUESTACKS >>GUESTS >> Framebuffer >> 0

and change : Height and Width, but use DECIMAL instead of Hexadecimal to setup the size of the BS window.

I have a 22" Monitor with 1600x1200 resolution, and the BS resolution that worked for me was Height=1024 (decimal) and Width=1400 (decimal)

If after you change these values your BS hangs, go to the registry and input different values, it should work after a couple of tries, Mine did with the first change.

Did I help you in any way? Hit THANKS button! :good:
[Android Software/Hacking General [Developers Only]] rocketero:
How to show the Drawer and Google Store in your main BS screen

By default when BS get installed, the BS launcher doesn't show the Google Play Store icon on the screen, and there is not Drawer to see other apps. So the way to show the drawer and icons for Google Store is by installing an additional Android Launcher like ADW Launcher (EX)., GO Launcher EX or other BS compatible Launcher. If after installing one of these launchers you don't see the Google Store icon, just click on the Drawer and drag the icon to the main screen.

Did I help you in any way? Hit THANKS button! :good:
[Android Software/Hacking General [Developers Only]] Sage:
damn the last 10 pages went completely over my head! :)

Can someone write up the latest and easiest way to get root and r/w on the latest bluestacks? :) (for non linux users!)

Ill click Thanks a million times!!
[Android Software/Hacking General [Developers Only]] shinobisoft:
Go Launcher also makes a launcher - Go Launcher HD for tablets. I use it with my BS.

---------- Post added at 01:10 AM ---------- Previous post was at 01:03 AM ----------

Download rocketero and codelover's zip from here

Download my installer here

Unzip them both into the same folder and run bluestacksrootinstaller.exe .
[Android Software/Hacking General [Developers Only]] veiks16:
cannot unzip Root.fs-and-initrd.img.zip
[Android Software/Hacking General [Developers Only]] dari-woka:
yeah!, me neither
[Android Software/Hacking General [Developers Only]] rocketero:
As I compressed the files using 7zip, I just tested, downloaded, and first thing I did was checking the md5 and sha-1, they were OK, then I proceeded to unzip it with 7zip and was OK. But when I used winzip to unzip-it it gave me the same error you posted.

Could you please use 7zip and let me know if it works for you, so I can leave the edited-comment I have just posted on the download page?

The file is good to go, just that I should have named it Root.fs-and-initrd.img.7z to reflect that was compressed with 7zip.

After I use 7zip, I went even farther testing the integrity of the extracted files Root.fs and initrd.img, and got the same values for md5 on both files to the ones I use in my BS. Here they are:

Root.fs -----> MD5 -------> 6FABED84796395BED5845C8E0B30CA48

initrd.img --> MD5 --------> B1869F6AE44B78E06F0C0AF91B024367

---------- Post added at 05:01 PM ---------- Previous post was at 04:39 PM ----------

I used apktool to extract superuser.apk v3.1.3 but I didn't fine and 'Assets' folder. what tool did you use? Anyways thanks for the heads up, I placed sutools-x86 (renamed sutools) in the appropriate folder and now it works, su binary now updates.

---------- Post added at 05:07 PM ---------- Previous post was at 05:01 PM ----------

Thanks for the recommendation, I switched my ADW launcher for this one, has more function. But the only thing that I can not adjust with this Go Launcher HD for tables is the margins right and left are too big, and not configuration to make them smaller. One could fit another icon in there if the view is setup for 'small-icons' Is there anyway to adjust this?

---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------

Read post # 490 for @codelover's solution to this message.

Did I help you in any way? Hit THANKS button! :good:
[Android Software/Hacking General [Developers Only]] shubhkirtisharma:
Thnx the method worked!!!!!
[Android Software/Hacking General [Developers Only]] dari-woka:
ok! thanks!

It worked with 7zip!
[Android Software/Hacking General [Developers Only]] rocketero:
Could you also report how it's working after you boot BS with these new files, what messages you get if any, so we can make the necessary changes to them in case something doesn't work the way it should? Thanks, much appreciated!

PS. you could install TB as I outlined on post 493 on previous page, to check for root and /system size (500MB).

Also the command: 'df /system', in a terminal, should give you the proper size.

---------- Post added at 07:38 PM ---------- Previous post was at 07:16 PM ----------

Never mind where I asked you how to extract ramdisk.img, I follow the merryckville's guide on how to extract initrd.img and it also applies to ramdisk.img

I'll check if I can find the global environment PATH to see if I can change it as the contents of ramdisk.img I just saw it contains the init.rc file that BS shows at the root.

But I do have another kind of different question for you. I have a user with a tablet that is not rooted, and we need to get a copy of the /init.rc file and somehow it doesn't allow to copy that file or even do a cat /init.rc > /sdcard/init.rc.txt as it gives permissions denied. How one would go and copy either that file or the contents of that file so this person can send it to me ?
[Android Software/Hacking General [Developers Only]] codelover:
yeap they are both cpio gzipped.

That's the reason why people need to root their devices! Well the easiest way i could think of is find out the ROM being used and grab a copy of it and do it with your pc, sounds easier right? :D
[Android Software/Hacking General [Developers Only]] codelover:
Any tool will do, my Superuser.apk 3.1.3 is 1.4 Mb and has MD5 of E0BC7B7284B68C9539B6EC6B306310E0.

---------- Post added at 03:26 AM ---------- Previous post was at 03:16 AM ----------

The check should be placed in initrd 'init' as the one i posted earlier, check before /dev/sda1 got mounted, and once mounted you can move log to /system/

---------- Post added at 03:29 AM ---------- Previous post was at 03:26 AM ----------

Any possibility to tell what device is it?
[Android Software/Hacking General [Developers Only]] rocketero:
thanks, I'll give it a try later on.

About the apktool I got not idea why is not showing the Assets folder, I used only the command :

apktool d superuser.apk superuiser113

I don't know if there is another option after d to show the Assets.

---------- Post added at 08:34 PM ---------- Previous post was at 08:30 PM ----------

it's a LePan model S, 9.8" with ICS 4.0.3. We have already rooted the 2 previous models LePan1 and Lepan2
[Android Software/Hacking General [Developers Only]] LfcFan1977:
If you only want to extract it, instead of using ApkTool you can just change .apk to .zip and extract with 7zip.

BTW, thank you very much for you help (and codelover... and others).

My BS is now rooted properly with the Superuser.apk popups.

Using your zip from post 486

346Mb free in /system with terminal emulator

363Mb free with Ti
[Android Software/Hacking General [Developers Only]] dari-woka:
Hello!

Im trying to use Wifi Analyzer and another wifi apps, and everytime I have problems with the wifi

Its like this apps cannot handle wifi in bluestacks.

I have it rooted, and also the file sutools-x86 changed, and the superuser updated well after this changes

But the wifi apps it does not seems to work

Wifi Analyzer

WifiKill

FaceSniff

......

anyone has this apps runing?

thanks

EDIT

I have this error in the wifi settings:

But yes, internet is working, explorer, Google Play, whatsapp...

but not this those other kind of apps
[Android Software/Hacking General [Developers Only]] codelover:
Sorry to disappoint you but there is no wifi thing in Bluestacks, you cannot access your real wifi devices from it, at least for now.
[Android Software/Hacking General [Developers Only]] rocketero:
Thanks, didn't know that, always learning something new!

but still not Asset or Assets folder. I'll look for the superuser that @codelover posted the md5, I think the problem is in the version of the apk I have. It's just for fun I guess as I already got what I needed, the sutools(x86)

UPDATE: yeap, that was the issue, the apk file I had didn't have that assets folder, thanks again LfcFan
[Android Software/Hacking General [Developers Only]] rocketero:
I've got some progress on the e2fsck,

I placed the 2 lines on init :

[COLOR="Blue"]e2fsck -vpy /dev/sda1 > /tmp/fsck_sda1.log[/COLOR]
mount -t tmpfs tmpfs /android
cd /android
zcat /mnt/$SRC/ramdisk.img | cpio -id > /dev/null
if [ -e /mnt/$SRC/system.sfs ]; then
mount -o loop /mnt/$SRC/system.sfs /sfs
mount -o loop /sfs/system.img system
elif [ -e /mnt/$SRC/system.img ]; then
mount -o loop /mnt/$SRC/system.img system
else
remount_rw
mount --bind /mnt/$SRC/system system
fi
[COLOR="Blue"]mv /tmp/fsck_sda1.log > /android/system/fsck_sda1.log[/COLOR]

the boot process took extra 10 seconds but that's normal with these extra code to run, and I see now a file in /system with the name fcsk_sda1.log. just that the size is zero, and content is blank. but if the command executed shouldn't say or output some message? .. on a second and third boot, the same, size zero and blank file.
[Android Software/Hacking General [Developers Only]] shinobisoft:
I think there is a setting for changing the size of the icons, but I seem to remember only two sizes. ( Upper right corner of BS Display, not the BS Window ) Go to "Preferences->Screen", I think.
[Android Software/Hacking General [Developers Only]] rocketero:
yeah it's in the settings>>screen_settings>>icon_size, there are 3 sizes big, default and small, choosing either of the 3 leaves the same margins at right and left of screen. Not a big deal as I chose small icons I can fit 10 columns by 9 rows of icons, more than plenty.
[Android Software/Hacking General [Developers Only]] rocketero:
I'm trying to address the issue of sutools in the Root.fs I posted for download (Root.fs-and-initrd.img.zip), so users can update the su binary without having to research in this forum where or how to place and get sutools.x86.

I extracted ramdisk.img and created a data/data/com.noshufu.android.su/files folder and placed the sutools file there.

I repacked with cpio gzip to a new-ramdisk.img, 285.6KB in size(original is 196Kb), I then replaced the ramdisk.img in Root.fs, with this new-ramdisk.img, and repacked a new Root.fs .. AFter booting with this new Root.fs, I Don't see any sutools file in /data/data/com.noshufu.android.su/files folder.

I don't know if that's due to I deleted the original sutools I had there before I replace my Root.fs with this new Root.fs that sutools was not created. Any idea what could have happened or what should I do or change to fix it?
[Android Software/Hacking General [Developers Only]] dari-woka:
Try ADW launcher EX (its paid software) but is great! great diference between the normal ADW
[Android Software/Hacking General [Developers Only]] freakozoid:
Hey,

i cant play the game plague inc. every time i start the game it loads a few seconds ( 20 secs or so) and the force close without any failer massage
[Android Software/Hacking General [Developers Only]] codelover:
That's why i said earlier it is really matter where & when you are performing the check.

And i think you got the wrong idea for checking /dev/sda1 instead of system.img, since checking /dev/sda1 itself might not resolve problems/errors in /system.

You can try something like the following:

elif [ -e /mnt/$SRC/system.img ]; then
[COLOR="Red"]e2fsck -vfy /mnt/$SRC/system.img > fsck_system.log[/COLOR]
mount -o loop /mnt/$SRC/system.img system
[COLOR="red"]mv fsck_system.log system/[/COLOR]
else

* Referring to the rooted Root.fs with system.img

If you want to check /dev/sda1 as well you may need to try different method, also you can try to add another drive eg /dev/sde1 and save the log there, if you want to use this method you might need to consider umount the new drive as soon as the log file has been saved.

---------- Post added at 06:44 PM ---------- Previous post was at 06:30 PM ----------

Do you need me to remind you that /data itself is a mountpoint?
[Android Software/Hacking General [Developers Only]] rocketero:
If that's true, then I should place sutools in ramdisk.img in the folder /data/com.noshufu.android.su/files/sutools (not /data/data/....)

But after doing that and with the new ramdisk.img and new Root.fs, still the sootols file is not created after rebooting BS.

I have started another way to do this but so far not a go. I have extracted the superuser313.apk and look at the applets folder, it contains 2 files, the sutools-armeabi and the sutools-x86.

So if one installs this regular superuser313.apk into BS, the sutools-armeabi is renamed sutools and copied to the ....android.su/files in /data/data.

So I was thinking, and I did try, after extracting the superuser312.apk I renamed the sutools-armeabi >> sutools-x86 and the other way around.

But I used apktool to put back the apk and after trying to installing in BS it fails to intalls. I even used apksing.jar to sign the created apk but still not a go.
[Android Software/Hacking General [Developers Only]] codelover:
When i said /data is a mountpoint i was referring to 'data' folder in ramdisk, so it doesn't matter where you put the subfolder inside data.

For the apk, technically it should work if you have properly packed & signed the apk, and removed the old apk as well as it's existing data.
[Android Software/Hacking General [Developers Only]] shinobisoft:
A thought. I rooted BS 0.7.2 last night for some one. I replaced /system/xbin/su with su.x86. I installed supersu.apk to /system/app and its binaries to /system/bin to avoid any conflicts with the su.x86 version. I'm not sure about su prompts but the person I rooted it for says its working great. When I get off work, I'll pm him to see.

Sent from my LG-P509
[Android Software/Hacking General [Developers Only]] codelover:
The existing su & Superuser work just fine, is just @rocketero insist to get rid the red warning message in the info page with his Root.fs,

so users can have a better looking Superuser interface without having to fix it on their own.

I was looking for 'su' x86 that is compatible with SuperSU but could not find any, the one comes with SuperSU that i have is ARM version.

Need to find out what Root Checker says about the su in the mentioned /system/bin/su
[Android Software/Hacking General [Developers Only]] rocketero:
I gave up on that pursuit as I now realize that even if I could get that fixed, once there is un update on Google Store for a superuser app, then this new app will replace the already fixed sutools(x86 version) with its own sutools (armeabi) version. So let's each and every one fix it on their own :fingers-crossed:

Now about copying two different versions of su, one to /bin and other to /xbin, I wouldn't recommend it, it may work but in the long run is better to stick with the su-3.2.x86 that is working fine in both folders as I placed them in the downloadable Root.fs. this in case one wants to replace the su with the next release, there is a fallback while deleting in one folder (/bin) then replacing it, chmod/chown it and then once this is done move to the next folder /xbin and replace it also without loosing root and without having to create another Root.fs
[Android Software/Hacking General [Developers Only]] shinobisoft:
OK. Question then. As I mentioned, I rooted BS 0.7.2 but I run 0.7.5.2700. Would I run into any issues trying to boot the older version? Haven't tried, tho it won't b to hard to figure out.

Sent from my LG-P509
[Android Software/Hacking General [Developers Only]] rocketero:
I'm not sure what you're trying to do, you rooted 0.7.2.x which stills uses Data.fs and SDcard.fs, I guess you took Root.fs appart and injected su to system.img. if you use that Root.fs in 0.7.5.x will it work? and what about the initrd.img, did you also took it apart and changed anything to it?
[Android Software/Hacking General [Developers Only]] shinobisoft:
I'll try to clarify in an hour or so. To hard to Peck out on my phone.

Sent from my LG-P509
[Android Software/Hacking General [Developers Only]] Juanmatol:
really you have done all that to install play store?

i only install Launcher Pro... and my play store is runing...

sorry for my english

very good forum and post!!

pd. i have very doubt about android and blue stacks, i hope to learn very much!