yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] codelover:
Wrong! or should i say not completely true.

Let me make it clear. An app is NOT consider uninstalled until you run the 'Uninstall' feature from within the Android or with adb.

Simply delete the APK & app data folder will NOT remove the app from system, not completely.

---------- Post added at 10:28 AM ---------- Previous post was at 10:27 AM ----------

What is your output for 'su -c whoami' in terminal?
[Android Software/Hacking General [Developers Only]] sga999:
Sorry, codelover, I decided to try a different rar file, just to see if it might fix some of my issues, but I'm back to not having root now. I didn't get rid of superuser or su before I did this. I merely did HD-Quit, extracted the rar file into the right place. I'm sure that wasn't good enough! Anyway, I no longer get the # when I say 'su' in terminal emulator now. When I get back to a state where I can do 'su -c whoami', I'll let you know. What should I expect to learn from this?
[Android Software/Hacking General [Developers Only]] mohazia:
Ok, now if I go on

Adb uninstall com.nosh*

then, quit bs

Mount root.fs, mount system.img,

Remove /system/app/*uperuser.apk

cp official or ur superuser.apk to /system/app

Umount all

Run bs, it will be ok

if so, if I share root.fs, when others just replace root.fs & run bs, it 'll automatic create /data/data/com.nosh*?
[Android Software/Hacking General [Developers Only]] codelover:
Yes, correct. But one thing, you should ask you user to uninstall any existing Superuser in their system first before they replace the images.
[Android Software/Hacking General [Developers Only]] rocketero:
I've haveen out of the picture in the last 4 or 5 pages here, so here are a few comments.

@mohaiza, when you first tried the @codelover process on post 668, you forgot one thing: you should have su in both places, in /system/bin and /system/xbin. So with that, when you go an install Superuser4BS apk and replace the su you have in /system/xbin with su.3.2.x86 then you still have root to do this process. Otherwise you'll loose root as you have experienced. Having su in both folders is a way to have a fall-back in case you want to replace them for a new version.

Also if you just delete superuser.apk from /system/app or /data/data/com.noshufou.... then you also loose root even that you still have the su file in /system/bin (or ../xbin). You have to uninstall, as @codelover mentioned by uninstalling com.noshufou.....and after uninstalling that then you can proceed and install the Superuser4BS apk.

And if you loose root for any reason, all you have to do to get it back is quit completely BS and then replace the Root.fs in .../android for the Root.fs in the .rar I posted or someonelse's posted. Simple as that. No need to bother mounting Root.fs and exctracting system.sfs and doing all those steps again.

@sga99, you don't really need to update the su from the Root.fs I posted in the rar, it already has su v.3.2.x86

But you can update the superuser.apk by the process on port # 668 from @codelover. just follow the steps exactly as described and you'll be fine.
[Android Software/Hacking General [Developers Only]] codelover:
Hey it's now your turn to forgot, he is the one that provide tutorial & images on the other thread for 0.7.7.813. Is it the page growing too fast? :D

And one thing, before you type the 'mv /system/xbin/su.3.2.x86 su', the current su in action, but once you typed, the new su take over immediately and any further cmd that requires root will be using the new su. There supposed to be 0% chance of losing root if they followed properly. You can confirm by deleting your /system/bin/su copy and try the commands.
[Android Software/Hacking General [Developers Only]] rocketero:
you're right on that, just having a copy of su in /system/bin would help in those miliseconds that you loose root when renaming the one in /system/xbin. just for precauction as nobody knows what the system is doing at that time and one milisecond may become seconds. Anyways in case one want's to copy the su, use this command:

cd /system/xbin
/system/xbin/busybox cp -p su /system/bin/su

And I noticed something, after replacing the superuser with the one you provided Superuser4BS the su binary update don't work. When one click on the (i) in the upper right corner of the app, now it shows all in green in 'su binary 3.2 (18)' but clicking in that area it not longer opens the 'update su binary' window. Any reason for that? Also I didn't know what that box that says TEMP UNROOT was for , I selected the other day and lost root, and had to replace the Root.fs for the one in the .rar :silly:
[Android Software/Hacking General [Developers Only]] codelover:
If you don't already know, the update binary has been disabled in Superuser 3.2 by the creator as it's buggy and useless, why do you need to update su binary when you already have the latest and working perfectly, that's why when you use Superuser.apk 3.1.3 you can see the update binary section shows latest su version is 3.1.x not 3.2 while you already have your su 3.2 installed. The Temp Unroot/OTA-On The Air survival are for real device which supposed to help OTA update & retain the root after device OTA update by ISP/Provider, but not always working tho.
[Android Software/Hacking General [Developers Only]] sga999:
codelover, I spent LOTS of time trying to uninstall and reinstall everything again (I had lots of trouble with BS services still running), and I'm back up again....but withOUT root...again! At least I did have it for a fleeting moment. Painful. So your su -c whoami command returns nothing, just the $ prompt. I know you wanted to see what it said when I WAS rooted, but I had already started over by the time you asked that.

Rocketero, thanks for you hints about what I should do when I lose root (like right now!), but I don't think I have the heart to tackle it right now. Part of post 668 says something about having to be rooted and write-able, but I'm not rooted! So how am I supposed to do those steps? Sorry, I think my mind has turned to mush after doing this for about a day (with a few hours sleep), so I guess I'll just put it aside for a little while. Maybe that post 668 will somehow become clear to me, but for now, I just don't get it!

I'm appreciative of all the help!

---------- Post added at 08:53 PM ---------- Previous post was at 08:37 PM ----------

Rocketero or codeloverl, let me take one more stab at it before quitting for the night. I'm trying part of post 668.

This next command fails. I suppose that means that somehow the install of this apk did not work? But I watched it install!

adb uninstall com.noshufou.android.su

Now a very dumb question. Where do I download this next apk to so that this command works? When I installed the com.noshu...apk above, I did it from windows, telling it to use the BS Apk Handler. But now that I'm issuing commands in the terminal emulator, how do I put it in a place where this command sees it? Boy, I know I'm really asking something quite basic.

adb install Superuser4BS.apk

One of my problems is that I have no experience with any Linux or Ubuntu systems, commands, etc. So I really need to do more reading or find a tutorial!

Thanks again.
[Android Software/Hacking General [Developers Only]] codelover:
Nop, i wanted to make sure your have the right image.

Let me see your output for busybox mount & ls -la /system/xbin/su if possible, screenshot for that output part is enough.

---------- Post added at 12:59 PM ---------- Previous post was at 12:54 PM ----------

That won't work for you, you need to have your su -c whoami returns 'root' first.
[Android Software/Hacking General [Developers Only]] sga999:
codelover, I've never attached or uploaded a file. I'm trying the "insert image" icon and pointing to a file on my laptop, but this may just look like garbage. All I see right now before I post this is just something showing the filename with [/IMG] before and after it.

As expected, no good! Let me know how to show you this screen shot.
[Android Software/Hacking General [Developers Only]] codelover:
You can upload to pic sharing site like http://imgur.com/ and get the url then click the thumbnail icon in your compose window and paste the image url there, but for now you can upload as attachment.
[Android Software/Hacking General [Developers Only]] sga999:
So sorry to not know these things.. I see 7 icons above where I'm writing now, the 5th is for insert image. But I don't see anything that allows me to attach a file from my d: drive.
[Android Software/Hacking General [Developers Only]] codelover:
Go to http://imgur.com/ -> Upload images -> Computer -> Start Upload, after finished copy the Linked BBCode and paste it in your compose window.
[Android Software/Hacking General [Developers Only]] sga999:
Since you said to just do as an attachment for now, I didn't think you wanted me to do it by uploading to a site and getting a URL. Let's see how this goes.
[Android Software/Hacking General [Developers Only]] codelover:
OK, so far so good, now download my Superuser4BS.apk, extract and place it in C:\ProgramData\BlueStacks\UserData\SharedFolder\

Then run below commands in terminal:

cd /mnt/sdcard/bstfolder/BstSharedFolder
ls # Must be able to see Superuser4BS.apk
pm uninstall com.noshufou.android.su
pm install Superuser4BS.apk

Please DO NOT set your Superuser to Automatic Allow first, let's be default for now.

Try type su see how.
[Android Software/Hacking General [Developers Only]] sga999:
There wasn't a SharedFolder under Userdata, but I made one, and once I copied the .apk file there, the cd and ls commands worked great. But both pm commands say "Killed".
[Android Software/Hacking General [Developers Only]] codelover:
Try HD-Quit and start BS and do it again.
[Android Software/Hacking General [Developers Only]] sga999:
No luck, same result. After the first pm for the uninstall, in addition to "Killed" on the terminal screen, a message pops up briefly that says something like "Application failure detected. Try again".

P.S. If I do try again, it still gets killed, but the failure pop-up message does not occur again.
[Android Software/Hacking General [Developers Only]] codelover:
This is weird! how about just type 'pm'? usually if the first try get killed, the second time would work.
[Android Software/Hacking General [Developers Only]] sga999:
"pm" all by itself displays a long list of information about commands, e.g. the last part is about the SetInstallLocation command.

EDIT: "pm getInstallLocation" works, i.e displays "0[auto]".
[Android Software/Hacking General [Developers Only]] rocketero:
It's hard to tell when you see that message: 'application failure detected' what's the exact application that is failiing. I had that message after updating BS from 0752700 to 077813. The one way I found out, or at least tried to find out, was with the mesg and logcat utilities.

in order to see the contents of these 2 utilities, one can redirect them to a file, like this: in a terminal

dmesg > /sdcard/output-of-dmesg.txt
su -c 'logcat -d -f /sdcard/output-of-logcat.txt'

then opeing those .txt files and examining for words like 'failed' will give you a clue of what apps are crashing/failing and then uninstalling them / reinstall them may fix the faulty app.

On my case was the application 'ROM Toolbox Pro' the one failing and I could reinstall it and fix it and that message hasn't shown any more.

For the screenshot you posted above I could see that when you typed 'su' the command prompt still shows $ instead of #, that is because your superuser apk is not installed or is causing problem somewhere, as the outpus of 'ls -la su' shows that is fine, it's rws-r-s-r-x and the size is the one for su..3.2x86.
[Android Software/Hacking General [Developers Only]] codelover:
Nvm, that is useless now, some questions for you:

1) Do you still have Superuser installed now?

2) Do you know how to use adb? (Android Debug Bridge)
[Android Software/Hacking General [Developers Only]] sga999:
Yes, I still have superuser installed. And I'm certainly not proficient but I should be able to use adb. I tried some commands earlier when I thought maybe I could use post 668 (that may not be the right number). So you don't want me to do the mesg or logcat stuff, right?
[Android Software/Hacking General [Developers Only]] codelover:
Tell me what you get with the following, really need to find out whether your su work or not:

adb shell su -c whoami
[Android Software/Hacking General [Developers Only]] sga999:
It says 'root'!
[Android Software/Hacking General [Developers Only]] codelover:
If adb is root you should be able to uninstall/install without problem, curious....

Any idea where is your Superuser.apk located?

adb uninstall com.noshufou.android.su
adb install Superuser4BS.apk
[Android Software/Hacking General [Developers Only]] sga999:
I can't look at /data at all, but I would guess superuser.apk is in /data/app? The adb uninstall says "Failure", but maybe I need to cd to the right place? And for the install, it can't find the apk. Do I need to cd to that sharedfolder where I put it before?

---------- Post added at 11:11 PM ---------- Previous post was at 11:08 PM ----------

Ah, the install worked by just copying the apk right where I happened to be running the adb commands from. 1199898 bytes, success.

And! su command in terminal now displays $! But the uninstall never worked...meaning it never got installed? How can I be causing this?
[Android Software/Hacking General [Developers Only]] codelover:
Maybe you run some commands in #668 before, so now do you have root in terminal? type 'su' & 'whoami' in terminal, what is the output?
[Android Software/Hacking General [Developers Only]] sga999:
I did try part of 668 earlier, but right when I was doing that, either you or Rocketero told me it wasn't going to work (sorry, I have no idea who said what now!). I made a mistake above, I meant su now displays #, Then whoami says 'root'. I can now look at /data! I can't find superuser.apk in either /data/app or /system/app. Where should it be?
[Android Software/Hacking General [Developers Only]] codelover:
You now have full root, what else are you looking for? Remember don't set Superuser Auto respond to Allow, let it be Prompt until the apps get added in superuser database. The apk name should be /data/app/com.noshufou.android.su*.apk now.
[Android Software/Hacking General [Developers Only]] sga999:
Okay, codelover, I am happy! But I was just curious about why I couldn't find the apk. I can't thank you enough. I had started to do those adb commands earlier, but then we started all this sleuthing. Several hours that I can never give back to you!

One last question about allow vs. prompt. The procedure I followed just says to change it to allow after installing com.noshufou,,,,apk. Is that aligned with what you are saying? I don't know when the apps are added into the superuser database.

Again, your patience and dedication are amazing. Someone will probably want to delete all these pages! Thank you very much.

EDIT: My post 740 did say that I tried the adb uninstall command but it failed. I'll never know what went wrong, but that's okay...I'll live with it!
[Android Software/Hacking General [Developers Only]] codelover:
The apk has been renamed to the app internal name /data/app/com.noshufou.android.su*.apk.
[Android Software/Hacking General [Developers Only]] dooby-doo:
GUI tools:

Windows

Total Commander (two panel file manager) ADB Plugin.

Linux

File Mounter script from hacktolive.org

and ark packager to edit squashfs.
[Android Software/Hacking General [Developers Only]] rocketero:
What sort of apps can we run in BS that are worth it

@sga99, now that you have root, don't forget to shut down BS completely and make a backup of your working Root.fs, you don't know how many times I have blown up BS and having to start with the Root.fs from the .rar I made. But it's better to have a copy of the Root.fs one is working actually with so the changes one make don't get lost.

In a another topic, now that we have more time to explore BS, I am also starting to get a bit disappointed as mohaiza pointed out somewhere, about the sort of android applications we can run on it. For instance some basic games that I enjoy like 'cut the rope', 'where's my water', don't run on it, they crash after launch them. Also heavy duty games like shadowgun, n.o.v.a 3, mc3, mass effect, etc don't even launch and shadowgun in particular make BS crash. So the question is what apps are all of you running that makes a difference to say this program is really worth it. Because even my Pandigital Supernova8 tablet runs Shadowgun, Massefffect and others that BS don't, and I'm running also Gingerbread on it.
[Android Software/Hacking General [Developers Only]] merrickville:
BlueStacks is 'BETA', it's really a good way off from a release candidate.

Keep in mind, it's an 'emulator', like VirtualBox is an emulator of a PC's (80386 & x64), BlueStacks is an emulator of Android (ARM) 32bit and x86 emulation runt side by side.

Don't expect it to be 100% compatible with your Android phone, for now anyway.
[Android Software/Hacking General [Developers Only]] rocketero:
Backing up BlueStacks.

I just got an idea on how to truly backup your BS.

After one has installed it, rooted it, and installed all the apps that want to run with it, then proceed to backup it up doing this:

To Backup your Bluestacks:

1. Shutdown BS completly

2. Download RegScanner (x86 or x64)

3. Copy C:\>Program Files\Bluestacks folder (64bit is program files (x86)) and past it in another place under same folder structure: let's say as D:\>BluestacksBacup\Program Files\Bluestacks

4. Copy C:\>ProgramData/Bluestacks folder and past it as D:\>BluestacksBackup\ProgramData\Bluestacks

5. Copy C:\>ProgramData\BluestacksSetup folder and past it to D:\>BluestacksBackup\ProgramData\BluestacksSetup

6. Run RegScanner and select the 3rd box that says: "Display Values With the Following Types" and select all items on the right and left boxes. then type Bluestacks on the "Finding String" and click OK.

7. After all items have been found, on the window that opens up click the Edit Menu and "Select All"

8. In this same window on step 6, select from File Menu: "Export Selected Items" and give it a name, .reg

That would be all, next time you want to recover BS would be to copy back the folders on steps 3 ,4 and 5 and then run the .reg file from step 8.

Any comments, adjustments or other methods are welcome.

Edited: to include step 4.
[Android Software/Hacking General [Developers Only]] dari-woka:
woow! this sounds great! Does anyone has tried yet?
[Android Software/Hacking General [Developers Only]] mohazia:
Thanks, I will add it and link the method to this post, if you have any modification, plz edit it

---------- Post added at 08:36 PM ---------- Previous post was at 08:26 PM ----------

actually, I already have su in both bin & xbin, I have no prob with su binary, the problem with superuser. I'm now deleting BS completely to start from beginning and test it. my prob is that I first root 0.7.2 then keep data.fs and replace it in 0.7.7
[Android Software/Hacking General [Developers Only]] codelover:
Actually 'CTR' did have problem with either previous version of BS or the app itself, but the latest version runs fine and smooth, it's just a my screen too small to support the vertical orientation view. While 'Where is my water' also runs, it's just too slow that you can't even move your mouse!
[Android Software/Hacking General [Developers Only]] mohazia:
the silly joy, that we spend days of installing, rooting, collecting resources, for what, to browse via android browser :p, and what JB or ICS browser NO it's GB browser. what more, ya XDA Premium, FB, Twitter, Flipboard, Pulse, Gmail that's all.

Actually, I was in via request from nagar.xda, that he asked for Arabic support for BS. and I pushed on and then I can't getting out, old methods, un-assorted techniques. you should collect from a lot of posts. that why I summarize methods that I understand in just one first post.

then I found libwebcore.so is compiled into libwebcore.so-arm :crying: .

if merrickville, codelover or rocketero feel that u r interesting in BS, just PM me to delete my post and start your own to follow with.

Today I review my methods and add removing methods and attach codelove superuser and try from scrash step by step to perfecting the method.

---------- Post added at 02:37 AM ---------- Previous post was at 02:10 AM ----------

I didn't claim credits for me, I cited on the first lines all credits to all of you. & I claim that I only summarized what I learn from you.

I even used the same commands, inspite of, I know that sfs should be treated by unsquashfs command and I can repack it via mksquashfs. I even can change directory names.

I didn't make the thread to grow too fast. because I don't have knowledge and time, because I'm a dentist with 2 master degree one in crown & bridges and other with implants and thanks GOD full booking appointments.

Finally, I summarize ur efforts, because BS not worthy to spend days in rooting it then browse it for an hour, then uninstall it. for u as a codelover maybe the story different but for majority of us is to explorer new methods of using android.

Finally (again), I don't blame you, no, you teach me some thing, and our profit encourage us to thank who tech us good things, more over "who don't thanks people, don't thank GOD", so thank you, only I want to explain my goal of making new threads and summarize your efforts.
[Android Software/Hacking General [Developers Only]] codelover:
LOL there must be some miss-understanding, what i was referring to is THIS thread was growing too fast back few pages (yea that was spammed by me & sga999) until rocketero has forgotten that you already have the rooted image and no need to download again because you are infact the one uploaded the latest rooted image. I was laughing at rocketero actually, same case like when merrickville forgot rocketero already knows how to root, but his case was a little bit different because he took drug, opss i mean medicines. :X and still helpful to post.

Infact i do appreciate your effort for making the new thread as some newcomer arrived and just read the first post and then claim it didnt work for them. Just like what i did few months back :X, how good if there was a latest root guide available few months ago, then i don't have to waste weeks just to figured out how to get it rooted by myself.

No worries k, teamwork and together make BS a better toy for pc.
[Android Software/Hacking General [Developers Only]] mohazia:
Don't worry, I'm so sorry for that & it's my pleasure to be with ur team, if I left too long, plz send me pm for updates or edit or to replace it with ur thread.

One more question. I removed bs completely also remove all related files, reinstal it, my /data should be free from com.nosh* (as any new user)

I mounted my /system, copy superuser & su. Then open bs. It will install superuser automaticly & create com.nosh*. If I share my root.fs or let's say I restore original /data. superuser will be installed automaticly and create com.nosh* or it keep a record that it was create this folder eailer?
[Android Software/Hacking General [Developers Only]] codelover:
It will be installed automatically and create com.noshufou.*, but if user already installed in their system then that might cause conflict.
[Android Software/Hacking General [Developers Only]] rocketero:
I don't use BS in a productive environment, I just use it to test apps before I install them on my 9.8" tablet running ICS 4.0.4. thou it would be nice to run games in Bluestacks in my 27" LCD monitor.

One game that I like is Angry birds, but in BS I can't zoom out to see the whole screen, if I use the center button or wheel in my mouse it zooms out but then if I try to use the mouse in the regular left button to shoot, it doesn't work afterwards. If I don't use the center wheel I can shoot but without zooming out there is not way to tell where one is aiming at. has n1 has the same issue? or how to fix it for this particular game?