Develop Bugs

[Q] How to test if your phone has Root using Terminal and other Rooting question

Ok. I want to know how can you test that your phone is rooted. When I'm doing the XDA method of rooting my G2, I push all the needed files to my phone, and do the thing where Terminal Force closes and you open again after you had ran rage. Now I have the root shell in Terminal.
When I run command:
$ su
not found
($) is my command line, and (blanks) is what came back. ^^
Is it suppose to say "not found"? or is it suppose to say something else? I did exactly what I was suppose to do. It wasn't all that hard. Before I did the rage command, it was
$ su
Permission Denied
That seems normal. But after I supposedly temporarily root my phone, if I open ROM manager, it tells me that I need to root my phone. What tha truck? Am I missing something?
I run:
$ /data/local/gfree -f
{export PATH=/data/local/bin:$PATH
# # /data/local/gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.}
I run command:
$sync
# {sync}
I run command:
$ /data/local/tmp/root
# {/data/local/tmp/root
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#}
(mkdir failed for /system/xbin, File exists) This is where I think I'm messing up. The directions say it should state:
( mkdir: /system/xbin already exists)
See the difference? The directions doesn't say "Failed" while mines does.
In Hboot mode:
VISION PVT SHIP S-OFF
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
(How to navigate)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
So what's going on? Is my phone rooted or not? Why when I go to recovery, there's this triangle thing there? LoL!! It's the picture of the phone with a red triangle.
Thanks for any help. And sorry. I completely changed the question.

I think for some reason you are missing the su binary do you have the superuser
app installed? when you type su, superuser should ask you if you want to allow terminal to access root and after accepting it $ will change to # which means you can run a command as root .
and for the red triangle, it is the stock recovery if you want to install clockworkmod ,you can flash it true Rom manager

bahmanxda said:
I think for some reason you are missing the su binary do you have the superuser
app installed? when you type su, superuser should ask you if you want to allow terminal to access root and after accepting it $ will change to # which means you can run a command as root .
and for the red triangle, it is the stock recovery if you want to install clockworkmod ,you can flash it true Rom manager
Click to expand...
Click to collapse
I have the SuperUser app installed on my phone. But once I get the root shell (#) symbol in Terminal Emulator, if i type (su) I get the response " not found ". I don't know what it's saying. It sounds like you're right when you say the file (su) isn't moving to my phone.
Dugh!!

When you're in terminal and you get the root # symbol there's nothing more to do. Just open terminal, type 'su' and hit enter. The $ should change to a # and that means you are root. If you get anything but that then like the other guy said, your su binaries are probably messed up.
In that case you the search function on here and look for something like 'reinstall su binaries'. That should set you straight. Btw, make sure to use the binaries from the gfree method, their the most current as far as I know.
Sent from my HTC Vision using XDA App

Ok. Now I really don't know what's going on. When I reboot while holding Power, and Vol+Down, I can see that I have S-Off, but when I open ROM Manager or any other root app, it tells me I need to Root my phone. Am I missing something?
And yes, I did check the forums about when people had this same problem. They aren't helping. Somehow, people are getting their root after they find something out, but I don't know what's going on.
It seems that my phone isn't TempRooting.
I did notice that when I go to Super User app, it tells me that there is an update to the SU Binary, and it fails to update, so there is a zip file on my SD Card, and that I should start the phone in recovery mode and flash it.
Right now, it says Superuser v2.3.6.1 Is that the most current, or no?
The zip file name is su-2.3.1-bin-signed.zip
Thanks for any help. I don't know how I got S-Off, a Root Shell, and still don't have Temp Root to go to PermaRoot.

What instructions did you use to root? Sounds like you might have skipped a step. Also how did you temporarily root?

What do you have in /system/xbin ?
HTC Vision 1.8 OC, CM7 RC1==HAPPY!!

[Q] Is my phone "really" rooted?

Ok. Let me tell you all what I have.
I have:
S-Off
Root Shell (#)
Super User App
Yet when I open ROM manager, it tells me I need to root my phone. Excuse me!? Is my phone not rooted? Am I missing something?
I tried rooting using this method (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) and when I did the gfree_verify, everything came out ok. But when I reboot, I lose my root shell and when I type "su" it tells me permission denied. I have to do the temp root method every time to get the root shell (#).
And here's the thing. Even though I have the root shell (#), root apps, like ROM manager tell me my phone isn't rooted. I thought your phone was tempRooted or Rooted if you had the Root shell, S-Off and Super User app.
Am I missing something? The gfree_verify and what I think the problem is, is below.
()()()C:\Users\Izaya\Downloads\Phone ROMS\G2 Root_2011\Newest Root Method>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
OK
gfree verify_secu_flag returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
start ril-daemon()()()
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
(Right Here, it looks like this is a problem. I made sure that I pushed all my files to my phone, so making sure that I pushed them to the phone is not why. Please have a different response from that. Thanks *smiley face*
()()()# ./root_psn
./root_psn
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
./root_psn: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#()()()
It looks like this busybox thing is what's messing up or something. Is there someway I can format the /data/local/tmp folder so I can just redo everything, or when I push the same file, does it over right? Because I've been pushing multiple times only to come up with this same error multiple times.

No_Nickname90 said:
Ok. Let me tell you all what I have.
I have:
S-Off
Root Shell (#)
Super User App
Yet when I open ROM manager, it tells me I need to root my phone. Excuse me!? Is my phone not rooted? Am I missing something?
I tried rooting using this method (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) and when I did the gfree_verify, everything came out ok. But when I reboot, I lose my root shell and when I type "su" it tells me permission denied. I have to do the temp root method every time to get the root shell (#).
And here's the thing. Even though I have the root shell (#), root apps, like ROM manager tell me my phone isn't rooted. I thought your phone was tempRooted or Rooted if you had the Root shell, S-Off and Super User app.
Am I missing something? The gfree_verify and what I think the problem is, is below.
()()()C:\Users\Izaya\Downloads\Phone ROMS\G2 Root_2011\Newest Root Method>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
OK
gfree verify_secu_flag returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
start ril-daemon()()()
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
(Right Here, it looks like this is a problem. I made sure that I pushed all my files to my phone, so making sure that I pushed them to the phone is not why. Please have a different response from that. Thanks *smiley face*
()()()# ./root_psn
./root_psn
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
./root_psn: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#()()()
It looks like this busybox thing is what's messing up or something. Is there someway I can format the /data/local/tmp folder so I can just redo everything, or when I push the same file, does it over right? Because I've been pushing multiple times only to come up with this same error multiple times.
Click to expand...
Click to collapse
Strange; try downloading Titanium Backup from the Market, select "Problems" and download BusyBox and SuperUser from there.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
Strange; try downloading Titanium Backup from the Market, select "Problems" and download BusyBox and SuperUser from there.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I don't think I made myself clear. (I'm not being sarcastic. LoL!!) What I'm saying is, although I did the tempRoot method and have the Root shell, even after the TempRoot method, ROM manager still says "I need to Root my phone" even though I have the root shell. I don't think my phone is even tempRooting, and it looks like for some weird reason, busybox isn't getting pushed to the right places.
IDK what's going on. I have yet to see this problem else where. *sad face* I want the joys of a custom ROM.
Remember, I can't even PermaRoot, if I can't even TempRoot. Visionary didn't even TempRoot my phone. I would do the Visionary method, open Terminal Emulator, type "su" and get "permission denied" *sad face*
If someone ever tells me "permission denied" Ima hurt them. LoL!!

[Guide] How to get Karmic Koala on your HTC Vision

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.

Ubuntu on Android

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

[Q] linux deploy fails when mounting any of the linux OS's

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