HOWTO: Linux and MTP - HTC One X+

This is a quick how to get MTP working on Linux, the guide is for distro's based on Debian (mint\debian\ubuntu) OpenSuse, Fedora AND Gentoo. If there's any missing for major distro's let me know, or add them to a separate post and i'll put them up here
***Debian based distros**
Code:
sudo apt-get install mtpfs
sudo mkdir /media/onex
sudo chmod 775 /media/onex
sudo mtpfs -o allow_other /media/onex
gedit /etc/udev/rules.d/51-android.rules
and add the following line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and then:
sudo service udev restart
***Arch Linux***
Code:
pacman -S libmtp
After installation, you have several mtp tools available. Upon connecting your MTP device, you use:
mtp-detect
and add the following line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and then reload udev rules:
udevadm control --reload
Arch Linux guide is from the ArchLinux wiki
**Redhat\Fedora16**
First of all, I using my computer with other people, who can come over the network, so the 0666 mode bits not a right choice for me. I make it all on a fedora 16, but the distro is really not important.
So the steps:
- add a user to the "disk" group (or whatever You want)
- make a mount point (the media doesn't work for me, across the init removes the content)
- add this mount point to the fstab, with some parameter
- create udevd rules
- restart udevd
- install fuse-mtpfs
- (re)login user
- try it
My common experience is that, the mtpfs is very very very very slow. Really slow, so I can use it only with CLI, any GUI has been coming back with time out
And the "code":
Code:
usermod -a -G disk $LOGINUSER
Code:
sudo mkdir /mnt/sgs2 ; sudo chgrp disk /mnt/sgs2; sudo chmod 0770 /mnt/sgs2
Code:
sudo echo "mtpfs /mnt/sgs2 fuse users,noauto 0 0" >> /etc/fstab
Code:
cat > /etc/udev/rules.d/51-android.rules <<EOF
SUBSYSTEM!="usb_device", GOTO="label_end"
ACTION!="add", GOTO="label_end"
# ATRRS{idVendor}== ertekei:
#Acer 0502
SUBSYSTEM=="usb",ATTRS{idVendor}=="0502",MODE="0660",GROUP="disk"
#ASUS 0b05
SUBSYSTEM=="usb",ATTRS{idVendor}=="0b05",MODE="0660",GROUP="disk"
#Dell 413c
SUBSYSTEM=="usb",ATTRS{idVendor}=="413c",MODE="0660",GROUP="disk"
#Foxconn 0489
SUBSYSTEM=="usb",ATTRS{idVendor}=="0489",MODE="0660",GROUP="disk"
#Fujitsu 04c5
SUBSYSTEM=="usb",ATTRS{idVendor}=="04c5",MODE="0660",GROUP="disk"
#Fujitsu Toshiba 04c5
SUBSYSTEM=="usb",ATTRS{idVendor}=="04c5",MODE="0660",GROUP="disk"
#Garmin-Asus 091e
SUBSYSTEM=="usb",ATTRS{idVendor}=="091e",MODE="0660",GROUP="disk"
#Google 18d1
SUBSYSTEM=="usb",ATTRS{idVendor}=="18d1",ATTRS{idProduct}=="4ee1",MODE="0660",GROUP="disk"
#Hisense 109b
SUBSYSTEM=="usb",ATTRS{idVendor}=="109b",MODE="0660",GROUP="disk"
#HTC 0bb4
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",MODE="0660",GROUP="disk"
#Huawei 12d1
SUBSYSTEM=="usb",ATTRS{idVendor}=="12d1",MODE="0660",GROUP="disk"
#K-Touch 24e3
SUBSYSTEM=="usb",ATTRS{idVendor}=="24e3",MODE="0660",GROUP="disk"
#KT Tech 2116
SUBSYSTEM=="usb",ATTRS{idVendor}=="2116",MODE="0660",GROUP="disk"
#Kyocera 0482
SUBSYSTEM=="usb",ATTRS{idVendor}=="0482",MODE="0660",GROUP="disk"
#Lenovo 17ef
SUBSYSTEM=="usb",ATTRS{idVendor}=="17ef",MODE="0660",GROUP="disk"
#LG 1004
SUBSYSTEM=="usb",ATTRS{idVendor}=="1004",MODE="0660",GROUP="disk"
#Motorola 22b8
SUBSYSTEM=="usb",ATTRS{idVendor}=="22b8",MODE="0660",GROUP="disk"
#NEC 0409
SUBSYSTEM=="usb",ATTRS{idVendor}=="0409",MODE="0660",GROUP="disk"
#Nook 2080
SUBSYSTEM=="usb",ATTRS{idVendor}=="2080",MODE="0660",GROUP="disk"
#Nvidia 0955
SUBSYSTEM=="usb",ATTRS{idVendor}=="0955",MODE="0660",GROUP="disk"
#OTGV 2257
SUBSYSTEM=="usb",ATTRS{idVendor}=="2257",MODE="0660",GROUP="disk"
#Pantech 10a9
SUBSYSTEM=="usb",ATTRS{idVendor}=="10a9",MODE="0660",GROUP="disk"
#Pegatron 1d4d
SUBSYSTEM=="usb",ATTRS{idVendor}=="1d4d",MODE="0660",GROUP="disk"
#Philips 0471
SUBSYSTEM=="usb",ATTRS{idVendor}=="0471",MODE="0660",GROUP="disk"
#PMC-Sierra 04da
SUBSYSTEM=="usb",ATTRS{idVendor}=="04da",MODE="0660",GROUP="disk"
#Qualcomm 05c6
SUBSYSTEM=="usb",ATTRS{idVendor}=="05c6",MODE="0660",GROUP="disk"
#SK Telesys 1f53
SUBSYSTEM=="usb",ATTRS{idVendor}=="1f53",MODE="0660",GROUP="disk"
#Samsung 04e8
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="6860",MODE="0660",GROUP="disk"
#Sharp 04dd
SUBSYSTEM=="usb",ATTRS{idVendor}=="04dd",MODE="0660",GROUP="disk"
#Sony 054c
SUBSYSTEM=="usb",ATTRS{idVendor}=="054c",MODE="0660",GROUP="disk"
#Sony Ericsson 0fce
SUBSYSTEM=="usb",ATTRS{idVendor}=="0fce",MODE="0660",GROUP="disk"
#Teleepoch 2340
SUBSYSTEM=="usb",ATTRS{idVendor}=="2340",MODE="0660",GROUP="disk"
#Toshiba 0930
SUBSYSTEM=="usb",ATTRS{idVendor}=="0930",MODE="0660",GROUP="disk"
#ZTE 19d2
SUBSYSTEM=="usb",ATTRS{idVendor}=="19d2",MODE="0660",GROUP="disk"
LABEL="label_end"
Code:
udevadm control --reload-rules
Code:
yum/apt-get/pacman/etc install mtpfs
Logout-login, for get in to the disk group, connect the device via usb, and try
Code:
mptfs
without any parameter, and it must write out some information:
Code:
[email protected]:~$ mtpfs
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 2, dev 4
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: (NULL)
fuse: missing mountpoint parameter
And finally mount /it must be working now with user account/:
[CODE]mount /mnt/sgs2
or dismount:
Code:
umount /mnt/sgs2
**OpenSuse 12.2**
this method will work for music and photos access only,
Code:
sudo zypper addrepo -f http://packman.inode.at/suse/12.2/ packman
sudo zypper ref (type a to always accept the packman repo)
sudo zypper in mtpfs
sudo vim /lib/udev/rules.d/69-libmtp.rules and add the following line (replace vim with gedit if you want a gui editor)
# HTC One X+
ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0dfc", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
sudo cp /lib/udev/rules.d/69-libmtp.rules /etc/udev/rules.d/.
reboot
When you plug in the phone you will see android phone icon on the desktop click on it to browse your files.
*note
disable any media players from trying to read the device...
** Gentoo **
Code:
Prerequisites
If your device is not recognized by libmtp, try upgrading to latest (or even git) version.
User needs to be in group plugdev to mount device.
MTPFS
You need to add option: user_allow_other in /etc/fuse.conf
$ mkdir ~/AndroidDevice
$ mtpfs -o allow_other ~/AndroidDevice
NOTE: this can take really long time, up to several minutes. As an indication of successful mount the mtpfs will go to background.
To unmount:
$ /usr/bin/fusermount -u ~/AndroidDevice
If mtpfs doesn't work for you try updating to latest version first.
Go-MTPFS
Seems to be more stable
$ emerge -a go
$ mkdir ~/go
$ export GOPATH=/home/$USER/go
$ go get github.com/hanwen/go-mtpfs
To mount:
$ ~/go/bin/go-mtpfs ~/AndroidDevice
To unmount:
$ /usr/bin/fusermount -u ~/AndroidDevice
Troubleshooting
Sometimes (e.g. on HTC One X) USB debugging automatically turns on when device is connected to PC. You need to turn debugging off, otherwise libmtp can't recognise device.
Make sure your Android device is not going to sleep and the screen is not getting locked. Set screen timeout to very long values, or enable in Development section flag "Do not turn off the screen".
Thanks to ihavoc and Fonya1 for the opensuse and redhat\fedora tutorials

thank you a lot for your help.
when i try to acces to the /media/onex direcory i have this :
ls: cannot access onex: Transport endpoint is not connected

After making changes reboot your session or pc and it will probably mount correctly which you've probably done by now.
Sent from my HTC One X+ using xda premium

somemadcaaant said:
After making changes reboot your session or pc and it will probably mount correctly which you've probably done by now.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
excuse me to ask many question but i am really noob. when all this done what would i see in /media/onex ? actualy after mounting the folder is empty
the only thing i need to do is copy files from/to my HOX+

Can anyone please confirm if this is exclusive to the HTC One X+, or would it work for other similar HTC devices such as One X, One S etc. as well?

It still dont work, i have tryed so many things these days to mount my HTC Ox+ as a USB Mass Storage and everything failed.
I tried tou manualy mount a MTP folder on my Ubuntu like Lloir explained here.
I tried to flash a TeamWorkRecovery and a ClockWorkRecovery to access the "Mount USB" option in the menu
my Device is seen by ubuntu but i am unable to read or write anything, for example if I copy a music album, the copy operation starts, takes a very long time an then end whith an error lik "error unable to copy xxxx.mp3 file does not exist"
actualy i am almost convicted that using an MTP device as an usb mass storage under Ubuntu is purely and simply IMPOSSIBLE !

HQRaja said:
Can anyone please confirm if this is exclusive to the HTC One X+, or would it work for other similar HTC devices such as One X, One S etc. as well?
Click to expand...
Click to collapse
works for ALL MTP devices

Thanks a bunch. This should come pretty handy. =)

Lloir said:
works for ALL MTP devices
Click to expand...
Click to collapse
does it works for you ?
how do you copy your files from/to your phone ?

Waiting for Ubuntu instructions (maybe)?

followed instructions to the letter and still cant mount my htc one xL running jellybean on ubuntu

Just a quick reply since this was linked on the front page. Tried with GNex and Ubuntu 12.10 and no dice.

spdrosin said:
Waiting for Ubuntu instructions (maybe)?
Click to expand...
Click to collapse
The instructions for Ubuntu are the first ones (Debian based distros), Lloir mentioned it at the start of the OP:
Lloir said:
This is a quick how to get MTP working on Linux, the guide is for distro's based on Debian (mint\debian\ubuntu) And Archlinux i will add others soon.
Click to expand...
Click to collapse

Linux really needs to add native support for MTP already. They also should add native support for adb as well while they are at it. Its annoying to have to add entrees to udev to even to be able to access the device.

One suggestion for anyone wanting to do this with a device other than an HTC:
You'll need to change the line you add to /etc/udev/rules.d/51-android.rules based on the vendor of your phone.
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Change the code to one of the following USB vendor ids:
Code:
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Fujitsu 04c5
Fujitsu Toshiba 04c5
Garmin-Asus 091e
Google 18d1
Hisense 109b
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenovo 17ef
LG 1004
Motorola 22b8
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10a9
Pegatron 1d4d
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony 054c
Sony Ericsson 0fce
Teleepoch 2340
Toshiba 0930
ZTE 19d2
Most up-to-date list is here: http://developer.android.com/tools/device.html
You can also have multiple vendor lines in your /etc/udev/rules.d/51-android.rules file, just put one on each line. As someone who's testing on a bunch of different devices, I simply put a line in for all of the above
If your vendor code isn't listed, enter the command "lsusb" in a terminal, and you'll see something like this:
Code:
Bus 001 Device 119: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Bus 001 Device 112: ID 18d1:4e42 Google Inc.
The first four hex values of the id is the vendor ID, e.g., for the Samsung it's 04e8.

cloverz7 said:
Just a quick reply since this was linked on the front page. Tried with GNex and Ubuntu 12.10 and no dice.
Click to expand...
Click to collapse
same here with GNex and ubuntu 12.04

Use Airdroid
Using Airdroid and wifi from Tethering hotspot, you can simply access your Android without USB Cable and you can use anything OS. Search on Google Play with keyword "Airdroid"

Hey I have to say first off thanks for taking the time to figure this out! My problem is I am very new to linux and ubuntu. So when I open the terminal and type all the commands after "sudo mtpfs -o allow_other /media/onex" I get the response: "Listing raw device(s) No raw devices found." So should I have the device attached when I do this? Secondly the following command opens a text window. Is this where i type "SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"? Because now I can't save the text file because I don't have root. Should I be typing literally everything in Terminal? or am I just too new and missing a step. Your help would be greatly appreciated because I would really like to learn a lot more about linux however I'm a bit cautious asking for root for things and ****ing up lol. I'm over windows and will never use a mac so I want to learn! Sorry to be an idiot and a pain just wanna learn.

