[X]Assistant

[Bloodyfoxy]

[GUIDE] Backup and restore partitions, firmware recovery, ADB under Linux, good old standard methods ...

Changelog: D

June 12, 2012- creating a theme. backup / restore and firmware recovery
June 13, 2012- added about mount / remount, etc.
June 15, 2012 - coloremNoahwas walking, a little about formatting for ext4 and wipe
June 20, 2012- a script for flash recovery (Linux), mentioned the JDK for the Android SDK
November 25, 2012- Backup applications via ADB, firmware recovery via fastboot, firmware ROM and bootloader via fastboot
November 26, 2012- Learn more about Java on Linux
Hooray! Update after a year!
January 24, 2014- Disassembly boot.img and recovery.img

Everything, now I backup more manually, creating images

Accordingly, it was necessary to do something, or rather restore it. I did it through ODIN, when I left Windows, because there was no choice (I had to back it up) better. How I did it thenhere. However, we will go the other way, as people who are friends with UNIX-like systems.

I will work with Ubuntu 12.04, like linux-ubuntu, so maybe, being a Windows driver, you will not understand everything.
By the way, this is one of the reasons for not using ODIN and Heimdall, for the second is horrible, and the first is purely for Windows. Believe me, the Android SDK gives us everything we need to sew recovery and so on.

What is required

Android SDKfor your platform (estessno)
Java Development kit (JDK)for its platform. I recommend 6.0 / 6.3. You can also download java Runtime Edition (JRE) for everyone.

For Linux Ubuntu (I don’t know the rest)

For 64-bit machines (amd64, x86_64)

sudo apt-get install ia32-libs

Build java

You do not need to install Java from Oracle, you can simply install openjdk by executing the commands

sudo apt-get install openjdk-6-jre openjdk-6-jdk

However, if it is capricious, then download Java 6 (JDK and JRE), creating an account on Oracle. Next in order ...

