Related
i read here
http://android-dls.com/wiki/index.php?title=Installing_Debian
you can run debian on android whit installing it.
and dont loos your droid
first isseu i got. chmodding the thing
download and push debian to /sdcard/debian
Code:
cd /sdcard/debian
su
chmod 4755 *
Code:
# su
su
su: access granted, courtesy of www.magicandroidapps.com
# chmod 4755 /sdcard/debian/*
chmod 4755 /sdcard/debian/*
Unable to chmod /sdcard/debian/bootdeb: Operation not permitted
#
than whitout bootdeb is chmodded i tried the installer.sh
Code:
cd /sdcard/debian as root
sh ./installer.sh
it just say's
Code:
# sh ./installer.sh
sh ./installer.sh
su: access granted, courtesy of www.magicandroidapps.com
#
so ?
Code:
# exit
Code:
# exit
exit
modprobe: not found
clear: not found
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
mkdir failed for /data/local/mnt, File exists
clear: not found
cp: not found
cp: not found
cp: not found
cp: not found
cp: not found
Unable to chmod bootdeb: Operation not permitted
clear: not found
VERSION 2.1
Custom Debian Bootloader is now installed! Quick huh?
This process does NO damage to your Android underlying OS!
Courtesy of http://www.androidfanatic.com
Installer by Mark Walker (ghostwalker)
To enter the Debian Linux console just type 'bootdeb'
PS: Be sure to run /scripts/onetime.sh as root from the shell after your FIRST
boot'.
??
Code:
# rm
rm
rm [-rR] <target>
availible
Code:
cp: not found
not availible.. Busybox availible only cp but the debian installer does not support the busybox way.
Code:
# busybox cp
busybox cp
BusyBox v1.8.1 (2007-11-14 10:11:37 EST) multi-call binary
Usage: cp [OPTION]... SOURCE DEST
enz.
Code:
#modprobe
not found
Code:
# busybox modprobe -h
busybox modprobe -h
modprobe: invalid option -- h
BusyBox v1.8.1 (2007-11-14 10:11:37 EST) multi-call bin
Usage: modprobe [-knqrsv] MODULE [symbol=value ...]
what to do to get this running?
Troubleshooting
Troubleshooting
If chmod 4755 * gives you an error stating that you do not have permissions, close Terminal Emulator and run su again, this time when SuperUserWhitelist asks for if you should give Terminal Emulator super user permissions hit yes instead of always.
If running installer.sh tells you that installer.sh could not be found, type su, followed by sh installer.sh
what whitelist?
I'm getting the same errors as u are. I belive the whitelist sugestion is only for those who have the app installed. The problem must lie somewhere else.
Have you done my busybox install (somewhere in this forum)? Looks like if you use stock ultities you don't have requirements...
bootdev.sh
keatonreckard said:
or you can simply rename the attached bootdev.sh.txt to bootdev.sh and put it in your debian folder and its good as new
Click to expand...
Click to collapse
these posts or were is that installer??
Yah I did have busybox installed.
superuser.apk
http://androidforums.com/all-things-root-behold-2/46137-how-root-apps-working-persistent-root.html
i think this is that superuser whitlist
I have fixed the bootdeb file, but im stuck at mounting the debian image...
Did anyone make any new progress on getting debian to work?
lgstoian said:
Did anyone make any new progress on getting debian to work?
Click to expand...
Click to collapse
I haven't made much progress...
But with Fyodor's 0.4.1 ROM modprobe works but i get this error when mounting the debian image:
ioctl: LOOP_SET_FD: Device or resource busy
Click to expand...
Click to collapse
And after that the rest ****s up...
Who can write a tutorial of Debian on TATTOO?
and when i get home to activate it, after buying a PNY 2gb card to try to root the new one, Verizons system crashes like 2 min before i am able to activate. I called customer service to try and activate it, and the lady asks for my number, she's like "that number isn't in our system sir" It's a new number, so i figured maybe i got it wrong, check my old incredible and yep, it's the right phone number. this goes on for a few minutes, with me giving her every number on my plan with her saying "nope, not in our system." I'm thinking wtf happened?!
she puts me on hold and comes back saying "sorry our system is down" duhhh. now i have a phone that I cannot activate
i'm in the ##778 menu trying to edit everything to match my phone right now, kinda frustrating!
will this work?
I know the PRL can't just be edited, I was trying and it froze the phone... maybe i can get by without it lol.
ok got my phone rooted before programming the phone. VZW is back up too.
now all i need now is a way to make root persistant, it doesn't seem to work for me
Code:
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
anything I did wrong?
generic.imitation said:
ok got my phone rooted before programming the phone. VZW is back up too.
now all i need now is a way to make root persistant, it doesn't seem to work for me
Code:
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
anything I did wrong?
Click to expand...
Click to collapse
You can only issue those commands from recovery root shell ATM.
rynosaur said:
You can only issue those commands from recovery root shell ATM.
Click to expand...
Click to collapse
I was in recovery.
I went thru the whole root process, was able to remove cityID, and got to the part where you make root persistant, but it keeps giving me that error.
I'm also curious about this... the same exact thing is happening to me. The whole process goes flawless until "ln - s /system/bin/su /system/xbin/su"
Hopefully someone has an idea... any help is appreciated.
*EDIT*
I'm not sure why this works, my guess is that perhaps system/xbin/ was being read and because of that it wouldn't allow me to write su to it (from system/bin/). Maybe I'm way off, but either way, this did fix my problem(s):
After following the instructions for rooting as far as possible, have the command "ln -s /system/bin/su /system/xbin/su" in cmd but don't press enter yet. On the phone, select "Reboot" and right after selecting reboot press enter on cmd. Press the up arrow key and press enter again (and repeat multiple times until the phone reboots). You may even want to make a .bat file for this.. If all went well, you saw something similar to:
Code:
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
ln: /system/xbin/su: Permission denied
ln: /system/xbin/su: Permission denied
ln: /system/xbin/su: Permission denied
ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
As you can see, right before the phone reboots it accepts the "
ln -s /system/bin/su /system/xbin/su" command. Unfortunately, you have to do the same
thing with the last command, "chmod 06755 /system/xbin/su". You have to get adb to recognize
your phone in recovery (again) by following one of the tutorials/10 min video tutorial and follow
the same steps as before.
Concise:
Follow your choice of tutorial for rooting phone up until "ln -s /system/bin/su /system/xbin/su"
Follow my terrible instructions for getting phone to accept the above command.
Again get adb to recognize your phone in recovery. (Including applying update.zip again).
Follow my terrible instructions for getting phone to accept the "chmod 06755 /system/xbin/su" command
Reboot.
I have the EXACT same problem... my entire process works up until that line and then it says permission denied... quite frustrating
is there any other way to get it to work without rebooting? The reason being i only get ADB to work about once every 50 years so once i reboot my chances of getting it back to do the final chmod line is another 3 day long process.. and also the remove command dosent work either it says no such file or directory found
There might be another way, hopefully somebody with more knowledge can help you out... in the worst case scenario you can try my above "method," but it's definitely a pain to accomplish.
i tried different method but i couldn't install Ubuntu or Debian in legend.........could someone post a tutorial..............????? pls
FOLLOW ME http://smartsreenath.blogspot.com/
smartsreenath said:
i tried different method but i couldn't install Ubuntu or Debian in legend.........could someone post a tutorial..............????? pls
Click to expand...
Click to collapse
I have tried too without sucess... Would be really cool if this would work on Legend too.
How do you go about even starting?
check this sites.......
http://www.saurik.com/id/10
http://nexusonehacks.net/
i hope some one will do a nice tutorial for us...........
FOLLOW ME http://smartsreenath.blogspot.com/
Does the Legend kernel have support for loop devices?
EDIT:
Well, I pulled the config file from my legend and the dumfuq OC kernel looks like it might do, but I'm not sure if it's commented out... Also, we need the loop devices in order to mount the Ubuntu images, so if support isn't there someone is gonna have to compile a few kernels that do have it...
EDIT:
Argh!!! I can't even download the sodding files needed, my internet keeps dropping out.
Buddy
Follow the instructions here
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
I had made a little change to the bootubuntu script , to make it work for legend
Download it from here
http://10stones.com/ubuntu/bootubuntu
I had tried it on stock rom , 2.1 update 2 , with temporary root access using the Universal And Root .
make sure you ran the "sh ./ubuntu.sh" command each time you change the bootubuntu.
Since mine was a temporary root i pushed the busybox binary to /data/ using
adb push busybox /data/
download the busybox binary from here
http://10stones.com/ubuntu/busybox
** For custom roms the busybox will be installed.
If you are facing any problems reply with the output of commands.
smartvinu said:
I had made a little change to the bootubuntu script , to make it work for legend
Download it from here
http://10stones.com/ubuntu/bootubuntu
Click to expand...
Click to collapse
how i can change the script ?
with sdk and cmd ?
tnx
Something ain't working here. The script fails (see below) then I get a forced reboot...
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Jrm: can't remove '/system/bin/fsrw': No such file or directory
rm: can't remove '/system/bin/bootubuntu': No such file or directory
rm: can't remove '/system/bin/unionfs': No such file or directory
unknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-ca
ll binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
cp: can't create '/system/bin/fsrw': Out of memory
cp: can't create '/system/bin/bootubuntu': Out of memory
cp: can't create '/system/bin/unionfs': Out of memory
cp: can't create '/system/bin/mountonly': Out of memory
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
chmod: su: No such file or directory
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
#
Click to expand...
Click to collapse
TheGrammarFreak said:
Something ain't working here. The script fails (see below) then I get a forced reboot...
Click to expand...
Click to collapse
what is the busybox version .. ?
I tried with 1.16.1
also check if you have enough phone memory
smartvinu said:
what is the busybox version .. ?
I tried with 1.16.1
also check if you have enough phone memory
Click to expand...
Click to collapse
Busybox 1.16.2
How much phone memory is enough?
I tried some more tinkering and now I just get an error about /bin/bash not existing whenever I try and run ubuntuboot...
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Junknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) mu
lti-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
chmod: su: No such file or directory
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
#
Click to expand...
Click to collapse
Can u try with the busybox i uploaded
smartvinu said:
Can u try with the busybox i uploaded
Click to expand...
Click to collapse
Still no joy...
C:\AndroidSDK\tools>adb push busybox /data/
1042 KB/s (1120536 bytes in 1.050s)
C:\AndroidSDK\tools>adb shell
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Junknown option -- /BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) mu
lti-call binary.
Usage: rm [OPTIONS] FILE...
Remove (unlink) FILEs
Options:
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
chmod: su: No such file or directory
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
#
Click to expand...
Click to collapse
This clearly throws a large number of errors, I just don't know why. The first command I issue is "su"
smartvinu said:
Can u try with the busybox i uploaded
Click to expand...
Click to collapse
why don't you check it after rooting your mobile? you already posted that your phone is hafly rooted and using stock rom........why don't you move it to azure rom and post custom bootubuntu [sorry my opinion]
FOLLOW ME http://smartsreenath.blogspot.com/
here is my log just check it smartvinu
E:\sdk\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
xxxxxxxxxxxxx device
E:\sdk\tools>adb shell
# su
su
# su
su
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: chdir(/lib/modules): No such file or directory
←[H←[Jrm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
mkdir failed for /data/local/mnt, File exists
←[H←[Jrm failed for -/system/bin/mountonly, No such file or directory
Unable to chmod bootubuntu: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
Setting localhost on /etc/hosts
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
[1] Illegal instruction chroot ${mnt} /b...
Shutting down Ubuntu
#
Click to expand...
Click to collapse
FOLLOW ME http://smartsreenath.blogspot.com/
HTC legend hvn't full R/W on system files ...
edit : sorry i'm french
smartsreenath said:
here is my log just check it smartvinu
FOLLOW ME http://smartsreenath.blogspot.com/
Click to expand...
Click to collapse
@smartsreenath
Can u check that after doing this steps the /data/local/ubuntu is mounted with the ubuntu.img
Umm, post missing??
I can run ubuntu with sucess and access it with vlc-viewer to localhost.
Do a "cat ubuntu.sh" and manually enter commands to see whish fail
and the same with bootubuntu.
Oops
I'll try again to make it work tomorrow
mmm my post was deleted ?!
I can't mount with indigo bean rom ...
But with anothersotckrom that work fine ^^
Hi,
For description, look here http://my-android-travels.blogspot.com/2012/02/android-build-system-ndk-toolchain.html and here http://my-android-travels.blogspot.com/2012/02/android-build-system-ndk-toolchain_21.html
https://docs.google.com/open?id=0B2qClbkV-4gpYWY5ZTE5NWYtYmU0ZC00MTAzLWIwN2MtNjQ4YTZmNzgyNTZj
Just place it on your sdcard, su, cd /, tar xzf /mnt/sdcard/ndk.tar.gz
When done, you find it in /data/local
I'm searching for people which wants to help me port in the first step the whole tools known as build-essential in debian. In a second step apt. If you are seeing yourself doing that, have the needed knowledge or the will to learn, please pm me
Have Fun
Ralph
I tried your NDK build on a 2.2 device (a Toshiba AC100) but, I run into a weird error when I try to run some of the executables:
Code:
/storage/home/t/data/local/bin $ file ./ar
./ar: symbolic link to `arm-linux-androideabi-ar'
/storage/home/t/data/local/bin $ ls -l ./arm-linux-androideabi-ar
-rwxr-xr-x 2 10035 10035 651482 Feb 20 20:47 ./arm-linux-androideabi-ar
/storage/home/t/data/local/bin $ file ./arm-linux-androideabi-ar
./arm-linux-androideabi-ar: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, BuildID[sha1]=0x5ee70e99463cef4692571cb07050ebf3819024ad, not stripped
/storage/home/t/data/local/bin $ strace ./arm-linux-androideabi-ar
execve("./arm-linux-androideabi-ar", ["./arm-linux-androideabi-ar"], [/* 16 vars */]) = -1 ENOENT (No such file or directory)
write(2, "strace: exec: No such file or dir"..., 40) = 40
exit(1) = ?
I cannot figure out why the command fails to run , and I'm hoping that you can help me out here,
try it on an android 4
also be sure that its located on an ext partition. put it into /data/local
Hi Ralph,
I'm running the binaries off an ext4 partition (and tried it from /data/local path(/data is ext4), as per the instructions). However, I don't have the luxury of using ICS. I'm stuck on FroYo as Toshiba no longer provides updates for my device , and doesn't release the sources either .
Could you give me some insight on why the binary will run on ICS, yet fail on FroYo?
Code:
/storage/home $ cd /data/local/bin/
/data/local/bin $ for i in arm-* ; do echo ------$i------- ; $i --help >/dev/null ; done
------arm-linux-androideabi-c++-------
------arm-linux-androideabi-cpp-------
------arm-linux-androideabi-g++-------
------arm-linux-androideabi-gcc-------
------arm-linux-androideabi-gcc-4.4.3-------
------arm-linux-androideabi-gcov-------
------arm-linux-androideabi-gdb-------
Segmentation fault
------arm-linux-androideabi-run-------
Segmentation fault
------arm-linux-androideabi-addr2line-------
sh: arm-linux-androideabi-addr2line: not found
------arm-linux-androideabi-ar-------
sh: arm-linux-androideabi-ar: not found
------arm-linux-androideabi-as-------
sh: arm-linux-androideabi-as: not found
------arm-linux-androideabi-gccbug-------
sh: arm-linux-androideabi-gccbug: not found
------arm-linux-androideabi-gprof-------
sh: arm-linux-androideabi-gprof: not found
------arm-linux-androideabi-ld-------
sh: arm-linux-androideabi-ld: not found
------arm-linux-androideabi-nm-------
sh: arm-linux-androideabi-nm: not found
------arm-linux-androideabi-objcopy-------
sh: arm-linux-androideabi-objcopy: not found
------arm-linux-androideabi-objdump-------
sh: arm-linux-androideabi-objdump: not found
------arm-linux-androideabi-ranlib-------
sh: arm-linux-androideabi-ranlib: not found
------arm-linux-androideabi-readelf-------
sh: arm-linux-androideabi-readelf: not found
------arm-linux-androideabi-size-------
sh: arm-linux-androideabi-size: not found
------arm-linux-androideabi-strings-------
sh: arm-linux-androideabi-strings: not found
------arm-linux-androideabi-strip-------
sh: arm-linux-androideabi-strip: not found
/data/local/bin $ mount |grep data
/dev/block/mmcblk3p5 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
I want to install busybox to other path, so i need to change $PATH
but $PATH define in init.environ.rc, but this file is in ramdisk and will be rewrote on every boot
Is there any way to change it without patch kernel? because i hate screen display that "kernel is not xxxxx, set warranty bit kernel"
I tried install-recovery.sh and install-recovery-2.sh. but it not work, it may not run at every boot so install-recovery-2.sh will not be loaded
if run install-recovery-2.sh manually, create dir, install busybox and soft link is worked but still can not change $PATH...
in init.rc file, what dos "seclabel u:r:flash_recovery:s0" mean?
Code:
service flash_recovery /system/etc/install-recovery.sh
class main
seclabel u:r:flash_recovery:s0
oneshot
install-recovery.sh
Code:
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/etc/install-recovery-2.sh
install-recovery-2.sh
Code:
#!/system/bin/sh
#Script for init Busybox on every boot by BZH
busybox_path=/system/etc
busybox_bin=busybox-armv7l-1221
busybox_install_path=/root/bin
$busybox_path/$busybox_bin mount -o rw,remount /
$busybox_path/$busybox_bin mkdir -p /root/bin
$busybox_path/$busybox_bin cp $busybox_path/$busybox_bin $busybox_install_path/
$busybox_path/$busybox_bin chmod -R 755 /root
$busybox_install_path/$busybox_bin --install -s $busybox_install_path/
$busybox_install_path/$busybox_bin ln -s $busybox_install_path/$busybox_bin /system/bin/busybox
$busybox_install_path/$busybox_bin ln -s $busybox_install_path/$busybox_bin /system/xbin/busybox
sync
$busybox_path/$busybox_bin mount -o ro,remount /
export PATH="/root/bin:$PATH"
up...