Nschneider7 said:
Hey I have to say first off thanks for taking the time to figure this out! My problem is I am very new to linux and ubuntu. So when I open the terminal and type all the commands after "sudo mtpfs -o allow_other /media/onex" I get the response: "Listing raw device(s) No raw devices found." So should I have the device attached when I do this? Secondly the following command opens a text window. Is this where i type "SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"? Because now I can't save the text file because I don't have root. Should I be typing literally everything in Terminal? or am I just too new and missing a step. Your help would be greatly appreciated because I would really like to learn a lot more about linux however I'm a bit cautious asking for root for things and ****ing up lol. I'm over windows and will never use a mac so I want to learn! Sorry to be an idiot and a pain just wanna learn.
Click to expand...
Click to collapse
That "SUBSYSTEM..." line needs to be appended to the file opened in the text editor. It shouldn't be entered on the command line.
And add "sudo" to in front of that gedit line...i.e., "sudo gedit /etc/udev/rules.d/51-android.rules"
Good luck!

I prefer to use adb. If you want a GUI you can use QtADB:
http://qtadb.wordpress.com/

Related

EVO3d ubuntu 11.04 setup

If you are having troubles getting your ubuntu 11.04 to recognize your Evo3d here is what I did to get ADB working on mine:
I am assuming you have adb setup.
1. Plug your EVO3d into your pc as charge only
2. in terminal type
lsusb
3. You should see something like this:
Bus 001 Device 007: ID 0bb4:0cba High Tech Computer Corp
that is your evo3D(verify the eight digit id is the same before doing step 6 if it is not change to match your evo3d vendor id)
sudo gedit /etc/udev/rules.d/99-android.rules
4. Enter your ubuntu password if prompted
5. This should have brought up a new gedit file with 99-android.rules as
the title
6. copy and paste this into that gedit document:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
and save the new document.
7. make the new document executable:
sudo chmod a+rx /etc/udev/rules.d/99-android.rules
8. then restart dev environment:
sudo restart udev
9. open terminal and enter
adb devices
10. your evo 3d should be setup
Hopefully this helps anyone having the same issues I was having.
If someone tries this please let me know if i need to change anything.
Sent from my PG86100 using XDA Premium App
I am currently running the same setup. I will try soon and report back. Thank you!
Sent from my PG86100 using XDA Premium App
MiSfit211 said:
If someone tries this please let me know if i need to change anything.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
That will work. It's exactly what I had to do about 5 days ago to get ADB to work with my 3D. Prior to doing that, i would just get "List of Devices attatched : ??????????? NO permissions". I did a bit of googling and found the steps you just posted. Definitely would've saved me some searching if this was up last week This should help out anyone with the same problem, because it definitely works. Nice write up.
working perfect, thank you very much for the guide.
The only thing I had to do in addition was restart the adb server (since it was already running)
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT16MHX28070 device
(Also, the chmod to executable won't hurt anything but isn't necessary)
Thanks for the post!
thanks buddy. this couldnt have been any more helpful. it worked like a charm. this was very easy to follow. I am new to linux and appreciate the effort that you put in to explain getting this to work.
I used this thread and it works perfectly.
XDA/showthread.php?p=11823740#post11823740
MiSfit211 said:
If you are having troubles getting your ubuntu 11.04 to recognize your Evo3d here is what I did to get ADB working on mine:
I am assuming you have adb setup.
1. Plug your EVO3d into your pc as charge only
2. in terminal type
lsusb
3. You should see something like this:
Bus 001 Device 007: ID 0bb4:0cba High Tech Computer Corp
that is your evo3D(verify the eight digit id is the same before doing step 6 if it is not change to match your evo3d vendor id)
sudo gedit /etc/udev/rules.d/99-android.rules
4. Enter your ubuntu password if prompted
5. This should have brought up a new gedit file with 99-android.rules as
the title
6. copy and paste this into that gedit document:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
and save the new document.
7. make the new document executable:
sudo chmod a+rx /etc/udev/rules.d/99-android.rules
8. then restart dev environment:
sudo restart udev
9. open terminal and enter
adb devices
10. your evo 3d should be setup
Hopefully this helps anyone having the same issues I was having.
Click to expand...
Click to collapse
great post.just a heads up, you shouldn't have to do this on 11.10 though. after a fresh install of 11.10 and android-sdk all seems to be working without doing this.

[GUIDE] How To Compile TWRP Recovery for QVGA And Other Unsupported Devices.

