Okay I'm on the latest official miui nothing special
This is the error I get
$ export PATH=/data/local/bin:$PATH
$ su
# cd /sdcard/ubuntu
# sh ubuntu.sh
mkdir: can't create directory '/data/local/mnt': File exists
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Invalid argument
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or directory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: 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: ip 192.168.1.6 mask 255.255.255.0 flags [up broadcast running multicast]
chroot: can't execute '/root/init.sh': No such file or directory
Shutting down Ubuntu ARM
umount: can't umount /data/local/mnt/sdcard: No such file or directory
umount: can't umount /data/local/mnt/external_sd: No such file or directory
umount: can't umount /data/local/mnt/dev/pts: No such file or directory
umount: can't umount /data/local/mnt/proc: No such file or directory
umount: can't umount /data/local/mnt/sys: No such file or directory
umount: can't umount /data/local/mnt: Invalid argument
#
Please help I would love to get Ubuntu running the instructions I followed are from Ubuntu installer from the market I also tried Linux installer but it fails aswell
Sent from my HTC Glacier using Tapatalk
Anybody?
Sent from my HTC Glacier using Tapatalk
This is a Tutorial to install Ubuntu/Debian in any Android mobile.
* Installing Ubuntu or Debian Linux does not format your Android OS or change anything to your phone.
The Operating Systems run over the underlying Android OS which continues to function as normal
Choosing your Linux OS:
There are few things you must be aware of before installing Ubuntu/Debian on youe Android Phone
Ubuntu does not support earlier ARM CPUs like the ones used in the Motorola Cliq. Samsung Galaxy Fit (ARMv6), Samsung Galaxy Y, etc.
( Reason behind this is , Your Android OS Kernel must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it. )
You need at least an ARMv7 CPU like the kind found in the Motorola Droid, Samsung Galaxy S,HTC EVO 3D, Sony Experia Play, etc. most newer phones (Hummingbird, Snapdragon, Tegra2, etc.).So you can Install Ubuntu if you have ARMv7 or newer Processor.
If you have ARMV6 or any other moderate Processor don't be sad, because Debian supports the CPU on practically all Android devices, so if you prefer Debian, or you can't run Ubuntu, choose the Debian download link.
* If you're not sure what CPU your device has, look up your device on http://pdadb.net/, click the link under CPU, and read the line for "Supported Instruction Set(s)".
e.g. : My Phone which is a " Samsung Galaxy Fit" uses ARMV6 Instruction Sets.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Pre-Requirements:
Hardware Required:
an Android Phone
SD Card with more than 2GB of free Space
Android root environment:
Most important! Your Android device should be “rooted” because you need root access to run Ubuntu/Debian off your Android. If your device is not rooted you have to root your device.
Linux Operating System:
Download suitable OS from the following Link:
Ubuntu 11.04 (Natty Narwhal)
linux.ubuntu-natty.tar.bz2 Ubuntu 11.04 (Natty)
Ubuntu 11.10 Oneiric Ocelot
linux.ubuntu-oneiric.tar.bz2 Ubuntu 11.10 (Oneiric)
Debian 6.0 Squeeze
linux.debian-squeeze.tar.bz2 Debian 6.0 (Squeeze)
Click to expand...
Click to collapse
Applications Required:
BusyBox Installer
A terminal emulator like Better Terminal Emulator ( Recommended ) or Terminal Emulator.
Optional Apllications:
androidVNC
Or
ConnectBot
Click to expand...
Click to collapse
Procedure ----------------------------------------------->
Step 1:
(Mount the SD card on your computer.)
Extract the .tar.bz2 file you downloaded to your SD card. You should now have a folder named "linux" on the root of your card.
(Unmount the SD card.)
Open Busybox Installer, and install Busybox.
Open Better Terminal Emulator, and install Better Terminal Emulator.
Click to expand...
Click to collapse
Step 2:
Open your terminal emulator. (If using ConnectBot, connect to 'local', not 'ssh'.)
Run the following commands:
Code:
[B]su[/B]
( If Prompt for Superuser Request then allow )
Code:
cd /sdcard/linux
sh install.sh
If you don't see any errors, Linux is now installed.
Click to expand...
Click to collapse
Step 3:
Open your terminal emulator.
To start a chroot session
Code:
su
linux
To start the SSH server
Code:
su
linux ssh
You can then use ConnectBot (SSH: [email protected]) on your device, or any SSH client to connect to your device. See Login Information, below.
Click to expand...
Click to collapse
To start a VNC session
( Firest you need androidVNC to be installed , then type the following in terminal )
Click to expand...
Click to collapse
Code:
su
linux vnc
The first time you run VNC, it will prompt you to create a VNC password.
You can then use androidVNC (host: localhost port: 5901), or any VNC client to connect to your device.
Configure The VNC App as follows:
Note: The default desktop environment is icewm. If you wish to replace it, for example, with LXDE:
Run the following as root in Linux:
Code:
apt-get autoremove icewm- lxde+
Secure your Log in Password:
Please remember to change these passwords if you are planning on using the SSH server. Malicious people can do Very Bad things to your device if you don't.
There are two accounts included in the images:
root
Password:cheesecake
user
Password:dessert
Click to expand...
Click to collapse
After a successful connection to host you will be able to use Ubuntu / Debian in graphical interface just like in your PC ! It will keep your Android OS as it is and just run in the upper layer over it
These are some of the screen shots taken from my Samsung Galaxy Fit!
Click to expand...
Click to collapse
Linux vs Linux Terminal Emulator :
Terminal Emulator only Emulates Linux terminal, but after Linux Installation you can get full features; more than just the limited commands which runs on Android shell rather than Linux Shell.
Please Leave your Feedback and Queries below. Thank You
Verry Good
I'll test it now. Thanks for the tutorial
Did a long time ago...
even i managed to install Backtrack 5..
anyway nice post...
there is app call BotBrew...try it...
vs4vijay said:
Did a long time ago...
even i managed to install Backtrack 5..
anyway nice post...
there is app call BotBrew...try it...
Click to expand...
Click to collapse
Nice app Bro
Its very hard to get low end devices to perform flawlessly.
but who cares as long as u can work around it
great thanks
screenshots please.
Linux won't install
I love this forum. Over the last couple months I've been reading the forums and learning how to root my phone and install custom ROMs. For the last 10 years I've been using Linux on my computers and netbooks. I like Android because it's a mobile version of Linux, but I would like to get a full version of Linux running on my phone. I followed this thread many times with and cannot get Linux to install. I'll try to give the details:
I am running a rooted Samsung Galaxy S 4G T959V running the Valhalla-Black edition ROM (Gingerbread). I installed Busybox V1.20.0 and Busybox Installer V1.20 without uninstalling either. I have Android Terminal Emulator installed with su privileges. I keep getting the same mount error with all the 3 linux images shown on this thread. Here is what I got (the first error has to do with mount):
****************************************************************************************************************************************************
# sh install.sh
Remounting /system rw ...
mount: No such file or directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Installing scripts in /system/bin ...
cp: can't create '/system/bin/fsrw': File exists
Unable to chmod /system/bin/fsrw: Read-only file system
cp: can't create '/system/bin/linux': File exists
Unable to chmod /system/bin/linux: Read-only file system
Mounting the Linux image ...
Mounting: Prepwork ...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Mounting: Loopback mount ...
mknod: /dev/block/loop254: File exists
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished
*********************************************************************************************************************************
What am I missing here?
Marty
LinuxHippy said:
I love this forum. Over the last couple months I've been reading the forums and learning how to root my phone and install custom ROMs. For the last 10 years I've been using Linux on my computers and netbooks. I like Android because it's a mobile version of Linux, but I would like to get a full version of Linux running on my phone. I followed this thread many times with and cannot get Linux to install. I'll try to give the details:
I am running a rooted Samsung Galaxy S 4G T959V running the Valhalla-Black edition ROM (Gingerbread). I installed Busybox V1.20.0 and Busybox Installer V1.20 without uninstalling either. I have Android Terminal Emulator installed with su privileges. I keep getting the same mount error with all the 3 linux images shown on this thread. Here is what I got (the first error has to do with mount):
****************************************************************************************************************************************************
# sh install.sh
Remounting /system rw ...
mount: No such file or directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Installing scripts in /system/bin ...
cp: can't create '/system/bin/fsrw': File exists
Unable to chmod /system/bin/fsrw: Read-only file system
*********************************************************************************************************************************
What am I missing here?
Marty
Click to expand...
Click to collapse
I guess mount command in install.sh didnt work
Maybe you can edit it. to correct one, may be this or may be not
Code:
echo "Remounting /system rw ..."
#busybox mount -o remount,rw /system
sh $kit/scripts/fsrw
zcop said:
I guess mount command in install.sh didnt work
Maybe you can edit it. to correct one, may be this or may be not
Code:
echo "Remounting /system rw ..."
#busybox mount -o remount,rw /system
sh $kit/scripts/fsrw
Click to expand...
Click to collapse
I placed these lines in install.sh and deleted the 3 original lines that looked similar to it. I still got messages about mount, but these are a bit different:
# sh install.sh
Remounting /system rw ...
mount: No such file or directory
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Mounting: Loopback mount ...
mknod: /dev/block/loop254: File exists
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished
Full install.sh
Code:
sdcard=$(readlink -f /sdcard)
kit=$sdcard/linux
img=$kit/linux.img
mnt=/data/local/mnt
export bin=/system/bin
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=screen
export HOME=/root
echo "Remounting /system rw ..."
[COLOR="Red"]#Mount command
busybox mount -o remount,rw /system
#This script just mount system. We mount it above so we dont need it again.You can see [B]fsrw[/B] with notepad....
#sh $kit/scripts/fsrw[/COLOR]
echo "Installing scripts in $bin ..."
cd $kit/scripts
for file in *; do
cp $file $bin
chmod 755 $bin/$file
done
cd - > /dev/null
echo "Mounting the Linux image ..."
#mount the image
$bin/linux mount
echo "Customizing the image ..."
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
#echo "Setting localhost on /etc/hosts "
#echo "127.0.0.1 localhost" > $mnt/etc/hosts
echo " Installing root-scripts ..."
#install custom root-scripts in $mnt/root/scripts
if [ ! -d $mnt/root/scripts ]; then
mkdir $mnt/root/scripts
fi
chmod 755 $mnt/root/scripts
cp $kit/root-scripts/* $mnt/root/scripts
chmod 755 $mnt/root/scripts/*
echo "Install finished"
Try it again and let see what happen
same thing:
Remounting /system rw ...
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Mounting: Loopback mount ...
mknod: /dev/block/loop254: File exists
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished
so install.sh working. Now problem is in /script/linux
edit
Code:
mount -o dev,remount $sdcard
to
Code:
busybox mount -o dev,remount [COLOR="Red"]$sdcard[/COLOR]
it not work change $sdcard to /mnt/sdcard
zcop said:
so install.sh working. Now problem is in /script/linux
edit
Code:
mount -o dev,remount $sdcard
to
Code:
busybox mount -o dev,remount [COLOR="Red"]$sdcard[/COLOR]
it not work change $sdcard to /mnt/sdcard
Click to expand...
Click to collapse
It got a little further this time by adding this to /sdcard/linux/scripts/linux:
busybox mount -o dev,remount
this is what happened:
# sh install.sh
Remounting /system rw ...
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Mounting: Loopback mount ...
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished
hey guys.
Thanx to the author of this forum on debian on android. I had the same problem you see in the error logs above. the problem is between regular "mount" command and busybox "mount". you need to use the busybox mount. so I added the word busybox infront of every mount word in the script. eg. busybox mount -o , rw /system remount. the alternative is to delete the mount found on /system/bin so that the terminal will use the busybox one automatically on /system/xbin.
nice tutorial
Good article but...
I have some issues about installing it.I tried it with XXKPI 2.3.4 on my Fit but it only caused my phone to give me bunch of error codes on the terminal and my phone started to not dedecting sdcard and sometimes it doesnt mount on computer.I have SdCard issues.I have edited all the mount codes in fsrw,linux and install.sh (by typing a busybox like busybox mount -o)but still have problems.I have installed XXKPI in 4 Part inst. with Odin and wiped the device before and after the installation and after the Odin inst. i rooted it with UnlockRoot v 2.2.1 so it is rooted.Done a binary update on SU and installed BusyBox 1.9.3 because newer versions are incompatible with my phone.This is my last terminal session(all included)
Code:
$ su
# cd /sdcard/linux
# sh install.sh
Remounting /system rw ...
mount: mounting /dev/stl12 on rfs failed: No such file or directory
Installing scripts in /system/bin ...
Mounting the Linux image ...
Mounting: Prepwork ...
Mounting: Loopback mount ...
mount: Invalid argument
Mounting: Setting up chroot environment ...
mount: mounting /dev on /data/local/mnt/dev failed: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or directory
mount: mounting /proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting /sys on /data/local/mnt/sys failed: No such file or directory
mkdir failed for /data/local/mnt/media/sdcard, No such file or directory
mount: mounting /mnt/sdcard on /data/local/mnt/media/sdcard failed: No such file or directory
[ Done ]
Customizing the image ...
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
install.sh: cannot create /data/local/mnt/etc/resolv.conf: directory nonexistent
Installing root-scripts ...
mkdir failed for /data/local/mnt/root/scripts, No such file or directory
Unable to chmod /data/local/mnt/root/scripts: No such file or directory
cp: can't create '/data/local/mnt/root/scripts/ssh.sh': No such file or directory
cp: can't create '/data/local/mnt/root/scripts/vnc.sh': No such file or directory
Unable to chmod /data/local/mnt/root/scripts/*: No such file or directory
Install finished
#
So what can i do about it?I want to install Debian 6.0 so much and i am getting impatient about it.
Any help would be appreciated.
Sorry for my English if i have mistakes.
R: [ Tutorial ] How to Install Debian Linux on Your Samsung Galaxy Fit
Is possible install aircrack-ng airodump-ng and airmon-ng on ubuntu...
Sent from my GT-5670 using xda premium
can't install inside debian
I managed to install debian and in terminal mode, i cannot install anything, i get the error about "ldconfig" when installing xterm
dpkg: warning: 'ldconfig' not fount in PATH or not executable
the same with 'start-stop-daemon'
can you help me? i wish to install a terminal like xterm inside debian and some other app
Regards,
Works
Thanks
I was able to install this on my galaxy fit very smooth. Like your tutorials
Dwi Aulia Rahman Putra said:
screenshots please.
Click to expand...
Click to collapse
Screens have been given
hi all,
I am trying very hard to root my huawei mediapad but not getting success.
Following are my setup -
My device - Huawei MediaPad 7
OS - Android 4.0.3
I have enabled USB debugging mode
My PC is on Windows 7 Home Premium.
I following so many posts for rooting this device. I followed the following posts.
Link1
Link2
In link1, i downloaded the zip file and run the Install Root.cmd script. But it shows me following errors
Code:
failed on '/data/local/tmp' - Permission denied
link failed File exists
ÅÑαѺáúαπªáѼ (1/3)
/system/bin/sh: cannot create /data/local.prop: Permission denied
ÅÑαѺáúαπªáѼ (2/3)
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
sh: /system/xbin/install_bb: No such file or directory
rm failed for /system/xbin/install_bb, No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
ÅÑαѺáúαπªáѼ (3/3)
éßÑ ú«Γ«ó«!!!
Press any key to continue . . .
On Link2 - the download link does not work and shows error as follows
Code:
Oops! Google Chrome could not connect to depositfiles.com
Suggestions:
Access a cached copy of depositfiles.*com/*files/*9f8mfimjz
Try reloading: depositfiles.*com/*files/*9f8mfimjz
Search on Google:
Someone please help.
I would need help with this http://forum.xda-developers.com/showthread.php?t=1866675
When i am trying to run dualboot-rom-convert script there comes this error
[email protected]:~$ /home/juho/Lataukset/dualboot-rom-convert/convert.sh cm.zip
Dualboot Rom Converter
Converts GT-P31xx Roms
to run from external
SD card and dualboot.
mkdir: cannot create directory `tmp/': File exists
cp: cannot stat `cm.zip': No such file or directory
Extracting boot image...
unzip: cannot find or open tmp/cm.zip-dualboot.zip, tmp/cm.zip-dualboot.zip.zip or tmp/cm.zip-dualboot.zip.ZIP.
mkdir: cannot create directory `tmp/unpack': File exists
Unpacking boot image...
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 13: ./unpackbootimg: No such file or directory
mkdir: cannot create directory `tmp/unpack/ramdisk': File exists
cpio: premature end of archive
Modifiying boot image...
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 18: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 19: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 20: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 21: init.espresso.rc: No such file or directory
mv: cannot stat `init.espresso.rc.t': No such file or directory
Repacking boot image...
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 24: ./mkbootfs: No such file or directory
cat: tmp/unpack/boot.img-base: No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 25: ./mkbootimg: No such file or directory
cp: cannot stat `tmp/boot.img': No such file or directory
cp: cannot stat `patches/system/': No such file or directory
zip warning: name not matched: tmp/boot.img
zip error: Nothing to do! (tmp/cm.zip-dualboot.zip)
zip warning: name not matched: system/
zip error: Nothing to do! (try: zip -r cm.zip-dualboot.zip . -i system/)
Modifiying updater-script
unzip: cannot find or open tmp/cm.zip-dualboot.zip, tmp/cm.zip-dualboot.zip.zip or tmp/cm.zip-dualboot.zip.ZIP.
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 35: tmp/updater-script: No such file or directory
mv: cannot stat `tmp/updater-script.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 36: tmp/updater-script: No such file or directory
mv: cannot stat `tmp/updater-script.t': No such file or directory
/home/juho/Lataukset/dualboot-rom-convert/convert.sh: line 37: tmp/updater-script: No such file or directory
mv: cannot stat `tmp/updater-script.t': No such file or directory
Repacking updater-script...
mkdir: cannot create directory `tmp/META-INF': File exists
mkdir: cannot create directory `tmp/META-INF/com': File exists
mkdir: cannot create directory `tmp/META-INF/com/google': File exists
mkdir: cannot create directory `tmp/META-INF/com/google/android': File exists
mv: cannot stat `tmp/updater-script': No such file or directory
zip warning: name not matched: META-INF/com/google/android/updater-script
zip error: Nothing to do! (cm.zip-dualboot.zip)
cp: cannot stat `tmp/cm.zip-dualboot.zip': No such file or directory
Complete!
I have given executable permissions to: unpackbootimg,, mkbootfs, and whatever the last one is (I forgot the last file name).
Did you try running the script ad root?
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Did you try running the script ad root?
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
Yes, I tried
It looks like the script can't find the file. Try putting a "./' before "cm.zip".
Posted from my Galaxy Tab 2 with CM10.1
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
1. Install unpackbootimg
Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git clone command.
extract files
cd directory
make
now you will find unpackbootimg and mkbootimg in this directory
2. copy unpackbootimg and mkbootimg to /usr/bin
sudo cp unpackbootimg /usr/bin
sudo cp mkbootimg /usr/bin
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
3. Extracting boot.img from your device
What we need
1. A rooted phone
2. Enable Usb Debugging in Developer Mode
3. ADB command knowldge
connect your phone via usb cable ensure that usb debugging is enabled
open terminal and type adb devices
if it is showing your device’s serial no than we are ready to go
C. type
adb shell
su
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
please note this command may vary by device to device. What we are doing here we want to know partition scheme of your device.
note down block name of /boot partition
example it will be like boot -> /dev/block/mmcblk0p7
d. type this
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img
now boot.img succesfully transfered to your SD card Copy it to your Desktop
now path should be /home/user/Desktop/boot.img or similar but remeber path name alternatively you can type pwd in terminal to know this
creating device/Vendor-Name/Device-codename
cd to your working directory
Syntex: ./build/tools/device/mkvendor.sh Vendor-Name Device-CodeName ~/Path to your/boot.img
Example:
./build/tools/device/mkvendor.sh GIONEE GIONEE_WBL7511 ~/Desktop/boot.img
Now it will create following file in /device/Vender-Name/Device_CodeName
AndroidBoard.mk
cm.mk
recovery.fstab
AndroidProducts.mk
device_GIONEE_WBL7511.mk
system.prop
BoardConfig.mk
kernel
Note1: Please creater vendorsetup.mk file in this directory manualy. To use source build/envsetup.sh
Note2: Please double check BoardConfig.mk file and ensure every partition size is correct in this file. Also check recovery.fstab showing correct mount point
Note3: Here kernel is prebuilt kernel. If you want to compile kernel as well as download your kernel source in /kernel/Vender-Name/Device_CodeName dirtectory. You will find kernel related config in BoardConfig.mk
Please note it will not create vendorsetup.sh file and following Directory
1./vendor/Vender-Name/Device_CodeName
2. /kernel/Vender-Name/Device_CodeName
Wait for next post for more info
Thank You
Thank you very much for the tutorial I will try to do it
Enviado desde mi A7010a48 mediante Tapatalk
Also here http://azodik.com/how-to-create-device-tree-for-android-rom-building/
Are you ready with the post about creating the vendor tree?
thanks mate, but there's more than this, for example different flags for build for mtk device and different flags for qualcomm devices
Thank you for this great tut, but I have a noob error that I couldn't found "mkbootimg" and "unpackbootimg" in "/bootimg-tools-master" folder
But in "/bootimg-tools-master/mkbootimg" I found "bootimg.h, mkbootimg, mkbootimg.c, mkbootimg.o, unmkbootimg, unmkbootimg.c, unmkbootimg.o"
Also, I have read your note:
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
but I couldn't figure out what to do to check that
Additional info. : I am doing that to build a LineageOS Rom
Tree and API dependance
Amazing tutorial yet a small query - are the device (and vendor) trees android version dependant?
Could I use the boot.img of say Android 6.0 for building a 7.0 Nougat based ROM?
i am getting errors !
[/QUOTE][/QUOTE]
jai44 said:
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
1. Install unpackbootimg
Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git clone command.
extract files
cd directory
make
now you will find unpackbootimg and mkbootimg in this directory
2. copy unpackbootimg and mkbootimg to /usr/bin
sudo cp unpackbootimg /usr/bin
sudo cp mkbootimg /usr/bin
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
3. Extracting boot.img from your device
What we need
1. A rooted phone
2. Enable Usb Debugging in Developer Mode
3. ADB command knowldge
connect your phone via usb cable ensure that usb debugging is enabled
open terminal and type adb devices
if it is showing your device’s serial no than we are ready to go
C. type
adb shell
su
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
please note this command may vary by device to device. What we are doing here we want to know partition scheme of your device.
note down block name of /boot partition
example it will be like boot -> /dev/block/mmcblk0p7
d. type this
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img
now boot.img succesfully transfered to your SD card Copy it to your Desktop
now path should be /home/user/Desktop/boot.img or similar but remeber path name alternatively you can type pwd in terminal to know this
creating device/Vendor-Name/Device-codename
cd to your working directory
Syntex: ./build/tools/device/mkvendor.sh Vendor-Name Device-CodeName ~/Path to your/boot.img
Example:
./build/tools/device/mkvendor.sh GIONEE GIONEE_WBL7511 ~/Desktop/boot.img
Now it will create following file in /device/Vender-Name/Device_CodeName
AndroidBoard.mk
cm.mk
recovery.fstab
AndroidProducts.mk
device_GIONEE_WBL7511.mk
system.prop
BoardConfig.mk
kernel
Note1: Please creater vendorsetup.mk file in this directory manualy. To use source build/envsetup.sh
Note2: Please double check BoardConfig.mk file and ensure every partition size is correct in this file. Also check recovery.fstab showing correct mount point
Note3: Here kernel is prebuilt kernel. If you want to compile kernel as well as download your kernel source in /kernel/Vender-Name/Device_CodeName dirtectory. You will find kernel related config in BoardConfig.mk
Please note it will not create vendorsetup.sh file and following Directory
1./vendor/Vender-Name/Device_CodeName
2. /kernel/Vender-Name/Device_CodeName
Wait for next post for more info
Thank You
Click to expand...
Click to collapse
Adityas-Mac-Pro:android aditya$ . build/tools/device/mkvendor.sh htc m8et /Users/aditya/Desktop/boot.img
Arguments: htc m8et /Users/aditya/Desktop/boot.img
dirname: illegal option -- b
usage: dirname path
dirname: illegal option -- b
usage: dirname path
-bash: pushd: no other directory
-bash: popd: directory stack empty
Output will be in //device/htc/m8et
mkdir: //device/htc/m8et: Permission denied
mkdir: /tmp/aditya/bootimg: Permission denied
cp: /tmp/aditya/bootimg: No such file or directory
-bash: pushd: /tmp/aditya/bootimg: No such file or directory
error: could not load image 'boot.img'
mkdir: ramdisk: File exists
gunzip: can't stat: ../boot.img-ramdisk.gz (../boot.img-ramdisk.gz.gz): No such file or directory
0 blocks
cat: /tmp/aditya/bootimg/boot.img-base: No such file or directory
cat: /tmp/aditya/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/aditya/bootimg/boot.img-pagesize: No such file or directory
-bash: /tmp/aditya/bootimg/sedcommand: No such file or directory
cp: /tmp/aditya/bootimg/boot.img-zImage: No such file or directory
-bash: popd: directory stack empty
find: /Volumes/android/.DocumentRevisions-V100: Permission denied
find: /Volumes/android/.TemporaryItems: Permission denied
find: /Volumes/android/.Trashes: Permission denied
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/AndroidManifest: No such file or directory
-bash: //device/htc/m8et/AndroidManifest.tests: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/java_file: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/java_tests_file: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/layout: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/strings: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/FrameworkDatabase: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build_rule: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/target: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/tools_def: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/click_events: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/stylus.prop: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/temp.arg: No such file or directory
cat: /Volumes/android/external/clang/test/CXX/temp/temp.arg/temp.arg.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/index.html: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/testResults.php: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/customTest.xml: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/testing.properties: No such file or directory
-bash: //device/htc/m8et/plugin.xml: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/Common.pl: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build-local.properties: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
cat: /Volumes/android/external/icu/icu4j/eclipse-build/features.template: Is a directory
-bash: //device/htc/m8et/features: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/plugins: No such file or directory
cat: /Volumes/android/external/icu/icu4j/eclipse-build/plugins.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/Version.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/string.view: No such file or directory
cat: /Volumes/android/external/libcxx/test/std/experimental/string.view/string.view.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/string.view: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
cat: /Volumes/android/external/libcxx/test/std/strings/string.view/string.view.template: Is a directory
-bash: //device/htc/m8et/NativeLibraries: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_event_cpp: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_event_h: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_eventhandler_h: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ar_eventhandlerfile_h: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/knobs: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/README: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/compile_commands.json: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/DriverRS.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/DriverView.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ACTIVITY.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/DriverRS.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ACTIVITY.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/ACTIVITY.java: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/jmxremote.password: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/snmp.acl: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/jmxremote.password: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/snmp.acl: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/string.view: No such file or directory
cat: /Volumes/android/prebuilts/ndk/r13/sources/cxx-stl/llvm-libc++/test/std/experimental/string.view/string.view.template: Is a directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/revision: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/AndroidManifest: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/activity: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/java_file: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/launcher_intent_filter: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/layout: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/preference_intent_filter: No such file or directory
-bash: //device/htc/m8et/string: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/strings: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/test_instrumentation: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/test_uses-library: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/uses-sdk: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/prefs: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/build_gradle: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/uibuild: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
-bash: //device/htc/m8et/asan.options.off: No such file or directory
sed: /tmp/aditya/bootimg/sedcommand: No such file or directory
mv: rename //device/htc/m8et/device.mk to //device/htc/m8et/device_m8et.mk: No such file or directory
Creating initial git repository.
-bash: pushd: //device/htc/m8et: No such file or directory
Reinitialized existing Git repository in /Volumes/android/.git/
Click to expand...
Click to collapse
I tried to search but cannot get anything I'm using mac os x 10.12.6
thumbs up
Scripts to extract device vendor files and generate AOSP makefiles.
https://github.com/pdsouza/android-generate-vendor
Set of scripts to automate AOSP compatible vendor blobs generation from factory images
https://github.com/anestisb/android-prepare-vendor
Will these scripts work on MTK devices?
jai44 said:
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
1. Install unpackbootimg
Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git clone command.
extract files
cd directory
make
now you will find unpackbootimg and mkbootimg in this directory
2. copy unpackbootimg and mkbootimg to /usr/bin
sudo cp unpackbootimg /usr/bin
sudo cp mkbootimg /usr/bin
Note this is necessary if you are getting error
” “unpackbootimg not found. Is your android build environment set up and have the host tools been built?
Click to expand...
Click to collapse
Did not get what you meant by host tools been built
Sparker0i said:
Did not get what you meant by host tools been built
Click to expand...
Click to collapse
Same question from me.
You are supposed to get two files in step two. I only got one - unpackbootimg is missing.
How to set up android build environment and install host tools? Is there a guide somewhere around?
jai44 said:
How to create Device tree for Android Rom building
I assume you already downloaded source code
before we start please do following
Thank You
Click to expand...
Click to collapse
Is this thread dead or any hope of further guidance.
What fo you mean source code
does this work for MTK devices?
adityaparmar07 said:
i am getting errors !
Click to expand...
Click to collapse
[/QUOTE]
I tried to search but cannot get anything I'm using mac os x 10.12.6
[/QUOTE]
several years late, but you had a space between . and build instead of a /
FeyoMx said:
Thank you very much for the tutorial I will try to do it
Enviado desde mi A7010a48 mediante Tapatalk
Click to expand...
Click to collapse
what source are you talking about sir?