Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.
goister said:
Hi,
I have a OMAP3630 board running Froyo that I rooted using the z4root app. I then installed busybox 1.19.4 using the busybox installer free app. I discovered that this version of busybox contained tools that were of an older version than what I need, so I uninstalled it using the app's uninstall option.
I then downloaded another busybox version manually, and according to instructions, placed it in /data/busybox, changed its executable permissions with chmod, then ran ./busybox --install.
The installation works, and the tools are of a recent enough version for my purposes. However, now whenever I run su, it gives me the error message "su: unknown user root"
Additionally, when I run "busybox" it shows that it's version 1.16.0. However, when I run some of the tools such as mkfs, it shows busybox version 1.19.3. Seems like there are multiple versions of busybox installed. How do I clear them so that su works again, and then reinstall only the version of busybox that I want?
Thanks.
Click to expand...
Click to collapse
Same problem, I am using a polaroid tablet, I installed busybox by doing the following
busybox --install /system/bin
I believe it overwrote some files and cant find the fix
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
You should be able to just run the root.bat if you have the folder with all contents extracted to desktop.
Sent from my MB865 using xda premium
Aimless Rambler said:
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
Click to expand...
Click to collapse
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Re-Rooted!
jimbridgman said:
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Click to expand...
Click to collapse
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Hmm
Aimless Rambler said:
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Click to expand...
Click to collapse
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
update on strange problem
Aimless Rambler said:
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
Click to expand...
Click to collapse
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Aimless Rambler said:
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Click to expand...
Click to collapse
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Rooted again??
jimbridgman said:
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Click to expand...
Click to collapse
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin it alone did not fix the problem. I still could not access root. So I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Aimless Rambler said:
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Click to expand...
Click to collapse
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
jimbridgman said:
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
Click to expand...
Click to collapse
Thanks! I'm sure I did something to cause the troubles but can't recall exactly what it was I did wrong! My brain is getting old. Ha! But to answer your question ... other than my original root (using Motofail) I've hesitated to do anything until after the ICS update. I recently bought the phone 2nd hand to replace my Samsung Captivate so I could experiment with a Lapdock (in my line of work portability and multi-role is a plus). The phone was stock when I got it. Also, I had moved the root.sh file and superuser.apk into my Android/Platform_Tools folder which is in my system path (android rules,etc), so there was some forethought prior to dragging the script into terminal. Next time I'll 'cd it like ya recommend!
Could it be there was an issue with how I did the original GB motofail root?
In any case all seems to be good now.
Thanks again!
Yep, you read that correctly. I have optware, ssh, samba, transmission, and flexget working on my Minix X5 Mini. This should work for any rooted device which has an adb connection enabled. This will work on the original ROM. In fact, I use the stock ROM. For those not using a Minix device this should work on any ARM device. Sorry but all the binaries are built on ARM.
JUST AS EVERY OTHER DEVELOPER: I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE! MAKE A BACKUP!
Requirements:
Linux box with adb (don't ask me about windows, I don't support bad habits)
clockworkmod (for a backup)
root
internet connection
Process:
Make a backup of your ROM!
Download files (gitHub)
You have two options here:
Download the zip via https://github.com/erichlf/AndroidSeedBox/archive/master.zip and unzip it.
Clone the repo using git via 'git clone [email protected]:erichlf/AndroidSeedBox.git'
Make script executable
chmod +x optware-etc.sh
Obtain adb connection to device (covered in another thread)
Gain root access on local machine (adb seemed to require this for things to work)
sudo su
Run script and follow directions
./optware-etc.sh
Use SManager to run /opt/home/root/sysinit at every restart.
Notes:
The script can be modified to change the various programs that I install. You could exchange transmission for deluge for example.
Transmission can be accessed from the minix through localhost:9091 or from some other machine using your ip-address and the port 9091. If that doesn't work you should edit the config file located at /opt/home/root/.config/transmission-daemon/settings.json
username: root
password: you provided this in the install script
Without SManager nothing will start automatically. However, if you have a ROM which has init.d support you can move the scripts in /opt/etc/init.d to /etc/init.d I would suggest maybe linking the two instead of just moving the scripts or possibly adding a script to /etc/init.d which runs the items in /opt/etc/init.d The reason is because when installing things using ipkg the startup scripts will be placed in /opt/etc/init.d and not /etc/init.d However, it is extremely important that optware is started, and this is partly what sysinit accomplishes.
To list available packages
ipkg list
To install a new package use the command
ipkg install <new package>
To remove a package use the command
ipkg remove <package to remove>
cron is weird and I couldn't get it to work like it should, but I got it to work
While on the Android device (ssh or terminal emulator)
Create a .crond file in the home directory of your device (/opt/home/root/) with some schedule in it. Remember to leave a blank line at the end of the file.
Tell cron about the .crond file
crontab -u root /opt/home/root/.crond
Make sure cron sees the cron file
crontab -l
If you want to edit your cronfile use a text editor and edit the file directly and then tell cron about the file again.
Many things are installed in what seem like strange places, so use
which <binary you are looking for>
Feel free to help develop the code. I think what would be best is an update.zip or a CWM flashable zip. Right now I don't know how to do this, but once I get more time I will look into it. So, any help on this front is welcomed.
Enjoy!
I really wish you would have kept the repo up. It seems kind of pointless to go through all that trouble just to delete the repo and leave people wondering what you did.
I have been busy and didn't update this particular post, since there had been no activity on it.
git clone [email protected]:erichlf/androidseedbox.git
https://bitbucket.org/erichlf/androidseedbox/get/master.zip
Sorry, I didn't need to be rude. I was just excited to find this and then sad when it was gone. Thanks for pointing me in the right direction!
Current rooted version: 0.8.3.3026
!!!UPDATE 07DEC13!!! -> With SuperSU v1.80!
Here are the rewritable rooted filesystem-files for BlueStacks. Easy if you want to install BlueStacks for development reasons and don't want to go through the trouble of rooting it yourself.
I'll try to keep it updated as they make their updates, but since they don't really announce them, forgive me if I skip some. :silly:
It's also allowed to point me out there's a new version, I'll probably get to it faster that way.
Anyway,
Usage:
Install BlueStacks
Quit Bluestacks completely.
- (By clicking on their tray icon and selecting Quit, or by running the HD-Quit.exe)
Go to your 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)
Unpack and replace Root.fs and initrd.img with the 2 files in this 7zip
Restart BlueStacks
If "Installer" asks root access, give it root access... ;p
Done!
Code:
[URL="http://cur.lv/5atkp"][COLOR="DeepSkyBlue"][U]Download both files 7zip'd from 'ADrive' here[/U][/COLOR][/URL] (269.3MB)
Mirrors:
[URL="http://cur.lv/5atb6"][COLOR="SeaGreen"][U]Download both files 7zip'd from 'FileDropper' here[/U][/COLOR][/URL] (269.3MB)
[URL="http://cur.lv/5blid"][COLOR="DarkBlue"][U]Download both files 7zip'd from 'Dev-Host' here[/U][/COLOR][/URL] (269.3MB)
[URL="http://cur.lv/5blth"][COLOR="DarkOrchid"][U]Download both files 7zip'd from 'MediaFire' here[/U][/COLOR][/URL] (269.3MB)
[URL="http://cur.lv/5bpjr"][COLOR="Red"][U]Download both files 7zip'd from 'Android File Host' here[/U][/COLOR][/URL] (269.3MB)
---
[URL="http://bit.ly/1bP5VjD"]MD5 Checksum[/URL]: 0f199f0f353e701a7b9c535098b243b3
Please excuse me trying to get something out of the trouble, though. ;p
----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----
Then, for the noobs that just can't get it working and the limitless downloaders who just don't look at filesize, next, I give you the full 'Android' directory! 7zipped while not running, these files are a certainty that all should work, because they come with /system and /data together and are meant to replace your own. All your own apps and settings (not your backupz to SD) will have gone after doing the following, so it's only recommended when you're planning to start anew anyway or when you just can't get the root into it for some reason... Or maybe you planned ahaed and backed everything up anyway... ;p These files are certain to give you not only SuperSU-root access, but also a Play Store ready to use and as a bonus a full Debian Linux (Jessie) installed underneath it. (This is why it's so much bigger. ;p)
A little info on the linux:
Debian's root password is set to "bluestacks", and it's also the password for the "BlueStacks" user. You can change these without any problems. You can also just enter Debian Linux by opening the installed Terminal. I already preset it to do this. I also used the none standard Terminal app so you can use the normal one for your own purpouses without constantly fiddling and swapping with it's settings. ;p
So, just kill BlueStacks completely and swap the contents of this 7z with the contents of your ProgData-BlueStacks-Android dir (except for the missing sdcard.sparsefs, of course).
It should be located here:
- For XP: x:\documents and settings\all users\application data\BlueStacks\Android
- For Vista, 7, 8,...: x:\programdata\BlueStacks\Android
(x marks the drive your windows is installed on. )
And restart BlueStacks.
Code:
[URL="http://cur.lv/5d4xj"][COLOR="DeepSkyBlue"][U]Download the BlueStacks Androdebian Project from 'ADrive' here[/U][/COLOR][/URL] (622.3MB)
[URL="http://cur.lv/5dbr7"][COLOR="SeaGreen"][U]Download the BlueStacks Androdebian Project from 'FileDropper' here[/U][/COLOR][/URL] (622.3MB)
[URL="http://cur.lv/5dct9"][COLOR="DarkBlue"][U]Download Part 1 of the BlueStacks Androdebian Project from 'Dev-Host' here[/U][/COLOR][/URL] (311.5MB)
[URL="http://cur.lv/5dcyx"][COLOR="DarkBlue"][U]Download Part 2 of the BlueStacks Androdebian Project from 'Dev-Host' here[/U][/COLOR][/URL] (310.8MB)
[URL="ttp://cur.lv/5d51y"][COLOR="DarkOrchid"][U]Download the BlueStacks Androdebian Project from 'MediaFire' here[/U][/COLOR][/URL] (622.3MB)
[URL="http://cur.lv/5dciu"][COLOR="Red"][U]Download the BlueStacks Androdebian Project from 'Android File Host' here[/U][/COLOR][/URL] (622.3MB)
---
[URL="http://bit.ly/JbVniG"]MD5 Checksum (Full File)[/URL]: 5763bf8f96d4f4990494d4bab1b2fd0b
[URL="http://bit.ly/18mVKlB"]MD5 Checksum (Part 1)[/URL]: 32ee4dc23717c2c5878dfdf125231fe1
[URL="http://bit.ly/Jg3v1H"]MD5 Checksum (Part 2)[/URL]: 7a989a027454786ab45fe4eb6d3917b7
----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----
And btw, if you want to try it yourself, I always write down my steps taken, so here they are:
Rooting BlueStacks as I did it:
For this you will need the following programs:
BlueStacks (of course)
IOBit Uninstaller
7zip
Notepad++
Portable Ubuntu
I used Windows XP x86, but I added the info for higher windows versions and x64 windows versions as well)
x marks the drive your windows is installed on.
Winkey-R (Run) "%programfiles%\BlueStacks\HD-Quit.exe" (or "%Programfiles(x86)%\BlueStacks\HD-Quit.exe" for x64);
Kill HD-LogRotatorService.exe in Task Manager;
I used IOBit Uninstaller because I hate waiting on the Windows internal one and it does a lot more stuff we need done.
(If you want it and haven't already, get IOBit Uninstaller here!);
Uninstall BlueStacks with IOBit Uninstaller;
Choose to scan for remaining stuff and delete all of the findings;
Uninstall BlueStacks Notification Center
When it asks to keep all data and userfiles, say no;
Delete x:\Documents and Settings\All Users\Application Data\BlueStacksSetup (or x:\ProgramData\BlueStacksSetup in Vista or higher)
('BlueStacks' dir has been removed by clicking 'yes' in uninstall, if not, remove it as well);
If you can't delete hyperviser.log, you'll have to reboot first, then delete the BlueStacks folder before you'll be able to continue.
Re-install BlueStacks
(If you haven't already, get BlueStacks here!);
Download "busybox-i686" from this site and rename it to "busybox";
Download SuperSU in flash zip format from this site.
Inside this zip is more then just SuperSU. Unzip these files to "c:\pubuntu":
(out of zipped directory "/common"
- "Superuser.apk";
- "install-recovery.sh";
- "99SuperSUDaemon";
(out of zipped directory "/x86"
- "su";
Open Superuser.apk with 7zip, extract the files "/assets/chattr.x86.png" and "/assets/supersu.x86.png to any temporary directory, rename the files to "chattr.arm.png" and "supersu.arm.png", re-insert them (by dragging them back to the still open 7zip) and replace the other 2 png-files.
(If you haven't already, get 7zip here!);
Close 7zip and save;
Open x:\Documents and Settings\All Users\Application Data\BlueStacks (or x:\ProgramData\BlueStacks in Vista or higher);
Open "initrd.img" with 7zip;
Unpack "initrd" to any temporary dir;
Open "initrd" with Notepad++
(If you haven't already, get Notepad++ here!);
Search for " ro " (including the spaces, not the quotationmarks)
There should be two results, change the first to " rw "
- Hint: It's not the one which starts with "Option: ro (read-only",
It's the one that resembles 'try_mount ro $1 /mnt && [ -e /mnt/$SRC/ramdisk.img ]'. ;P;
Save "initrd" and close Notepad++;
Drag it back into the 7zip application where "initrd.img" is still open and overwrite existing "initrd";
Close 7zip;
Then you'll need Portable Ubuntu
(If you haven't already, get Portable Ubuntu here!);
NOTE: Portable Ubuntu does not work on x64 Windows, so if you're not running an x86 Windows, you'll need to use a Linux box or vm (with shared folders) here instead.
- If you have Windows installed on any other drive than C, do the following, if it's installed in C, skip this:
- Open Ubuntu Portable folder;
- Go to the "config" subfolder;
- Edit the file "portable_ubuntu.conf";
- Under the line: "shared_folder0=c:\" add "shared_folder1=x:\" (where x is still the drive your windows is on);
- Save "portable_ubuntu.conf" and exit Notepad++;
Open Portable Ubuntu;
Open the terminal window once it's fully loaded;
Do the following in the exact order:
Code:
sudo su
(pubuntu's password is '123456')
mkdir /n
mkdir /n/rootfs
mkdir /n/sfs
mkdir /n/img
[B]- If windows was on C:[/B]
e2fsck -f -y "/media/cofs2/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs2/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs2/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" /n/rootfs
[COLOR="Gray"](or for Vista and up:
e2fsck -f -y "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" /n/rootfs
)[/COLOR]
[B]- If not:[/B]
[I]e2fsck -f -y "/media/cofs3/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs3/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs3/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" /n/rootfs
[COLOR="Gray"](or for Vista and up:
e2fsck -f -y "/media/cofs3/ProgramData/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs3/ProgramData/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs3/ProgramData/BlueStacks/Android/Root.fs" /n/rootfs
)[/COLOR][/I]
mount -o loop /n/rootfs/android/system.sfs /n/sfs
cp /n/sfs/system.img /n/rootfs/android
e2fsck -f -y /n/rootfs/android/system.img
resize2fs -f /n/rootfs/android/system.img 480M
umount /n/sfs
rm /n/rootfs/android/system.sfs
rmdir /n/sfs
mount -o loop /n/rootfs/android/system.img /n/img
mkdir /n/img/bin/.ext
mkdir /n/img/etc/init.d
cp "/media/cofs2/pubuntu/su" /n/img/xbin/daemonsu
cp "/media/cofs2/pubuntu/su" /n/img/xbin/su
cp "/media/cofs2/pubuntu/su" /n/img/bin/.ext/.su
cp "/media/cofs2/pubuntu/Superuser.apk" /n/img/app/SuperSU.apk
cp "/media/cofs2/pubuntu/install-recovery.sh" /n/img/etc/install-recovery.sh
cp "/media/cofs2/pubuntu/99SuperSUDaemon" /n/img/etc/init.d/99SuperSUDaemon
cp "/media/cofs2/pubuntu/busybox" /n/img/xbin
echo 1 > /n/img/etc/.installed_su_daemon
chown 0:2000 /n/img/bin/.ext
chown 0:2000 /n/img/bin/.ext/.su
chown 0:2000 /n/img/xbin/su
chown 0:2000 /n/img/xbin/daemonsu
chmod 777 /n/img/bin/.ext
chmod 6755 /n/img/bin/.ext/.su
chmod 6755 /n/img/xbin/su
chmod 6755 /n/img/xbin/daemonsu
chmod 755 /n/img/etc/install-recovery.sh
chmod 755 /n/img/etc/init.d/99SuperSUDaemon
chmod 644 /n/img/etc/.installed_su_daemon
chmod 644 /n/img/app/SuperSU.apk
umount /n/img
rmdir /n/img
chown 0:2000 /n/rootfs/android/system.img
chmod 0644 /n/rootfs/android/system.img
umount /n/rootfs
rmdir /n/rootfs
rmdir /n
exit
exit
Shutdown Portable Ubuntu;
Boot BlueStacks;
Install custom launcher like ADW, Go or Apex (Superuser app does not show up in BlueStacks' Launcher);
Install Root Explorer;
Move custom launcher from "/data/app" to "/system/app";
Reboot BlueStacks;
You can now safely remove apps like "Launcher2.apk" and "new_Home.apk" and other original launcher related stuff.
Enjoy and grtz,
~ Nephatiu
Can you explain the steps to root my version manually instead of downloading a 500mb file, if not possible then can you please provide a mirror since Adrive gives Public File Busy error all the time to me?
Thanks
Edit:
Never mind, ignore it. Got it now. Although it's better if you could provide mirrors for others as Adrive is giving problems. I had to download using a premium downloader.
nicesoni_ash said:
Can you explain the steps to root my version manually instead of downloading a 500mb file, if not possible then can you please provide a mirror since Adrive gives Public File Busy error all the time to me?
Thanks
Edit:
Never mind, ignore it. Got it now. Although it's better if you could provide mirrors for others as Adrive is giving problems. I had to download using a premium downloader.
Click to expand...
Click to collapse
Still want instructions, then?
Cause I wrote down the steps I took, so I could easily paste them here (and adapt them a little for others to read, of course. ).
Grtz,
~ Nephatiu
Sure go ahead if you already wrote them down. It will be useful since it's a separate thread then your other post where you put these download links. The only thing messing up my plans right now is to download that portable linux for 1+gb file so for now I have downloaded your files and they work great, I will make them manually next time when there will be a new bluestack update.
Thanks
Rewritable initrd.img (1.3MB)
Rooted Root.fs (500MB)
Click to expand...
Click to collapse
Don't work this url...
nicesoni_ash said:
Sure go ahead if you already wrote them down. It will be useful since it's a separate thread then your other post where you put these download links. The only thing messing up my plans right now is to download that portable linux for 1+gb file so for now I have downloaded your files and they work great, I will make them manually next time when there will be a new bluestack update.
Click to expand...
Click to collapse
Okay, I'll add it in the original post,... ;p
Grtz,
~ Nephatiu
New Version
Version 0.8.2.3018 is out.
I accepted the update & Root Checker Pro says I still have root.
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
0.8.2.3018 updates and root is still there except the root apk is gone as the Root.fs has been replaced.
Almighty2 said:
0.8.2.3018 updates and root is still there except the root apk is gone as the Root.fs has been replaced.
Click to expand...
Click to collapse
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
Nephatiu said:
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
Click to expand...
Click to collapse
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 ~
Chakkas said:
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 ~
Click to expand...
Click to collapse
Good idea. I don't know why I didn't do that in the first place...
Ah, well, I'll 7zip them and up them again,...
Grtz,
~ Nephatiu
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!!
huisterduin said:
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.
Click to expand...
Click to collapse
Why? What's so new about it? This one works and was already unpacked to me. (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. (Haven't checked though. )
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.
I'll see what I can do next release.
Grtz,
~ Nephatiu
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.
Almighty2 said:
1.75 has actually been available on Google Play Store since November 20, 2013 and these are the changes:
Click to expand...
Click to collapse
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 ) 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. 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.
Almighty2 said:
- 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
Click to expand...
Click to collapse
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... (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)
Almighty2 said:
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.
Click to expand...
Click to collapse
Apart from the fact it didn't even want to update in my Market,...
Almighty2 said:
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.
Click to expand...
Click to collapse
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...
Grtz,
~ Nephatiu
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.
Almighty2 said:
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.
Click to expand...
Click to collapse
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.
Almighty2 said:
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.
Click to expand...
Click to collapse
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. 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
Almighty2 said:
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.
Click to expand...
Click to collapse
And a good job they did, imho. ;p
Grtz,
~ Nephatiu
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.
CptKlink said:
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.
Click to expand...
Click to collapse
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:
Code:
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? 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