yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Zuckstone:
New Version

Version 0.8.2.3018 is out.

I accepted the update & Root Checker Pro says I still have root.
[Miscellaneous Android Development] huisterduin:
SuperSU updated

SuperSU just updated a few hours ago. Problems to update the apk. Could someone please update Root.fs and initrd.img with the new superSU apk.

Thank you
[Miscellaneous Android Development] Almighty2:
0.8.2.3018 updates and root is still there except the root apk is gone as the Root.fs has been replaced.
[Miscellaneous Android Development] Nephatiu:
I'll be adding my new Root.fs here later today. ;) Just got back from a few days trip, and first of all I need some sleep, but when I wake, I'll get right to it. ;)

Grtz,

~ Nephatiu
[Miscellaneous Android Development] Chakkas:
If possible could the root files be compressed before theyre uploaded by any chance in .7z? it would half the download size from 500MB to around 256MB, im sure the many with sucky internet speeds would appreciate it >.<

Hope you enjoyed le trip ~
[Miscellaneous Android Development] Nephatiu:
Good idea. I don't know why I didn't do that in the first place... :p

Ah, well, I'll 7zip them and up them again,... ;)

Grtz,

~ Nephatiu
[Miscellaneous Android Development] huisterduin:
Great!!, you update with the last version of bluestacks, but supersu.apk is still version 1.69. Could you please update with SuperSU version 1.75. This is the last one.

Thanks!!
[Miscellaneous Android Development] Nephatiu:
Why? What's so new about it? :confused: This one works and was already unpacked to me. :D (Lazyness ftw. ;p) Also, it's still the last one available on Google Play Store, since it doesn't want to update, so I'm guessing that it's probably not that much of an update. :p (Haven't checked though. :D)

And I don't see why you wouldn't be able to upgrade it yourself... Just install the new SuperSU (replace other in system/app or install in data and don't touch system/app, your choice. :p

I'll see what I can do next release. ;)

Grtz,

~ Nephatiu
[Miscellaneous Android Development] Almighty2:
1.75 has actually been available on Google Play Store since November 20, 2013 and these are the changes:

What's New

- Fixed OTA survival 4.3 --> 4.4

- Fixed unresponsive tabs on 2.x devices

- Fixed white flicker when using dark theme

- Fixed issue with language resetting on some firmwares

- Fixed upgrading from CWM SU to SuperSU on 4.3+ without reboot

- Added mgyun root (vroot) uninstall procedure

- Added xxhdpi and xxxhdpi icons (if available)

- Stop touching .has_su_daemon

- Several dozen security hardening commits (mini-audit by Kevin Cernekee)

- Fixed issues with sd-ext based ROMs

- Updated language files

Except from reading the thread, 1.75 still has problems with some devices as some people have lost root trying to upgrade according to the xda thread so better wait for a stable version before replacing it. 1.69 is fine as long as swiping works across the tabs and the request for su prompt comes up as that was what people were complaining about in 1.69.

I'll test to see if 1.75 works by upgrading once I finish downloading since installing rhe apk is the easy part, it's updating the su binary that is always the problem with SuperSU.
[Miscellaneous Android Development] Nephatiu:
Ok, strange, I checked yesterday on BlueStacks, right before posting my answer (to make sure). I opened Play Store on it, looked up SuperSU (had to go through the whole 1-click setup again, even :p) and it said: Open and Uninstall... No update.

I'll admit I did wanted it not to be, so I had a proper excuse next to me being lazy, but I swear to you, I checked and there wasn't. :p Not on my BlueStacks, anyway. Haven't checked my phone, since there was no version numbering to be found in their "What's New", so I had no way to check it there without first installing it.

This was indeed what it said when I checked for the update on BlueStacks,... But it did not give me the Update button, just the Open button, so I expected it to have been the 1.69 release adding those stuff... :p (I don't really follow SuperSU, so for as far I knew, it could have been and would've easily be explained by the '.su' file and the 'otasurvival' zip in 1.69... ;p)

Apart from the fact it didn't even want to update in my Market,... :D

You think SuperSU won't be able to update, when it's already the main superuser app? I understand the problems when changing with apps from other users you have no control over, but not over one's own stuff...

Why is this SuperSU app so wanted anyway? It seems to have more bugs than any other... And 99% of the time you're just going to push "Allow" anyway... :p

Grtz,

~ Nephatiu
[Miscellaneous Android Development] Almighty2:
The version numbering is always under the description in Google Play Store. I downloaded the Root.fs and initrd.img and just tried to update to SuperSU 1.75 and just as I had suspected, installation of the su binary failed. CWM's Superuser installs but the su binary on that one seems to be dead as it doesn't prompt and one can't even su in terminal mode with all versions released after the CWM Superuser you included in the earlier BS Root.fs.

As for SuperSU, here is the comparison and I think both CWM and SuperSU are good, it's just the original Superuser that sucks...

Superuser, the original by chainsdd, is open source, and has been used the longest. The problem is that it has been outdated and it required work to get it on 4.2

SuperSU is a closed source app from chainfire, a well known developer. Its got a ton of options and its well made. This one was made because of the issues in the original superuser app. Lots of people personally use this one.

Superuser by koush was designed to make a working superuser app, that was open source. It comes built into the settings menu of AOKP and Cyanogenmod.
[Miscellaneous Android Development] Nephatiu:
Always wondered where that info was... It somehow feels like it should have a more obvious place. And although this seems to be the official place for it, indeed, it's often mentioned in What's New too,... Anyway, I know now, and I can clearly see version 1.75, but then I wonder why I didn't get the Update button in BlueStacks? Because that's the main thing I took as evidence. :D

Yeah, I was along with everybody else to change and change it every ROM again,... But then CM began to build in theirs (as did AOKP), and it didn't actually bother me, had the same functionality (notification per app settings and such...) and has a much nice clear popup, imho, where as SuperSU has that small white one which still looks Gingerbreadlike. ;p So, again, in my eyes as I did before, I moved on. :p Some people tend to get stuck with their first change, they never change again, that's why I ask why SuperSU would be better, if it's such a mess even updating it... ;p As I remember CWM's su updated just fine, even on BlueStacks... Dunno if it could handle SuperSu, though, but if it didn't I'd expect it to be more SuperSU's fault than CMWsu's. ;p

And a good job they did, imho. ;p

Grtz,

~ Nephatiu ;)
[Miscellaneous Android Development] CptKlink:
My problem is SuperSU is nice but the SU binary isen't istalled. I keep getting no root privilages error. am i doing something wrong?