chmod u + x jre-6-linux- [platform] .bin
./jre-6-linux-[platform[.bin
sudo mkdir -p / usr / lib / jvm
sudo mv jre1.6.0 / usr / lib / jvm /
sudo update-alternatives --install "/ usr / bin / java" "java" "/usr/lib/jvm/jre1.6.0/bin/java" 1
sudo update-alternatives - install "/usr/lib/mozilla/plugins/libjavaplugin.so" "mozilla-javaplugin.so" "/usr/lib/jvm/jre1.6.0_34/lib/i386/libnpjp2.so" 1
sudo update-alternatives --install "/ usr / bin / javaws" "javaws" "/usr/lib/jvm/jre1.6.0/bin/javaws" 1

chmod u + x jdk-6-linux- [platform] .bin
./jdk-6-linux-[platform[.bin
sudo mv jdk1.6.0 / usr / lib / jvm /
sudo update-alternatives --install "/ usr / bin / java" "java" "/usr/lib/jvm/jdk1.6.0/bin/java" 1
sudo update-alternatives --install "/ usr / bin / javac" "javac" "/usr/lib/jvm/jdk1.6.0/bin/javac" 1
sudo update-alternatives --install "/usr/lib/mozilla/plugins/libjavaplugin.so" "mozilla-javaplugin.so" "/usr/lib/jvm/jdk1.6.0/jre/lib/i386/libnpjp2.so" one
sudo update-alternatives --install "/ usr / bin / javaws" "javaws" "/usr/lib/jvm/jre1.6.0/bin/javaws" 1

Now select the newly installed Java by default by executing

sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config mozilla-javaplugin.so
sudo update-alternatives --config javaws

In Linux there is a problem that will not allow us to work with ADB - udev. It is solved simply.

Troubleshooting udev

1. Turn on the development mode on our device. On ICS in the "development" menu, in 2.3.6, like in the "Applications".
   
2. Opens a terminal. We write:
   
   sudo nautilus
   
   we drive in the password of the user, the stub is clear. We have opened the file manager nautilus with root rights. Go along the way/etc/udev/rules.d/
   Create a file with a name, for example51-android.rules.
   Open gedit (text editor, you can, though, any). Enter:
   
   SUBSYSTEM == "usb", ATTR {idVendor} == "0bb4", MODE = "0666", GROUP = "bloodyfoxy"
   
   
   But not all at once!To find out what to write inGROUP =, you need to write in the terminalid.
   He gives me this:
   
   bloodyfoxy @ bloodyfoxy: ~ / android_project / android-sdk-linux / platform-tools $ id
   uid = 1000 (bloodyfoxy) gid = 1000 (bloodyfoxy) groups = 1000 (bloodyfoxy), 4 (adm), 24 (cdrom), 27 (sudo), 30 (dip), 46 (plugdev), 109 (lpadmin), 124 (sambashare)
   
   Accordingly, I take mygid.
   And again, not all!Now you need to know the manufacturer ID for the parameterATTR {idVendor} =
   
   ID

   !!ID may not match. You can learn it then by typing a command
   

   sudo lsusb

   
   We get, for example
   

   Bus 001 Device 005: ID 18d1: 0005 Google Inc

   
   or
   

   Bus 001 Device 005: ID 04e8: 681c Samsung Electronics Co., Ltd Galaxy Portal / Spica / S

   
   18d1and04e8- ID for devices (Meizu and Samsung, who are interested)
   Acer0502
   ASUS0b05
   Dell413c
   Foxconn0489
   Fujitsu04c5
   Fujitsu Toshiba04c5
   Garmin-asus091e
   Google18d1
   Hisense109b
   HTC0bb4
   Huawei12d1
   K-Touch24e3
   KT Tech2116
   Kyocera0482
   Lenovo17ef
   LG1004
   Meizu0492
   Motorola22b8
   Nec0409
   Nook2080
   Nvidia0955
   OTGV2257
   Pantech10a9
   Pegatron1d4d
   Philips0471
   PMC-Sierra04da
   Qualcomm05c6
   SK Telesys1f53
   Samsung04e8
   Sharp04dd
   Sony054c
   Sony Ericsson0fce
   Teleepoch2340
   Toshiba0930
   ZTE19d2
   List taken fromhttp://developer.android.com/guide/developing/device.html(and who will find that I added personally - will receive +).
   The most complete list in my opinion is here:http://cvsweb.netbsd.org/bsdweb.cgi/~check...dev/usb/usbdevs
   
   Save the file.
   
3. We close nautilus, disconnect the phone from USB. We return to the terminal.
   
   service udev restart
   
   Check the rights to the device. We write:
   
   sudo lsusb
   
   We get something like
   
   Bus 001 Device 005: ID 04e8: 681c Samsung Electronics Co., Ltd Galaxy Portal / Spica / S
   
   It is my phone. We write:
   
   sudo ls -l / dev / bus / usb / 001
   
   bus 001 means / dev / bus / usb / 001is the logic clear? Perfectly.
   I answer this:
   
   total 0
   crw-rw-r-- 1 root root 189, June 0 12 18:26 001
   crw-rw-r-- 1 root root 189, 2 June 12 18:26 003
   crw-rw-r-- 1 root root 189, 3 June 12 18:26 004
   crw-rw-rw- + 1 root bloodyfoxy 189, 4 June 12 19:12 005
   
   YES! I have rights to the device.
   

adb: command not found

Easy to solve. In the way where we unpacked the Android SDK (/ android-sdk-linux / platform-tools), we just write./adbshowing the system on a binary file. By the way, you can also add a path to the system to the ADB by writing:

export PATH = $ PATH: / home / [your path] / android-sdk-linux / platform-tools /

But I work calmly, for example: happy:

Install the SDK

In the terminal go to/ android-sdk-linux / tools
Write

./android

Download Android SDK platform-Tools

Permission war

Sometimes it does not want to run this or that file. The problem is solved simply:

sudo chmod 777 [file]

Windows

Download just the driver for your device. Nuggle them. Yeah, trite. But everything will work.
Well, let's launch the SDK and download the platform-tools.

Having received all that we need, let's proceed toto violencebackups and restores.
So, to work with sections, we need to know sections.
Honestly, it’s quite simple to find out where that lies is so simple. Mounted sections look easy, but non-mounted ... Where are they?
So, at least in Samsung, I noticed this trend (with xda-developers)

Look sections!

We sew custom recovery

First, we will find a recovery for our device, download it. Zakinym until downloadedrecovery.imgatplatform-tools

Method 1

Write in the terminal

./adb push recovery.img /sdcard/recovery.img
./adb shell
su
echo in which case we allow the superuser on the device screen. Although the superuser is not required if it goes without it.
dd if = / dev / block / mmcblk0p13 of = / sdcard / recovery_backup.img
echo made a backup of the recovery, now we will sew a new one
dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
exit
exit
./adb reboot recovery

If you have $ PATH or Windows, then write adb without a dot and a slash

method 2, for noobs

Write in the terminal

./adb push recovery.img /sdcard/recovery.img
./adb shell
flash_image / dev / block / mmcblk0p13 /sdcard/recovery.img
exit
./adb reboot recovery

If you have $ PATH or Windows, then write adb without a dot and a slash

Method 3 Linux Script

Script examplehere.
He usesAdband sews in/ dev / block / mmcblk0p13Unlike my tutorial, he uses nodd, butcat. It does not matter. And that writes from a file to a file, and sections in UNIX-systems are represented as files.

Method 4, fastboot

Enter your device in fastboot mode with handles or through

./adb reboot bootloader

And now let's sew

fastboot erase recovery
fastboot flash recovery recovery.img

We sew an image, original images can be flashed the same way, so don’t worry too much about their backup. The main thing is to check whether these images.

Backup and restore

Backup of all useful

We write:

./adb shell
cat / proc / mounts

Get a list of mounted devices. We are important

/ dev / block / mmcblk0p15 / system
/ dev / block / mmcblk0p16 / cache
/ dev / block / mmcblk0p27 / efs
/ dev / block / mmcblk0p17 / data

And also need

/ dev / block / mmcblk0p8 boot
/ dev / block / mmcblk0p13 recovery

We continue:

su
you need to skip the superuser's echo, look at the screen
dd if = / dev / block / mmcblk0p17 of = / sdcard / data.ext4
dd if = / dev / block / mmcblk0p16 of = / sdcard / cache.ext4
dd if = / dev / block / mmcblk0p27 of = / sdcard / efs.img
dd if = / dev / block / mmcblk0p15 of = / sdcard / system.ext4
dd if = / dev / block / mmcblk0p8 of = / sdcard / boot.img
dd if = / dev / block / mmcblk0p13 of = / sdcard / recovery.img
exit
exit

Yeah ... And now how to recover.
Restoring:

./adb shell
su
dd if = / sdcard / data.ext4 of = / dev / block / mmcblk0p17
dd if = / sdcard / cache.ext4 of = / dev / block / mmcblk0p16
dd if = / sdcard / efs.img of = / dev / block / mmcblk0p27
dd if = / sdcard / system.ext4 of = / dev / block / mmcblk0p15
dd if = / sdcard / boot.img of = / dev / block / mmcblk0p8
dd if = / sdcard / recovery.img of / dev / block / mmcblk0p13
exit
exit

We recovered as bekapali, only in the reverse order.

Backing up applications and their data

Saving

./adb backup -apk -shared -all -system -f ~ / backup / backup.ba

Command description

adb backup [-f<file>] [-apk | -noapk] [-shared | -noshared] [-all] [-system | -nosystem] [<packages ...>]
- write to the device<file>.
If no -f option
to "backup.ab" in the current directory.
(-apk | -noapk enable / disable backup of the .apks themselves
in the archive; the default is noapk.)
(-shared | -noshared enable / disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system | -nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages ...>is a list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)

If you do not need to save system applications, select the flag-nosystemin return-system.

пїЅf ~/backup/backup.ba download

then we save to our home folder on our computer.
When creating a backup, a window will appear on the device screen, where we have to enter the backup password. You know what to do)

Now restore:

adb restore ~ ​​/ backup / backup.ba

It does not recover quickly, so do not panic and wait)

Mounting devices

Often, with a hard kill of the firmware, only the recovery is loaded, and if the recovery is not CWM, then it will be very fun to recover, because, I must say, nothing is mounted. For example,I went into the recoveryand./adb shell-new.

bloodyfoxy @ bloodyfoxy: ~ / android_project / android-sdk-linux / platform-tools $ ./adb shell
bloodyfoxy @ bloodyfoxy: ~ / android_project / android-sdk-linux / platform-tools $ ./adb shell
~ # cd sdcard
/ sdcard # ls
/ sdcard # cd ..
~ # mount / sdcard
~ # cd sdcard /
/ sdcard # ls
00005.vcf caustic
00006.vcf ch.amana.android.cputuner
???? ? ? .doc clockworkmod
???????. doc devicefriendlyname.txt
Alarms droidhen
Android external_sd
AppBak foursquare
ApparatusLevels foursquare_photo_tmp.jpg
Bloody.mbworld gameloft
Boat_Browser_Free games
Books gmon
CallLogBackupRestore gscript
CameraZOOM gunman
DCIM layar
DiskCacheIndex-97780911.tmp media
DiskCacheIndex984169234.tmp miner_savegames
Download moduletri
GarageAcidLab neotokyo_recon_nsf.jpg
Kokak ololo.pas
LOST.DIR openfeint
Mem.doc opera
Movies primer.pas
... (well, and further here)

Accordingly, we see that having not mounted a partition, we do not have access to the file system, and therefore to the files. So, we will mount ALL THAT is necessary.

./adb shell
mount / sdcard
mount / system
echo we mounted the system with write permissions immediately (by default). add -r parameter for reading
mount / cache
mount / data
mount / efs
mount / emmc
echo eemc - memory card. Although, it can be mounted differently.

Standard HELP with UNIX

For those who are too lazy to write mount --help

/ sdcard # mount --help
BusyBox v1.19.4-cm9 static (2012-02-05 18:41 +0100) multi-call binary.

Usage: mount [OPTIONS] [-o OPTS] DEVICE NODE

Mount a filesystem. Filesystem autodetection requires / proc.

-a Mount all filesystems in fstab
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount files systems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a] sync Writes are [a] synchronous
[no] atime Disable / enable updates to inode access times
[no] diratime Disable / enable atime updates to directories
[no] relatime Disable / enable atime updates relative to modification time
[no] dev (Dis) allow device of special device files
[no] exec (Dis) allow use of executable files
[no] suid (Dis) allow set-user-id-root programs
[r] shared Convert [recursively] to a shared subtree
[r] slave Convert [recursively] to a slave subtree
[r] private Convert [recursively] to a private subtree
[un] bindable Make mount point [un] able to be bind mounted
[r] bind bind a file or directory [recursively] to another location
move relocate an existing mount point
remount Remount a mounted filesystem, changing flags
ro / rw Same as -r / -w

There are filesystem-specific -o flags.

Unmounting partitions

You can unmount partitions in the same way as you mounted, the command is true, umount (simple, isn't it?). All the same, look higher for more information.

./adb shell
umount / sdcard
umount / system
echo we mounted the system with write permissions immediately (by default). add -r parameter for reading
umount / cache
umount / data
umount / efs
umount / emmc
echo eemc - memory card. Although, it can be mounted differently.

From help

For the lazy type umount --help

/ sdcard # umount --help
BusyBox v1.19.4-cm9 static (2012-02-05 18:41 +0100) multi-call binary.

Usage: umount [OPTIONS] FILESYSTEM | DIRECTORY

Unmount file systems

-r Try to remount devices as read-only if mount is busy
-l Lazy umount (detach filesystem)
-f Force umount (i.e., unreachable NFS server)
-d Free loop device if it has been used

Actually, I would not unmount a partition with the -r option, although ... It depends on the situation. If I stupidly cd-shnili in this directory, why not?
-l - this is how to forcefully pull out a flash drive
-f - and this is quite brazenly "snatch the flash drive"

Remounting with write / read permissions

You may always need to remount something with write / read permissions. This is done by the command

mount -o remount -rw / system

Of course, instead/ systemThere can be any partition that needs to be re-mounted for rewriting. You need to remount it if the device is already mounted. If not, then just mount it with write permissions.

mount -w / system

Mounting partitions from CWM recovery

We clickmounts and storage, there you can mount everything ... But if we mount for the ADB shell, then in my opinion it is easier to do it through itself. Well, if for firmware (something does not want to do), then it can be from there.

Formatting partitions (in development)

In theory, you can not bathe and clean the contents, for example, recovery and boot section so

erase_image / dev / block / [section]

or for the card system (why do you need to clean the system? Although ...)(I’m not sure about that and I don’t want to test it yet)

erase_image / sdcard

Formatting / sdcard, / emmc

Sometimes you realize that you need to format / sdcard
This is done simply.

./adb shell
cat proc / mounts | grep / sdcard

example output:

/ dev / block / vold / 179: 28 / mnt / sdcard vfat rw, dirsync, nosuid, nodev, noexec, relatime, uid = 1000, gid = 1015, fmask = 0702, dmask = 0702,
allow_utime = 0020, codepage = cp437, iocharset = iso8859-1, shortname = mixed, utf8, errors = remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro, relatime, size = 0k, mode = 000 0 0

Now let's format:

mkfs.vfat / dev / block / vold / 179: 28

The memory card (emmc) is also formatted in the same way, just grep it. (cat proc / mounts | grep / emmc)

Formatting under ext4

ext4 is a great journaling FS. Any Linuxer will tell you that it is better than FAT32 and NTFS, which is painfully familiar to Vindauser because they have to constantly defragment them. And we - no: P
So, based on my knowledge, the partitions are formatted in which / system, / cache, / data, / preload, / efs, butlike blocksi.e. For example / dev / block / mmcblk0p16 - my / cache.
Format it? Yeah. I will show the example of the cache.

./adb shell
make_ext4fs / dev / block / mmcblk0p16

Conclusion:

Creating filesystem with parameters:
Size: 62914560
Block size: 4096
Blocks per group: 32768
Inodes per group: 3840
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 15360
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/3840 inodes and 1278/15360 blocks

But we format it with standard parameters.

Options

make_ext4fs [-l<len>] [-j<journal size>] [-b<block_size> ]
[-g<blocks per group>] [-i<inodes>] [-I<inode size> ]
[-L<label>] [-f] [-a<android mountpoint> ]
[-z | -s] [-t] [-w] [-c] [-J]
<filename> [<directory>]

So we ask ourselves from this? I will explain in part.
-bblock size There should be a number in the degree of 2-ki, starting with 512. That is, 512 bytes, 1KB, 2KB, 4KB and further. 4Kb - standard and quite enough for him.
-jlog size. ext4 journaling system same ... Values ​​as in the past case.
-Lname for the section. it is senseless for us to set it up IMHO. Androyd is the same. But for / sdcard, you can only format it in another file system.
-amount point for Android (/ data, / system, etc.). It is very useful if we still decided, for example, to cut down / sdcard for the sake of a cache or something else, because from it we create a file system and a new mount. It is better not to prescribe there values ​​for an unauthorized mount (formatting the cache - mount the cache).
-sdo not display information about the process (silent)

Wipe / system, / data

You can run a wipe of user data and the system ... Teamwipe: D

localhost bin # wipe
wipe<system | data | all>

system means '/ system'
data means '/ data'

The section is in development, because the borers from Google did not want to cram mkfs and will have to use their commands to create file systems.

Color bash-walked (for convenience)

The bash I provided was torn from Cm9. Its version is 4.1.Newer compiles themselves, my compiler does not want for some reason and produces stupid errors. And in the end I get bash under amd64: - / A compiler under ARM.
Downloadbash_shell_4.1_ARM.zip(277.16 KB)
. Extract to platform-tools. In the terminal:

./adb remount
./adb push bash / system / bin / bash
echo or system / xbin / bash
./adb shell
chmod 777 / system / bin / bash
exit

Now we have a colored bash. However, it is runable and will not run by default. Therefore, to look at it, just run it with the "bash" command.

As well as the color on the launch immediately in the terminal emulator

Open on the device "Terminal Emulator", in the settings, select the item "command line" in the "topic" "command shell". We will prescribe:

/ system / bin / bash

those. Where is our BES. We are happy to open a new window.

Post has been editedNatacha - 16.04.15, 18:56

Reason for editing: CHANGELOG!

[Bloodyfoxy]

We sew firmware and bootloader through fastboot

First, download the image of the firmware and bootloader, or recovery or what you want? Usually, the firmware in the disk image is only stock, by the way. So it is very easy to restore stock.
Having a Nexus 7, I will take its firmware as an example.
Factory images for all Google Nexus

Bang inplatform-toolsafter which we will enter your device into fastboot mode with handles, holding a special combination or command

./adb reboot bootloader

Now open the bootloader

fastboot oem unlock

A warning will appear on the screen that when opening the bootloader, all our data will be destroyed. Well, we do not mind them.

Agreeing to clean up sections.

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata

Now we will boot the bootloader, reboot it and flash the image

fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-xxxxx.zip

And close the bootloader (if desired, although I advise you to close and reopen it to avoid problems)

fastboot oem lock

Dismounting boot.img and recovery.img

Just writing)

Post has been editedBloodyfoxy - 24.01.14, 12:59

Reason for editing: Disassembly boot.img and recovery.img

[Anrdaemon]

Stopped reading after "chmod 777"
I ask moderators to hang up a big warning sign on this topic "NEVER DO IT THUS."

[kupass]

What command should I enter to see the sections?

[Findlee]

Kupass @ 07/07/2012, 16:01

What command should I enter to see the sections?

if you are about all sections that are available then:
cat / proc / mtd

[kupass]

maybe
cat / proc / partitions
How under the second spoiler so that with the names?

[DANGER1979]

1. What does it mean when turned on?
Fast Boot Mode U-Boot 1.3.4 SMDKC110 N Type

2. When flashing what window should appear with what choice?

3. How to save and than the current firmware. So that you could then go back to her?

4. How are firmware image files viewed? system.img, etc.

[DANGER1979]

1. Do you need to unlock the bootloader?
2. How to know that it is blocked?
3. which program is safe to unblock it?

[xabk]

There is a ZTE V880E phone. You need to merge the original recovery.img from it. I have already tried many ways to get no working recovery, help: blush:

[Bloodyfoxy]

xabk,
It merges as a partition image, just copied by cat or dd. You just need to know in which section the recovery lies ... And initially only the manufacturer knows this.

AnrDaemon @ 07/04/2012, 21:41

Stopped reading after "chmod 777"

My laziness is limitless. True to me too lazy to write a + x.

DANGER1979 @ 07/21/2012, 10:46 PM

2. When flashing what window should appear with what choice?

3. How to save and than the current firmware. So that you could then go back to her?

4. How are firmware image files viewed? system.img, etc.

2. LOLTO?
3. cat, dd to help. Take images of system, boot, cache, data
4. Mounted as a disk to the system.

mount -o loop -t / media / floppy1
umount / media / floppy1

To do with the root. Mounts as a floppy, the second unmounts. If not mounted, create the folder / media / floppy1 as root (sudo will do)

DANGER1979 @ 07/22/2012, 10:44

1. Do you need to unlock the bootloader?
2. How to know that it is blocked?
3. which program is safe to unblock it?

1. Not always. Depends on the situation. You can enter the recovery - cool, do not.
2. ...
3. Usually written in the developer's developer area.

[Rstop]

I would be very grateful if you tell me how to act in my case, how can I open root-rights to mount internal memory (samsung gt-s5830 android 2.3.3) in Windows or Macos? I would like to use data recovery software, both for regular flash and hdd media. Objective: Try to restore contacts (data / data / com.android.providers.contacts / databases / contacts.db), reset after setting the factory settings on the device. Synchronized Contacts with gmail for some reason are not available on the server. At the moment, root access is open, I cling adb, various manipulations with the mount command do not lead to anything. What I want to do at all possible?

[boTbl4]

I can not find boot, the list is missing
http://i40.fastpic.ru/big/2012/0905/c6/e8b...b5f15af8ac6.png
sections

cat / proc / partitions

major minor #blocks name

7 0 14585 loop0
7 1 2111 loop1
7 2 13545 loop2
7 3 26019 loop3
7 4 14585 loop4
7 5 20822 loop5
7 6 23940 loop6
179 0 3792000 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 408576 mmcblk0p3
179 4 408576 mmcblk0p4
179 5 854016 mmcblk0p5
179 6 2084064 mmcblk0p6
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 15554048 mmcblk1p1
254 0 14584 dm-0
254 1 2110 dm-1
254 2 13545 dm-2
254 3 26019 dm-3
254 4 14584 dm-4
254 5 20821 dm-5
254 6 23940 dm-6

ls

ls
acct
advanced_meta_init.project.rc
advanced_meta_init.rc
cache
config
d
data
default.prop
dev
emmc @ android
emmc @ cache
emmc @ ebr1
emmc @ fat
emmc @ sec_ro
emmc @ usrdata
etc
init
init.aee.customer.rc
init.factory.rc
init.goldfish.rc
init.project.rc
init.rc
init.usb.rc
init.xlog.rc
meta_init.rc
mnt
proc
res
root
sbin
sdcard
sys
system
ueventd.goldfish.rc
ueventd.rc
vendor

ls -l / dev

ls / dev -l
crw ------- root root 253, 0 2012-09-05 16:07 BOOT
crw ------- root root 237, 0 2012-09-05 16:07 FM50AF
crw-rw-rw- root root 188, 0 2012-09-05 16:07 M4U_device
crw ------- root root 251, 0 2012-09-05 16:07 MT6575-SMIMonitor
crw ------- root root 243, 0 2012-09-05 16:07 MTK_MAU
crw ------- root root 249, 0 2012-09-05 16:07 MT_pmic_adc_cali
crw-rw-rw- root root 160, 0 2012-09-05 16:07 Vcodec
crw ------- root root 242, 0 2012-09-05 16:07 accdet
crw ------- root root 10, 34 2012-09-05 16:07 aed0
crw ------- root root 10, 33 2012-09-05 16:07 aed1
crw-rw-r-- system radio 10, 59 2012-09-05 16:07 alarm
crw-rw-rw- root root 10, 43 2012-09-05 16:07 als_ps
crw-rw-rw- root root 151, 0 2012-09-05 16:07 ampc0
crw ------- root root 239, 14 2012-09-05 16:07 android
crw-rw ---- adb adb 10, 37 2012-09-05 16:07 android_adb
crw-rw-rw- root root 10, 60 2012-09-05 16:07 ashmem
crw-rw-rw- root 10, 58 2012-09-05 16:07 binder
drwxr-xr-x root root 2012-09-05 16:08 block
crw ------- root root 239, 18 2012-09-05 16:07 bmtpool
crw ------- root root 239, 8 2012-09-05 16:07 bootimg
crw-rw ---- bluetooth bluetooth 246, 0 2012-09-05 16:07 btn
crw ------- root root 239, 15 2012-09-05 16:07 cache
crw ------- root root 235, 0 2012-09-05 16:07 camera-eis
crw ------- root root 252, 0 2012-09-05 16:07 camera-fdvt
crw-rw-rw- root root 236, 0 2012-09-05 16:07 camera-isp
crw-rw-rw- root root 232, 0 2012-09-05 16:07 camera-resmgr
crw-rw-rw- root root 234, 0 2012-09-05 16:07 camera-sysram
crw-rw-rw- root root 184, 0 2012-09-05 16:07 ccci
crw-rw ---- root root 178, 0 2012-09-05 16:07 ccci_fs
crw ------- root root 183, 0 2012-09-05 16:07 ccci_ipc_135_0
crw-rw-rw- root root 184, 42 2012-09-05 16:07 ccci_md_log_rx
crw-rw-rw- root root 184, 43 2012-09-05 16:07 ccci_md_log_tx
crw-rw-rw- root root 184, 4 2012-09-05 16:07 ccci_pcm_rx
crw-rw-rw- root root 184, 5 2012-09-05 16:07 ccci_pcm_tx
crw ------- root root 184, 2 2012-09-05 16:07 ccci_sys_rx
crw ------- root root 184, 3 2012-09-05 16:07 ccci_sys_tx
crw ------- root root 184, 6 2012-09-05 16:07 ccci_uart1_rx
crw ------- root root 184, 7 2012-09-05 16:07 ccci_uart1_rx_ack
crw-rw-rw- root root 184, 18 2012-09-05 16:07 ccci_uem_rx
crw-rw-rw- root root 184, 19 2012-09-05 16:07 ccci_uem_tx
crw ------- root root 5, 1 2012-09-05 16:31 console
crw ------- root root 10, 40 2012-09-05 16:07 cpu_dma_latency
drwxr-xr-x system system 2012-09-05 16:07 cpuctl
crw ------- root root 10, 236 2012-09-05 16:07 device-mapper
crw-rw-rw- root root 176, 0 2012-09-05 16:07 drvb
crw ------- root root 239, 1 2012-09-05 16:07 dsp_bl
crw ------- root root 244, 0 2012-09-05 16:07 dummy_eeprom
crw-rw ---- root audio 10, 52 2012-09-05 16:07 eac
crw ------- root root 239, 3 2012-09-05 16:07 ebr1
crw ------- root root 239, 13 2012-09-05 16:07 expdb
crw ------- root root 239, 17 2012-09-05 16:07 fat
crw-rw-rw- root root 193, 0 2012-09-05 16:07 fm
crw-rw-rw- root root 1, 7 2012-09-05 16:07 full
crw ------- root root 10, 229 2012-09-05 16:07 fuse
crw-rw-rw- root root 233, 0 2012-09-05 16:07 gps
drwxr-xr-x root root 2012-09-05 16:07 graphics
crw-rw-rw- root root 10, 44 2012-09-05 16:07 gsensor
crw-rw ---- bluetooth bluetooth 10, 46 2012-09-05 16:07 hid-keyboard
crw-rw-rw- root root 10, 45 2012-09-05 16:07 hwmsensor
drwxr-xr-x root root 2012-09-05 16:07 input
crw-rw-rw- root root 245, 0 2012-09-05 16:07 kd_camera_flashlight
crw ------- root root 238, 0 2012-09-05 16:07 kd_camera_hw
crw ------- root root 1, 2 2012-09-05 16:07 kmem
crw ------- root root 1, 11 2012-09-05 16:07 kmsg
drwxr-xr-x root root 2012-09-05 16:07 log
crw ------- root root 239, 12 2012-09-05 16:07 logo
crw ------- root root 239, 2 2012-09-05 16:07 mbr
crw ------- root root 1, 1 2012-09-05 16:07 mem
crw ------- root root 239, 11 2012-09-05 16:07 misc
crwxrwxrwx root root 10, 53 2012-09-05 16:07 misc-sd
crw-rw-rw- root root 241, 0 2012-09-05 16:07 mt6575-MDP
crw-rw-rw- root root 10, 47 2012-09-05 16:07 mtgpio
crw ------- root root 240, 0 2012-09-05 16:07 mtk-adc-cali
crw-rw-rw- root root 10, 42 2012-09-05 16:07 mtk-kpd
crw-rw-rw- root root 250, 0 2012-09-05 16:07 mtk_jpeg
crw ------- root root 10, 62 2012-09-05 16:07 mtk_monitor
crw-rw ---- root mtp 10, 36 2012-09-05 16:07 mtp_usb
crw ------- root root 10, 39 2012-09-05 16:07 network_latency
crw ------- root root 10, 38 2012-09-05 16:07 network_throughput
crw-rw-rw- root root 1, 3 2012-09-05 16:07 null
crw ------- root root 239, 5 2012-09-05 16:07 nvram
crw ------- root root 10, 61 2012-09-05 16:07 ple
crw ------- root root 239, 4 2012-09-05 16:07 pmt
crw-rw ---- radio vpn 108, 0 2012-09-05 16:07 ppp
crw ------- root root 239, 0 2012-09-05 16:07 preloader
crw ------- root root 10, 1 2012-09-05 16:07 psaux
crw-rw-rw- root root 5, 2 2012-09-05 20:26 ptmx
drwxr-xr-x root 1970-01-01 04:00 pts
lrwxrwxrwx root radio 2012-09-05 16:07 ptty2cmd1 ->/ dev / pts / 7
lrwxrwxrwx root radio 2012-09-05 16:07 ptty2cmd2 ->/ dev / pts / 8
lrwxrwxrwx root radio 2012-09-05 16:07 ptty2cmd3 ->/ dev / pts / 9
lrwxrwxrwx root radio 2012-09-05 16:07 ptty2data ->/ dev / pts / 5
lrwxrwxrwx root radio 2012-09-05 16:07 ptty2noti ->/ dev / pts / 6
lrwxrwxrwx root radio 2012-09-05 16:07 pttycmd1 ->/ dev / pts / 2
lrwxrwxrwx root radio 2012-09-05 16:07 pttycmd2 ->/ dev / pts / 3
lrwxrwxrwx root radio 2012-09-05 16:07 pttycmd3 ->/ dev / pts / 4
lrwxrwxrwx root radio 2012-09-05 16:07 pttydata ->/ dev / pts / 0
lrwxrwxrwx root radio 2012-09-05 16:07 pttynoti ->/ dev / pts / 1
lrwxrwxrwx root radio 2012-09-05 16:07 pttyvt ->/ dev / pts / 10
crw ------- root root 2, 0 2012-09-05 16:07 ptyp0
crw ------- root root 2, 1 2012-09-05 16:07 ptyp1
crw ------- root root 2, 2 2012-09-05 16:07 ptyp2
crw ------- root root 2, 3 2012-09-05 16:07 ptyp3
crw ------- root root 2, 4 2012-09-05 16:07 ptyp4
crw ------- root root 2, 5 2012-09-05 16:07 ptyp5
crw ------- root root 2, 6 2012-09-05 16:07 ptyp6
crw ------- root root 2, 7 2012-09-05 16:07 ptyp7
crw ------- root root 2, 8 2012-09-05 16:07 ptyp8
crw ------- root root 2, 9 2012-09-05 16:07 ptyp9
crw ------- root root 2, 10 2012-09-05 16:07 ptypa
crw ------- root root 2, 11 2012-09-05 16:07 ptypb
crw ------- root root 2, 12 2012-09-05 16:07 ptypc
crw ------- root root 2, 13 2012-09-05 16:07 ptypd
crw ------- root root 2, 14 2012-09-05 16:07 ptype
crw ------- root root 2, 15 2012-09-05 16:07 ptypf
crw-rw-rw- root 230, 0 2012-09-05 16:07 pvrsrvkm
crw-rw-rw- root 1, 8 2012-09-05 16:07 random
crw ------- root root 239, 9 2012-09-05 16:07 recovery
crw-rw ---- root 10, 63 2012-09-05 16:07 rfkill
crw ------- root root 254, 0 2012-09-05 16:07 rtc0
crw-rw ---- root root 182, 0 2012-09-05 16:07 sec
crw ------- root root 239, 10 2012-09-05 16:07 sec_ro
crw ------- root root 239, 6 2012-09-05 16:07 seccfg
drwxr-xr-x root root 2012-09-05 19:03 socket
crw ------- root root 248, 0 2012-09-05 16:07 spc
crw-rw-rw- root root 192, 0 2012-09-05 16:07 stpbt
crw-rw ---- root root 191, 0 2012-09-05 16:07 stpgps
crw-rw ---- system system 190, 0 2012-09-05 16:07 stpwmt
crw-rw-r-- root 10, 41 2012-09-05 16:07 touch
crw ------- root root 10, 49 2012-09-05 16:07 tpd_em_log
crw-rw-rw- root root 5, 0 2012-09-05 16:07 tty
crw-rw ---- root system 4, 0 2012-09-05 16:07 tty0
crw ------- root root 4, 1 2012-09-05 16:07 tty1
crw ------- root root 4, 10 2012-09-05 16:07 tty10
crw ------- root root 4, 11 2012-09-05 16:07 tty11
crw ------- root root 4, 12 2012-09-05 16:07 tty12
crw ------- root root 4, 13 2012-09-05 16:07 tty13
crw ------- root root 4, 14 2012-09-05 16:07 tty14
crw ------- root root 4, 15 2012-09-05 16:07 tty15
crw ------- root root 4, 16 2012-09-05 16:07 tty16
crw ------- root root 4, 17 2012-09-05 16:07 tty17
crw ------- root root 4, 18 2012-09-05 16:07 tty18
crw ------- root root 4, 19 2012-09-05 16:07 tty19
crw ------- root root 4, 2 2012-09-05 16:07 tty2
crw ------- root root 4, 20 2012-09-05 16:07 tty20
crw ------- root root 4, 21 2012-09-05 16:07 tty21
crw ------- root root 4, 22 2012-09-05 16:07 tty22
crw ------- root root 4, 23 2012-09-05 16:07 tty23
crw ------- root root 4, 24 2012-09-05 16:07 tty24
crw ------- root root 4, 25 2012-09-05 16:07 tty25
crw ------- root root 4, 26 2012-09-05 16:07 tty26
crw ------- root root 4, 27 2012-09-05 16:07 tty27
crw ------- root root 4, 28 2012-09-05 16:07 tty28
crw ------- root root 4, 29 2012-09-05 16:07 tty29
crw ------- root root 4, 3 2012-09-05 16:07 tty3
crw ------- root root 4, 30 2012-09-05 16:07 tty30
crw ------- root root 4, 31 2012-09-05 16:07 tty31
crw ------- root root 4, 32 2012-09-05 16:07 tty32
crw ------- root root 4, 33 2012-09-05 16:07 tty33
crw ------- root root 4, 34 2012-09-05 16:07 tty34
crw ------- root root 4, 35 2012-09-05 16:07 tty35
crw ------- root root 4, 36 2012-09-05 16:07 tty36
crw ------- root root 4, 37 2012-09-05 16:07 tty37
crw ------- root root 4, 38 2012-09-05 16:07 tty38
crw ------- root root 4, 39 2012-09-05 16:07 tty39
crw ------- root root 4, 4 2012-09-05 16:07 tty4
crw ------- root root 4, 40 2012-09-05 16:07 tty40
crw ------- root root 4, 41 2012-09-05 16:07 tty41
crw ------- root root 4, 42 2012-09-05 16:07 tty42
crw ------- root root 4, 43 2012-09-05 16:07 tty43
crw ------- root root 4, 44 2012-09-05 16:07 tty44
crw ------- root root 4, 45 2012-09-05 16:07 tty45
crw ------- root root 4, 46 2012-09-05 16:07 tty46
crw ------- root root 4, 47 2012-09-05 16:07 tty47
crw ------- root root 4, 48 2012-09-05 16:07 tty48
crw ------- root root 4, 49 2012-09-05 16:07 tty49
crw ------- root root 4, 5 2012-09-05 16:07 tty5
crw ------- root root 4, 50 2012-09-05 16:07 tty50
crw ------- root root 4, 51 2012-09-05 16:07 tty51
crw ------- root root 4, 52 2012-09-05 16:07 tty52
crw ------- root root 4, 53 2012-09-05 16:07 tty53
crw ------- root root 4, 54 2012-09-05 16:07 tty54
crw ------- root root 4, 55 2012-09-05 16:07 tty55
crw ------- root root 4, 56 2012-09-05 16:07 tty56
crw ------- root root 4, 57 2012-09-05 16:07 tty57
crw ------- root root 4, 58 2012-09-05 16:07 tty58
crw ------- root root 4, 59 2012-09-05 16:07 tty59
crw ------- root root 4, 6 2012-09-05 16:07 tty6
crw ------- root root 4, 60 2012-09-05 16:07 tty60
crw ------- root root 4, 61 2012-09-05 16:07 tty61
crw ------- root root 4, 62 2012-09-05 16:07 tty62
crw ------- root root 4, 63 2012-09-05 16:07 tty63
crw ------- root root 4, 7 2012-09-05 16:07 tty7
crw ------- root root 4, 8 2012-09-05 16:07 tty8
crw ------- root root 4, 9 2012-09-05 16:07 tty9
crw-rw ---- root root 169, 0 2012-09-05 20:08 ttyC0
crw ------- root root 169, 1 2012-09-05 16:07 ttyC1
crw ------- root root 169, 2 2012-09-05 16:07 ttyC2
crw ------- root root 231, 0 2012-09-05 16:07 ttyGS0
crw ------- root root 231, 1 2012-09-05 16:07 ttyGS1
crw ------- root root 231, 2 2012-09-05 16:07 ttyGS2
crw ------- root root 231, 3 2012-09-05 16:07 ttyGS3
crw ------- root root 204, 209 2012-09-05 16:07 ttyMT0
crw ------- root root 204, 210 2012-09-05 16:07 ttyMT1
crw-rw-rw- system system 204, 211 2012-09-05 16:07 ttyMT2
crw ------- root root 204, 212 2012-09-05 16:07 ttyMT3
crw ------- root root 3, 0 2012-09-05 16:07 ttyp0
crw ------- root root 3, 1 2012-09-05 16:07 ttyp1
crw ------- root root 3, 2 2012-09-05 16:07 ttyp2
crw ------- root root 3, 3 2012-09-05 16:07 ttyp3
crw ------- root root 3, 4 2012-09-05 16:07 ttyp4
crw ------- root root 3, 5 2012-09-05 16:07 ttyp5
crw ------- root root 3, 6 2012-09-05 16:07 ttyp6
crw ------- root root 3, 7 2012-09-05 16:07 ttyp7
crw ------- root root 3, 8 2012-09-05 16:07 ttyp8
crw ------- root root 3, 9 2012-09-05 16:07 ttyp9
crw ------- root root 3, 10 2012-09-05 16:07 ttypa
crw ------- root root 3, 11 2012-09-05 16:07 ttypb
crw ------- root root 3, 12 2012-09-05 16:07 ttypc
crw ------- root root 3, 13 2012-09-05 16:07 ttypd
crw ------- root root 3, 14 2012-09-05 16:07 ttype
crw ------- root root 3, 15 2012-09-05 16:07 ttypf
crw-rw ---- system vpn 10, 200 2012-09-05 16:07 tun
crw ------- root root 239, 7 2012-09-05 16:07 uboot
crw-rw ---- system net_bt_admin 10, 223 2012-09-05 16:07 uinput
crw-rw-rw- root root 1, 9 2012-09-05 16:07 urandom
crw-rw ---- root usb 10, 35 2012-09-05 16:07 usb_accessory
crw ------- root root 239, 16 2012-09-05 16:07 usrdata
crw ------- root root 7, 0 2012-09-05 16:07 vcs
crw ------- root root 7, 1 2012-09-05 16:07 vcs1
crw ------- root root 7, 128 2012-09-05 16:07 vcsa
crw ------- root root 7, 129 2012-09-05 16:07 vcsa1
crw ------- root root 247, 0 2012-09-05 16:07 watchdog
crw-rw-rw- root root 10, 51 2012-09-05 16:07 xLog
crw-r - r-- root 10, 48 2012-09-05 16:07 xt_qtaguid
crw-rw-rw- root root 1, 5 2012-09-05 16:07 zero

there is a scatter file

PRELOADER 0x0
{
}
DSP_BL 0x40000
{
}
MBR 0x600000
{
}
EBR1 0x604000
{
}
__NODL_PMT 0x608000
{
}
__NODL_NVRAM 0xa08000
{
}
__NODL_SECCFG 0xf08000
{
}
UBOOT 0xf28000
{
}
BOOTIMG 0xf88000
{
}
RECOVERY 0x1588000
{
}
SEC_RO 0x1b88000
{
}
__NODL_MISC 0x2188000
{
}
LOGO 0x21e8000
{
}
__NODL_EXPDB 0x24e8000
{
}
ANDROID 0x26e8000
{
}
CACHE 0x1b6e8000
{
}
USRDATA 0x346e8000
{
}
__NODL_FAT 0x689e8000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}