How To Compile TWRP Recovery For QVGA And Other Unsupported Devices​
Guys a humble request don't spam this thread. If you face any error reply to this thread or PM me i will help and after you build it please don't post your bugs here this thread is only for compiling and not for resolving bugs in your build. I can only help with the errors you face during compilation because i faced a lot .
I thank XDA members cybojenix, kD as i got an idea of how to make guides from them
I would also thank Dees_troy for the sources.
I have worked hard in creating this guide so when you release your build please give proper credits .
Click to expand...
Click to collapse
Minimum Requirements:-
1. RAM:- 4GB
2. HDD Space:- More than 18GB required for CM7 source code (I am going to use CM7 for this guide as CM9 is not yet supported for many devices).
3. Processor:- Equal to Core 2 Duo or Anything above it.
4. Internet Speed:- Minimum of 2 Mbps as we will be downloading files of large size.
5. Patience:- A lots of it needed to get success
Click to expand...
Click to collapse
Ok Lets Start With Step 1:- Setting Up Your Computer For Development.
Getting Linux​
Please note your PC/Laptop must satisfy the minimum requirements to continue. If it doesn't contact any person who is developing for your device to develop this.
Click to expand...
Click to collapse
For compiling you need Linux the most common and free Linux available for development is Ubuntu. Go ahead choose your version and download it.
If you wish to use Ubuntu 10.04 64-Bit for Development use this link
http://releases.ubuntu.com/lucid/ubuntu-10.04.4-desktop-amd64.iso
Click to expand...
Click to collapse
If you wish to use Ubuntu 10.10 64-Bit for Development use this link
http://releases.ubuntu.com/maverick/ubuntu-10.10-desktop-amd64.iso
Click to expand...
Click to collapse
If you wish to use Ubuntu 11.04 64-Bit for Development use this link
http://releases.ubuntu.com/natty/ubuntu-11.04-desktop-amd64.iso
Click to expand...
Click to collapse
If you wish to use Ubuntu 11.10 64-Bit for Development use this link
http://releases.ubuntu.com/oneiric/ubuntu-11.10-desktop-amd64.iso
Click to expand...
Click to collapse
If you wish to use Ubuntu 12.04 64-Bit for Development use this link
http://releases.ubuntu.com/precise/ubuntu-12.04-desktop-amd64.iso
Click to expand...
Click to collapse
After downloading install it in a Virtual Machine or dual boot it alongside another OS you are using now. If you are using a Virtual Machine make sure you allocate more than 50GB of HDD space.
So far so good now that you have Linux installed :victory: you can proceed to the next step of setting up which is followed in the second post.
Setting Up Your Laptop/PC For Development.​
Note:- You may be asked for a password when using sudo command.
Click to expand...
Click to collapse
Installing Python-2.7.5:-
First and foremost is installing Python. For those who are wondering what Python is well here is the answer Python is a language like C,C++,Java which primarily centers around Linux.
1. Open Terminal by hitting Ctrl+Alt+T.
2. Type or copy paste these codes into terminal (I prefer typing though )
Code:
sudo apt-get install build-essential gcc
cd Downloads
wget http://www.python.org/ftp/python/2.7.5/Python-2.7.5.tgz
tar -xvzf Python-2.7.5.tgz
cd Python-2.7.5
./configure --prefix=/usr/local/python2.7
make
sudo make install
sudo ln -s /usr/local/python2.7/bin/python /usr/bin/python2.7
3. Python is now installed to make sure type this code in terminal
Code:
python
and it should produce an output like this
Code:
Python 2.7.2+ (default, Jul 20 2012, 22:15:08)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or " lincense" for more information.
>>>
4. If it shows something like that you are good to go.
5. Press Ctrl+D, close the terminal and proceed to install Java 6 JDK.
Installing Java 6 JDK:-
I have to thank cybojenix and kD for this part as it is theirs and i didn't write this part .
Click to expand...
Click to collapse
If you are using Ubuntu 12.04 follow these commands others skip this set of commands.
1. Download Java 6 JDK from here.
2. After Downloading copy that to the Downloads folder.
3. Open Terminal.
4. Type these commands one by one in the terminal
Code:
cd Downloads
chmod +x jdk-6u34-linux-x64.bin
sudo ./jdk-6u34-linux-x64.bin
sudo mv jdk1.6.0_34 /usr/lib/jvm/
sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_34/bin/java 1
sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.6.0_34/bin/javac 1
sudo update-alternatives --install /usr/bin/javaws javaws /usr/lib/jvm/jdk1.6.0_34/bin/javaws 1
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config javaws
If you are not using Ubuntu 12.04 follow these commands:-
1. Open terminal
2. Type these commands one by one in the Terminal.
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
If you had done those steps correctly then you must now have Java installed.
To check and make sure it is installed type this command in terminal.
Code:
java -version
and the output should be
Code:
java version "1.6.0_34"
Java(TM) SE Runtime Environment (build 1.6.0_34-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.9-b04, mixed mode)
If the output was some thing similar you are now ready to install GNU Make.
Close the Terminal and proceed.
Installing GNU Make 3.81
Note:- Any other version of make either lower or higher won't work for compiling TWRP.
Click to expand...
Click to collapse
1. Open Terminal
2. Type these codes in terminal.
Code:
wget -o make.tar.gz http://ftp.gnu.org/gnu/make/make-3.81.tar.gz
tar -xvzf make-3.81.tar.gz
cd make-3.81
./configure
sudo make install
3. That's it now you got make installed.
To check and make sure that Make is installed type this command in Terminal.
Code:
make -v
and it shoud give the output
Code:
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This Program built for x86_64-unknown-linux-gnu
If it was something smiliar to that you can close the terminal and proceed to the next step.
Ok now we got the big guns rolling it's now time for small guns without whom we can't compile yes I mean't the dependencies.
Open Terminal and apply these commands:-
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc gedit git schedtool
export USE_CCACHE=1
If you are using Ubuntu 10.10 apply this:-
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
If you are using Ubuntu 11.04 apply this:-
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
sudo apt-get install libx11-dev:i386
If you are using Ubuntu 12.04 apply this:-
Code:
sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
sudo apt-get install libx11-dev:i386
sudo apt-get install libncurses5-dev:i386 libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 zlib1g-dev:i386
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Good now you will have dependencies installed.
It is now time for SDK and ADB which will be continued in the next post.
Installing SDK and ABD​
Installing SDK:-
1. Download Android SDK from here.
2. Extract it to your home folder.
3. Rename the folder to sdk.
4. Open the Terminal and type these commands
Code:
cd sdk/tools
./android sdk
5. A window should popup and there will will be a list of Packages.
6. Install Android SDK Tools and Android SDK Platform-Tools.
Checking ADB:-
Since you installed Android SDK Tools and Android SDK Platform-Tools ADB must now be checked and configured.
1. Enable USB Debugging in your device and connect your phone to computer.
2. Now execute these commands in Terminal
Code:
cd sdk/platform-tools
./adb devices
It should give the output as
Code:
List of devices attached 0123456789ABCDEF device-name (Note the number-letter combination may vary)
If it does give like that skip Adding Permissions.
Or if it gives the output as
Code:
List of devices attached ????????????????? no permissions
Don't worry we have add permission to your device that's it.
Adding Permissions:-
1. Open Terminal
2. Execute this command.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
3. It should open text editor
4. Paste this line
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="xxxx", MODE="0666"
5. Replace Vendor ID with your Vendor id given in the list.
For e.g if your vendor is Acer you will replace "xxxx" with "0502"
Here is a list of Vendor ID's
Code:
Acer - 0502
ASUS - 0b05
Dell - 413c
Foxconn - 0489
Fujitsu - 04c5
Fujitsu Toshiba - 04c5
Garmin-Asus - 091e
Google - 18d1
Hisense - 109b
HTC - 0bb4
Huawei - 12d1
K-Touch - 24e3
KT Tech - 2116
Kyocera - 0482
Lenovo -17ef
LG - 1004
Motorola - 22b8
MTK - 0e8d
NEC - 0409
Nook - 2080
Nvidia - 0955
OTGV - 2257
Pantech - 10a9
Pegatron - 1d4d
Philips - 0471
PMC-Sierra - 04da
Qualcomm - 05c6
SK Telesys - 1f53
Samsung - 04e8
Sharp - 04dd
Sony - 054c
Sony Ericsson - 0fce
Teleepoch - 2340
Toshiba - 0930
ZTE - 19d2
6. Save and close the editor.
7. Execute this command in Terminal.
Code:
sudo gedit /etc/udev/rules.d/99-android.rules
8. Again paste this line
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="xxxx", MODE="0666"
Replace "xxxx" with Vendor ID.
9. Save it and close the file.
10. Execute these commands one by one in the Terminal
Code:
sudo chmod a+r /etc/udev/rules.d/99-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Now RESTART your Ubuntu and type these codes in the Terminal.
Code:
cd sdk
./adb devices
You must not get the output with ???????????????? no permission still if you get it please reply below I will help.
Now we need to edit .bashrc so that we can access adb from anywhere
Execute these codes in the Terminal.
Code:
cd
sudo gedit .bashrc
It should open text editor copy paste this line at the end.
Code:
export PATH=${PATH}:~/sdk/tools
export PATH=${PATH}:~/sdk/platform-tools
Save it and close it.
Now in terminal type adb devices it should give output List of devices attached.
That's it you got Ubuntu, Python, Java 6 JDK, GNU Make-3.81, SDK and ADB ready.
Now you are ready to start development go on to the next step to download source code.
Intializing Repo And Download Source Code
Step 2:- Initializing Repository And Downloading Source Code​
Initializing Repository​
First step is to download the Repo which is essential to download the source code.
1. Open Terminal
2. Execute these commands one by one in Terminal
Code:
mkdir ~/bin
PATH=~/bin:$PATH
sudo apt-get install curl
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Downloading Source Code​
After you have initialized the repo you are set to download the source code.
1. Open Terminal
2. Execute these commands one by one in Terminal
Code:
mkdir source
cd source
repo init -u git://github.com/Cyanogenmod/android.git -b gingerbread
sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo sync -jx (Replace x with a number this number corresponds to number simultaneous download you want for e.g if you give 5 it will download 5 files at once so go on increase to whatever you like but be reasonable :D)
The Source Code is around 15GB - 17GB so have patience and more importantly HDD space.
Click to expand...
Click to collapse
.
The download will take hours if you are on slow connection like it will be a 2 days is 512kbps connection so if you are planning to develop please have a good internet connection with a reasonable fast speed. Every developer recommends more than 1Mbps and sometimes 4Mbps.
After downloading is finished go to source folder you must have many folders inside them. Also make a backup of the source folder just in case as we will modifying it so if something goes wrong you don't have to re-download it all again.
Go to the next step to start the actual development.
Modding Files And Stuff
Step 3:- Modding Files And Folders To Make Your Device Supportable.​
First up is to compile a build of ClockworkMod.
Building ClockworkMod:-
1. Open Terminal
2. Type these commands one by one in Terminal
Code:
. build/envsetup.sh
lunch (it should show you list of devices select your device with their serial number select your device by typing the serial number)
make clean
make -j4 recoveryimage
If you didn't receive an error you are ready to compile TWRP for your device.
If you do receive and error reply to the post I will help you.
Modifying Files And Folder:-
The original Dees_Troy's build folder isn't gonna work as your device resolution doesn't support it. So I have patched the build folder with some extra libs added to prelink map and patched recovery folder with gui changes for smooth compilation.
If you have experience with using git you can clone the repo or you can download it directly from github.
Click to expand...
Click to collapse
If you are going to clone execute these commands in terminal. (Thanks to cybojenix for this so that there will no manual copying).
Code:
cd source
rm -rf build/
rm -rf bootable/recovery/
git clone git://github.com/chainhacker/TWRP_Build -b 2.3 build
git clone git://github.com/chainhacker/TWRP_Recovery -b 2.3 bootable/recovery
If you are going to download directly use the following link make sure you are downloading 2.3 branch and extract it.
Here is the link for the patched build folder------>TWRP_Build
Here is the link for the patched recovery folder------>TWRP_Recovery
After you have done downloading from the above two files.
Replace the contents of source/build folder with the patched one.
Similarly replace the contents of source/bootable/recovery folder with the patched one.
I have 240x320 resolution already in the patched ones but if your device is not 240x320 and also not supported by TWRP download a theme made by other members which has your device's resolution or create a theme. I didn't create the theme though I resized the images and made changes in ui.xml. If you are interested in theming follow the official TWRP theming guide in their website.
If you did find a theme or created it rename the theme folder to your device resolution folder for e.g. If your device resolution is 320x240 you would rename the folder as 320x240.
Copy the theme folder into source/bootable/recovery/gui/devices.
That's it finished the basic requirements next up is configuring BoardConfig.mk.
Editing BoardConfig.mk:-
1. Navigate to source/device/your_vendor/your_device.
your_vendor:- Vendor of your device e.g for me it is lge.
your_device:- Your device name.
Click to expand...
Click to collapse
2. Find BoardConfig.mk and open it in a text editor.
3. Come to the last and add these line
Code:
#twrp
DEVICE_RESOLUTION:= [I]your_device_resolution[/I] (e.g If your resolution is 240x320 type it)
RECOVERY_GRAPHICS_USE_LINELENGTH := true
2. Save it and close it.
Yay you have finished everything only thing left out is compiling which is carried out in the next post.
Psssst.......
After you have compiled your first successful build here are few other things that you could add to BoardConfig.mk
Note:- You can add this after finishing first successful build of recovery till then avoid these.
Click to expand...
Click to collapse
Code:
RECOVERY_SDCARD_ON_DATA := true -- this enables proper handling of /data/media on devices that have this folder for storage (most Honeycomb and devices that originally shipped with ICS like Galaxy Nexus)
BOARD_HAS_NO_REAL_SDCARD := true -- disables things like sdcard partitioning
TW_INCLUDE_DUMLOCK := true -- includes HTC Dumlock for devices that need it
TARGET_RECOVERY_GUI := true -- uses gui format instead of ui.xml
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565" -- to change the colour
TARGET_USE_CUSTOM_LUN_FILE_PATH :=/sys/devices/platform/usb_mass_storage/lun0/file
TW_CUSTOM_POWER_BUTTON := 107 -- to get a power button on the home screen of recovery
TW_EXTERNAL_STORAGE_PATH := "/sdcard" -- default external storage path
TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard" -- default external mount point
TW_FLASH_FROM_STORAGE := true -- enables you to flash zips form the sdcard (You don't neeed o add this it is activated by default)
TW_HAS_DOWNLOAD_MODE := false -- to enable download or more precisely enabling usb mass storage
TW_HAS_NO_RECOVERY_PARTITION := true -- do this only if you device has no partion to recovery
TW_INCLUDE_CRYPTO := false
TW_INCLUDE_JB_CRYPTO := false
TW_NEVER_UNMOUNT_SYSTEM := true -- always keeps the system mounted
TW_NO_BATT_PERCENT := false -- shows battery percentage
TW_NO_REBOOT_BOOTLOADER := true --- disables rebooting into bootloader
TW_NO_USB_STORAGE := false -- disabled usb storage
TW_SDEXT_NO_EXT4 := false
Compiling Recovery
Step 4:- Compiling Recovery​
Finally you have come to the final part of the guide which is compiling recovery.
1. Open Terminal.
2. Execute these commands in Terminal
Code:
. build/envsetup.sh
lunch (Again select your device)
make -j4 recoveryimage
.
That's it when it is finished grab recovery.img from:
out/target/product/your_product_name/recovery.img
Flash it in your device test it fix the bugs and release it.
Wait if you don't want flash and just see how it looks so that you can flash another recovery if it is not working do these
I am not resposible if your device gets bricked in fastboot mode but mostly it won't happen though
Click to expand...
Click to collapse
1. Copy the recovery.img to sdk/platform-tools
2. Boot your device into fastboot mode.
3. Open Terminal
4. Execute these commands one by one in Terminal
Code:
fastboot devices (wait for your device to show up int terminal)
fastboot boot recovery.img
You can test out all the features except flash zip, backup and restore.
Victory :victory: you have successfully compiled TWRP recovery for your device go ahead have fun and enjoy.
If you really like my work express your gratitude by pressing the Thanks button. See you soon in another thread :victory: :laugh: :fingers-crossed:
Click to expand...
Click to collapse
Reserved
reserved just in case :fingers-crossed:
Contributions
You can Contribute to this guide by suggesting improvements and stuff are welcome PM about the contribution and i will add by giving credits to the person contributed
Does it make any difference if I want to compile it for an ARMV6 device?
Gesendet von meinem Skate mit Tapatalk 4 Beta
Joe4899 said:
Does it make any difference if I want to compile it for an ARMV6 device?
Gesendet von meinem Skate mit Tapatalk 4 Beta
Click to expand...
Click to collapse
Nope it won't make any difference it is just the same even if your device is ARMv6 or ARMv7. Make sure your device is supported by CM
Chain Hacker said:
Nope it won't make any difference it is just the same even if your device is ARMv6 or ARMv7. Make sure your device is supported by CM
Click to expand...
Click to collapse
i'm wondering if it will work for Tegra's device
666satyr666 said:
i'm wondering if it will work for Tegra's device
Click to expand...
Click to collapse
Yes it will work go ahead give it a shot :good:
So that's me again :laugh: Wanted to compile TWRP 2.6.0.0 for cm10.1 so I have set up everything so far but get an error when I try to compile
build/core/base_rules.mk:130: *** external/fuse/lib: MODULE.TARGET.STATIC_LIBRARIES.libfuse already defined by bootable/recovery/fuse.
Click to expand...
Click to collapse
Seems to be really stupid, so far I understand is the libfuse defined twice in recovery and base_rules.mk so think (thought ) it's an easy part - just to remove this libfuse from one of them... But I can't find something with "libfuse", "static libraries" or anything like that in base_rules.mk
Joe4899 said:
So that's me again :laugh: Wanted to compile TWRP 2.6.0.0 for cm10.1 so I have set up everything so far but get an error when I try to compile
Seems to be really stupid, so far I understand is the libfuse defined twice in recovery and base_rules.mk so think (thought ) it's an easy part - just to remove this libfuse from one of them... But I can't find something with "libfuse", "static libraries" or anything like that in base_rules.mk
Click to expand...
Click to collapse
I have never tried compiling 2.6.0.0 because Dees_Troy is evaluating my theme for my device such that it gets official support so if you are ready to use CM7 and TWRP 2.3.3.0 you can follow my guide and i can help you with the errors but any other version please ask Dees_Troy for the solution.
How I compile twrp if my phone is not officially/unofficially supported?is it possible?
Sended from my ascend g330 using tapatalk 4 [VIP]
andrea210701 said:
How I compile twrp if my phone is not officially/unofficially supported?is it possible?
Sended from my ascend g330 using tapatalk 4 [VIP]
Click to expand...
Click to collapse
It is possible after successful build with no bugs you can contact Dees_Troy for evaluation and get official support.
Sent from my LG-P350 using Tapatalk 2
Error detected
Hi, Chain Hacker.
Does it matter how to write address after "git://"?
I mean this:
Code:
[B]repo init -u git://github.com/Cyanogenmod/android.git -b gingerbread[/B]
Should it be like this:
Code:
[B]repo init -u git://github.com/Cyanogen[COLOR="Red"]M[/COLOR]od/android.git -b gingerbread[/B]
By the way, it's a very good manual for those who are just starting to understand how to compile
maximik1980 said:
Hi, Chain Hacker.
Does it matter how to write address after "git://"?
I mean this:
Code:
[B]repo init -u git://github.com/Cyanogenmod/android.git -b gingerbread[/B]
Should it be like this:
Code:
[B]repo init -u git://github.com/Cyanogen[COLOR="Red"]M[/COLOR]od/android.git -b gingerbread[/B]
By the way, it's a very good manual for those who are just starting to understand how to compile
Click to expand...
Click to collapse
No i doesnt matter at all the only thing that is case sensitive are the words after cyanogenmod as they must be written as it is so it is your wish whether you are gonna write Cyanogenmod or CyanogenMod and by the way thanks for the complement
Sent from my LG-P350 using Tapatalk 2
TWRP Recovery size...
Hi again...
I've managed to compile a TWRP-Recovery 2.6.0.1 based on CM9 for my Huawei Ascend Y101 (8186).
But I had to change recovery partition size in BoardConfig.mk (originally it was BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000, I changed it to 0x00600000), because without these changes it wasn't possible to build a recovery.img ("recovery.img is too large... etc.")
When I flashed it on my device, the TWRP recovery started and worked perfectly, but I wasn't able to boot my device. But it's not a problem for me, I understand why it wasn't able to boot very good.
The question is the following: is it possible to decrease somehow the source files' sizes of TWRP recovery (maybe images, don't know...) in order to compile the recovery.img that would be less than 4.85 MB (actually it's size is 5*095*424, it's more than my recovery partition....... )
By the way, the size of a CWM-recovery (cm9) that I've compiled is 4*489*216, so it fits like a glove :good: and works fine...
Thanks in advance. I understand that you compiled a TWPR recovery based on CM7, but I don't see much differences...
maximik1980 said:
Hi again...
I've managed to compile a TWRP-Recovery 2.6.0.1 based on CM9 for my Huawei Ascend Y101 (8186).
But I had to change recovery partition size in BoardConfig.mk (originally it was BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000, I changed it to 0x00600000), because without these changes it wasn't possible to build a recovery.img ("recovery.img is too large... etc.")
When I flashed it on my device, the TWRP recovery started and worked perfectly, but I wasn't able to boot my device. But it's not a problem for me, I understand why it wasn't able to boot very good.
The question is the following: is it possible to decrease somehow the source files' sizes of TWRP recovery (maybe images, don't know...) in order to compile the recovery.img that would be less than 4.85 MB (actually it's size is 5*095*424, it's more than my recovery partition....... )
By the way, the size of a CWM-recovery (cm9) that I've compiled is 4*489*216, so it fits like a glove :good: and works fine...
Thanks in advance. I understand that you compiled a TWPR recovery based on CM7, but I don't see much differences...
Click to expand...
Click to collapse
The difference is no on the source dude so relax. You have to modify your kernel and change the compression method to lzma. Contact Dees_Troy for this because i dont know how to change it. You can chat with him through IRC.

[SOURCE](TUT){LEGION-MODZ}WARP3D 420 $ROM$ R3TURNZ- cd ~/XDA/$ROM$

