@android:/ $ export PATH=/data/local/bin:$PATH
@android:/ $ cd mnt/sdcard/ubuntu
@android:/mnt/sdcard/ubuntu $ su
@android:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
Error: Image file not found!(mnt/sdcard/ubuntu/ubuntu.img)
1|@android:/mnt/sdcard/ubuntu #
this is my error. i've tried many things, any suggestions?
the image file is there, and ive downloaded it again, checked permissions, it is the large image from the complete linux installer app.
now i did some other things, and have gotten the responce:
$ export PATH=/data/local/bin:$PATH
$ cd mnt/sdcard/ubuntu
$ su
Segmentation fault
$ sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
sh: can't open /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
$
i re- rooted my device and am now coming up with the original error message again.
so, i added a \ to before mnt and now it says:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cd /mnt/sdcard/Ubuntu
[email protected]:/mnt/sdcard/Ubuntu $ su
[email protected]:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/Ubuntu/ubuntu.img
Validating image checksum... /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh: line 74: /data/data/com.zpwebsites.linuxonandroid/files/busybox: Permission denied
FAILED!
Error: Checksum failed! The image is corrupted!
1|[email protected]:/mnt/sdcard/ubuntu #
so im going to download and add the large ubuntu file to the directory
same error: "dirname : not found"
I have the same error, "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found"
freewalk said:
I have the same error, "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found"
Click to expand...
Click to collapse
Use root explorer or es file explorer to check if
the folder exists. Also, running sh script should be written like this: sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
ireakhavok said:
@android:/ $ export PATH=/data/local/bin:$PATH
@android:/ $ cd mnt/sdcard/ubuntu
@android:/mnt/sdcard/ubuntu $ su
@android:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
Error: Image file not found!(mnt/sdcard/ubuntu/ubuntu.img)
1|@android:/mnt/sdcard/ubuntu #
this is my error. i've tried many things, any suggestions?
the image file is there, and ive downloaded it again, checked permissions, it is the large image from the complete linux installer app.
now i did some other things, and have gotten the responce:
$ export PATH=/data/local/bin:$PATH
$ cd mnt/sdcard/ubuntu
$ su
Segmentation fault
$ sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh mnt/sdcard/ubuntu/ubuntu.img
sh: can't open /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
$
i re- rooted my device and am now coming up with the original error message again.
so, i added a \ to before mnt and now it says:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cd /mnt/sdcard/Ubuntu
[email protected]:/mnt/sdcard/Ubuntu $ su
[email protected]:/mnt/sdcard/ubuntu # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /mnt/sdcard/Ubuntu/ubuntu.img
Validating image checksum... /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh: line 74: /data/data/com.zpwebsites.linuxonandroid/files/busybox: Permission denied
FAILED!
Error: Checksum failed! The image is corrupted!
1|[email protected]:/mnt/sdcard/ubuntu #
so im going to download and add the large ubuntu file to the directory
Click to expand...
Click to collapse
" $ su
Segmentation fault" This error prevents you from having real superuser. Try to reinstall the ROM without wiping data.
" Error: Image file not found!(mnt/sdcard/ubuntu/ubuntu.img)"
Make sure that the image really is there with root explorer or es file explorer.
" line 74: /data/data/com.zpwebsites.linuxonandroid/files/busybox: Permission denied"
It seems that the script is trying to use its own busybox. That is all I know from this issue.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Use root explorer or es file explorer to check if
the folder exists. Also, running sh script should be written like this: sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
The folder and the script exist, "…linuxonandroid/files/bootscript.sh". I have installed the app, "Complete Linux Installer", to my Galaxy Tab 10.1 (P7500). I have rooted my Galaxy Tab ("TAB"). The app also confirms that the path contains the target image (i.e. /mnt/sdcard/ubuntu/ubuntu.img).
However, when the app runs the bootscrip, there is an error message "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found". The code line is at below.
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Could you please kindly let me know what goes wrong? Thanks in advance.
freewalk said:
The folder and the script exist, "…linuxonandroid/files/bootscript.sh". I have installed the app, "Complete Linux Installer", to my Galaxy Tab 10.1 (P7500). I have rooted my Galaxy Tab ("TAB"). The app also confirms that the path contains the target image (i.e. /mnt/sdcard/ubuntu/ubuntu.img).
However, when the app runs the bootscrip, there is an error message "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found". The code line is at below.
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Could you please kindly let me know what goes wrong? Thanks in advance.
Click to expand...
Click to collapse
I can't test it in my tablet, because I'm not home. But when I get there I will test the app myself. You could try using the native Ubuntu from development section. Its kernel can dual boot ICS test 4.0.4.
Edit: worked for me. Here is the log
http://snipurl.com/24sad15
Remember that /mnt/sdcard is externalsd and /sdcard/ is internal memory.
Delete everything you downloaded and the app. Then redo everything, following the guide perfectly.
Sent from my GT-I9100 using xda app-developers app
Thanks and How to try native Ubuntu in Galaxy Tab?
julle131 said:
I can't test it in my tablet, because I'm not home. But when I get there I will test the app myself. You could try using the native Ubuntu from development section. Its kernel can dual boot ICS test 4.0.4.
Edit: worked for me. Here is the log
snipurl.com/24sad15
Remember that /mnt/sdcard is externalsd and /sdcard/ is internal memory.
Delete everything you downloaded and the app. Then redo everything, following the guide perfectly.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot. I shall try again.
One more thing. How to try the native Ubuntu?
freewalk said:
Thanks a lot. I shall try again.
One more thing. How to try the native Ubuntu?
Click to expand...
Click to collapse
Its like installing a custom ROM. There is a topic for it in development section. You put archos.ext4 to /data/local (or was it /mnt/storage? Just read from the topic.) Then flash kernel from the same topic. To return just flash stock ROM and reinstall custom ROM. It doesn't affect to sde.
Sent from my GT-I9100 using xda app-developers app
freewalk said:
The folder and the script exist, "…linuxonandroid/files/bootscript.sh". I have installed the app, "Complete Linux Installer", to my Galaxy Tab 10.1 (P7500). I have rooted my Galaxy Tab ("TAB"). The app also confirms that the path contains the target image (i.e. /mnt/sdcard/ubuntu/ubuntu.img).
However, when the app runs the bootscrip, there is an error message "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found". The code line is at below.
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Could you please kindly let me know what goes wrong? Thanks in advance.
Click to expand...
Click to collapse
I have the same issue, indeed that the 'dirname' can not be found.
the $PATH show the following 2 dirs '/system/bin:/system/xbin' and none of them contain 'dirname'.
might it be because I have rooted my galaxy note 2 N8000 with the stock image according method 1 on rootgalaxynote.com ?
rootgalaxynote.com galaxy-note-10-1-root/how-to-root-galaxy-note-10-1/
any help would be appreciated....
freewalk said:
"/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found".
export imgfile=$(dirname $0)/ubuntu.img # Default image file, another can be set by using an argument
Click to expand...
Click to collapse
C'mon folks, It's all there for you in the error message!
It breaks down like this ; dirname is a program the tells you the directory name of an executable file location, well in reality it probably just trims the value pass in looking the last / the print everything before that i.e calling
Code:
dirname /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh
will give an out put of
Code:
/data/data/com.zpwebsites.linuxonandroid/files
this is normally part of busybox. Is suspect however that whatever busybox binary it's attempting to use does has not been configured to include dirname or at the very least the symlink hasn't been created so it would need to be called with a busybox prefix , i.e
Code:
export imgfile=$([B]busybox dirname[/B] $0)/ubuntu.img
or just save the f*****g about and hardcore imgfile to the path of the image file, for example
Code:
export imgfile=/mnt/sdcard/ubuntu/ubuntu.img
or wherever you're ubuntu.img is located, should be that simple, If you run into further trouble post the full content of the /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh shell script. I suppose someone could tell the dev to add some sanity checking to his scripts if alot of people are running into this problem!
metacm said:
I have the same issue, indeed that the 'dirname' can not be found.
the $PATH show the following 2 dirs '/system/bin:/system/xbin' and none of them contain 'dirname'.
might it be because I have rooted my galaxy note 2 N8000 with the stock image according method 1 on rootgalaxynote.com ?
rootgalaxynote.com galaxy-note-10-1-root/how-to-root-galaxy-note-10-1/
any help would be appreciated....
Click to expand...
Click to collapse
already found the issue, busybox installation went wrong.... 'Busybox Installer' app didn't worked out, but luckly 'BusyBox free' did the work.
which version of busybox is installed
metacm said:
already found the issue, busybox installation went wrong.... 'Busybox Installer' app didn't worked out, but luckly 'BusyBox free' did the work.
Click to expand...
Click to collapse
can you tell which version of busybox is installed
same error
Hi all,
Sorry for my poor language...
I have same all of you dirname issue, bootscript.sh is in the path (tested with root explorer).
Can somebody tell me what is exactly this error "/data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh[29]: dirname : not found".
Because we can understand 2 thinks :
1-dirname not found bootscript.
2-Busybox not found dirname.
Thank for your help.
Related
I was trying to root my G2 using the method illustrated in this thread.
http://forum.xda-developers.com/showthread.php?t=928160
The problem is that after typing in the 4th line of code in the terminal emulator, Im getting an error saying
"/data/local/perm_root: not found"
DON_58 said:
I was trying to root my G2 using the method illustrated in this thread.
http://forum.xda-developers.com/showthread.php?t=928160
The problem is that after typing in the 4th line of code in the terminal emulator, Im getting an error saying
"/data/local/perm_root: not found"
Click to expand...
Click to collapse
If are you sure you ran this command right?
Code:
# cp /sdcard/root_files/perm_root /data/local/perm_root
because its saying the file is not in your data/local, also make sure that there is a folder on the root of your sd card named root_files and in it there is a file named perm_root.
Then re run this
Code:
$ su
# cp /sdcard/root_files/perm_root /data/local/perm_root
# chmod 777 /data/local/*
# /data/local/perm_root
Yeah but that wasn't the issue. I downloaded gfree and visionary individually and added each to the root of the sd. It wasn't until about the 10th time I reread the post that I realized that all the files I needed were bundled in a nice zip file at the bottom of the post.
Thanks for your input though.
So, for all of you guys down here that are Debian junkies, then you're gonna love this. I managed to get Ubuntu Karmic Koala on my G2 after a bit of messing around with adb. This is my first tutorial on xda-developers, so please tell me how I'm doing. Remember to hit the Thanks button at the bottom if you're satisfied
Code:
#Your warranty has been voided
#I am not the cause of any damage done to your device
#Should you accuse me, I will laugh at you
Reasons why you should follow this tutorial:
- It allows you to make use wide array of applications available in Debian/Ubuntu's repos.
- It doesn't overwrite the current Android operating system.
- It'll allow you to turn your G2, Desire Z, etc. into more than just a sub-par cellphone.
- If you're developing software/applications, this will give you the proper environment for you test them on, if you don't care for Virtualbox or don't have access to a computer at the current moment.
- This tutorial will make the best use of Android and Linux's open-source nature.
Please note that this DOES NOT replace Android nor is it a port of Ubuntu/Debian. Ubuntu/Debian support ARM EABI which is the underlying architecture of Android.
READ EVERYTHING BEFORE DOING ANYTHING. I KNOW IT'S LONG, I WROTE THIS TUTORIAL
For those of you that can't use, can't set it up, or don't care for adb, you can still get Ubuntu to work on your device using a Terminal Emulator app, but you're probably gonna be stuck at the command line. I haven't actually tried setting up the GUI using the Terminal, so I'm not 100% sure. Now, before I start the tutorial, you NEED to be rooted.
NOTE: Whenever you see a $ or a # sign, those are indicators for the next command. Please do not enter them as you're typing in the commands. The same goes for the "[email protected]:/#" sign.
Before we begin we will need the following:
On your phone, have the following installed and/or readily available
-androidVNC application
-Terminal Emulator app (use this to boot into Ubuntu shell)
-Busybox (preferably, the latest one. If you rooted your phone using the method on the xda wiki OR your custom ROM has it pre-installed, then continue)
- At least 2GB space free on your microSD card
- Loopdevice support for your ROM. I think Cyanogen and another kernel should do the trick.
On your computer have the following installed and/or on the desktop:
-Ubuntu Karmic Koala image. If you don't have it, download it from this link ->http://bit.ly/moghJ3
-adb installed and fully functioning on your computer
EDIT 4 June, 2011: For those of you having troubles getting the shell to boot up, I found an alternative bootubuntu file. Extract it and replace the one that comes with the image with this one http://bit.ly/j7zORF
Let's begin, shall we?
Step 1: Connect your phone to your computer. Make sure you have "USB Debugging" checked off in "Settings -> Applications -> Development", then mount your sd card.
Step 2: Transfer the extracted "ubuntu" folder to the root of your sd card [NOT IN ANY FOLDERS, JUST the sd card itself, for those of you who don't know]. It might take a few minutes, so you might wanna make yourself a little snack for the wait.
Step 3: When the file transfer is done, disable the USB connection, so we can make use of adb. This is where USB Debugging is CRUCIAL. Open up a command window/terminal, go to where adb is located and enter the following commands:
Code:
$ adb shell
$ cd /sdcard/ubuntu
# su
# sh ./ubuntu.sh
# bootubuntu
At this point, you've set up the Ubuntu shell, as indicated by the "[email protected]:/#" sign.
However, our shell is still incomplete. We're gonna need a GUI for actual usage. If you're fine with using the command line then stop here. If you want to give yourself a PC-like experience, then please continue. You might wanna connect to WiFi if you're in an area where your mobile data is inconsistent or restricted to an EDGE connection.
Step 4: With the command prompt/terminal window that contains your adb/ubuntu shell, let's continue entering some commands to get our GUI set up.
Code:
[email protected]:/# apt-get update
[email protected]:/# apt-get install tightvncserver
[email protected]:/# apt-get install lxde
[email protected]:/# export USER=root
[email protected]:/# vncserver -geometry 1024x800
After entering the last command, you'll be prompted to enter a password. It'll ask you to set up a second one, just press "n" then continue.
For the second and third commands, press "y" when prompted to then hit ENTER, so you can install the packages. The reason why we set the VNC server's resolution is because even though the G2/Dz's resolution is 800x480, a higher resolution will provide a better viewing experience. If you want it set up to your phone's resolution, then swap it with "800x480" to scale the server's resolution to your phone's screen size.
Step 5: Enter the following commands. After entering the first command, you'll notice there's no user indicator at the left side. DON'T PANIC. Just continue entering the following commands:
Code:
[email protected]:# cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
Then, press Ctrl+D twice and press enter. You'll be back at "[email protected]:/#" (Conversely, if you're on Mac OS or Linux, just press Ctrl+D once)
Step 6: Go to your phone, and open up the androidVNC app. We're gonna need this to view our desktop. set the nickname to "root" and enter the password you set earlier. Set the port to "5901" and press connect.
Step 7a: And bam! You've got your own cool GNOME desktop! (Though in my experience, it switches over to lxde after a few uses.) Now, we need to get the VNC app to open up every time we boot into our shell. We need to enter a few more commands (yeah I know, it's getting a bit tedious at this point.)
Code:
[email protected]:/# cat > front
export USER=root
cd /
rm -r -f tmp
mkdir tmp
cd /
vncserver -geometry 1024×800
Again, you can replace "1024x800" with any screen resolution you desire.
Step 7b: Enter just a few more commands [trust me, we're almost done ]
Code:
[email protected]:/# cat front /root/.bashrc > temp
[email protected]:/# cp temp /root/.bashrc
Step 8: To check that everything is working, enter the following commands in your command prompt/terminal window that contains our adb/ubuntu shell that I hope you kept open all this time.
Code:
[email protected]:/# exit
# bootubuntu
And you're done! Give yourself a round of applause and a pat on the back, because now you have Ubuntu Linux running alongside Android. Yay!!!!!!
To boot into your shell AFTER you're done, use the Terminal Emulator app to access your shell:
Code:
$ su
# bootubuntu
That's it, you're finished.
Now, I don't know why this happens, but after rebooting your phone, it'll take a few extra seconds for your devices to start up. I think it's because of all the files that are in the phone's internal memory. I'm not sure. Also, the VNC server might not open up after you're done with the tutorial. It's only a minor setback, you can still manually open it yourself which is in itself relatively quick.
When you're done with the tutorial, be sure to type in "exit" in the terminal and press enter for a clean kill of Ubuntu. Otherwise, you're gonna have to redo the entire procedure.
If you have any questions, please email me at [email protected]
FAQ
- I don't have adb, can I still follow this tutorial?
A: Yes you can. However, you're probably going to be stuck at Step 3 with the command line. You can still use the shell, but you won't have a GUI.
- Why does my phone show a black screen after rebooting?
A: It's probably because of all the modding that's a result of the commands we entered.
Don't worry, Your phone will boot up normally. However, if this goes on longer than usual, you might have to install a different ROM. I've tested it on CM7 (Stable and Nightly), Stock G2 ROM, Virtuous 1.0.2, Virtuous G-Lite 1.0.2, and their respective ROM bases with no problems.
- I get an error that won't let me boot into the Ubuntu shell. Help me!!!!!
A: Yeah, you probably either downloaded an incomplete image OR you entered an important command wrong. I suggest deleting the ubuntu image from your sdcard and then copy the image you extracted onto your sdcard. Then what you have to do is redo the entire tutorial.
Interesting...
Sent from my T-Mobile G2 using XDA Premium App
Spastic909 said:
Interesting...
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
What's interesting about this?
Edit: can't wait to try this!
Ouch. . .
It's my first tutorial. . .
I just want to know what he found interesting about this tutorial. No need to get so defensive over a comment some other guy made.
Sent from my T-Mobile G2 using XDA Premium App
Didn't mean any offense dude especially if you weren't trying to be rude. You know how the internet doesn't portray emotion very well in text. Just sounded snappy. Back on topic. Can't wait to try this!
Sent from my HTC Vision using XDA Premium App
I'm not much of a software junky, so what exactly would this do? It looks easy enough to accomplish, since most of it is done through terminal, but I kinda wanna know what this DOES xD
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
Didn't mean any offense dude especially if you weren't trying to be rude. You know how the internet doesn't portray emotion very well in text. Just sounded snappy. Back on topic. Can't wait to try this!
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Edit: Remember to hit that thanks button!
ohshootrawr said:
I'm not much of a software junky, so what exactly would this do? It looks easy enough to accomplish, since most of it is done through terminal, but I kinda wanna know what this DOES xD
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Well, Ubuntu is a distribution of the Debian family of Linux.
Essentially, you have access to the plethora of apps that exist in Ubuntu/Debian's repos, and it's also possible to use this shell as a test monkey for applications that you might be developing.
Any idea if this will work with the new Ubuntu 11.04? Though I do hate the new layout
boost3d23 said:
Any idea if this will work with the new Ubuntu 11.04? Though I do hate the new layout
Click to expand...
Click to collapse
in theory, yes if the image has been compiled properly. also, the new layout technically can get overwritten with lxde or whatever desktop environment you installed.
reserved for future use.
im getting some errors in terminal when trying to set this up, im running mexdroid v3 android 2.3.4
C:\push\tools>adb shell
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# su
su
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir: can't create directory '/data/local/mnt': File exists
←[H←[Jchmod: 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
←[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 AndroLinux.com ,G2Hacks.com and NexusOn
eHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
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
losetup: /dev/block/loop1: Device or resource busy
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
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
losetup: /dev/block/loop1: Device or resource busy
#
teh5abiking said:
Well, Ubuntu is a distribution of the Debian family of Linux.
Essentially, you have access to the plethora of apps that exist in Ubuntu/Debian's repos, and it's also possible to use this shell as a test monkey for applications that you might be developing.
Click to expand...
Click to collapse
Seriously? Mmm, okay. I'm gonna try it sometime this week ;D
Sent from my HTC Vision using XDA Premium App
strker45 said:
im getting some errors in terminal when trying to set this up, im running mexdroid v3 android 2.3.4
C:\push\tools>adb shell
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# su
su
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir: can't create directory '/data/local/mnt': File exists
←[H←[Jchmod: 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
←[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 AndroLinux.com ,G2Hacks.com and NexusOn
eHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
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
losetup: /dev/block/loop1: Device or resource busy
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
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
losetup: /dev/block/loop1: Device or resource busy
#
Click to expand...
Click to collapse
I had this issue aswell.
To solve it firts fix your permissions in Rom manager.
Then install busy box.
This should then allow you to install ubuntu. (atleast it did with me)
Hope this is some help to you
teh5abiking said:
What's interesting about this?
Click to expand...
Click to collapse
The post dude.. would you rather I said boring? Settle down
Do u know what interesting means? It means I am interested in this..didn't think you could mistake that but guess I was wrong
Sent from my T-Mobile G2 using XDA Premium App
Spastic909 said:
The post dude.. would you rather I said boring? Settle down
Do u know what interesting means? It means I am interested in this..didn't think you could mistake that but guess I was wrong
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
hey man, i just wanna know what you found interesting about the tutorial.
i wasn't trying to be3 a smart aleck.
I really don't know **** about linux except for the few times I've had to run it on a virtual machine for rooting certain phones or to check out a few programs. With linux installed on my phone,
does that mean that I would be able to run any linux based program? For example aircrack or something like it?
Edit: I basically want to know what the purpose of doing this would be. What it would enable me to do
* I'm just sayin......
gazlufc said:
I had this issue aswell.
To solve it firts fix your permissions in Rom manager.
Then install busy box.
This should then allow you to install ubuntu. (atleast it did with me)
Hope this is some help to you
Click to expand...
Click to collapse
installed newest version of busybox 1.19.0 and fixed permissions and still received the same errors :/
strker45 said:
installed newest version of busybox 1.19.0 and fixed permissions and still received the same errors :/
Click to expand...
Click to collapse
.
Create a backup of you current rom using Rom manager.
Then install a new rom from the developer section of the G2/Desire z
First install busybox.
Second fix permissions.
Third is reboot
open adb and now try the process this should now allow you to install ubuntu.
Has anybody got this working?
I've done some searching and a few people have said it works on the Play.
However:
Sent from my R800i using XDA
It works for me. It took me some time to get it working, but now it works. I tried several "ubuntu.img"s and "ubuntu.sh"s and I think I edited the ubuntu.sh that I'm using now and created some folders myself to be able to boot.
If I remember correctly, I used this app to download the files needed. The image that the app downloads is good because you can choose between Gnome and LXDE at startup. I'll post my ubuntu.sh file here so if the one from the app doesn't work and it's different from mine, try mine (it's attached)
All this was on the stock GB rom + kernel
I used the same app.
I tried your file:
Sent from my R800i using XDA
The screenshot isn't very good because it won't let me upload the full sized image. Incorrect filetype or something.
Sent from my R800i using XDA
$ export PATH=/data/local/bin:$PATH
$ su
# cd sdcard
# cd ubuntu
# sh ubuntu.sh
cut: not found
[: not found
[: not found
mknod: /dev/block/loop255: File exists
losetup: not found
mount: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
mount: mounting /sdcard/external_sd on /data/local/mnt/external_sd failed: No such file or directory
net.ipv4.ip_forward = 1
ubuntu.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
ubuntu.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
ubuntu.sh: cannot create /data/local/mnt/etc/hosts: directory nonexistent
Ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
chroot: can't execute '/root/init.sh': No such file or directory
Shutting down Ubuntu ARM
failed.
failed.
failed.
failed.
failed.
failed.
losetup: not found
# su
# sh ubuntu.sh
cut: not found
[: not found
mkdir failed for /data/local/mnt, File exists
[: not found
mknod: /dev/block/loop255: File exists
losetup: not found
mount: Invalid argument
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
mount: mounting /sdcard/external_sd on /data/local/mnt/external_sd failed: No such file or directory
net.ipv4.ip_forward = 1
ubuntu.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
ubuntu.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
ubuntu.sh: cannot create /data/local/mnt/etc/hosts: directory nonexistent
Ubuntu is configured with SSH and VNC servers that can be accessed from the IP:
eth0: No such device
chroot: can't execute '/root/init.sh': No such file or directory
Shutting down Ubuntu ARM
failed.
failed.
failed.
failed.
failed.
failed.
losetup: not found
#
Sent from my R800i using XDA
Does this folder exist on your device?
/data/local/mnt
If not, try creating it yourself, reboot, and see if it works.
I was getting this error too. After that I created some folders that were missing and it worked, but I can't remember which...
EDIT: also check if /data/local/mnt/etc exists, and create that too
Mnt existed but etc didn't. I created etc and got the same errors.
Sent from my R800i using XDA
What kernel and rom do you use?
Sent from my R800i using XDA
Stock kernel and TrueAncestor 1.4.
Sent from my R800i using XDA
Can you post what you get when you run the script without root permissions (before typing su)? Also, try updating busybox, if you don't have the latest version... If you look at the first error, it cannot find the "cut" command...
Sent from my R800i using XDA
Same error without su.
Sent from my R800i using XDA
Do you have busybox installed? What happens if you run "busybox" (in the terminal)?
Sent from my R800i using XDA
leots said:
Do you have busybox installed? What happens if you run "busybox" (in the terminal)?
Sent from my R800i using XDA
Click to expand...
Click to collapse
This:
$ export PATH=/data/local/bin:$PATH
$ busybox
BusyBox v1.16.2androidfull (2010-08-01 14:57:25 EDT) multi-call binary.
Copyright (C) 1998-2009 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2.
See source distribution for full notice.
Usage: busybox [function] [arguments]...
or: function [arguments]...
BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as.
Currently defined functions:
[, [[, arp, ash, awk, basename, bbconfig,
brctl, bunzip2, bzcat, bzip2, cal, cat,
catv, chgrp, chmod, chown, chroot, cksum,
clear, cmp, cp, cpio, cut, date, dc, dd,
depmod, devmem, df, diff, dirname, dmesg,
dnsd, dos2unix, du, echo, ed, egrep, env,
expr, false, fdisk, fgrep, find, fold, free,
freeramdisk, fuser, getopt, grep, gunzip,
gzip, head, hexdump, id, ifconfig, insmod,
install, ip, kill, killall, killall5,
length, less, ln, losetup, ls, lsmod, lspci,
lsusb, lzop, lzopcat, md5sum, mkdir, mke2fs,
mkfifo, mkfs.ext2, mknod, mkswap, mktemp,
modprobe, more, mount, mountpoint, mv, nc,
netstat, nice, nohup, nslookup, ntpd, od,
patch, pgrep, pidof, ping, pkill, printenv,
printf, ps, pwd, rdev, readlink, realpath,
renice, reset, rm, rmdir, rmmod, route,
run-parts, sed, seq, setsid, sh, sha1sum,
sha256sum, sha512sum, sleep, sort, split,
stat, strings, stty, swapoff, swapon, sync,
sysctl, tac, tail, tar, tee, telnet, test,
tftp, time, top, touch, tr, traceroute,
true, tty, tune2fs, umount, uname, uniq,
unix2dos, unlzop, unzip, uptime, usleep,
uudecode, uuencode, vi, watch, wc, wget,
which, whoami, xargs, yes, zcat
$
Sent from my R800i using XDA
Updated Busybox and got new errors.
$ export PATH=/data/local/bin:$PATH
$ cd sdcard/ubuntu
$ su
# sh ubuntu.sh
Checking loop device... FOUND
losetup: /dev/block/loop255: No such file or directory
Error: Unable to attach image to loop device! (Image = ./ubuntu.img)
#
Sent from my R800i using XDA
The image unzipped in a folder so I moved it. It's now verifying the checksum.
I wonder what the next error will be...
Sent from my R800i using XDA
. .
. .
What happened? How did it extract? Tell me moar! Getting a new error is good. It seems there was a problem with your busybox installation
Were you using my script when you got this last error? (I'm asking because my script works for me, and I have stock Rom with doomkernel)
Sent from my R800i using XDA
I got it working.
The new error was just the image file being in a folder in the ubuntu folder, so I had to move it.
It must have been a BusyBox problem, it worked after updating it. I think I'm using the file you uploaded.
I've been messing around on it and it works ok. Can you get sound when playing music & videos? I'm assuming it might be possible cos there's a music player.
Also, I couldn't access my SD card, is there a way to do that?
Sent from my R800i using XDA
I don't think VNC supports sound :/ There might be another way though...
As for the SD card, it mounts on /sdcard (in the Ubuntu filesystem. If you select Gnome, you will see it on the desktop! I'd post two screenshots but they are in PNG format and it won't let me post them from my phone
EDIT: here are links to the screenshots on my Dropbox
http://db.tt/TxzhASdX
http://db.tt/Yyu8iwwN
Sent from my R800i using XDA
This guide was tested on my samsung galaxy [email protected] gt-B5330 and it worked.
WARNING: this can brick your phone, used on your own risk (both eyes wide open).
The idea behing can be ported on any phone that allows you to upload custom firmware (most samsungs with odin).
The idea is that you escalate to superuser by setting suid on /system/bin/toolbox executable.
By duing that you can run most of the unix commands on android as a superuser.
I is enought for you to copy su utility somewhere where there is not a nosuid option on mountpoint. and make it a suided executable then execute su and get the #.
It's all down hill from here.
I cannot verify for every ics rom out there, but it seems that now ics uses ext4 filesystem for the system partition.
I have made a script that inspects a stock rom firmware isolate the permissions for the toolbox executable and add to them SUID,SUIG.
After that it pachs the firmware back and you can flash it to your device and have a easylly rootable device. (I will post the stept to take to get a standard rooted device).
What you need:
a linux/gnu (it will not work with cygwin because we have to mount the ext4 partition).
simg2img utility (you can get it from xda site it is in ext4_utility packet).
su, busybox and superuser.apk binaries for android (you can take them from a rooting package).
heimdal (for linux) xor odin (for windows and if you cannot flash the firmware on your phone form linux).
I've put all untilities that are not standard into the tar.
just unpack and you have the universal-patch.sh to run over an .tar.md5 firware stock rom.
And post-firmwareUpdate.sh to run after you flash in order to make the root a standard android root.
This was not tested on any other phone (was tested only on GT-B5330) and do it on your own risk.
This rooting does not exploit any weakness (or flaw) in kernel or any thing, it just modifies the stock firmware to make it more flexible so it should be forward compatible with any version of android after ics.
I assume this would exclude HTC's since you meed to be s-off to flash a firmware. I would probably verify that and edit the title if necessary. Other than that, this looks like it could be helpful.
Help to understand the procedure
Hi ETTT,
first of all thanks for your job and effort in finding a solution to this issue.. it has been driving me crazy till now.. but thanx to you i see the light :good: I see it but i cannot really understand the procedure.. Could you please write a step by step explanation of what i need to do. (I am not what we could call a genius with linux).
Thanks in advance.
The First said:
Hi ETTT,
first of all thanks for your job and effort in finding a solution to this issue.. it has been driving me crazy till now.. but thanx to you i see the light :good: I see it but i cannot really understand the procedure.. Could you please write a step by step explanation of what i need to do. (I am not what we could call a genius with linux).
Thanks in advance.
Click to expand...
Click to collapse
If you are refering to the procedure that the script is doing here is the version of step by step (with-out the script):
http://forum.xda-developers.com/showthread.php?t=1956653
If you want to know the step by step with the script, here (I will not respond to more basic than this, like how to boot ubuntu and stuff.):
mkdir -p /tmp/foo
sudo mkdir /mnt
cd /tmp/foo
tar -xzf universal-patch.tar.gz
export PATH=./:$PATH
{get the firmware here and unzip it, it should have a file with .tar.md5 suffix}
./universal-patch.sh {the name of the firmware including the .tar.md5 suffix}
wait a while. you should have by the way about 10 times the size of the zip as free space.
if all goes well you will have a myfrm.tar.md5 rady for flashing.
flash the firmware, and after boot enable usb debuging, hook the phone to pc
sudo adb devices
./post-firmwareUpdate.sh
you should have a rooted phone.
you cannot go any more basic than that.
Have fun.
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
The file after qa
phyxar said:
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
Thanks for testing and input.
phyxar said:
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
XWALH3 i've produce from your universal-patch cannot being flashed to my phone, odin crash each time open those files
phyxar said:
XWALH3 i've produce from your universal-patch cannot being flashed to my phone, odin crash each time open those files
Click to expand...
Click to collapse
I'm puting the xdelta to the XWALH3
here are the md5s for the original and patched firmware.
cfe3ca545c4a2c8d453e02cd549655a1 B5330XWALH3_B5330OJVALH1_B5330XXLH4_HOME.tar.md5
624f63943bff54941e4042a39d7928f2 myfrm.tar.md5
Now I have some question in order to debug:
does the patching you have done yeild the same file as I have here?
have you use the same imput? (that's why I've give you the md5 of my imput).
Hey you have rooted you b5330 then do you notice any performance upgrade
Sent from my GT-B5330 using xda premium
Can I patch the firmware using windows??
Because I'm on win
I don't really understand using linux
Or can you make single click batch file that I can use it to patch my firmware???
I really appreciate it if someone provide it
Thanks
Sent from my GT-B5330 using xda app-developers app
byboyz said:
Can I patch the firmware using windows??
Because I'm on win
I don't really understand using linux
Or can you make single click batch file that I can use it to patch my firmware???
I really appreciate it if someone provide it
Thanks
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
I don't know windows that much to make a batch clone of the script. so you need linux.
But you can use a live cd (maybe from ubuntu) to run the script.
ETTT said:
I don't know windows that much to make a batch clone of the script. so you need linux.
But you can use a live cd (maybe from ubuntu) to run the script.
Click to expand...
Click to collapse
Thx for ur reply
How can I open XWALH3.patch that u give earlier??
Bcause I don't know anything about linux
Sent from my GT-B5330 using xda app-developers app
byboyz said:
Thx for ur reply
How can I open XWALH3.patch that u give earlier??
Bcause I don't know anything about linux
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
that patch is an xdelta patch.
There is an xdelta application on windows, don't know if it works, but it should work.
ETTT said:
If you are refering to the procedure that the script is doing here is the version of step by step (with-out the script):
http://forum.xda-developers.com/showthread.php?t=1956653
If you want to know the step by step with the script, here (I will not respond to more basic than this, like how to boot ubuntu and stuff.):
mkdir -p /tmp/foo
sudo mkdir /mnt
cd /tmp/foo
tar -xzf universal-patch.tar.gz
export PATH=./:$PATH
{get the firmware here and unzip it, it should have a file with .tar.md5 suffix}
./universal-patch.sh {the name of the firmware including the .tar.md5 suffix}
wait a while. you should have by the way about 10 times the size of the zip as free space.
if all goes well you will have a myfrm.tar.md5 rady for flashing.
flash the firmware, and after boot enable usb debuging, hook the phone to pc
sudo adb devices
./post-firmwareUpdate.sh
you should have a rooted phone.
you cannot go any more basic than that.
Have fun.
Click to expand...
Click to collapse
hi there, I'm stuck at last point/step: ./post-firmwareUpdate.sh
my terminal respond many error about busybox
the code like this:
2684 KB/s (91980 bytes in 0.033s)
4016 KB/s (996704 bytes in 0.242s)
4491 KB/s (1085140 bytes in 0.235s)
.//busybox: 1: .//busybox: Syntax error: word unexpected (expecting ")")
.//busybox: 1: .//busybox: Syntax error: word unexpected (expecting ")")
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nolonger with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
cd /system/xbin
for k in
nt/obb/su # copy the su binary to a place that can be sudoed <
/mnt/obb/su: cannot open for write: Permission denied
1|[email protected]:/ $ chown 0.0 /mnt/obb/su # modify the owner
Unable to chmod /mnt/obb/su: No such file or directory
10|[email protected]:/ $ chmod 6755 /mnt/obb/su # set SUID flag.
Unable to chmod /mnt/obb/su: No such file or directory
10|[email protected]:/ $ /mnt/obb/su # becomes root !!
/system/bin/sh: /mnt/obb/su: not found
# remount the system partition as readwrite. <
mount: Operation not permitted
/system/xbin/su #copy su in path <
/system/xbin/su: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory
10|[email protected]:/ $ chmod 6755 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory
# close the security hole (toolbox is nolonger with SUID) <
Unable to chmod /system/bin/toolbox: Read-only file system
er.apk of=/system/app/Superuser.apk # copy the superuser application <
/system/app/Superuser.apk: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
10|[email protected]:/ $ chmod 666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
10|[email protected]:/ $ #now this is done for busybox
10|[email protected]:/ $ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/ $ chmod 755 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/ $ cd /system/xbin
[email protected]:/system/xbin $ for k in
Click to expand...
Click to collapse
smhybrid said:
hi there, I'm stuck at last point/step: ./post-firmwareUpdate.sh
my terminal respond many error about busybox
the code like this:
Click to expand...
Click to collapse
Ok it seams busybox has a thing against ")" in comments.
Here is the script without comments, so try this.
ETTT said:
Ok it seams busybox has a thing against ")" in comments.
Here is the script without comments, so try this.
Click to expand...
Click to collapse
no good, it's still have same error...
maybe the problem is in busybox?
and i don't know why I'm unable to do chmod
smhybrid said:
no good, it's still have same error...
maybe the problem is in busybox?
and i don't know why I'm unable to do chmod
Click to expand...
Click to collapse
give this command:
adb shell ls -l /system/bin/toolbox
and let's see if the toolbox has suid.
ETTT said:
give this command:
adb shell ls -l /system/bin/toolbox
and let's see if the toolbox has suid.
Click to expand...
Click to collapse
what i get is
-rwxr-xr-x root shell 99068 2012-08-09 11:59 toolbox
how to get suid?
smhybrid said:
what i get is
-rwxr-xr-x root shell 99068 2012-08-09 11:59 toolbox
how to get suid?
Click to expand...
Click to collapse
have you flash the patched firmware?
ETTT said:
have you flash the patched firmware?
Click to expand...
Click to collapse
well, I've just do all of Your step, except this:
flash the firmware, and after boot enable usb debuging, hook the phone to pc
Click to expand...
Click to collapse
because I don't know the meaning of flash the firmware. How to do that?
So I skip that and hook the phone to pc with usb debugging enabled
i'm new at linux, but I want to try this method for my galaxy chat
At first I thought it was maybe because I didnt'nt have enough free space on my sd card so I made sure I had 3GB's free but I still got this when I clicked install:
[13:04:26] Updating configuration file ... done
[13:04:27] >>> begin: install
[13:04:27] Checking mount points ... done
[13:04:27] Checking installation path ... done
[13:04:27] Making new disk image (512 MB) ... fail
[13:04:27] <<< end: install
And this when I try to reconfigure:
[13:02:49] Updating configuration file ... done
[13:02:50] >>> begin: configure
[13:02:50] Mounting partitions:
[13:02:50] / ... fail
[13:02:50] <<< end: configure
When I check my root stutus I get this message:
Congratulations! You have root access!
Super User Application Status:
SuperSU application by Chainfire - version 2.36 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 71264 2014-11-30 16:22 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SM-T800 - Android 4.4.2 device by Root Checker Pro version 1.3.9 from joeykrim in the Android Market
Can anybody tell me why I get this fail message after clicking install?i
Please help
Thank You
AO!
Same issue
Im currently having the same issue with trying to install kali on my tab s. Have root and even sd formated to ext4 but still issues .
Check your SE(Linux) status on Settings / About Device. If it says Enforcing then this is the cause of the problem.
You need to change it to permissive, but you can't do it on a stock rom. You need a kernel with permissive mode
enable or a custom rom with a permissive kernel.
Good Luck
eupeso4 is wrong. You don't need a different kernel. There is an app called SELinuxModeChanger... It works charms
I've attached the app below.
soulcrusher101 said:
eupeso4 is wrong. You don't need a different kernel. There is an app called SELinuxModeChanger... It works charms
I've attached the app below.
Click to expand...
Click to collapse
Also, go to terminal emulator after this.
Code:
su
getenforce
If you get "Enforcing" as a response, it's FUBAR. you can try to run the command "setenforce 0" as su as a workaround but if the app didn't work, it won't likely work either.
Molikai1988 said:
Also, go to terminal emulator after this.
Code:
su
getenforce
If you get "Enforcing" as a response, it's FUBAR. you can try to run the command "setenforce 0" as su as a workaround but if the app didn't work, it won't likely work either.
Click to expand...
Click to collapse
Okay i got enforcing. my deviceis SC-04E thats is S4 (docomo). i want to set SE Linux to premissive tell me the solution
soulcrusher101 said:
eupeso4 is wrong. You don't need a different kernel. There is an app called SELinuxModeChanger... It works charms
I've attached the app below.
Click to expand...
Click to collapse
Doesn't work on stock kernels.
I tried everything. But it doesn't work even after changing the SELinux to permissive., But after searching a lot, I found a thread which said me to change the partition to ext2. I changed the partition and then it all worked like charm.., If you still have issues, follow the guide in this link from start to end-https://github.com/meefik/linuxdeploy/issues/183, This solved most of the issues I had..
Linux Deploy Mounting Partitions Fail
Bro problem solved by me..
Check out this video
https://youtu.be/n5opus76c3k