which devices are system, cache, efi, data? bootimg is it a boot
Chinese smartphone Thl W3 Dual Core, Android 4.0.4

Post has been editedboTbl4 - 05.09.12, 19:47

[Bloodyfoxy]

Rstop,
You make a bootable USB flash drive with Linux, or you make it under a Mac (like you can).
Take a disk image that is mounted as data (learn "cat proc / mounts"), remove dd or cat, and then mount it to the computer as described above. Throw the right, unmount the image, shove back the same way.
boTbl4,
/ proc / mounts shows you system, cache, data
bootimg - boot most likely (skopiraste image, look what is there)
I don't know about efi yet.

[fazergoo]

boTbl4,

cat / proc / dumchar_info

This time, the output is something like this:

preloader 0x0000000000040000 0x000000000000000000 2 / dev / misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 / dev / misc-sd
mbr 0x0000000000004000 0x000000000000000000 2 / dev / block / mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 / dev / block / mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 / dev / block / mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 / dev / block / mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 / dev / block / mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 / dev / block / mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 / dev / block / mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 / dev / block / mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 / dev / block / mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 / dev / block / mmcblk0
logo 0x0000000001400000 0x0000000001a40000 2 / dev / block / mmcblk0
expdb 0x00000000000a0000 0x0000000002e40000 2 / dev / block / mmcblk0
ebr2 0x0000000000004000 0x0000000002ee0000 2 / dev / block / mmcblk0
android 0x0000000020100000 0x0000000002ee4000 2 / dev / block / mmcblk0p6
cache 0x0000000020100000 0x0000000022fe4000 2 / dev / block / mmcblk0p2
usrdata 0x0000000020100000 0x00000000430e4000 2 / dev / block / mmcblk0p3
fat 0x000000016dffc000 0x00000000631e4000 2 / dev / block / mmcblk0p4
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 / dev / block / mmcblk0