{
"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"
}
I started this thread because my pre-paid phone is not a supported device.
I have to start this over from scratch, so no need to dwell in the past. The reason I started learning this stuff was to help others. I don't even use custom roms in my phone. I have always liked computers, and anything to do with electronics. I don't care for this N00Bz word. I don't care for people that look down on another human being for anything. God above made us all differently for a reason. Society made sellers and buyers, translated to the Android community as builders and users.. My old lady thinks ROOTING is something you do in the garden.. My new project has nothing to do with Cyanogenmod,AOKP, or JellyBeer. I like to do things that no one has done yet. That is why I am not going to reveal my new Source code. Seems like everytime I come up with an idea somebody else gets "motivated" to do it. lol To be honest I will be working on two seldom done roms, i'm repo sync'n the first one right now. Also, during my stay at XDA- i will make a very detailed tutorial on building from Source. Starting with
1. dual and tri booting your PC, for the Windows lovers. (u need Linux 2 build)
2. Learning to use "Google" , this is your new best friend, It never gets tired of your questions, it never runs out of answers, and open 24 hours a day...
3. Learn basic linux commands ....cd, su, apt-get, etc
4. Setting up your build by yourself
5. Setting up a pre-made build box (see step 1)
6. Learn to use Github
7. Use your newly acquired knowledge to "git" your Sources
8. Build a device tree
9. Build a kernel
10. Put together a script to pull Prop files
11. Building
12. Beating your head on the desk when you can't figure out why it wont build, boot , and why you have so many "bugz"
I AM NOT A DEVELOPER
But when i finish this tutorial, i will be.
this tutorial will not cover anything to do with "cooking" a rom, that is cheating...lol
Now I'm going to try my luck at these new $ROM$.
Thank you for visiting and God bless you
"MORE TO FOLLOW"
In the Beginning ,there was DARKNESS and cheap phones
STEP 1​
Windows 7 and Ubuntu,BBQ, or Mint,etc,Build boxes or from live CD. Despite their opposing missions, can get along like best pals on a single computer. Here's how to set up a dual boot or tri boot system that lets you enjoy the best of both worlds in perfect harmony. I know this works because it is how my system at home and on my laptop are setup.
HINT: Linux has around 100 viruses, Windows , it can't be counted. In linux it is harder to get viruses on a PC. Also, Windows viruses don't carry over to your Linux build OS.
Seen in this comparison article
"The expression is intended to suggest that proprietary software is more secure by virtue of its closed nature. If hackers can't see the code, then it's harder for them to create exploits for it--or so the thinking goes.
Unfortunately for Windows users, that's just not true--as evidenced by the never-ending parade of patches coming out of Redmond. In fact, one of Linux's many advantages over Windows is that it is more secure--much more. For small businesses and other organizations without a dedicated staff of security experts, that benefit can be particularly critical."
http://www.pagestart.com/win7heptaboot01.html
1. Make sure you have CD's or USB's with your Distro's on them. I use image burn. If it's Windows, PAY FOR IT!!! if it's Linux, IT'S FREE!!!
2. You are going to need extra space on your hard drive, or PG suggested you can use an extra hard drive.
a. Each repo is going to use up 30 GB
b. Your build tools maybe 5 GB
c. 300 mb for the boot
d. 5-10 GB for the SWAP
e. I use a 1TB for a tri-boot ,500 GB for Windows 7- 250 GB for each of my Linux distros
f. RAM,RAM,RAM,RAM and then some more RAM-- u can thank me later.
g. If you don't have RAM, like on my laptop, I just hooked it to my Internet connection, and let it pull Source while I was sleeping.
3. I like to start fresh--Make a backup, Then I use "KILLDISK" ,it is free and it will write zero's on your hard drive. "Warp, Why do u do that?"
I don't like viruses.
4. Use your Recovery partition or your Windows XP/VISTA/7/8 disk to install the OS.
5. Many hours later, boot into Windows, and hit Start..type diskmgmt.msc
6. If you haven't partitioned a hard drive ,Google it, and learn, this is not a game.
7. Dual boot = 2 primary partitions Tri boot = 3 primary partitions.
Logical is OK for Linux, but dynamic is no good.
8. Pop that fresh copy of your distro in
9. If you are new to Linux "Google it"
10. If you press install alongside windows, it will search out the empty partition and install
11. I don't like GRUB2.
12 Get the non-commercial version of "EasyBCD for Windows, install it, u will be needing it.
13. This is also a free app Google "use easy BCD for dual boot"
14. The only other step needed on the tri boot setup is logging into the first Linux distro u install, open terminal and execute update-grub2 . after everything else is done...
15. If you opted for the "Build Box, skip the setting up build step....
There is also another method to installing Linux on a Laptop, or a stubborn PC with Graphics issues and that is with the "Alternate Ubuntu installer"
I have only got this to work on 12.04 lots with recovery failsafex mode
REMOVE
SYSTEM RESERVED:
THIS CAN MESS UP YOUR PC:
I'M ONLY ADDING THIS FOR ADVANCED USERS:
ALL THE STEPS ARE HERE AT THIS LINK, BUT I USED WHATS IN THE CODE BOX AND IT WORKED FOR ME.
http://www.terabyteunlimited.com/kb/article.php?id=409​
Code:
Open Disk management ,
give SYSTEM a drive letter of e:
Run CMD as Admin
reg unload HKLM\BCD00000000 (if you get an ERROR: bla bla bla) then this may already be removed)
robocopy e:\ c:\ bootmgr
robocopy e:\Boot C:\Boot /s
dir c:\ /ah
If the bootmgr file and the Boot folder show up in the list, the procedure was successful.
bcdedit /store c:\boot\bcd /set {bootmgr} device partition=C:
bcdedit /store c:\boot\bcd /set {memdiag} device partition=C:
Close the Command Prompt window.
Return to Disk Management
Right-click on the Windows partition and select Mark Partition as Active
IF YOU HAVE TO ASK "WHY" I DID THIS ...DON'T DO IT (see number 7.) also easyBCD can do this process as well
Then came GOOGLE!
STEP 2​
This is a SIMPLE STEP...
WWW.GOOGLE.COM
Not www.goggle.com which is a real site, made by Hack3rz. it will mess your PC up.
This step is not limited to one search engine, Google is just my preferred one, because it links in UTUBE in search results and i like it.
Here is a list of other search engines.
Code:
General
No. Name
1 Baidu
2 Bing
3 Blekko
4 DuckDuckGo
5 Exalead
6 Gigablast
7 Google
9 Sogou
10 Soso.com
11 Volunia
12 Yahoo!
13 Yandex
14 Youdao
P2P search engines
No. Name
1 FAROO
2 Seeks
3 YaCy
Metasearch engines
No. Name
1 Blingo
2 Yippy
3 DeeperWeb
4 Dogpile
5 Excite
6 Harvester42
7 HotBot
8 Info.com
9 Ixquick (StartPage)
10 Kayak & SideStep
11 Mamma
12 Metacrawler
13 Mobissimo
14 Otalo English
15 PCH Search and Win
17 WebCrawler
Geographically limited scope
No. Name
1 Accoona
2 Alleba
3 Ansearch
4 Biglobe
5 Daum
5 Egerin
6 Goo
7 Guruji.com
8 Leit.is
9 Maktoob
10 Miner.hu
11 Najdi.si
12 Naver
13 Onkosh
14 Rambler
15 Rediff
16 SAPO
17 Search.ch
18 Sesam
19 Seznam
20 Walla!
21 Yandex.ru
22 Yehey!
23 ZipLocal
I got this list from using "Google"
1. you need to know how many MB in a GB , Google it =1024
2. You need a copy of a missing file ...
3. Anything you aren't sure of.....
4. If you can't find it then go to XDA, Android Forums, unleashedprepaids.com, etc and Search it. Chances are somebody has had the same problem as you.. DONE STEP 2
No, You mean I have to learn something to make a $ROM$
STEP 3​
Unix commands
Note that there are thousands of commands available on a typical unix box. In bash, just hit the "Tab" key twice and say yes, to display the the commands currently available on your machine. A standard unix operating system lists currently thousands of commands. Type x to list all commands starting with x. The following list contains some of the more frequently used programs.
Code:
Access Control
exit - terminate a shell (see "man sh" or "man csh")
logout - sign off; end session (C shell and bash shell only
passwd - change login password
rlogin - log in remotely to another UNIX system
ssh - secure shell
slogin - secure version of rlogin
yppasswd - change login password in yellow pages
Communications
mail - send and receive mail
mesg - permit or deny terminal messages and talk requests
pine - send and receive mail
talk - talk to another logged-in user
write - write to another logged-in user
Programming Tools
as - assembler, specific to each machine architecture
awk - pattern scanning and processing language
bc - online calculator
cc - C compiler
csh - C shell command interpreter
dbx - source-level debugging program
f77 - Fortran compiler
gdb - GNU Project debugger
gprof - display profile of called routines
kill - kill a process
ld - the UNIX loader
lex - generate lexical analysis programs
lint - check C source code
make - maintain large programs
maple - symbolic mathematics program
math - symbolic mathematics program
nice - run a command at low priority (see "man nice" or "man csh")
nohup - run a command immune to hangups
pc - Pascal compiler (xlp on ADS)
perl - Popular script interpreter
prof - display profile data
python - Python programming language
sh - Bourne shell command interpreter
yacc - generate input parsing programs
xcalc - graphical calulator under x
Documentation
apropos - locate commands by keyword lookup
find - locate file (i.e. find . -name *.tex -print)
info - start the info explorer program
man - find manual information about commands
whatis - describe what a command is
whereis - locate source, binary, or man page for a program
Editors
emacs - screen-oriented text editor
pico - screen-oriented text editor (renamed called nano)
sed - stream-oriented text editor
vi - full-screen text editor
vim - full-screen text editor ("vi-improved")
File and Directory Management
cd - change working directory
chmod - change the protection of a file or directory
chown - change owner (or group) of a file or directory
chgrp - change group of a file or directory
cmp - compare two files
comm - select/reject lines common to two sorted files
cp - copy files
crypt - encrypt/decrypt files (CCWF only)
diff - compare the contents of two ASCII files
file - determine file type
grep - search a file for a pattern
gzip - compress or expand files
ln - make a link to a file
ls - list the contents of a directory
lsof - list of open files
mkdir - create a directory
mv - move or rename files and directories
pwd - show the full pathname of your working directory
quota - display disk usage and limits
rm - delete (remove) files
rmdir - delete (remove) directories
stat - status of file (i.e. last access)
sync - flush filesystem buffers
sort - sort or merge files
tar - create or extract archives
tee - copy input to standard output and other files
tr - translate characters
umask - change default file protections
uncompress - restore compressed file
uniq - report (or delete) repeated lines in a file
wc - count lines, words, and characters in a file
Code:
File Display and Printing
cat - show the contents of a file; catenate files
fold - fold long lines to fit output device
head - show first few lines of a file
lpq - examine the printer spooling queue
lpr - print a file
lprm - remove jobs from the printer spooling queue
more - display a file, one screen at a time
less - like more with more features
page - like "more", but prints screens top to bottom
pr - paginate a file for printing
tail - show the last part of a file
zcat - display a compressed file
xv - show print, manipulate images
gv - show ps and pdf files
xpdf = shopw pdf files (use gv)
File Transfer
ftp - transfer files between network hosts
rsync - fast and flexible sync between computers
scp - secure version of rcp
Miscellaneous
alias - define synonym commands
chquota - change disk quota on ACITS UNIX systems
chsh - change default login shell
clear - clear terminal screen
echo - echo arguments
pbm - portable bitmap manipulation programs
popd - pop the directory stack (C shell only)
pushd - push directory on stack (C shell only)
script - make typescript of terminal session
setenv - set an environment variable (C shell only)
stty - set terminal options
News/Networks
netstat - show network status
rsh - run shell or command on another UNIX system
ssh - secure-shell version of rsh
Process Control
bg - put suspended process into background
fg - bring process into foreground
jobs - list processes
^y - suspend process at next input request
^z - suspend current process
Status Information
clock - determine processor time
date - show date and time
df - summarize free disk space
du - summarize disk space used
env - display environment
finger - look up user information
history - list previously issued commands
last - indicate last login of users
lpq - examine spool queue
manpath - show search path for man pages
printenv - print out environment
ps - show process status
pwd - print full pathname of working directory
set - set shell variables (C shell, bash, or ksh)
spend - lists year-to-date ACITS UNIX charges
stty - set terminal options
time - timing programs
top - list top cpu processes
uptime - show system load, how long system has been up
w - show who is on system, what command each job is executing
who - show who is logged onto the system
whois - Internet user name directory service
whoami - who owns the shell
Image Processing
gimp - photoshop type image processing program
xfig - drawing program
xv - image viewer
xvscan - scan picture
xpaint - paint program
kpaint - kde paint program
Sound
mplayer - mpg player
realplay - realaudio player
timidity - midi to wav converter and player
xmms - mp3 player
Text Processing
abiword - open source word processor
addbib - create or extend bibliographic database
col - filter reverse line feeds
diction - identify wordy sentences
diffmk - mark differences between files
dvips - convert TeX DVI files into PostScript
explain - explain phrases found by diction program
grap - pic preprocessor for drawing graphs
hyphen - find hyphenated words
ispell - check spelling interactively
latex - format text in LaTeX (based on TeX)
pdfelatex - latex with pdf output
latex2html - Latex to html
lookbib - find bibliography references
macref - make cross-reference listing of nroff/troff macro files
ndx - create a subject-page index for a document
neqn - format mathematics with nroff
nroff - format text for simple display
pic - make simple pictures for troff input
psdit - filter troff output for Apple LaserWriter
ptx - make permuted index (not on CCWF)
refer - insert references from bibliographic databases
roffbib - run off bibliographic database
sortbib - sort bibliographic database
spell - find spelling errors
ispell - interactive spell checker
style - analyze surface characteristics of a document
tbl - format tables for nroff/troff
tex - format text
tpic - convert pic source files into TeX commands
wget - grab webpage
X windows
grabmode - info on screen: i.e. "1152x864" 51.213kHz/56.59Hz
import - grab window (i.e. import ppm:- >out.ppm)
xdpyinfo - number of colors
xkill - kill xwindow
xlock - lock screen
xterm - xterminal
xwininfo - information on open window
Web
html2ps - html to ps
latex2html - latex to html translator
lynx - text based webbrowser
netscape - webbrowser
sitecopy - sitecopy is for easily maintaining remote web sites.
weblint - html sytax and style checker
MOST OF THESE YOU WON'T USE...
All by myself, I did it!!
STEP 4​
This next step is not easy, it is time-consuming. So if you chose a "Build Box" I understand..
Lucky for you, i have already found everything for you , So split your screen .
On one side a fresh terminal, on the other side my tutorial, and copy/paste from the beginning of part B).
HINT: When adding any file with apt-get. Watch for anything being removed and anything being added. Also copy any SUGGESTED programs to a text- editor ,research them and add them if you like..
Also when adding things with the command--- $ sudo apt-get install , numerous items can be added behind the command, but i recommend doing it one by one.
This is because of obsoleted software or missing software errors.
This is only going to be a basic list: Seperated in two parts, by A)what you need and B)how to get it.
A) TOOLS OF THE TRADE:
1. Compile Dependencies (libs)
2. Python 2.7.3 (3.2 and 3.3 opt.)
3. GNU MAKE (3.81 or 3.82)
4. Java JDK 6.xx ( not 7)
5. Android SDK
6. ADB & Fastboot
7. USB Configs
8. Repo command
9. Add everything to the PATH in ./bashrc
When you see this symbol "$", it means you are in terminal, but not as "ROOT"
Although if you see this symbol # , you are the "ROOT" user .
Your directory name will be in Red as well.
"But Warp, I don't know how to ROOT my Linux Box"
You don't say...
terminal: $ sudo passwd root
this will then open up Unix for you
add some passwords /confirm password /REMEMBER YOUR PASSWORD!!!
My password is ********** lol.
But Warp, I'm a brave "new user" I want "ROOT" access to file manager..
For Ubuntu
Terminal: $ gksudo nautilus
enter password-- DONE
For Mint (cinnamon)
Terminal: $ gksudo nemo
enter password-- DONE
For Mint (Mate)
Terminal: $ gksudo caja
enter password-- DONE!!!
B)
Libs
1..
$ sudo apt-get install git
sudo apt-get install git-core
sudo apt-get install gnupg
sudo apt-get install flex
sudo apt-get install bison
sudo apt-get install gperf
sudo apt-get install build-essential
sudo apt-get install zip
sudo apt-get install curl
sudo apt-get install zlib1g-dev
sudo apt-get install libc6-dev
sudo apt-get install lib32ncurses5-dev
sudo apt-get install ia32-libs
sudo apt-get install x11proto-core-dev
sudo apt-get install libx11-dev:i386
sudo apt-get install libreadline6-dev:i386
sudo apt-get install lib32z-dev
sudo apt-get install libgl1-mesa-glx:i386
sudo apt-get install libgl1-mesa-dev
sudo apt-get install g++-multilib
sudo apt-get install mingw32
sudo apt-get install tofrodos
sudo apt-get install python-markdown
sudo apt-get install libxml2-utils
sudo apt-get install xsltproc
sudo apt-get install readline-common
sudo apt-get install libreadline6-dev
sudo apt-get install libreadline6
sudo apt-get install lib32readline-gplv2-dev
sudo apt-get install libncurses5-dev
sudo apt-get install lib32readline5
sudo apt-get install lib32readline6
sudo apt-get install libreadline-dev
sudo apt-get install libreadline6:i386
sudo apt-get install bzip2
sudo apt-get install libbz2-dev
sudo apt-get install libbz2-1.0
sudo apt-get install libghc-bzlib-dev
sudo apt-get install lib32bz2-dev
sudo apt-get install libsdl1.2-dev
sudo apt-get install libesd0-dev
sudo apt-get install squashfs-tools
sudo apt-get install pngcrush
sudo apt-get install schedtool
sudo apt-get install python
sudo apt-get install gcc-4.7-multilib
sudo apt-get install ccache
sudo apt-get install eclipse
sudo apt-get install lzop
sudo apt-get install libwxgtk2.8-dev
sudo apt-get install liblzo2-dev
sudo apt-get install uuid
sudo apt-get install uuid-dev
sudo apt-get install zlib1g-dev liblz-dev
sudo apt-get install wmctrl
sudo apt-get install kernel-package
sudo apt-get install jfsutils
sudo apt-get install mcelog
sudo apt-get install xfsprogs
Code:
sudo apt-get install git git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev gcc-4.6-multilib squashfs-tools pngcrush schedtool python ccache eclipse lzop libwxgtk2.8-dev wmctrl debhelper liblzo2-dev uuid uuid-dev zlib1g-dev liblz-dev kernel-package jfsutils mcelog xfsprogs
EXTRAS suggested by apt-- I wouldn't advise you installing anything unless you need them...
apport-gtk apport-kde valac gnome-user-guide desktop-base lightdm
gnome-sushi python-launchpadlib python3-launchpadlib ri ruby-dev
ruby1.9.1-examples ri1.9.1 graphviz ruby1.9.1-dev ruby-switch
ubuntu-sso-client-gui ubuntuone-client-proxy zeitgeist-datahub
imagemagick-doc autotrace enscript ffmpeg gnuplot grads hp2xx html2ps
libwmf-bin povray radiance texlive-base-bin transfig ufraw-batch
libjline-java-doc librhino-java-doc xfonts-cyrillic
git-daemon-run git-daemon-sysvinit git-doc git-el git-arch git-cvs git-svn
git-email git-gui gitk gitweb
bison-doc lib32mudflap0 ncurses-doc libasound2-doc pulseaudio-esound-compat libglib2.0-doc
dh-make debian-keyring g++-multilib g++-4.7-multilib gcc-4.7-doc
libstdc++6-4.7-dbg libstdc++6-4.7-doc libmail-box-perl lib32stdc++6-4.7-dbg libxcb-doc libxext-doc gcc-doc cpp-doc
python-markdown-doc ttf-bitstream-vera ghc-prof ghc-doc haskell-doc llvm-3.0 libghc-bzlib-doc libghc-bzlib-prof
libgmp10-doc libmpfr-dev distcc distccmon-gnome distcc-pump
ant-gcj ant-doc libbsf-java liboro-java libxalan2-java libjaxp1.3-java
liblog4j1.2-java jython antlr libbcel-java libjdepend-java libgnumail-java
libcommons-net-java javacc ant-optional-gcj junit-doc
libcommons-beanutils-java-doc libcommons-collections3-java-doc
libcommons-dbcp-java-doc libcommons-digester-java-doc
libcommons-httpclient-java-doc libavalon-framework-java
libcommons-logging-java-doc libexcalibur-logkit-java libdb5.1-java-gcj
libeasymock-java-doc ecj libecj-java-gcj libfelix-bundlerepository-java-doc
libfelix-gogo-command-java-doc libfelix-gogo-runtime-java-doc
libfelix-gogo-shell-java-doc libfelix-osgi-obr-java-doc
libfelix-shell-java-doc libfelix-utils-java-doc
libgeronimo-jpa-2.0-spec-java-doc libgeronimo-jta-java-doc
libgeronimo-osgi-support-java-doc libice-doc jetty8 libjetty8-java-doc
libjtidy-java-doc libosgi-compendium-java-doc libosgi-core-java-doc
libosgi-foundation-ee-java-doc libsm-doc libswt-gtk-3-java-gcj tomcat7
wx2.8-doc libgnomeprintui2.2-0 libxt-doc openjdk-7-demo openjdk-7-source
visualvm
i386 items
murrine-themes:i386 kde-config-gtk-style:i386 libpam-ldap:i386
libpam-winbind:i386 libnss-ldap:i386 libroar1:i386 libsndio0:i386
roaraudio-server:i386 libasound2-python:i386 nas:i386 glibc-doc:i386
locales:i386 libcanberra-pulse:i386 libdv-bin:i386 oss-compat:i386
pulseaudio-esound-compat:i386 rng-tools:i386 libgd-tools:i386 libglide3:i386 ibx11-doc:i386 xml-core:i386
gnome-keyring:i386 gnutls-bin:i386 gphoto2:i386 gtkam:i386 gpm:i386
krb5-doc:i386 krb5-user:i386 gstreamer-codec-install:i386
gnome-codec-install:i386 gstreamer0.10-tools:i386 jackd2:i386
libjasper-runtime:i386 liblcms-utils:i386 libmyodbc:i386
odbc-postgresql:i386 tdsodbc:i386 unixodbc-bin:i386 libportaudio2:i386
libroar-compat2:i386 ttf-baekmuk:i386 ttf-arphic-gbsn00lp:i386
ttf-arphic-bsmi00lp:i386 ttf-arphic-gkai00mp:i386 ttf-arphic-bkai00mp:i386
libqt4-declarative-folderlistmodel:i386 libqt4-declarative-gestures:i386
libqt4-declarative-particles:i386 libqt4-declarative-shaders:i386
qt4-qmlviewer:i386 libqt4-dev:i386 libicu48:i386 qt4-qtconfig:i386
libraw1394-doc:i386 librsvg2-bin:i386 hpoj:i386 hplip:i386
libsane-extras:i386 sane-utils:i386 libsasl2-modules-otp:i386
libsasl2-modules-ldap:i386 libsasl2-modules-sql:i386
libsasl2-modules-gssapi-mit:i386 libsasl2-modules-gssapi-heimdal:i386
speex:i386 libxcb-doc:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
After you do all this, may be a good idea to add $ sudo apt-get upgrade
2. I don't get this step. Python is already on there, and if it ain't when you input "sudo apt-get install python" it will be...
3. Gnu Make , Your suppose to get this inside of build-essential , I like to know i got the newest one ,so i do it like this.
go to http://ftp.gnu.org/gnu/make/
Download GNU MAKE 3.82
Open up file manager
go to download folder
cut file
go to home directory
paste
extract
close file manager
Open Terminal:
$ cd <name of gnu make folder(exact)>
then it will look something like this
gnu make $
$ ./configure
$ make
# make install
# make clean...DONE
4. Get rid of pre-installed "JAVA"
$ sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
Add new Oracle JAVA 6
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
If you want to check the version after it is done
Terminal: $java -version
http://developer.android.com/sdk/index.html#download
5.Terminal: $ wget http://dl.google.com/android/android-sdk_r22-linux.tgz
When that finishes downloading
Terminal: $ tar -xvzf android-sdk_r22-linux.tgz
After extracting the package, run the command below to change into the tools directory.
cd ~/android-sdk-linux/tools
Finally, run the commands below to begin the installation.
./android update sdk
./android
"wget" is the same thing as "curl"
6. This may seem like a pointless step.
Warp, I already have ADB & Fastboot when I installed SDK, but do you have the 4.2.2 update ??
Just to make sure..
Terminal: $ sudo apt-get install android-tools-adb android-tools-fastboot
7. Create a folder in Home dir "51-android.rules" .
Now open a terminal and input: $ gksudo gedit /etc/udev/rules.d/51-android.rules
When another screen pops up copy and paste this inside--
Code:
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
Save & Close text-editor.
Now fire up another terminal
To set proper permisisons: (Provide read permission to all users, in addition to whatever other permissions are pre-set)
input:
Terminal: $ sudo chmod a+r /etc/udev/rules.d/51-android.rules
8. Terminal: $ mkdir -p ~/bin
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Terminal: $ chmod a+x ~/bin/repo
Terminal: $ export PATH=${PATH}:~/bin
9. You can make this change to the path permanent for all future Terminal sessions:
Terminal: gedit ~/.bashrc
add export PATH=${PATH}:~/bin, on its own line, then save the file.
If you ever have problems with repo.. try this
- Make sure you have a bin/ directory in your home directory and that it is included in your path: (Very Important)
$ PATH=~/bin:$PATH
- Next,
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod +x ~/bin/repo
I don't wanna do it
STEP 5​
This step was included , for no particular reason. If you chose a build box, and you made it past step 1 without using it, you did something wrong. Go back to step 1
But I might as well include a few sources for build boxes
BBQLinux http://sourceforge.net/projects/bbqlinux/files/
SuperR's ubuntu or mint buildbox http://unleashedprepaids.com/thread-8191-post-61357.html
h311sdr0id's--h311's kitchen http://forum.xda-developers.com/showthread.php?t=2152398
How did he do that???
STEP 6​
GitHub is a web-based hosting service for software development projects that use the Git revision control system. GitHub offers both paid plans for private repositories, and free accounts for open source projects.
If you are a person that wants to "build" and become more than just a "user", then your next stop is at "Github"...
Your old buddy "Google" can get you there pretty fast.
The site provides social networking functionality such as feeds, followers and the network graph to display how developers work on their versions of a repository.
According to the terms of service,if an account's bandwidth usage significantly exceeds the average of other GitHub customers, the account's file hosting service may be immediately disabled or throttled until bandwidth consumption is reduced. In addition, while there is no hard limit, the guideline for the maximum size of a repository is one gigabyte.
GitHub also has their standard GUI application available for download (Windows, Mac, Linux) directly from the service's website.
Ever wonder, "How did this Dev get this unsupported device to boot the latest rom?" Chances are, the way they did it will be inputted in Github.
Pay attention to the device names and models, This is important, because like I said every device is different... Everyday lately, I spend an hour or two looking through Github. Not just at my device, but at other models, other kernels, other Solutions...
Now I'm not saying go there, Find a boardconfig you like, cut/paste it into your device tree, but you may find some answers to problems.
(some info from github Wiki)
beginner's links
http://blog.jonathanargentiero.com/?p=114
http://ryanflorence.com/git-for-beginners/
http://dotnet.dzone.com/articles/intro-git
http://stackoverflow.com/questions/315911/git-for-beginners-the-definitive-practical-guide
http://blog.xkoder.com/2008/08/13/git-tutorial-starting-with-git-using-just-10-commands/
http://www.webdesignermag.co.uk/features/a-beginners-guide-to-git-and-github/
git gui
http://www.collab.net/downloads/giteye
"GIT" it!!!
STEP 7​
"GOT RAM" This is when it will come in handy. EDIT: If you like to multi-task. "message for the anal thread readers"
Open up file manager, HOME directory ,make new folder, name it "android" (easy way to do it)
Open "android" folder, make new folder, name it "system"
Close file manager
or
Fire up a terminal
$ mkdir android
$ cd android
$ mkdir system
To get your Source, all you need are three things.
1. Git
2. Curl
3. Repo command
Whether you used a "build box" or set it up yourself , you have everything, but to pull Source, that's all it uses...
How to Initialize the source repository
Code:
REPOSITORY'S OF FAMOUS ROMS (Select One)
AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-4.2.2_r1.2
PAC-Man :
Code:
repo init -u git://github.com/PAC-man/android.git -b cm-10.1
repo init -u git://github.com/PAC-man/android.git -b cm-10.2
CM 10.1 :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
CM10 :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
BeerGang :
Code:
repo init -u git://github.com/BeerGang/android.git -b cm-10.1
Aokp
For 4.2
repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr1
For 4.1
repo init -u https://github.com/AOKP/platform_manifest.git -b jb
MIUI
repo init -u git://github.com/MiCode/patchrom.git -b ics
Paranoid android
repo init -u git://github.com/ParanoidAndroid/android.git -b jellybean
slim bean
repo init -u git://github.com/SlimRoms/platform_manifest.git -b jb4.2
teambaked
repo init -u https://github.com/TeamBAKED/platform_manifest.git -b jb
(I got this from another guide)
There are other codes out there, but these are main-stream.
So, what you want to do is , open a Terminal
cd = change directory
So you will
$ cd android
$ cd system
$ repo init -u git://github.com/PAC-man/android.git -b cm-10.1
At this point half your terminal or all your terminal will fill with text.
Two ways this will play out
1. it will let you register with name and email
2. it will give you on-screen codes to config it to your name and email
If you want the "Goodies" DO AS IT TELLS YOU
Now after you got that taken care of,
$ repo sync
Learn this code, remember this code, love this code.
it not only pulls the Source to your PC, but it also updates it every time you input it.
So, say Pacman adds a bluetooth update, BAM, that's how you get it.
It depends on your PC specs, to whether how long downloading your Source will take.
PG gets it quick, i get it slow, but we both get it...
For the next month or 4ever, this is where your "repo" will live..
Learn this folder, Open every folder, learn what's in there.
DO NOT ALTER, DO NOT DELETE, DO NOT REMOVE ANYTHING YET!!!
This tree has broken branches
STEP 8​
Creating a basic new device tree
First step to this is to search Github for a device tree for your specific device.
This is where I got lucky.
PG and his associates lol, had already put together a working device tree for our device.
Chances are ,if your device didn't just hit the stores this week, somebody may have started work on a device tree for it.
Although if you do not have anything to start with, You must first open your device folder in the "repo" you "sync'd" to your PC, look at the supported devices
This will be a tool only for reference.
As I open my folder I notice the following
Code:
1. A "bluetooth" folder, with a config file
2. An "include" folder
3. An "overlay" folder
4. A "prebuilts" folder
5. A "recovery" folder
6. A "releasetools" folder
7. AndroidBoard.mk
8. AndroidProducts.mk
9. Boardconfig.mk
10. CM.mk
11. device_warp2.mk
12. extract-files.sh (this is to pull prop blobs)
13. full_warp2.mk
14. Proprietary-files.txt( a list of the prop files you will pull from your stock phone)
15. recovery.fstab
16. setup-makefiles.sh
17. system.prop
18. USBcontroller.cpp
With this group of files, i was able to get a built, but not bootable copy of Jellybeer 10.1.
Now some devices have less and some have alot more files in the device folder.
If you are really serious about becoming a developer, you have to search out others on Github, forums, etc
This step will take teamwork.
Below are two explanations of the files that go into making a device tree...
The directions below describe how to configure make files for new mobile devices and products.
Code:
Create a company directory in //device/partner.
mkdir device/partner/<company_name>
Create a products directory beneath the company directory you created in step 1.
mkdir device/partner/<company_name>/products/
Create a product-specific make file, called device/partner/<company_name>/products/<first_product_name>.mk, that includes the following code:
$(call inherit-product, target/product/generic.mk)
#
# Overrides
PRODUCT_NAME := <first_product_name>
PRODUCT_DEVICE := <board_name>
In the products directory, create an AndroidProducts.mk file that point to (and is responsible for finding) the individual product make files.
#
# This file should set PRODUCT_MAKEFILES to a list of product makefiles
# to expose to the build system. LOCAL_DIR will already be set to
# the directory containing this file.
#
# This file may not rely on the value of any variable other than
# LOCAL_DIR; do not use any conditionals, and do not look up the
# value of any variable that isn't set in this file or in a file that
# it includes.
#
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/first_product_name.mk \
Create a board-specific directory beneath your company directory that matches the PRODUCT_DEVICE variable <board_name> referenced in the product-specific make file above. This will include a make file that gets accessed by any product using this board.
mkdir device/partner/<company_name>/<board_name>
Create a product_config.mk file in the directory created in the previous step (device/partner/<company_name>/<board_name>). If this directory does not include a product_config.mk file, the build will fail.
# These definitions override the defaults in config/config.make for <board_name>
#
# TARGET_NO_BOOTLOADER := false
# TARGET_HARDWARE_3D := false
#
TARGET_USE_GENERIC_AUDIO := true
If you wish to modify system properties, create a system.prop file in your <board_name> directory(device/partner/<company_name>/<board_name>).
# system.prop for
# This overrides settings in the products/generic/system.prop file
#
# rild.libpath=/system/lib/libreference-ril.so
# rild.libargs=-d /dev/ttyS0
Add a pointer to <second_product_name>.mk within products/AndroidProducts.mk.
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/first_product_name.mk \
$(LOCAL_DIR)/second_product_name.mk
device/partner/<company_name>/<board_name> must include an Android.mk file with at least the following code:
# make file for new hardware from
#
LOCAL_PATH := $(call my-dir)
#
# this is here to use the pre-built kernel
ifeq ($(TARGET_PREBUILT_KERNEL),)
TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel
endif
#
file := $(INSTALLED_KERNEL_TARGET)
ALL_PREBUILT += $(file)
$(file): $(TARGET_PREBUILT_KERNEL) | $(ACP)
$(transform-prebuilt-to-target)
#
# no boot loader, so we don't need any of that stuff..
#
LOCAL_PATH := partner/<company_name>/<board_name>
#
include $(CLEAR_VARS)
#
# include more board specific stuff here? Such as Audio parameters.
#
To create a second product for the same board, create a second product-specific make file called device/partner/company_name/products/<second_product_name>.mk that includes:
$(call inherit-product, partner/google/products/generic.mk)
#
# Overrides
PRODUCT_NAME := <second_product_name>
PRODUCT_DEVICE := <board_name>
By now, you should have two new products, called <first_product_name> and <second_product_name> associated with <company_name>. To verify that a product is properly configured (<first_product_name>, for example), execute the following:
cd device
. ./envsetup.sh
partner_setup <first_product_name>
make PRODUCT-<first_product_name>-user
You should find new build binaries located in device/out/target/product/<board_name>.
New Product File Tree
The file tree below illustrates what your own system should look like after completing the steps above.
<company_name>
<board_name>
Android.mk
product_config.mk
system.prop
products
AndroidProducts.mk
<first_product_name>.mk
<second_product_name>.mk
Part 2
Right... So you want to build your own device tree, read on.
Disclaimer: this is by no means complete, and there will be omissions as have explained all this top of my head and copied pasted certain bits that I have here on my own device tree.
The device tree, for example, /device/lg/gt540would consist of the following make files:
Code:
Android.mk - this will tell the build system to include and to build sources specifically for your device. See below, for an example. This is dependant on the device and hardware, you could have libsensors, liblights, libcamera subdirectories under the example device tree, i.e. /device/lg/gt540/libsensors, /device/lg/gt540/liblights, /device/lg/gt540/libcamera etc.
AndroidBoard.mk - this is for the kernel, the build system uses that to drop the kernel image in place (more about this in a few minutes)
AndroidProducts.mk - specifies the appropriate device's make file, to use for building. i.e. /device/lg/gt540/device_gt540.mk, this is specific also.
device_xxxxx.mk - specifies the properties and extras to copy over into the final output, in this case, it could be for example, device_gt540.mk
BoardConfig.mk - This is the meat of it all, this is where compiler conditional flags are set, partition layouts, boot addresses, ramdisk size, and so on.
Lets peek into each of those to give a glance as to where it all fits in.
Code:
Android.mk:
ifeq ($(TARGET_BOOTLOADER_BOARD_NAME),xxxxx)
include $(call all-named-subdir-makefiles, recovery libsensors liblights libcamera ....)
endif
This is how the build will use that to build recovery, sensors, lights and camera (of course there will be more), its saying 'Yo Builder, go into each of the directories specified, and build the respective sources plskthxbai'
AndroidBoard.mk:
LOCAL_PATH := device/lg/gt540/
#
# Boot files
#
TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel
file := $(INSTALLED_KERNEL_TARGET)
ALL_PREBUILT += $(file)
$(file): $(TARGET_PREBUILT_KERNEL) | $(ACP)
$(transform-prebuilt-to-target)
Now this, is telling the build system, to be able to drop this kernel into the out/target/product/lg/gt540 (notice the correlation with the device tree directory?)
AndroidProducts.mk:
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/device_gt540.mk
Its telling the build as in 'Yo Builder, read that device make file please and process it upon completion of build.'
*device_xxxxx.mk: (for this example, device_gt540.mk) *
PRODUCT_NAME := lg_gt540
PRODUCT_DEVICE := gt540
PRODUCT_MODEL := LG GT 540
PRODUCT_COPY_FILES += \
... specific ...
PRODUCT_PROPERTY_OVERRIDES := \
ro.com.android.dateformat=dd-MM-yyyy \
... more stuff ...
This is where all the specifics for the device such as drivers, proprietary libraries, supporting scripts specifically for the device, gets copied over to out/target/product/lg/gt540/system/ in this case. Notice how the overrides for the properties, these end up in the build.prop found in the root of the /system of the Android ROM.
BoardConfig.mk:
LOCAL_PATH:= $(call my-dir)
TARGET_NO_BOOTLOADER := true
TARGET_PREBUILT_KERNEL := device/lg/gt540/kernel
TARGET_PREBUILT_RECOVERY_KERNEL := device/lg/gt540/recovery_kernel
# This will vary from device!
TARGET_BOARD_PLATFORM := msm7k
TARGET_ARCH_VARIANT := armv6-vfp
TARGET_CPU_ABI := armeabi
TARGET_CPU_ABI := armeabi-v6l
TARGET_CPU_ABI2 := armeabi
# OpenGL drivers config file path
BOARD_EGL_CFG := device/lg/gt540/egl.cfg
# Dependant, not to be taken literally!
BOARD_GLOBAL_CFLAGS += -DHAVE_FM_RADIO
# Dependant, not to be taken literally!
BOARD_KERNEL_BASE := 0x02600000
# this will be device specific, and by doing cat /proc/mtd will give you the correct sizes
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00480000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00480000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0cf80000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0d020000
BOARD_FLASH_BLOCK_SIZE := 131072
That is an excerpt, notice how we specify kernel's base address, this is how the boot.img gets generated after compilation is done and yet again, gets dropped into out/target/product/lg/gt540/boot.img. Also, more importantly, we're telling the build system to use the target platform for cross-compiling the sources (*TARGET_BOARD_PLATFORM*/*TARGET_CPU_ABI*) There will be more information in there such as conditional flags to pass to the compiler, for an example. we specified the directive HAVE_FM_RADIO to tell it, when it comes to handling the source for the FM radio system, to conditionally compile parts of the source. Again, this is hardware specific and mileage will vary, also this applies to the address for boot. In a nutshell, this is saying 'Yo Builder, read the damn variables and remember them and apply them when cross-compiling those source files!'
Now that the internals of each of those Android build make-files are shown.
Now, onto the vendor/ part of it, in AOSP, simply, once again, correlation and corresponds with the device/ tree, as in continuing with this example, vendor/lg/gt540/ which gets picked up by the lunch. There's more make files in there but the general consensus is there's a directory called proprietary which contains the proprietary libs (due to close-source etc) that gets copied over. The copying over of the libraries gets specified in the file device-vendor-blobs.mk, in this case, gt540-vendor-blobs.mk.
When the magic happens by doing the following:
. build/envsetup.sh
This is reading in the entire entries found in each of the device/ subdirectories and "remembers them", so the build system knows what type of target is used etc.
When the . lunch gets invoked, a menu appears prompting to pick the device that is required to build. Now the last and final step to do the build...
make -j5 > buildlog.log 2>&1
I run multitail on another terminal and monitor the buildlog.log file to check and make sure its building.
This last step will depend on how many cores you have (n cores + 1 as a rule) and it takes a while to build, GB build takes 40mins on my laptop running Arch Linux 64bit, ICS build takes about 2hrs 30 mins. So mileage will vary on what type of horsepower your machine has.
When the build is done, a little bell goes off and at the bottom of the said log file, I see this:
Combining NOTICE files: out/target/product/xxxxx/obj/NOTICE.html
Target system fs image: out/target/product/xxxxx/obj/PACKAGING/systemimage_intermediates/system.img
Install system fs image: out/target/product/xxxxx/system.img
out/target/product/xxxx/system.img+ total size is 108776448
As matter of interest JBQ (Jean Baptiste Queru - the 'boss' for managing/distributing the source from Google), his build step is this...
Code:
Extra code to use the ICS Repository
Now enter the following to initialize the repository:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b ics
Extra codes to use the JB Repository
Now enter the following to initialize the repository:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
This is not everything, because a device tree for every device is different, To start from scratch will take alot of time.
You will add, then remove, and then add again.
ASSEMBLE A TEAM...THIS IS A ADVANCED STEP
The president has spoken
STEP 9​
Building a kernel.
You're in deep waters once again.
To explain the kernel, I would say he is like the president of your phone.
He tells everyone what to do, and when to do it, and how to do it.
Kernel
The kernel is the core of an operating system. It functions on a low level (kernelspace) interacting between the hardware of the machine and the programs which use the hardware to run. To make efficient use of the CPU, the kernel uses a scheduler to arbitrate which tasks take priority at any given moment, creating the illusion of many tasks being executed simultaneously.
(From an article about Arch Linux)
"Do you like LAG?"
Well if you answered "no"
Then you better build a good kernel.
I entered "building a kernel for android" and i got a long list of tutorials on this.
So, if my section on kernels isn't enough, Google has more.
"git clone" is the code prefix if you luck out and find a kernel source on github.
first you would
$ cd android
$ cd system
$ cd kernel
$ mkdir <name of company>
$ cd <name of company>
$ git clone bla bla bla bla bla lol
But for the purpose of this step, you did not find a kernel source...
So, if you did step 8, or you found a device repo on Github, then you know alot more about your device now, specifically the hardware that pushes your device..
This table lists the name and locations of SOME kernel sources and binaries
Device / Binary location / Source location / Build configuration
manta / device/samsung/manta/kernel / kernel/exynos / manta_defconfig
mako / device/lge/mako-kernel/kernel / kernel/msm / mako_defconfig
grouper / device/asus/grouper/kernel / kernel/tegra / tegra3_android_defconfig
tilapia / device/asus/grouper/kernel / kernel/tegra / tegra3_android_defconfig
maguro / device/samsung/tuna/kernel / kernel/omap / tuna_defconfig
toro / device/samsung/tuna/kernel / kernel/omap / tuna_defconfig
panda / device/ti/panda/kernel / kernel/omap / panda_defconfig
stingray /device/moto/wingray/kernel / kernel/tegra / stingray_defconfig
wingray / device/moto/wingray/kernel / kernel/tegra / stingray_defconfig
crespo /device/samsung/crespo/kernel / kernel/samsung / herring_defconfig
crespo4g / device/samsung/crespo/kernel / kernel/samsung / herring_defconfig
This is for reference, these devices are supported..
You will want to look at the git log for the kernel binary in the device project that you are interested in.
Device projects are of the form device/<vendor>/<name>. This example is for the Panda...
$ git clone https://android.googlesource.com/device/ti/panda
$ cd panda
$ git log --max-count=1 kernel
The commit message for the kernel binary contains a partial git log of the kernel sources that were used to build the binary in question. The first entry in the log is the most recent, i.e. the one used to build that kernel. You will need it at a later step.
Downloading sources
Depending on which kernel you want,
Device projects are of the form device/<vendor>/<name>.
The goldfish project contains the kernel sources for the emulated platforms.
The msm project has the sources for ADP1, ADP2, Nexus One, Nexus 4, and can be used as a starting point for work on Qualcomm MSM chipsets.
The omap project is used for PandaBoard and Galaxy Nexus, and can be used as a starting point for work on TI OMAP chipsets.
The samsung project is used for Nexus S, and can be used as a starting point for work on Samsung Hummingbird chipsets.
The tegra project is for Xoom and Nexus 7, and can be used as a starting point for work on NVIDIA Tegra chipsets.
The exynos project has the kernel sources for Nexus 10, and can be used as a starting point for work on Samsung Exynos chipsets.
To git these
$ git clone https://android.googlesource.com/kernel/common.git
$ git clone https://android.googlesource.com/kernel/exynos.git
$ git clone https://android.googlesource.com/kernel/goldfish.git
$ git clone https://android.googlesource.com/kernel/msm.git
$ git clone https://android.googlesource.com/kernel/omap.git
$ git clone https://android.googlesource.com/kernel/samsung.git
$ git clone https://android.googlesource.com/kernel/tegra.git
Here are some other links for sources
http://www.htcdev.com/
http://opensource.samsung.com/
http://developer.sonymobile.com/wpor...ads/opensource
http://www.lg.com/global/support/ope...opensource.jsp
You may have to do some leg work and find your source.
As an example, we would build the kernel using the following commands:
Part A. Pre-build Steps
A. Open terminal and change to the root of your kernel directory
B. Type "export ARCH=arm"
C. Type "export CROSS_COMPILE=~/android/system/kernel/toolchains/arm-eabi-linaro-4.6.2/bin/arm-eabi-" (your toolchain may be different than this, it is an example)
Part B. The First Build
A. Type "make <your_config_name>_defconfig"
B. Type "make menuconfig" and make the required changes to use any modules you added or similar changes.
C. Type "make -j<maximum number of jobs>"
Part C. Re-Builds
A. Type "make clean"
B. Type "make oldconfig"
C. Type "make -j<maximum number of jobs>"
Part D. Building Modules
You have two options:
A. Type "make modules"
B. Type "make path/to/your/module.ko"
The above steps explained:
Part A.(These steps are required every time you close your terminal and re-open it to build again.)
A. Ok shouldn’t need to explain this.
B. This command sets your target architecture.
C. Defines the path to the toolchain we are going to use to compile our kernel. You can change this to point towards whatever toolchain you have downloaded or feel like using, the way it is currently configured it will use the Linaro toolchain that we downloaded above.
Part B.(These only need to be run the first time you build a kernel.)
A. Load's your configuration file from earlier.
B. Open up a menu to configure your kernel. It will use the config file you loaded in the previous step as a base.
C. Viola start the build. I typically allow 1 job per core, so on my quad core machine I put "make -j4". Just raising that number will not make your build faster, your processor needs to be able to support the number of jobs you are assigning it.
Part C. (Use the command's when you are building any-time outside of the first)
A. This command gets rid of any old/outdated binaries or modules you compiled before, and let's start fresh. I like to run it every I build unless my changes are really small and localized.
B. A very awesome command, it parses through what has changed and only prompts you about new options.
C. See the explanation for the above "Part C.".
Part D.(Use these for just building kernel modules.)
A. This will re-build all modules.
B. Will rebuild just the module you need. Very useful when you need to rebuild a WiFi module.
Outcome A. Build Succeds
W00t!! You have a kernel built by your self from source. There are a couple things you need in-order to use this kernel on your device any ".ko" modules and the zImage binary. If you pay attention to the output of your compiler then you will see the location of those objects. However the following commands will make your life a bit easier(Thanks Recognized Developer Hacre):
A. Open a terminal
B. Change to your root kernel directory
C. Type "mkdir ../<your_kernel>_output"
D. Type "cp arch/arm/boot/zImage ../<your_kernel>_output/zImage"
E. Type "find . -name "*.ko" -exec cp {} ../<your_kernel>_output \;"
The above steps explained:
A-C. Self-Explanatory
D. Move our kernel binary into our output folder
E. This handy bit of magic finds all ".ko" modules and also copies them into your output file.
You will also need to assemble a kernel image containing a initramfs for your device, along with the kernel binary and such. That however is beyond the scope of this tutorial. To get started though try searching the following phrases.
Code:
building android kernel image
xda build kernel image
xda unpack boot.img
Outcome B. Build Fails
Oh dear. It failed. Well guess what...this is going to happen..a LOT. Get used to it, and get used to googling and experimenting with different solutions. The following are some tips that will help you with debugging your issues.
Running a "Clean" build
A. Backup your config file(Type "cp .config ../backupConfig")
B. Re-run the build process using just your defconfig from earlier.
Limiting Output(Thanks Hacre.)
A. Another good tip is to run "make -j1" to get the error, as it will limit the amount of text you need to scroll through.
(from a kernel tutorial)(cred =thewadegeek)
The kernel binary is output as `arch/arm/boot/zImage`, and needs to be copied into the Android source tree in order to build the matching boot image.
Quotes from threads
"when building a whole ROM like AOSP,AOKP,PA or CM then they typically bundle the toolchain/kernel with the source, making this totally unneeded."
"You can typically find a manufacturer's configuration file in "arch/arm/configs". I believe the one for my HTC Flyer was called "flyer_hc_defconfig"
A Q&A from a thread
How can I build the latest kernel using all described stuff (aosp source, kernel config, latest kernel)?
Jean-Baptiste Queru
Mar 25
That's not possible without some work. Device-specific kernel are
typically 3 steps away from the upstream kernel: one step adds
android-specific code, one step adds chipset-specific code, one step
adds device-specific code.
THIS IS NOT COMPLETE.. IT IS A ADVANCED STEP ,LIKE STEP 8 it will take patience and time...
iT'S JUST NOT THE SAME
STEP 10​
This is the step for pulling the prop file or prop blobs from a "stock" phone...
This is the script that SuperR made for the Warp2
Code:
#!/bin/sh
VENDOR=zte
DEVICE=warp2
BASE=../../../vendor/$VENDOR/$DEVICE/proprietary
rm -rf $BASE/*
for FILE in `cat proprietary-files.txt | grep -v ^# | grep -v ^$`; do
DIR=`dirname $FILE`
if [ ! -d $BASE/$DIR ]; then
mkdir -p $BASE/$DIR
fi
adb pull /system/$FILE $BASE/$FILE
done
./setup-makefiles.sh
This is one from the LGE Mako
Code:
#!/bin/sh
VENDOR=lge
DEVICE=mako
BASE=../../../vendor/$VENDOR/$DEVICE/proprietary
rm -rf $BASE/*
for FILE in `cat proprietary-blobs.txt | grep -v ^# | grep -v ^$ | sed -e 's#^/system/##g'`; do
DIR=`dirname $FILE`
if [ ! -d $BASE/$DIR ]; then
mkdir -p $BASE/$DIR
fi
adb pull /system/$FILE $BASE/$FILE
done
./setup-makefiles.sh
NOTICE: the main thing that changed was the
VENDOR=zte
DEVICE=warp2
Your proprietary-file.txt depends on your phone.
I found that during a build, it actually told me diffrent .so files it needed.
Though if you made it this far, your phone is rooted, and you probably have "root explorer"
So you may want to open that up and orient yourself with what system files are in there.
Also, you can open other prop lists from similar phones and see what files they extracted.
Here is a list that PG and associates used
Code:
## RIL
bin/qmuxd
bin/rild
lib/libnv.so
lib/liboncrpc.so
lib/libreference-ril.so
lib/libril.so
lib/libril-qc-1.so
lib/libril-qc-qmi-1.so
lib/libril-qcril-hook-oem.so
lib/libauth.so
lib/libcm.so
lib/libdiag.so
lib/libdsm.so
lib/libdsutils.so
lib/libdss.so
lib/libgsdi_exp.so
lib/libgstk_exp.so
lib/libidl.so
lib/liboncrpc.so
lib/libpbmlib.so
lib/libpdapi.so
lib/libqmi.so
lib/libqmiservices.so
lib/libqueue.so
lib/libwms.so
lib/libwmsts.so
lib/liboem_rapi.so
lib/libpdsm_atl.so
lib/libqc-opt.so
lib/libqdi.so
lib/libqdp.so
lib/libuim.so
## GPS
lib/libcommondefs.so
lib/librpc.so
## Sensors
lib/hw/sensors.default.so
## EXTRA
bin/netmgrd
bin/port-bridge
bin/thermald
etc/media_profiles.xml
etc/thermald.conf
lib/libdsi_netctrl.so
lib/libnetmgr.so
lib/libv8.so
$$$$###$$# HINT #$$###$$$$
EVERY PHONE IS DIFFERENT!!!!
Let's see if it works
STEP 11​
TIME 2 BUILD
Another time when RAM will help you out.
Whatever steps you actually took to get here all depends on how much work has been put into your phone and how much of it you were able to find..
So if you have the following things done, You can continue to build if not, you better go get them.
1. Linux 64 OS
2. Build environment
3. up to date Repo
4. device repo
5. kernel source
6. proprietary files text/ extract.sh
7. prebuilts
8. ccache
9. Build command
10 Teamwork and Patience
"But Warp, you never explained some of this stuff.."
Yep, that's why there is a step about actually building it...
This next section is pulled from PG's read me
Getting my ZTE Sequent repo
$ cd ~/android/system/device/
$ mkdir zte
$ cd zte
$ git clone https://github.com/playfulgod/androi..._zte_warp2.git warp2
Note it says ZTE, not Sony, not Samsung, ETC
Then cd to the kernel directory:
$ cd ~/android/system/kernel
$ mkdir zte
$ git clone https://github.com/playfulgod/kernel_zte_warp2.git warp2
Then prop files from stock..
$ cd
$ cd ~/android/system/device/zte/warp2
$ ./extract-files.sh
When the environment is setup, we need to grab a copy of Term.apk. This is necessary to build CM10.
$ cd ~/android/system/vendor/cm
$ ./get-prebuilts
O k so I waited to tell you about CCACHE at the end. I guess I did that, because you don't need it untill the end anyway..OR is building just the beginning
You decide...
http://ccache.samba.org/manual.html
http://manpages.ubuntu.com/manpages/intrepid/man1/ccache.1.html
Ccache
There's a wonderful tool for gcc called ccache. You can read about it at their home page.
If you're always compiling the same programs over and over again — such as trying out several kernel patches, or testing your own development — then ccache is perfect. While it may take a few seconds longer to compile a program the first time with ccache, subsequent compiles will be much, much faster.
Now that we know what it is
HOW-TO-INSTALL
http://source.android.com/source/initializing.html
Setting up ccache
You can optionally tell the build to use the ccache compilation tool. Ccache acts as a compiler cache that can be used to speed-up rebuilds. This works very well if you do "make clean" often, or if you frequently switch between different build products.
Put the following in your .bashrc or equivalent.
export USE_CCACHE=1
By default the cache will be stored in ~/.ccache. If your home directory is on NFS or some other non-local filesystem, you will want to specify the directory in your .bashrc as well.
export CCACHE_DIR=<path-to-your-cache-directory>
example: export CCACHE_DIR=$HOME/.ccache
The suggested cache size is 50-100GB. You will need to run the following command once you have downloaded the source code:
prebuilts/misc/linux-x86/ccache/ccache -M 50G
When building Ice Cream Sandwich (4.0.x) or older, ccache is in a different location:
prebuilt/linux-x86/ccache/ccache -M 50G
This setting is stored in the CCACHE_DIR and is persistent. (pulled str8 from the link)
Now, we build (system being your work directory):
$ cd ~/android/system
To build for the ZTE Sequent:
$ . build/envsetup.sh && brunch warp2
All credit to PG for his readme file...Which he updated it recently, this is the old one ,I think...
Beating your head on the desk when you can't figure out why it wont build, boot , ...
STEP 12​
In the true nature of a 12 step program, this process never ends.. You will always run into errors, you will always be looking for fixes, patches, and anything to correct a problem you are having.
So, basically the 12th step is TEAMWORK
I hope if this tutorial didn't suck to bad, you will come on this thread and post your questions, post your answers, post your advice. I just started
AND no, just because I made a Tutorial and finished it, it DOES NOT make me a Developer. That was a joke. You have to earn that $hyt...
But one thing i am, is motivated...
I hope you enjoyed my rendition of "HOW-TO-BUILD-FROM-SOURCE"
Shout outz
SPECIAL THANKS TO:​
XDA​ @bcrichster, @NinjaInPyjamas, @Bizack, @danger_beast, @WildfireDEV @BobDabolina​ HACK3R1, PlayfulGod, Junkie 2100, SuperR, dizzle,​ EarlyMon, cooldudezach, rbheromax, Frank the Tank,​agat , downthemachine, hroark13, DM47021, thewadegeek, guspeed
Android,Cyanogenmod, BeerGang,
ChameleonOS, ibotpeaches, 0xD34D,
BO$$HOGG,,and Madhatter34​
warning: (MTD_MSM_NAND && MTD_DOC2000 && MTD_DOC2001 && MTD_DOC2001PLUS) selects MTD_NAND_IDS which has unmet direct dependencies (MTD && MTD_NAND)
If you ever get this one...heres a fix
http://lists.infradead.org/pipermail/linux-mtd/2012-January/039122.html
Code:
Fix the following build warning:
warning: (MTD_DOC2000 && MTD_DOC2001 && MTD_DOC2001PLUS) selects MTD_NAND_IDS
which has unmet direct dependencies (MTD && MTD_NAND)
Signed-off-by: Fabio Estevam <fabio.estevam at freescale.com>
---
drivers/mtd/devices/Kconfig | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/devices/Kconfig b/drivers/mtd/devices/Kconfig
index 952e956..3560fca 100644
--- a/drivers/mtd/devices/Kconfig
+++ b/drivers/mtd/devices/Kconfig
@@ -191,6 +191,7 @@ comment "Disk-On-Chip Device Drivers"
config MTD_DOC2000
tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
+ depends on MTD_NAND
select MTD_DOCPROBE
select MTD_NAND_IDS
---help---
@@ -213,6 +214,7 @@ config MTD_DOC2000
config MTD_DOC2001
tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
+ depends on MTD_NAND
select MTD_DOCPROBE
select MTD_NAND_IDS
---help---
@@ -234,6 +236,7 @@ config MTD_DOC2001
config MTD_DOC2001PLUS
tristate "M-Systems Disk-On-Chip Millennium Plus"
+ depends on MTD_NAND
select MTD_DOCPROBE
select MTD_NAND_IDS
---help---
--
1.7.1
Wow. Thanks for the huge tutorial man!
Another piece of info.
"make clobber"
In software engineering, clobbering a file or computer memory is overwriting its contents. In makefiles, a common target clobber means complete cleanup of all unnecessary files and directories produced by previous invocations of the make command.
"make clean"
deletes any files generated by previous attempts, leaving you with clean source code
These are codes to use when
1. encountering fatal errors
2. when you "repo sync" new data
3. when you make changes to make files etc...
THIS IS A ROOTING TOOL FROM JUNKIE2100,​IT WORKS FOR THE WARP SEQUENT N861​
www.oldphoneshyte.gov
I updated the picture, I updated the SuperUser.apk and I updated the SU binary...​
Warped420 said:
THIS IS A ROOTING TOOL FROM JUNKIE2100,​IT WORKS FOR THE WARP SEQUENT N861​[/SIZE
I updated the picture, I updated the SuperUser.apk and I updated the SU binary...
Click to expand...
Click to collapse
Updated for what/why??
Sent from my confused Warp/Nexus using Tapatalk 2
This is MY JellyBeer BeerGang 10.1 $ROM$​
I started this project over two months ago.
This is the new v4.30
This is the first build ,nothing is fixed
It doesn't have sound, sd card etc​Without PG and associates I wouldn't have gotten this built, see SPECIAL THANKS section​I have two more $ROM$ coming soon...
www.idon'thavethisphoneanymore.org​
WARP SEQUENT N861​

[Q] [Ubuntu] adb does not recognize device

Hello everyone,
I have a short question which you might be able to answer (at least I hope so).
I just got a cheap Android phone on which I want to learn to do some Android app development. So, I want to use the "adb" tool on Ubuntu to push my app to the device.
First of all, I wanted to find out which vendor is the right one (as the phone itself does not have branding), so I ran "lsusb". The output was
Code:
Bus 001 Device 010: ID 1782:5d01 Spreadtrum Communications Inc.
Thus I figured that "1782" is the vendor ID and I created an udev-rule named "51-android.rules" which contains
Code:
"SUBSYSTEM=="usb", ATTR{idVendor}=="1782", MODE="0666"
I set file permissions with
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
and restarted the udev service aswell as the adb server. But still the output of "adb devices" does not show any connected devices. What am I doing wrong?
I am running Ubuntu 13.04 with Kernel 3.8.0-34. USb debugging on the phone is enabled.
Any help would be highly appreciated,
Phil

[ROM]Samsung S3 Intl Sailfishos

Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attempting since monday tonight.
I'll explain more and I'll give more shots on working.
My issue now is to build the boot, recovery image to flash and boot it. The jolla sailfishos as a GUI operating system on Galaxy S3 I9300 model.
FIY : filename = sfa-i9300-ea-1.0.8.19-my1.tar.bz2
Instructions for chroot co,pilation on ubuntu amd64 x86_64 bit:
Code:
sudo mkdir -p /srv/mer/
mkdir -p $HOME/mer/
nano .bashrc
export $MER_ROOT=/srv/mer/
export $MER_ROOT=$HOME/mer/
ctrl +x to save and y
but type sudo apt-get install -y curl
for do the downloading file.
next do the following commands on terminal:
export $MER_ROOT=/srv/mer/
cd $HOME; curl -k -O https://img.merproject.org/images/mer-sdk/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
sudo mkdir -p $MER_ROOT/sdks/sdk ;
cd $MER_ROOT/sdks/sdk ;
sudo tar --numeric-owner -p -xjf $HOME/mer-i486-latest-sdk-rolling-chroot-armv7hl-sb2.tar.bz2 ;
echo "export MER_ROOT=$MER_ROOT" >> ~/.bashrc
echo 'alias sdk=$MER_ROOT/sdks/sdk/mer-sdk-chroot' >> ~/.bashrc ; exec bash ;
echo 'PS1="MerSDK $PS1"' >> ~/.mersdk.profile ;
sdk
Now, do the following instructions:
$HOST>
nano $HOME/.hadk.env
export MER_ROOT="[/home/$user]"
export ANDROID_ROOT="$MER_ROOT/android/droid"
export VENDOR="[samsung]"
export DEVICE="[i9300]"
ctrl +x and y for save it.
nano $HOME/.mersdkubu.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
export PS1="HABUILD_SDK [\${DEVICE}] $PS1"
hadk
save it again
nano $HOME/.mersdk.profile
function hadk() { source $HOME/.hadk.env${1:+.$1}; echo "Env setup for $DEVICE"; }
hadk
now save this file.
Now in ctrl + alt + x, it will show a terminal:
type this:
sdk
type your password
hadk
TARBALL=ubuntu-quantal-android-rootfs.tar.bz2
curl -O http://img.merproject.org/images/mer-hybris/ubu/$TARBALL
UBUNTU_CHROOT=/parentroot/$MER_ROOT/sdks/ubuntu
sudo mkdir -p $UBUNTU_CHROOT
sudo tar --numeric-owner -xvjf $TARBALL -C $UBUNTU_CHROOT
hadk
ubu-chroot -r /parentroot/$MER_ROOT/sdks/ubuntu
exit
git config --global user.name "Your Name"
git config --global user.email "Your email"
back again for
hadk
cd $HOME
mkdir -p $HOME/mer/android/droid
repo init -u git://github.com/mer-hybris/android.git -b hybris-10.1
repo sync
after this, you will have HABUILD_SDK
DEVICE=i9300
export $DEVICE
source build/envsetup.sh
breakfast $DEVICE
now type
make hybris-hal
But now as a ota file for flashing on i9300, in this last 2 days in my laptop core2Duo Extreme I'm facing overheating.
So, everyone can test it.
Code:
A little change on mount fixups.
Go to the directory hybris/hybris-boot
nano mount-fixups on i9305| encore)
put the "i9305" | "encore" | "i9300")
Script for booting sailfishingos on an android terminal. This script is to mount the binds folders and for fixing for preventing the /dev/null issue when we all boot the chroot sailfishos.
name of the script : sailfishos.sh - made it on the /extsdCard/ folder.
1) nano /extSdCard/sailfishos.sh and copy the following code
2) ctrl +x to save it
3) bash sailfishos.sh
Code:
su
mount -o bind /dev /data/.stowaways/sailfishos/dev
mount -o bind /proc /data/.stowaways/sailfishos/proc
mount -o bind /sys/ /data/.stowaways/sailfishos/sys
chroot /data/.stowaways/sailfishos/ /bin/su -
echo "nameserver 8.8.8.8" > /etc/resolv.conf
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
See folders on it.
PS: I'll give more shots also more instructions very soon. Thanx.
Another PS: I'll give more news about Jolla sailfish os very soon.
But I need to tell this, I've got i9300 defconfig kernel for Jolla sailfishos very similar to defconfig i9305 kernel and I got it compiled with very success on hadk Ubuntu chroot on mine Ubuntu 14.04 LTS version.
astronfestmon said:
Hi there!
Following the hadk pdf from jolla porting guide.
I've got the sailfishos working on terminal android running. Booting on top attemptinh since yesterday tonight.
Code:
Procedures:
1) get cm 10.1 flash it.
2) recovery mode to flash it.
3) download my sailfish i9300 tar.bz2 from d-h.st
4) Copy it for your /extSdCard
Code:
Procedures inside adb:
1) sudo adb kill-server
2) sudo adb start-server
3) adb devices
4) adb shell
5) su
6) cd /extSdCard/
8) mkdir -p /data/.stowaways/sailfishos
8) tar --numeric-owner -xvf filename -C /data/.stowaways/sailfishos
9) mount -o bind /dev /data/.stowaways/sailfishos/dev
10) mount -o bind /proc /data/.stowaways/sailfishos/proc
11) mount -o bind /sys /data/.stowaways/sailfishos/sys
finally:
chroot /data/.stawaways/sailfishos/ /bin/su-
you'll see sailfish os version something 15
try this on it:
cd /
ls
[LINK] http://d-h.st/gX5 [/LINK]
sees folders on it.
Click to expand...
Click to collapse
Screenshots?
Sent from my SM-G900F using XDA Free mobile app
Fantastic... I'll give a try. Plz provide some more details, screenshots & new features from your currently running sailfish os. Thanx for sharing
i fed with adb commands & not able to flash
Uhm ... I gonna wait for this ...
Sent from my SM-G900F using XDA Free mobile app
how to install ?
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
astronfestmon said:
When I had the rom for flashing in recovery. I'll explain it.
For now, it can be installed through the adb, to work it inside the android terminal.
Click to expand...
Click to collapse
any update on this?
I followed the above procedure and I can see the Sailfish version and the files list from adb. What next?
EDIT: Just saw your PS in OP
In the end of the week probably I'll release the boot kernel working on.
astronfestmon said:
In the end of the week probably I'll release the boot kernel working on.
Click to expand...
Click to collapse
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
astronfestmon said:
Aye. I've notice that.
I'm fixing some issues in quantal chroot.
E.g. inside the sources.list I add the 12.04 lts mirrors. Made by a website with the sources.list for 12.04 lts mirrors.
Yeah. I've done the boot kernel image and it made the same as you.
But with meld diff I've compared the i9305 defconfig with mine i9300 defconfig.
I'm going to test it with the changes meld diff made with a comparison with i9305 defconfig.
Now I made a make systemtarball and I'll try a make bootimage or a make factory_image for it.
Click to expand...
Click to collapse
It would be great if you could make it to boot.
I will try to compile the kernel with CONFIG_CMDLINE="console=tty0" . I'm hoping that would direct kernel panic message to the screen so we could idenfity what the problem is with booting hybris-boot.img
So... Any development?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
astronfestmon said:
Hi! All of you! I'm doing efforts between these days. In these vacation days. I'll report more when I got home back.
Click to expand...
Click to collapse
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
redrum781 said:
I've successfully built boot and recovery images, packed the zip for flashing in recovery but there is a problem with the boot.img.
I'm trying to find out why it doesn't boot (the phone stays at the galaxy logo)
The actual guide for porting misses some stuff and there are errors here and there. Besides, there is a problem with the trusty chroot, quantal is working.
Click to expand...
Click to collapse
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
rusty88 said:
Hi, I've also been trying to port sailfish os to i9300. I've been successful in creating an image that works, i.e. got it to boot into sailfish but there are some issues that I haven't been able to fix, like for instances, the wlan is detected but fails to establish a connection with any network, GSM is also not working. A full list with details can be found here https://wiki.merproject.org/wiki/Adaptations/libhybris
Maybe we should try to work together to get a fully functional sailfish os image
Cheers
---------- Post added 19th August 2014 at 12:01 AM ---------- Previous post was 18th August 2014 at 11:12 PM ----------
The phone may be stuck at the galaxy logo, but there's a way to debug to find out what's wrong, follow this steps (only tested on linux):
1) connect your phone with the computer, the initramfs in boot.img will create a network interface (phone's ip is: 192.168.2.15) and enable a telnet deamon (default port: 23) and also a udhcp server, so luckily the computer will ask for an ip that everything will be set up automatically. If not try configuring static ip (192.168.2.20 and adding a route to 192.168.2.0)
2) telnet 192.168.2.15
3) when you're in the telnet session, you can check /diagnostic.log (i think) it will show why the boot failed. It is possible to execute commands into the init, by writing to (/init-ctl/stdin)
When logged into the telnet session it will dump a bit of information, be sure to read it as is useful .
Also check HADK 9.2 Operating Blind on an Existing Device
PS: the files may contain mistakes as I wrote this post without checking for the correct names (I don't have sailfish flashed at the moment).
Also consider visiting the IRC channel (#sailfishos-porters), if you're not doing it already
Hope it helps
Click to expand...
Click to collapse
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
MaxAndroided said:
Will this os improve our device? Whats the pro and the con for a change (if it works finaly)?[emoji4]
Click to expand...
Click to collapse
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
msri3here said:
@rusty88, I am no developer/expert, but is there any way we can try and use I9300 native libraries or binaries to make GSM (or some other functionality for that matter) work? maybe RIL libs/binaries for GSM?
Click to expand...
Click to collapse
yes @msri3here technically that is what i'm doing, its using RIL lib based on cm10.1.3 that was working fine before I flash sailfish, but on sailfish the log that RIL daemon dumps is really a mess and haven't figure out why is failing. One thing that I've notice is that RILD (one of its child process) creates the socket at /dev/socket/rild but it's killed afterwards, the sockets disappear and the process restarts all over again
Stracing RILD is not helping either as it seems that everything is Ok.
I'm trying to buy a new smartphone for day to day use so I can dedicate more time to debug on my i9300.
rusty88 said:
well maxAndroided all I can say at the moment is that the OS looks very promising... the UI is very smooth. Is another approach to mobile interaction based on gestures. I'm really loving it, sadly I can used it for day to day activities yet.
The jolla phone at the moment is able to run android apps and hopefully soon that will be available for any image built for android phones. So what that means is that if you don't find a suitable native app for sailfish os, you can always run your favorite android app in sailfish os
Anyone that wants to help bring sailfish os to i9300 is welcome to help, so if you have any idea on how to debug and fix the issues let me know
PS: if any one would like to try it, take a look at my previous post here
Click to expand...
Click to collapse
tried your rom but stuck on "samsung galaxy s 3 gt-i9300" screen nothing is happening plus if i touch the screen i get a response from the capacitive buttons but thats all

Categories

Resources