www.chinaphonearena.com

This post is designed to reduce the size of a tutorial under construction.
Its not essential to the tutorial but might reduce questions, not that I expect to be inundated....giggles

NOT ALL cross linking done at this stage

Why Linux?
A live cd or dvd or usb stick install of Linux does not have to be installed to your internal hard drive. -----This does affect the speed (roughly the order is)
floppy is slowest, live cd, live dvd, hard drives installs, RAM drive systems.

Some live cds are slow to load but load completely into RAM. Linux uses a completely different Android device detection ---in Windows terms, it means you don't need a Windows driver.

Some Linux live cds are designed for Admin work and not for general purpose. etc.
So look for desktop cds or dvds. You can see heaps at ttp://www.distrowatch.com
Linux does not need some kind of speed to associate Android device to Linux PC.

Source link
[Only registered and activated users can see links Click here to register]

(4) What kind of root (superuser) does your Linux use?
Linux distro fall into
camp 1 root gained thru command = sudo su
Ubuntu and LinuxMint type distros prefer you use
but I need you to use sudo su as my tutorial expects it, for the next line, where relevant.

camp 2 root gained thru command = su
(and you are expected to know the password)
----Note in Android, there is no password.

camp 3 root only cds such as Puppy. Do not download it for this tutorial please as it does not use debian commands by default.

source link = section (4)
[Only registered and activated users can see links Click here to register]

how to unzip

Method 1
Open a terminal and run the command

Method 2 is more suited to Windows users?
Click on the zip link
[Only registered and activated users can see links Click here to register]



Depending on distro will start either a download popup box or a popup box that offers to manage zip with a decrompression tool



After zip file is downloaded zip tool will unpack zip but not yet know where to save.
Hold down the control key and press a key to select ALL files then click on the extract button



A new dialog box asks where to?
Aptosid defaults to /tmp but that means you have to change directory before you type commands....so I prefer you save to home folder

Quick typers can type it in ..../home/name-of-local-user
(on aptosid live cd ---its aptosid)

slow typers can click on the button on the right hand side and choose the home folder. ----now click on the EXTRACT button


You now see a popup box where it will be saved to and click on open


Optional
You have completed task. You can review your success in the file manager at the home folder as per image



source link section (6a)
[Only registered and activated users can see links Click here to register]

How Linux treats internal hard drives and USB data media
distro = Gnu/Linux distribution

There is no universal rule but modern distros fall into:
camp 1
auto detection and auto mount under either:
/media/something
/mnt/sdxn
eg sda1 means a=first detected (internal) drive, 1= first partition.
Each drive is given a letter, each partition a number.

Local user can read but only root can write. (Very safe)

camp 2
auto detection and additional entries placed into /etc/fstab
---check it with command
cat /etc/fstab

to read the device manual command ----example only

camp 3
manual commands


Back to Windows stuff
So if you have downloaded into your Windows system your "target"
recovery image, I suggest you use your Windows Explorer to find
the exact pathway in C partition or D partition speak
eg c:\users\\ Documents\

Apparently "My" is being dropped in W7.
Apparently W8 may use Libraries

USB sticks or cables to external hard drives
When you buy an USB stick in Australia (made in China) it tends to be fat32 (LBA)
Some Windows users tend to re-format as exfat or NTFS. To swap between a Linux and
Windows for safe rw I suggest you only use fat32. For Linux, find usb sticks in
your file manager under /media or /mnt ---same as internal drives.

root powers
So for any distro, once we have mounted an USB stick or internal drive we can be sure
that we can write to the device using root powers.

I am sure Android users can spot some of these commands work under Android as well.

source link section (8)
[Only registered and activated users can see links Click here to register]

True root images
Before we show errors lets look at a good result
--You have USB debugging turned on.
--You may have a insecure kernel or had to used abdb insecure app
--No need to turn on USB storage, but if you do, it does not affect the tests.


Errors
I have not mentioned in error message that empty line is also
caused by not turning on USB debug......this is a read it test.

Below image permission denied is because of secure mode boot. Bypass it if you have the skills with an insecure mode kernel or better still install and turn on adbd insecure.

Quote:Permission denied

Below is another permission error. The top line of the image shows we already have rw status, but attempt to write to Android fails with a new permission error
----both were solved by using the google app.

Quote:failed to copy 'aus9' to '/system/aus9': Permission denied

Below image is you had the su (superuser) executable but the ROM maker left your system in read only mode. This is actually safer, but I assume you want to write to your flash device so need read-write mode.


Below image is a double effect. At top I am attempting to show that if you have a group permission error....my old phone had it, you will have problems

At bottom of image, I am attempting to show correct owner/group and owner/group permissions for writing to /system


One last error is a Linux error when your network fails. run
as a root user. If you do not see lo then you have a network error. This may occur if you have recently updated your network tools or made changes there without checking on what you are doing.

Occassionally its because something else is using the abd port. This should not happen if you are the only user!


source link
[Only registered and activated users can see links Click here to register]

Recovery script has a backup option

The command to run is

Note that this will always produce a same size image no matter what size you originally installed. And it will be the maximum byte size you input through the script.

I am not expecting many people to use this function so its hidden here in the link.

Start


Now just like nvram, we need to input a decimal number
This is likely to be larger than your nvram number.

Just like nvram script its safer to use copy and paste in the terminal where ever possible.


Again please pay attention to the byte size input.

Assuming you have accepted the input we have


source link was
[Only registered and activated users can see links Click here to register]