on MTK65XX boot.img recovery.img and much more needed for backup and firmware are in the same block mmcblk0 These are two,
how to get them out wrotehere, but this is for a specific device, in your case offsets (skip = ...) you need to look at the scatter file, but with the number of blocks (count = ...) - more difficult
Write downeverythingback through dd, it will not work even with the rights of a super-duper user, and the fastboot mode does not include and does not sew animals on MTK65XX except through the SP flash tool or SPMDT. These are three.

Post has been editedfazergoo - 09.11.12, 12:41

[pashk]

there is an Android phone without root
The SDK works great.
Windows platform.

Question:
Are there ways to access sections of the phone to which access denied?

And it turns out like this:
shell @ android: / $ dd if = / dev / block / mmcblk0p3 of = / mnt / extSdCard / efs.img
dd if = / dev / block / mmcblk0p3 of = / mnt / extSdCard / efs.img
/ dev / block / mmcblk0p3: cannot open for read: Permission denied

Is there a way to get around without installing root?

Thanks in advance.

[fazergoo]

pashk @ 11/09/2012, 09:34

Is there a way to get around without installing root?

adb root what answers? If the answer is negative, then the temporary root:

пїЅ

Temporary root

- in the terminal:
пїЅ пїЅ

adb shell mv / data / local / tmp /data/local/tmp.bak