For me in a sence its not really rooted it just has a superuser app installed which isen't rooted.
[Miscellaneous Android Development] Nephatiu:
And you are using my Root.fs ánd my initrd.img? Because they work fine here, though, and from recent reply's I think I can confirm more people having it working. :/ Try uninstalling BlueStacks completely, removing everything (like in the beginning of my tutorial for rooting BS in the OP), rebooting, and reinstalling BS with a clean slate. All su binaries and the sudaemon should be pre-installed on it. :/ I forgot to make a symlink to /system/bin this time, but apparently it wasn't needed and the /system/xbin/su should do. This can be done later (with root of course) by going to /system/bin with the android terminal and typing:

su
ln -s ../xbin/su

Oh, right, and do check if SuperSU doesn't get updated automatically by your Play Store or anything. It should stay v1.69, because it fails at updating it's own su binaries for some reason...

Can anyone else confirm the last release has working root, though, just to be sure? :p Because they could always have changed something to make rooting harder, disabling the 'just replace Root.fs' possibility with some build in checker. I highly doubt that's the case, though.

Anyway, keep me updated. ;p

Grtz,

~ Nephatiu
[Miscellaneous Android Development] elvensbane:
The root seemed to work, but the play store has quit downloading things. Any solution?

Edit- I went digging through the store and there was about 500 apps trying to be downloaded all at once. That solved it. Thanks for this!
[Miscellaneous Android Development] CptKlink:
I have gotten this problem your last version and this version and this time i was even straight from a fresh windows install. (I diden't do a fresh windows install for bluestacks it was another reason) Trying again right now.

OK how can it be i'm the only one getting this. I have followed your instructions to the letter 7 times now and still no SU binary. (thas how many times i have tried uninstalling, reinstalling, restarting and ever from a fresh windows install)

SuperSU is saying this in so SU binary, and SuperSU can't install it. This is a problem.
[Miscellaneous Android Development] CptKlink:
I will just use the outdated files from this thread (http://xdaforums.com/showthread.php?t=1298332&page=35) i have no problems with it. Thxs anyways
[Miscellaneous Android Development] Almighty2:
Getting koush's Superuser working is pretty simple. Assuming you have Root.fs working with the SuperSU v1.69, all you have to do is use root explorer and open the attached apk and then let it install, this is version 1.0.2.1 of koush's Superuser which is the latest one that works as 1.0.2.3 and later, the su binary would install but the su prompt is not coming up and su in the terminal would just time out.
[Miscellaneous Android Development] CptKlink:
Yes i have completely killed bluestacks i always hit ctrl.alt.delete and stop everything that has the start of HD and then delete origional root and initrd file and paste then modified ones in. and can tell the modded ones are working and when i installed a launcher there is SuperSU there but keep getting no SU binary installed everytime.
[Miscellaneous Android Development] memturbo:
Same here new windows install new blustack install did everything to the letter no su binary installed HELP!!!!!
[Miscellaneous Android Development] CptKlink:
Well at least i'm not alone in this problem and i have tried everything to get it to work and still no SU binary.
[Miscellaneous Android Development] Nephatiu:
If only I could reproduce it, but I can't,... Reinstalled bluestacks myself, replaced Root.fs and initrd.img and it works for me. Root returns as it should.

Anyway, I'll try using CWMsu again next release,... Like it better anyway.

Grtz,

~ Nephatiu
[Miscellaneous Android Development] Almighty2:
That isn't the correct way to kill BlueStacks, the way I did it was based on the instructions provided by others which is:

Windows key + R and then put in the following command with the quotes:

"%programfiles(x86)%\BlueStacks\HD-Quit.exe"

I think the thing might be how people kill BS since using ctrl-alt-del might not kill all the processes as BlueStacks has 6 processes running which all start with HD*.exe. Running the above command will kill everything except for the BlueStacks Log Rotator Service which doesn't need to be killed.

As for what's in the next release, I don't think it's related to which SU program is used my BS is upgraded so I should be the one having problems but I'm not.
[Miscellaneous Android Development] Nephatiu:
You'd have to kill 'HD-LogRotator.exe' yourself, though. ;p

Grtz,

~ Nephatiu
[Miscellaneous Android Development] Almighty2:
It's fine to leave that running as I have replaced the Root.fs without killing it without problems. It's only a two step process if it's done that way since assuming you kill HD-LogRotator.exe manually which isn't even required. Besides, I'm sure killing the processes manually is just like force shutting down Windows as it didn't sync the system first which can result in data corruption. I use Process Hacker and just highlight all the HD*.exe processes and then Terminate and it terminates them all at once.

On another note, have any of you gotten adb working with the rooted BlueStacks?
[Miscellaneous Android Development] CptKlink:
i killed every process that started with HD*.exe including the log ones just to be sure. And still get the same error. And also yes 1 out of the 8 times now i tried doing this i used the HD-kill.exe (which really is the same as CTRL-ALT-Deleteing) and still comes out the same no SU binary. If it matters at all i'm running Windows 7 x64 Ultimate.
[Miscellaneous Android Development] Nephatiu:
So, again,... Please go to your Play Store in your BlueStacks by clicking on the search button and typing: SuperSU

When you have the SuperSU-page in Play Store in front of you, does it say: OPEN and UNINSTALL?

If it does, click "Uninstall", because that means it was updated automatically by the Play Store and by 'uninstalling' you revert to the one I added to Root.fs, which is the one that works.

I hope this solves it.

And Almighty2,

;)

Grtz,

~ Nephatiu
[Miscellaneous Android Development] Almighty2:
I'm also running Windows x64 Ultimate and it works fine here. In your Launcher, is SuperSU colored or is it grayed color? Actually, if Google Play Store already updated SuperSU, uninstalling won't work as that was the first test I tried to see if I can get v1.75 to work and SuperSU in the launcher becomes greyed out because it seems the only way to install and have the su binary recognized is using the method how you originally got it in. Since they are already using your Root.fs anyways, what they can do is just sideload the apk as I have posted in post #25 and then run CWM's Superuser and see if it will install the su binary. If it does, then one can test if root works.

As for adb, I actually meant to ask if "adb remount" works.
[Miscellaneous Android Development] Almighty2:
In any case, was trying to see how the stock launcher - gamepop behaves:

SuperSU doesn't show up.

CWM's Superuser shows up as long as it's installed whether or not the su binary used is from CWM or SuperSU.

Google Play Store doesn't show up.

SuperSU, CWM Superuser and Google Play Store all show up fine in GO Launcher EX.

Also, from the reviews on Google Play Store, it appears the last two versions of CWM's Superuser is broken which explains why the su binary updates but it no longer works while reverting back to the apk in post #25 works.

I noticed a strange behavior with Root Explorer, normally on other devices when you hold down on a file, a menu will pop up but on BlueStacks, it will just go back to the Launcher apps drawer.
[Miscellaneous Android Development] CptKlink:
I'm uninstalling and reinstalling BS to see what it shows will report back

EDIT: Well i reinstalled BS and in the play store for SuperSU it says Open and Update it dosen't say anything about uninstall and once again it says no SU binary
[Miscellaneous Android Development] Chakkas:
Latest version of Bluestacks fixed the Play store randomly closing for me issue! Now i have a perfect Bluestacks :D thank you Nephatiu!

Just one question though... is it possible, by any means, to make Bluestacks have the Play Services installed in it in your root package? getting the play services apk from the play store simply doesnt work for me at all >.<

---------- Post added at 10:29 PM ---------- Previous post was at 10:25 PM ----------

Bluestack's stock launcher is and always was rubbish, dont use it, id rather use the command line to launch apps than use that. the fact that the default launcher of it always seems to download something in the background but doesnt show what irks me as well

Btw, i think it should be added in the first post that offline installer of Bluestacks can be gotten here for any version thats desired, its pretty well updated i believe http://xdaforums.com/wiki/BlueStacks_App_Player
[Miscellaneous Android Development] Almighty2:
Hmm, when you open it, it says no SU binary? I got that problem but that was when I tried to manually replace the SuperSU files to the same locations as in the instructions with the ones from 1.76 Beta. Before replacing the initrd.img and Root.fs files, what I did was made a backup of it called initrd.img.orig and Root.fs.orig even though the original files are in a zip file in the BlueStacks-ProgramData directory

- (In Windows Vista and up it's: x:\ProgramData\BlueStacks)

- (In Windows XP it'll be: x:\Documents and Settings\All Users\Application Data\BlueStacks)

And then I just either kill the HD*.exe processes or use the HD-Quit command and then I just copy and replace the two files.

---------- Post added at 01:16 PM ---------- Previous post was at 12:43 PM ----------

Google Play Services in the 0.7 beta didn't install because it kept claiming the user is cannot be shared or something, ofcourse that is probably due to it being based on Android 2.3.4.

With 0.8.x.x which is supposedly ICS 4.0.4 but there are some places saying it's Jellybean based, it will install Google Play Services but the way to do it is to install something that requires it like YouTube or Hangout and then it will install from Google Play Store. As one can't even find Google Play Services directly by searching.

No one said BlueStack's stock launcher is any good, just that it might come in handy for other things. You can always install something else and set that one as the default. I know with the 0.8.1.3051, there was something that was weird as it kept having a big tray that came up on the bottom 1/8th of BS regardless what launcher was used, and it can't be stock as that was not included in the Root.fs since my Go Launcher Ex was there so it could have been a bug in BS but 0.8.2 seems to have fixed that issue. Ofcourse one should expect problems with BS as it is Beta after all.

Thanks for the link for getting the full offline installer.
[Miscellaneous Android Development] Chakkas:
Finally got the play services working thanks to that! thanks man! Never knew Android 2.3 couldnt have Play Services on it, explains alot..

Btw, Play Services is here from the playstore https://play.google.com/store/apps/details?id=com.google.android.gms
[Miscellaneous Android Development] Maurice5813:
This is awesome! Been looking to dev for bluestacks:D
[Miscellaneous Android Development] CptKlink:
Ya i get a error saying there is no su binary installed and superSU can't install it. This is a problem. I also get errors trying to use any root access app it says i have no root privileges and closes that app.

Also another question out there. Anybody know to get portable ubuntu working on windows 7 x64? I'm going to try and make my own root files or if there is another way to to make the root files without portable ubuntu?
[Miscellaneous Android Development] Chakkas:
Im not sure if this applies to this to but if the only use of portable Ubuntu is the linux comandline, then wouldnt using cygwin be better a solution to make this? It lets Windows have a Unix shell to input commands in and etc... plus beats downloading portable Ubuntu which is somewhat a large file for this small purpose
[Miscellaneous Android Development] Nephatiu:
It is, but cygwin isn't that noob-friendly to work with, though. :p Or at least it wasn't when I last used it. It also has a large chance of problems if you have other stuff installed which uses cygwin. I personally run a personalized basic colinux on all of my pc's, so I use that. There are multiple other possibilities, though, like using a linux box or a virtual machine running linux with VMware or Virtualbox, but Portable Ubuntu is the noob-friendliest and can be installed multiple times without conflicts.

But I agree that if you know how to use cygwin and you have it working, it's probably the best way to go. ;)

For x64 I think it's best to install a virtual linux in a vm and do it in there with shared folders. ;)

Grtz,

~ Nephatiu
[Miscellaneous Android Development] Almighty2:
The specific error when trying to install Play Services is:

"Incompatible with other application(s) using same shared user id"

This happened with BlueStacks, not sure if it's because of Android 2.x but it seems to be the same problem with my HP Zeen C510 Tablet which is part of the eStation Printer. Both BS 0.7 and the HP Zeen run a 2.x Android version, BS used 2.3.4 Gingerbread while the HP Zeen is Froyo 2.2. The only thing is the HP is a Yahoo! device so there was no Google Market/Google Play Store on it until it was hacked with Google Apps after being rooted and BS on the other hand didn't come with Google Play Store as I think one of the requirements for Google Play Store is the Android device needed to have a camera so basically both were hacked to get Google Play to work and Google Play Services is a component of Google Play. I forgot to post the link to Play Services in Playstore as search can't find it directly which is why I said installing a Google app like youtube, Google+ or Hangouts will say it requires Google Play Services and then it will take you to Google Play Store to download it and with BS 0.8.x, it would install but with 0.7, it will have the error mentioned above. I tried placing the apk for Google Play Services but seems like the system isn't seeing it probably for the same reason.
[Miscellaneous Android Development] Nephatiu:
I think Play Store needs to be some version at the latest for Gingerbread,... I don't know which of course, but all versions from a certain version and up need Android ICS or up,... I've never heard of Play Store needing a camera though...:/

Grtz,

~ Nephatiu
[Miscellaneous Android Development] CptKlink:
I'm not trying to steal your thunder or anything. But I just thought I would post how i got around my little problem. And this works perfectly as it dosen't install any unneeded or unwanted apps along with it and just roots Bluestacks. Check this link out if you want to.

https://www.facebook.com/BlueStacksInc/posts/678965018790955

A nice little problem put together to do some rooting for you called Bluestacks RootEZ 32_64

As i still want to try and figure out how to root myself i hate to ask a super noob question. But since I kinda suck at useing linux what would be the command lines i would need to use and what folders would i need to share i already have C:\ProgramData\BlueStacks\Android set up for shareing in the VM.
[Miscellaneous Android Development] Almighty2:
Play Store works fine regardless of the version of Android, it's Google Play Services that doesn't install with that error as it has something to do with the uid being in conflict. Google Play Store was known as Google Market and atleast with HP, Google Play Store will not work on the Zeen C150 since it lacks the camera which is a hardware requirement for access to Google Play Store so in build.prop, one has to make it think it's some other device before it works since remember Google controls the access to Play Store and HP's Zeen Tablet which is part of the printer was HP's attempt to have a tablet on a printer as they bought WebOS from Palm so they never supported the OS part of the printer. Google has specific requirements before a device is allowed access to Google Play Store and it has to do with hardware as a majority of phones and tablets have a camera, whether or not it has a GPS is another issue. Even BlueStacks is getting access to Google Play Store as a T-Mobile Samsung GT-I9100 which is the device it is emulating as you can even see that in terminal.

http://en.wikipedia.org/wiki/Google_Play#Device_compatibility

and this one explains it in detail:

http://source.android.com/faqs.html#compatibility