Related
PLEASE NOTE: THIS THREAD IS NOW OBSOLETE, BUSYBOX COMES WITH JUST ABOUT EVERY COOKED ROM
Hi all,
This is my first attempt at compiling anything for the android platform. My reason for doing this is whilst the busybox version does what we need it to do when rooting our HTC Dream's / G1's, as an everyday app it fails because it segfaults all the time.
This isn't a dig at Benno because to be honest, he's a bit of a hero for compiling it the first time round, without him it would have been a lot harder (if not impossible) to root our G1's.
Problem is, his version of busybox was compiled over a year ago (14 nov 2007 if his blog is anything to go by) and segfaults quite a lot (probably because it wasn't compiled for the G1, but more for the Android emulator), particularly if you try and do "ls -al"..
So what I've done is I've compiled the latest stable version of busybox (1.13.1 as of 14 December 2008) for the G1, I've tested this on my own G1 and it seems to work fine, but I could do with some help extensively testing it.
You can grab it here (for G1: long press -> save, for other browsers: right click -> save as / save target)
Installation Instructions:
Download the above file to your G1, it should be saved as /sdcard/download/busybox2.asc
(if you downloaded it with the G1 browser that is, otherwise please copy it to your G1's SD card to that exact path / name)
Remount your /system partition with this command:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
Copy the busybox binary into the /system/bin/ folder by running this command:
Code:
dd if=/sdcard/download/busybox2.asc of=/system/bin/busybox
Set the busybox binary as executable with suid bit by running this:
Code:
chmod 4755 /system/bin/busybox
Remount your /system/bin partition as read only again (unless you want to create more shortcuts) by doing the following:
Code:
mount -o remount,ro /dev/block/mtdblock3 /system
And thats it! Please test it as thoroughly as you can and let me know in this post if you have any problems
Ps. I take no responsibility for any damage that occurs directly or indirectly from using this program. Although I will try and make amends if something doesn't work as expected, you must acknowledge that you are solely responsible for your actions when modifying the filesystem of your G1.
Please note, this version is compiled as follows:
* It is compiled against regular libC so is 1.8MB big
* It is compiled with the soft links options
I'm investigating compiling it against uClibC to get the size down dramatically, and compiling it with a seperate set of options so it auto-identifies when to use itself when you're shell is busybox sh.
Appears to have installed alright! Haven't had a chance to test it out otherwise, but I'll let you know if my phone explodes.
Excellent going through it now!!!
Thank you!
anybody else get
Code:
/system/bin/busybox: write error: no space left on device, 1045+0 records in , 1044+0 records out, then the speed stats
Im just gonna chmod it anyway, I wonder which file it forgot?
man all my G1 hack went smooth till I tried the market cache move, i got 1 file and 100 force closes, tried moving them back to no avail..HARD RESET, now I messed up this one somehow, Its par for my course these days, f'it...
bhang
edit:
I reran the "dd" command after I freed up almost a meg and it output same write error: no space left on device 1+0 records in 0+0 out, looks like it copied the last file I missed in the first run? do I need to chmod everything again since I dunno which 1 of the files it may have been..
on second thought 'dd' looks like it may have realized it only needed the 1 file but still needed more room cause 0+0 out, I dunno im confused any advice?
good work
installed successfully. so far no problems. does this new version contain commands not found in the previous versions, ie/ the version JesusFreke used in modified rc30 v1.2 (Sauriks' version from here: http://www.telesphoreo.org/pipermail/g1-hackers/2008-November/000032.html)?
edit: just realized that the previous ver i had installed was 1.12.2 (2008-11-16)
I think JesusFreke was compiling the bionic version last night. Might wanna check on that before you spend your time doing if it you have not already.
Darkrift said:
I think JesusFreke was compiling the bionic version last night. Might wanna check on that before you spend your time doing if it you have not already.
Click to expand...
Click to collapse
uninstall is just as easy as installing
-beers!
Bhang, have you installed anything else on your /system partition bar the stock files?
I'm working on a solution at the moment that moves all this to the /data partition to provide some more usability. For now I suggest you delete busybox from /system/bin/ so you don't fill up your /system partition.
syntax?
I could not quite get this to work as stated. I am no command line expert, so I guessed at what might work. I did the following:
Instead of this:
mount -o remount, rw /dev/block/mtdblock3 /system
I did this:
mount -o remount, -rw /dev/block/mtdblock3 /system
At the last I did this:
mount -o remount, -r /dev/block/mtdblock3 /system
Then I rebooted. Everything seems fine. I looked up some busybox commands, but they don't seem to do anything. Any way to know for sure?
my bad, it works!
Excuse a noob, I didn't know you had to type "busybox" in front of the command...
Hi, the link is down, can someone please re-upload? Thank you .
Please note, this is now obsolete as busybox comes with just about every other ROM out there.
foxdie said:
Please note, this is now obsolete as busybox comes with just about every other ROM out there.
Click to expand...
Click to collapse
Unfortunitally there have been people releasing versions without busybox recentl for the mytouch series mainly and we need a good version of Busybox if possible
Hi,
I know that, but I'm having problems getting SUFBS (http://forum.xda-developers.com/showthread.php?t=530271) to work correctly. I read through the thread and someone tried your busybox and it worked. Also, the one I have (using myhero 0.0.7) is using 1.8.1.
You can actually rip the busybox binary out of any of the roms that come with it.
Any instructions? It'd be simpler if foxdie's busybox is re-uploaded though. Thanks!
Wysie said:
Any instructions? It'd be simpler if foxdie's busybox is re-uploaded though. Thanks!
Click to expand...
Click to collapse
try this out, it's what i used http://benno.id.au/blog/2007/11/14/android-busybox
http://www.busybox.net/downloads/snapshots/busybox-snapshot.tar.bz2
can anyone please compile the latest source or explain how to do this with windows and visual studio?
I tried to build busybox latest with android bionic lib and gave up on passwd.
I had problems with bionic umtp, no strchrnul in string.h and no pw_gecos in passwd.
I can not understand how other busybox builds where able to get build. Any experiances?
EDIT: Doh, stupid me. I made 2 big mistakes. I will give it a new try with an other compile.
EDIT2: wich lib was taken to compile busybox? androids c lib bionic was not possible for me.
Does anyone have a compiled busybox for the EVO yet. Preferably in update.zip format. I'd like to get Debian working on the phone and Busybox is a requirement.
Im confused, I got busybox installed from titanium backup. Is that the same one you need? If so install titanium backup, hit 'problems' and install busybox that way.
I made a custom rom I just posted with BusyBox preinstalled. I will see if I can post an update.zip with busybox in it soon.
ChrisDos said:
Does anyone have a compiled busybox for the EVO yet. Preferably in update.zip format. I'd like to get Debian working on the phone and Busybox is a requirement.
Click to expand...
Click to collapse
here is one of my busybox binaries which should get you going. you'll have to manually install it, adb push to sdcard and then using root, mv to /data and chmod 755. should be good to go. if you're using unrevoked root, you can put it in the shadow directory and it'll appear in /system/bin.
http://forum.sdx-developers.com/android-2-1-development/(source)-sdx-busybox-for-android-2-1/ - where we maintain our latest version of busybox thanks to LouZiffer. I use this binary in all my ROMs. Its our community trade off for features with size..
my personally hosted mirror isnt always as updated as the link above - http://www.joeyconway.com/sdx/busybox/busybox (its the recovery version from link above with more features)
i'm sure somebody will throw up an update.zip which might be easier for most users.
joeykrim said:
here is one of my busybox binaries which should get you going
http://www.joeyconway.com/sdx/busybox/busybox
Click to expand...
Click to collapse
Even better Will installing it out of recovery work since it needs to add symlinks? You will probably need to go into recovery, and then adb shell busybox --install.
chuckhriczko said:
Even better Will installing it out of recovery work since it needs to add symlinks? You will probably need to go into recovery, and then adb shell busybox --install.
Click to expand...
Click to collapse
yea, so depends. if you're as root in normal android mode, unrevoked or one of toast/maejrep's rooted ROMs you can manually install w/o rebooting to recovery. if you dont have root in normal android mode, no custom ROM and no unrevoked root, you'll need to go into the recovery mode with root access.
i think the command to put sym links into /sbin which would be in the default PATH is:
busybox --install -s /sbin
i havent really experimented to see what people are using as their default install locations ... sorry for the rough guide!
I installed busybox entirely from my phone using the directions laid out in the troubleshooting section on the TitaniumBackup webpage (sorry, new user cannot post link, but you can link to it from the app in the market). I have toast's root and radio and flipz's .6 ROM, and I was able to do it all using a terminal on the phone, so, no recovery.
Thank you all. I got busybox installed and working fine. Though I guess I'll have to wait until an official ROM comes out with Ext4 support as it won't let me mount the partition that contains the Debian install. I suppose I could format the partition with yaffs2, but I haven't done any research into that file system. I might just have to be patient until an ASOP based ROM is released or someone includes a kernel with Ext4 support.
Thanks everyone. I appreciate all the hard work put towards this phone.
ChrisDos said:
Thank you all. I got busybox installed and working fine. Though I guess I'll have to wait until an official ROM comes out with Ext4 support as it won't let me mount the partition that contains the Debian install. I suppose I could format the partition with yaffs2, but I haven't done any research into that file system. I might just have to be patient until an ASOP based ROM is released or someone includes a kernel with Ext4 support.
Thanks everyone. I appreciate all the hard work put towards this phone.
Click to expand...
Click to collapse
can you post the files and directions to so i can get it installed? thanks
ChrisDos said:
Thank you all. I got busybox installed and working fine. Though I guess I'll have to wait until an official ROM comes out with Ext4 support as it won't let me mount the partition that contains the Debian install. I suppose I could format the partition with yaffs2, but I haven't done any research into that file system. I might just have to be patient until an ASOP based ROM is released or someone includes a kernel with Ext4 support.
Thanks everyone. I appreciate all the hard work put towards this phone.
Click to expand...
Click to collapse
if you use toast's kernel source released here, you can compile a working kernel with ext4 support ... just throwing out ideas cuz i'd hate to see you stop with your progress!
Busybox Installation Instructions
I use Linux, well, for all my computers, including my phone
So these instructions are biased for Linux...
Boot into torch's recovery.
Download busybox from joeykrim:
http://www.joeyconway.com/sdx/busybox/busybox
Place it in a directory and create this script:
Install_Busybox.sh:
#!/bin/bash
echo "Mounting /system"
adb shell mount -v /system
echo "Mounting /data"
adb shell mount -v /data
sleep 3
adb push busybox /data
adb shell chmod 755 /data/busybox
adb shell /data/busybox --install -s /system/xbin
echo "Waiting for system to stabilize before unmounting"
sleep 3
adb shell umount -v /system
adb shell umount -v /data
chmod 755 Install_Busybox.sh
./Install_Busybox.sh
Windows/Mac users can just manually run the adb commands and it should work fine.
joeykrim said:
if you use toast's kernel source released here, you can compile a working kernel with ext4 support ... just throwing out ideas cuz i'd hate to see you stop with your progress!
Click to expand...
Click to collapse
Well, I compile kernels all the time for my laptop and Myth boxes. Is there a bit of a how-to for compiling the kernel for ARM and install it/replace the current kernel. It's be nice to find out how-to on how to make an update.zip to provide the install for everyone else as well.
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
Hi all,
I noticed that a new stable release of was released, BusyBox 1.23.2 - so I did download and compiled it in order to replace my old one.
If you want to try it on, I recommend you to put the binary file under the directory /system/xbin/ to keep it apart from the rest of your system files. Make sure that you have enabled the read and the execution permission flag (r-x).
I have included my .config file. Feel free to use and reconfigure it as you like.
The ARM cross compiler I have used is the recommended one on the BusyBox FAQ and you can download it http://landley.net/aboriginal/downloads/binaries/.
Good luck!
Note: I cannot guarantee its functionality on your device, it seems to work on my LG G3 D855.
Hey k02a,
thanks! I was looking for that, and installed it over the custom install feature and works flawless.
But there is one more thing, and maybe you can help me. I am looking for a tar version for android
that supports the --H ustar option like the linux one. To create odin packages within the phone.
I cannot find anything usefull for this. Any Idea? Maybe cross compile?
Cheers
NewBit
Good to hear that the binary worked on your device too!
Regarding the lack of flags and options in BuxyBox, I assume the developers have made a trade-off between functionality and binary size. - and in your case, the need for supporting the -H ustar format (e.g. for making Samsung/Odin images) have obviously not been considered.
Anyway, to get around this problem, I looked at my LG G3:s tar binary and discovered that it obviously supports the ustar format. I have included this file and hopefully you are able to use it as well. I hope this will help you a bit.
Kind regards,
k02a
Code:
[email protected]:/ $ /system/bin/tar --version
/system/bin/tar --version
tar (GNU tar) 1.16
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software. You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
...and this:
Code:
[email protected]:/ $ /system/bin/tar --help
...
Archive format selection:
-H, --format=FORMAT create archive of the given format
FORMAT is one of the following:
gnu GNU tar 1.13.x format
oldgnu GNU format as per tar <= 1.12
pax POSIX 1003.1-2001 (pax) format
posix same as pax
ustar POSIX 1003.1-1988 (ustar) format
...
Here is the MD5 hash sum:
Code:
[email protected]:/ $ busybox md5sum /system/bin/tar
busybox md5sum /system/bin/tar
d19775629f7f966e65bf1de7e2f695cf /system/bin/tar
Some kind of integrity verification in Linux (Slackware 14.1).
Code:
bash-4.3$ file tar; md5sum tar tar.zip
tar: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
d19775629f7f966e65bf1de7e2f695cf tar
e72aefb1060bc70725a1e2e0d432c9e0 tar.zip
Bamn, it's done! Thank you so much. It works great, this is exactly i was heading for! I own you a favour!
Btw: I have a Samsung Rugby Pro I547C with Android 4.1.2 and CWR.
Cheers
NewBit
I'm just glad to be of some help.
Take care
k02a
k02a said:
Hi all,
I noticed that a new stable release of was released, BusyBox 1.23.2 - so I did download and compiled it in order to replace my old one.
If you want to try it on, I recommend you to put the binary file under the directory /system/xbin/ to keep it apart from the rest of your system files. Make sure that you have enabled the read and the execution permission flag (r-x).
I have included my .config file. Feel free to use and reconfigure it as you like.
The ARM cross compiler I have used is the recommended one on the BusyBox FAQ and you can download it http://landley.net/aboriginal/downloads/binaries/.
Good luck!
Note: I cannot guarantee its functionality on your device, it seems to work on my LG G3 D855.
Click to expand...
Click to collapse
Im on samsung galaxy s4 i9500, i want to update my rom with this, can you provide a flashable zip? Or tell me how to replace this with my currently busybox?
HAYLCION said:
Im on samsung galaxy s4 i9500, i want to update my rom with this, can you provide a flashable zip? Or tell me how to replace this with my currently busybox?
Click to expand...
Click to collapse
I made one and it works for the I547, but on my S3 it wasn able to install over TWRP.
Maybe you can send me a working zip file for your S4 and I will mod it for you with the busybox bins.
Cheers
NewBit
newbit said:
I made one and it works for the I547, but on my S3 it wasn able to install over TWRP.
Maybe you can send me a working zip file for your S4 and I will mod it for you with the busybox bins.
Cheers
NewBit
Click to expand...
Click to collapse
Thnks , sorry what should i send you? You mean a busybox installer pakage?
HAYLCION said:
Thnks , sorry what should i send you? You mean a busybox installer pakage?
Click to expand...
Click to collapse
Nooo, the busybox installer pakage is actucally that what you wanted!?
I ment a working update zip for whatever, but known as runable. So I could just add the code
for install the busybox binary. Anyway, I guess you want root anyway!? So i've just updated
the Chainfire UPDATE-SuperSU-v2.46.zip, which is very universal, with the busybox_1.23.2_k02a version.
It worked on my S3 GT-I9300. So give it shot and me a feedback.
How do you proof if busybox is proper installed?
newbit said:
Nooo, the busybox installer pakage is actucally that what you wanted!?
I ment a working update zip for whatever, but known as runable. So I could just add the code
for install the busybox binary. Anyway, I guess you want root anyway!? So i've just updated
the Chainfire UPDATE-SuperSU-v2.46.zip, which is very universal, with the busybox_1.23.2_k02a version.
It worked on my S3 GT-I9300. So give it shot and me a feedback.
How do you proof if busybox is proper installed?
Click to expand...
Click to collapse
Seems goot , thanks
Great, you already seemed to solve it even before I logged in! :good:
newbit said:
How do you proof if busybox is proper installed?
Click to expand...
Click to collapse
Via Terminal Emulator or on ADB, you can type "busybox" after you got superuser's permissions and check the version.
@k02a Does this busybox support x86 intel device?
@k02a i rooted my lenovo a7000 today. busybox installer shows busybox 1.21.1-jb installed in /sbin. so do i need to install busybox 1.23.2 and where to install? /system/xbin? and if yes then do i need to uninstall older one from /sbin?
NOT SYSTEMLESS!
This writes to system, so systemless master race stay away.
Someone wanna make a Magisk version?
Instructions:
0. Download zip below and place inside internal storage.
1. Boot to TWRP.
2. Mount>System
3. Flash zip
4. Boot to Android and open a terminal emulator
5. Run dnscrypt enable. You probably have to do this every reboot.
Changing resolver:
Edit /system/etc/init.d/99dnscrypt. There's a line RESOLVER_NAME, change it to a suitable one from here under Name. I suggest you ping every server geographically nearby and go with the lowest ping.
Changing DNS server:
On Nexus 5X at least, use a Terminal Emulator and run
Code:
setprop net.dns1 127.0.0.1:53
Self-compile guide:
Requirements:
Linux computer (x86_64)
Android NDK (r12b is the newest so far, get the 64-bit one)
libsodium
dnscrypt-proxy
Here's how I did it:
1. Extract the NDK (unzip android-ndk-rXXb.zip )
2. Run
Code:
export ANDROID_NDK_HOME=<NDK Location>
3. Extract libsodium and dnscrypt-proxy.
4. Enter the folder of libsodium/dist-build, then edit android-build.sh such that NDK_PLATFORM:-android-16 becomes NDK_PLATFORM:-android-24. Then modify android-armv8-a.sh and add
Code:
-mtune=cortex-a57.cortex-a53 -mcpu=cortex-a57.cortex-a53
to the end of CFLAGS.
5. Return to libsodium root folder (cd ..) and do ./autogen.sh then ./dist-build/android-armv8-a.sh. When the script finishes it will tell you where the output is.
6. (Optional) Run android-toolchain-armv8-a/aarch64-linux-android/bin/strip on the output .so (typically in libsodium-android-armv8-a/lib/libsodium.so)
7. Now we do
Code:
export SODIUM_ANDROID_PREFIX=<libsodium output>
8. Enter the folder of dnscrypt, do the same modifications to dnscrypt's dist-builds. Again, do ./autogen.sh and ./dist-build/android-armv8-a.sh.
9. Now you have a fresh compilation of AArch64 dnscrypt-proxy!
It's usually dnscrypt-proxy-android-armv8-a.zip
10. Finally, we need to edit the zip file and rename the /system/lib folder to lib64, and change references in updater-script and /system/addon.d/75-dnscrypt.sh.
11. (Optional) Add --ephemeral-keys to 99dnscrypt for extra security.
Credits:
qwerty12 for the basic instructions
Changelog:
02/19: Updated libsodium (1.0.8->master) and dnscrypt-proxy(01/27 master->master)
03/17: Pulled freshest code from masters, compiled with NDK r11b and platform android-23
09/26: Latest stable branch of libsodium and master of dnscrypt. Compilation target now android-24. Compiled with NDK r12b
Changes to both dnscrypt-proxy and libsodium:
dist-build/android-build.sh:
Code:
NDK_PLATFORM:-android-16 to NDK_PLATFORM:-android-24
dist-build/android-arm-v8-a.sh:
Code:
Appended:
-mtune=cortex-a57.cortex-a53 -mcpu=cortex-a57.cortex-a53
to end of CFLAGS
Why not just release the compiled binaries ? would safe others with tinkering compiling it
Flashable zip
DragonHunt3r said:
Why not just release the compiled binaries ? would safe others with tinkering compiling it
Click to expand...
Click to collapse
Uploaded. I just thought most people would be more comfortable compiling their own code rather than trust a stranger. I still don't know how to fix the updater script though, it's the default one for now.
aschere said:
Uploaded. I just thought most people would be more comfortable compiling their own code rather than trust a stranger. I still don't know how to fix the updater script though, it's the default one for now.
Click to expand...
Click to collapse
That's true, but at the other side we trust random flashable zips for roms, mods etc from XDA
Thanks for the upload will take a look
Edit: well it works but in DNSManager for example it shows greyed out "Enable DnsCrypt"
dnsleaktest.com shows dnscrypt works though
DragonHunt3r said:
That's true, but at the other side we trust random flashable zips for roms, mods etc from XDA
Thanks for the upload will take a look
Edit: well it works but in DNSManager for example it shows greyed out "Enable DnsCrypt"
dnsleaktest.com shows dnscrypt works though
Click to expand...
Click to collapse
Shows up OK in my device.
So can I just flash the zip and use dns manager? nothing else?
---------- Post added at 03:25 AM ---------- Previous post was at 03:17 AM ----------
Will this work with a non 64 bit snapdragon 805
gangrenius said:
So can I just flash the zip and use dns manager? nothing else?
---------- Post added at 03:25 AM ---------- Previous post was at 03:17 AM ----------
Will this work with a non 64 bit snapdragon 805
Click to expand...
Click to collapse
This works only on 64-bit devices. For 32-bit devices, a download is provided here.
Yes, this is a flashable zip. However, DNS needs to be changed manually such as through DNS Manager because iptables doesn't entirely work.
Any major changes with 4/6? Thanks for updating this BTW.
th3g1z said:
Any major changes with 4/6? Thanks for updating this BTW.
Click to expand...
Click to collapse
It's all commits from 03/17 to 04/06.
Installed the zip successfully, when in terminal emulator, its not working, pls help!:crying:
Using rooted Lenovo A7000
Here's the full text directly copied from terminal emulator:
[email protected]:/ $ dnscrypt enable
Enabling dnscrypt-proxy...
iptables v1.4.20: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.4.20: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
[INFO] - [cs-uswest] does not support DNS Security Extensions
[INFO] + Namecoin domains can be resolved
[INFO] + Provider supposedly doesn't keep logs
[NOTICE] Starting dnscrypt-proxy 1.6.1
[INFO] Generating a new session key pair
[INFO] Done
[INFO] Server certificate #808464433 received
[INFO] This certificate is valid
[INFO] Chosen certificate #808464433 is valid from [2015-11-05] to [2016-11-04]
[INFO] Server key fingerprint is 881A:AED0:0427:BAF0:47D6:BDFA:6161A38:F019:571C:9BD2:A083:4A5F:C938:7E5D:8434
iptables v1.4.20: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
Done
[email protected]:/ $
kuchienkz said:
Installed the zip successfully, when in terminal emulator, its not working, pls help!:crying:
Using rooted Lenovo A7000
Here's the full text directly copied from terminal emulator:
[email protected]:/ $ dnscrypt enable
Enabling dnscrypt-proxy...
iptables v1.4.20: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.4.20: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.4.20: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
Done
[email protected]:/ $
Click to expand...
Click to collapse
Did you read the error you got? You have to be root. Try running 'su' before 'dnscrypt enable'
aschere said:
Did you read the error you got? You have to be root. Try running 'su' before 'dnscrypt enable'
Click to expand...
Click to collapse
Lol, i would not post my problem here if that could solve my problem :v
Already tried that several times. Still gives the same error.
kuchienkz said:
Lol, i would not post my problem here if that could solve my problem :v
Already tried that several times. Still gives the same error.
Click to expand...
Click to collapse
Can you post what version of Android, what phone?
aschere said:
Can you post what version of Android, what phone?
Click to expand...
Click to collapse
Android Version: 5.0.2
Lenovo A7000 : Phone Spec
kuchienkz said:
Android Version: 5.0.2
Lenovo A7000 : Phone Spec
Click to expand...
Click to collapse
Hmmm... I can't really think of anything other than the root: are you sure you rooted it? When you type su, do you switch to the root user?
aschere said:
Hmmm... I can't really think of anything other than the root: are you sure you rooted it? When you type su, do you switch to the root user?
Click to expand...
Click to collapse
Ah nevermind, i just reinstalled my phone with stock ROM, then rooted it. Now it works. :good:
If you curious about last rom, it is MIUI 7
Thank you so much for your help :victory:
Btw now that i understand how to run it. But as u said that i have to run it on every boot. Is there a way to run it automatically? Actually, im quite new to Terminal Emulator
kuchienkz said:
Ah nevermind, i just reinstalled my phone with stock ROM, then rooted it. Now it works. :good:
If you curious about last rom, it is MIUI 7
Thank you so much for your help :victory:
Btw now that i understand how to run it. But as u said that i have to run it on every boot. Is there a way to run it automatically? Actually, im quite new to Terminal Emulator
Click to expand...
Click to collapse
Good to hear that!
For automatic execution, you can create a script in /system/su.d or /system/addon.d I guess.
Ah actually, it should be in /system/etc/init.d
aschere said:
Ah actually, it should be in /system/etc/init.d
Click to expand...
Click to collapse
And.... how to make that script?
Im seriously beginner here
I dont have any idea what kind of script it is and what language it uses.
Maybe you can give me link to a site where i could learn to make one
kuchienkz said:
And.... how to make that script?
Im seriously beginner here
I dont have any idea what kind of script it is and what language it uses.
Maybe you can give me link to a site where i could learn to make one
Click to expand...
Click to collapse
Actually, the script should already be in there. See this.