temporarily save the contents of / data / local / tmp in another file
пїЅ пїЅ

adb shell ln -s / data / data / local / tmp

create a symbolic link for / data to allow writing there
пїЅ пїЅ

adb reboot

here is a small hitch, for some reason, with the adb reboot command, my tablet completely turned off and turned on only after reset with a toothpick: D
- After turning on the tablet in the terminal:
пїЅ пїЅ

adb shell rm /data/local.prop> nul

delete the original local.prop file
пїЅ пїЅ

adb shell "echo \" ro.kernel.qemu = 1 \ "> /data/local.prop"

create a new local.prop
пїЅ пїЅ

adb reboot

turning on again through a toothpick
- After turning on the tablet in the terminal:
пїЅ пїЅ

adb shell id

if we get uid 0 / root then everything is in order, there is a temporary root

thereafter
mount -o remount rw / dev
do all dd (just don't confuse if and of!) and back
mount -o remount ro / dev

[Bloodyfoxy]

fazergoo
You can also get a temporary root using the zerg rush exploit (from a typical Doomlordovsky root).
To do this, type a binary in tmp and run it, run in advance chmod a + x to it.

Post has been editedBloodyfoxy - 14.11.12, 09:53

[fazergoo]

BloodyFoxy,No sourse no trust: D
I'm not paranoid about security, but why use something third-party when you can do it with the SDK? Moreover, the topic is just for this and that;)

[Bloodyfoxy]

fazergooyes just laziness sometimes attacks do long steps: D

[fazergoo]

Yes, you can use the script, there are ready-made ones on the network or you can write it yourself;

[fazergoo]

alexseyuhThis topic is called

Backup and restore partitions, firmware recovery, ADB underLinux

LIIIIINUX!

And the author of that article or Windows such or hands
His VID (Vendor ID) is the same and the PID (Product ID) for some reason has changed. On masday, this can happen even if the device is connected to one USB port during the installation of firewood and then for some reason turned on the other.
By the way, I connected my business plank to Windows on different computers, it works everywhere, and the options that define ADB firewood are:

Android Composite ADB Interface
Google ADB interface
and, ahtung,
HTC DESIRE: D
Well, the Chinese have registered in init.usb.rc:
setprop sys.usb.vid 0BB4
and this vid is assigned to the NTS