THIS IS NOW OBSOLETE DUE TO THE WONDERFUL CTR V 2.5 FROM CARLIV
see
I assume you are a Windows PC user. Try at own risk. Please read or skim read all my links except distrowatch.
Credits
vampirefo for adb and dumchar_info and great advice
snowdream for his udev rule
chainfire for his abdb insecure playstore app
roberts @ tinycorelinux.net for his root id test
Reasons to use include:
A) The Windows USB driver can not be found, maybe a clone
B) You are not quick enough to associate the Windows driver
c) The Flashtool instructions fail for your device.
Why Linux?
Android Preparation
Go into system settings --> Developer Options -> Tick or turn on----USB debugging mode. If you fail to do this, adb command won't work correctly!
Which Windows user are you?
First we need to separate you into 3 main camps
Camp 1 = no working cd/dvd burner or no optical drive. You need to use Windows to image Linux onto an USB stick or install Linux into a virtual machine running on your PC ---not discussed further otherwise this becomes a novel. You can google the answer if you like.
If you lack a burner and optical drive works you could loan a library Linux mag that comes with a cd/dvd or buy one and see if the cd/dvd boots up
Camp 2 = W8 or UEFI enabled with secure boot on. You need to find out if your motherboard will boot an UEFI aware Linux distro. Trouble is, I don't own UEFI bios. You need a 64 bit recent Linux live cd or dvd. Google to see if its UEFI aware please.
Camp 3 = Windows users with UEFI already turned off or an old bios
From now on I will assume you are in Camp 3. With a working burner.
INSTRUCTIONS
Please read all the instructions before starting anything.
1) Find out how to burn an iso image in your version of Windows
google it if not sure. I suggest you buy an dvdrw or cdrw ---depending on size, so if you make a mistake, you don't turn the cd/dvd into a coaster.
eg W7 users may try
2) Download a live Linux cd or dvd. There is lots to choose from. Please choose a debian/Ubuntu/LinuxMint or derived from Debian ---I don't want to show every package management system from the others.
distro=a distribution of Gnu/Linux also known as Linux
So download any you like or if not fussed try this 64 bit distro about 511 Mb
Its system requirements like RAM and video card are shown here
&func=display&sid=39
click on Download mirrors left hand pane if you wish to download from another country or choose KDE which is much larger download.
You may notice my iso download suggestion says amd64 and you may have an intel processor, such as me, its just a name tag. Remember if size of iso is greater than 700 Mb then use a dvd blank please.
Do NOT install this distro please. I want you to consider using only as a live cd.
I use debian sid on my internal hard drive but I don't have time to explain
why you should choose other Linux distros. Its safe to use as a live cd. All factors being equal.
3) Change your bios boot order to boot up the live cd or dvd. Check your motherboard how to do this. Some modern PC have a bios splash screen which tells you which button or button combinations to push.
eg my ECS mobo ---press the delete key.........---my old Dell mobo --press the F2 key.
4) When Linux boots up
(4) What kind of root (superuser) does your Linux use?
(5) Can you see your Andoid device?
Use the Linux menu to open a web browser and view this file ----or Windows users and their browser
Clones not found according to my eyesight. If you can see your device, then jump to step (6) please
If you can not see your device, then we need to show you how to make up a rule
that Linux can use.
5a) Plug your USB data cable into PC and Android.
5b) On Android enable USB storage thru the notifications menu.
5c) Some Linux distros will automatically mount your SD card
and internal storage......while others have a pop box asking you what to do.
mount = make readable a certain device in Linux speak.
For this part of the instructions press cancel if asked to mount your Android device. If you see no popup...don't worry it about....it won't affect the instructions.
5d) In Linux, open a terminal and use what ever method above to get root,
probably sudo su
---> you will get 15 lines of a log.
Do not close the terminal we will use it again shortly.
5e) Now we look at those 15 lines and hope to find a line that will show a different
device to mine (iOcean) but we are looking for the id of the Vendor = maker id
For example one of my output lines is this:
Jun 25 17:22:31 box kernel: usb 3-7: New USB device found, idVendor=0bb4, idProduct=0c03
so we know manufacturer id = 0bb4
5f) Now open a text file in Linux, you may find more than one.
It defaults to a new page. Copy and paste this into the text editor
# symbols indicate nothing on that line is to be actioned by the operating system
---just like Andoid.
Now you change 0bb4 to "something" where something is to the right of idVendor from our command above. The 666 means, when active, that the local user or non-root can use Linux commands to interact with their Android device.
This is different from Flashtool instructions so do not try to mix up my instructions with whatever you read in the past please!
Now click on file, save as.....just like MS word etc and save the file to your home folder as 55-android.rules
Filename is case sensitive, meaning do not use capitals please.
BUT your file will have a formula like this
If you want to add a second phone you need to follow the same discovery process and edit the same file.
5g) Now back to terminal. It should have opened to the live cd's default home user account ----which is /home/somename. AND you have saved a file under that local name. Lets check with a list command which is "ls" without the quotes
5h)
5i) Ubuntu/LinuxMint users need to refresh this new rule by
Debian users try
Other users try
Let me know if either method fails as your distro may be using some other service management system. Now leap to (7)....do not reboot.
(6) Your device was showing in link
If this section confuses you, use the manual method in section (5).
6a) Now a download of a zipped package
unzip under Windows, or the super quick way under Linux is
a) open terminal
b) run command
Here is LinuxMint action in image
It will be the same fast result in Ubuntu or Debian.
There are a heap of graphical unzippers in Linux but they are slower to use,
if interested here is one in the link
After unpack, contents are:
55-android.rules (modified from the 51-android link)
license to re-distribute the 51-android link
and three scripts: --root-checks --nvram --recovery
Which are discussed in Tutorial later.
6b) Now follow the root commands as shown in 5g then 5h and one of the commands ----from 5i to refresh the new rule.
### If you have got to here, well done.
Ideally you now have a Linux USB rule that should work with your device.
7) Now to get the latest adb command
Live cd/dvd are by their nature out-of-date. So we need to update
our package manager.....in Android terms that means sync.
Then we can download the adb command which is in a Linux package.
This might take a while.
8 USB stick and internal drive discussion
To keep it simple I suggest you have your recovery image on a fat32 USB stick. And use root powers to save your nvram backups to the same fat32 stick,
then copy to Windows and cloud storage.
see
I assume you are a Windows PC user. Try at own risk. Please read or skim read all my links except distrowatch.
Credits
vampirefo for adb and dumchar_info and great advice
snowdream for his udev rule
chainfire for his abdb insecure playstore app
roberts @ tinycorelinux.net for his root id test
Reasons to use include:
A) The Windows USB driver can not be found, maybe a clone
B) You are not quick enough to associate the Windows driver
c) The Flashtool instructions fail for your device.
Why Linux?
Android Preparation
Go into system settings --> Developer Options -> Tick or turn on----USB debugging mode. If you fail to do this, adb command won't work correctly!
Which Windows user are you?
First we need to separate you into 3 main camps
Camp 1 = no working cd/dvd burner or no optical drive. You need to use Windows to image Linux onto an USB stick or install Linux into a virtual machine running on your PC ---not discussed further otherwise this becomes a novel. You can google the answer if you like.
If you lack a burner and optical drive works you could loan a library Linux mag that comes with a cd/dvd or buy one and see if the cd/dvd boots up
Camp 2 = W8 or UEFI enabled with secure boot on. You need to find out if your motherboard will boot an UEFI aware Linux distro. Trouble is, I don't own UEFI bios. You need a 64 bit recent Linux live cd or dvd. Google to see if its UEFI aware please.
Camp 3 = Windows users with UEFI already turned off or an old bios
From now on I will assume you are in Camp 3. With a working burner.
INSTRUCTIONS
Please read all the instructions before starting anything.
1) Find out how to burn an iso image in your version of Windows
google it if not sure. I suggest you buy an dvdrw or cdrw ---depending on size, so if you make a mistake, you don't turn the cd/dvd into a coaster.
eg W7 users may try
2) Download a live Linux cd or dvd. There is lots to choose from. Please choose a debian/Ubuntu/LinuxMint or derived from Debian ---I don't want to show every package management system from the others.
distro=a distribution of Gnu/Linux also known as Linux
So download any you like or if not fussed try this 64 bit distro about 511 Mb
Its system requirements like RAM and video card are shown here
&func=display&sid=39
click on Download mirrors left hand pane if you wish to download from another country or choose KDE which is much larger download.
You may notice my iso download suggestion says amd64 and you may have an intel processor, such as me, its just a name tag. Remember if size of iso is greater than 700 Mb then use a dvd blank please.
Do NOT install this distro please. I want you to consider using only as a live cd.
I use debian sid on my internal hard drive but I don't have time to explain
why you should choose other Linux distros. Its safe to use as a live cd. All factors being equal.
3) Change your bios boot order to boot up the live cd or dvd. Check your motherboard how to do this. Some modern PC have a bios splash screen which tells you which button or button combinations to push.
eg my ECS mobo ---press the delete key.........---my old Dell mobo --press the F2 key.
4) When Linux boots up
(4) What kind of root (superuser) does your Linux use?
(5) Can you see your Andoid device?
Use the Linux menu to open a web browser and view this file ----or Windows users and their browser
Clones not found according to my eyesight. If you can see your device, then jump to step (6) please
If you can not see your device, then we need to show you how to make up a rule
that Linux can use.
5a) Plug your USB data cable into PC and Android.
5b) On Android enable USB storage thru the notifications menu.
5c) Some Linux distros will automatically mount your SD card
and internal storage......while others have a pop box asking you what to do.
mount = make readable a certain device in Linux speak.
For this part of the instructions press cancel if asked to mount your Android device. If you see no popup...don't worry it about....it won't affect the instructions.
5d) In Linux, open a terminal and use what ever method above to get root,
probably sudo su
Code:
sudo su
tail -n 15 /var/log/messages
Do not close the terminal we will use it again shortly.
5e) Now we look at those 15 lines and hope to find a line that will show a different
device to mine (iOcean) but we are looking for the id of the Vendor = maker id
For example one of my output lines is this:
Jun 25 17:22:31 box kernel: usb 3-7: New USB device found, idVendor=0bb4, idProduct=0c03
so we know manufacturer id = 0bb4
5f) Now open a text file in Linux, you may find more than one.
It defaults to a new page. Copy and paste this into the text editor
Quote:#iocean
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="666", GROUP="plugdev"
# symbols indicate nothing on that line is to be actioned by the operating system
---just like Andoid.
Now you change 0bb4 to "something" where something is to the right of idVendor from our command above. The 666 means, when active, that the local user or non-root can use Linux commands to interact with their Android device.
This is different from Flashtool instructions so do not try to mix up my instructions with whatever you read in the past please!
Now click on file, save as.....just like MS word etc and save the file to your home folder as 55-android.rules
Filename is case sensitive, meaning do not use capitals please.
BUT your file will have a formula like this
Quote:#myphone name
SUBSYSTEM=="usb", ATTRS{idVendor}=="string-found-from-commnd", MODE="666", GROUP="plugdev"
If you want to add a second phone you need to follow the same discovery process and edit the same file.
5g) Now back to terminal. It should have opened to the live cd's default home user account ----which is /home/somename. AND you have saved a file under that local name. Lets check with a list command which is "ls" without the quotes
Code:
ls
---> results should include 55-android.rules
(now we do command, copy and paste this to make it easier)
cp 55-android.rules /etc/udev/rules.d/
5h)
Code:
chmod 644 /etc/udev/rules.d/55-android.rules
5i) Ubuntu/LinuxMint users need to refresh this new rule by
Code:
service udev restart
Code:
udevadm control --reload-rules
Code:
systemctl restart udev
Let me know if either method fails as your distro may be using some other service management system. Now leap to (7)....do not reboot.
(6) Your device was showing in link
If this section confuses you, use the manual method in section (5).
6a) Now a download of a zipped package
unzip under Windows, or the super quick way under Linux is
a) open terminal
b) run command
Code:
unzip pack.zip
Here is LinuxMint action in image
It will be the same fast result in Ubuntu or Debian.
There are a heap of graphical unzippers in Linux but they are slower to use,
if interested here is one in the link
After unpack, contents are:
55-android.rules (modified from the 51-android link)
license to re-distribute the 51-android link
and three scripts: --root-checks --nvram --recovery
Which are discussed in Tutorial later.
6b) Now follow the root commands as shown in 5g then 5h and one of the commands ----from 5i to refresh the new rule.
### If you have got to here, well done.
Ideally you now have a Linux USB rule that should work with your device.
7) Now to get the latest adb command
Live cd/dvd are by their nature out-of-date. So we need to update
our package manager.....in Android terms that means sync.
Then we can download the adb command which is in a Linux package.
Code:
apt-get update
apt-get install android-tools-adb
8 USB stick and internal drive discussion
To keep it simple I suggest you have your recovery image on a fat32 USB stick. And use root powers to save your nvram backups to the same fat32 stick,
then copy to Windows and cloud storage.