Android applications. Samsung i9000 series (3). You do not need to brush your machine to easily obtain root permissions.

Android app. Samsung i9000 series guide (3). You do not need to brush your machine to easily obtain root permissions

Papaya 20110403

I. Preface

I have been busy with my work for just a few days since I purchased a mobile phone. Occasionally open at night
WiFi, suddenly found that the connection is not connected. Wifi is always at the IP address acquisition stage. Used to be
Good, no problem. At this time, I remembered that a friend of mine, Motorola me811, was also connected to wifi.
.
Obviously, this should be a problem of the anriod system itself. When I googled the Internet, I found that many netizens
There are two solutions to this problem: one is to use a static IP address, and the other is to delete/data/MISC/DHCP.
Files. I tried static IP, but it seems that it still does not work. I had to try the second method. The second method
It seems "simple", but you must first obtain the root permission!

Ii. root permissions

We know that android is based on Linux, and the highest privilege of this operating system is root! Count
For example, without root, it is like buying a villa, but only giving the key to the garage! Most people
No, so obtaining the highest permission is required!

3. Get root permissions

I9000 has been released for one year, and the operating systems are open-source. It is estimated that it has been thoroughly studied for a long time.
Think about Google without hesitation. The information on the Internet is still messy, and a lot of content is unreliable. Simplified
I sorted it out in the following ways:

1. Use z4root Software
2. Update update.zip using Android Recovery System
3. Use superoneclick
4. fl the ROM that supports Root

The following is a brief process:

1. z4root

Here we downloaded z4root (Version: z4root1.3.0) and performed the one-click root operation.
For details, see:

Getting Root Using z4root milestone 2 full tutorial
Http://tech.sina.com.cn/mobile/n/2010-12-24/06381611116.shtml

Although the above mentioned is the moto milestone 2, it is exactly the same for Samsung i9000! Select permanent
After root, the phone will be restarted. Use root explorer later (use version: rootexplorer_2.14.2)
Browse the file and find that the/data directory is still empty. To determine whether the root permission is obtained successfully, you only need
Whether the follow/data directory is empty. /If data is blank, the root permission cannot be obtained!

Then I changed z4root version (z4root1.2.1! It can only be noted that, although z4root
Many Samsung i9000 instances are available, but z4root does not work on the machine!

Local software version information:
Model: GT-I9000
Android: 2.2
Baseband version: i9000zsjpe
Kernel version: 2.6.32.9 root @ SE-S506 #3
Version: froyo. zsjpd

2. Update update.zip using Android Recovery System

If the z4rootline is not available, you can only try to update update.zip. For details, refer:

Method 2 of Samsung Galaxy S i9000 getting root permissions
Http://android.sj.91.com/content/2010-07-14/20100714181645219.shtml

Copy update.zip to the SD card. Press the three keys in the shutdown state: the volume key (left side ),
The Home key and the activation key (on the right) will enter the recovery mode.

The local Android recovery system is 3E, And the menu is blue. The prompt is yellow.
Use the volume key to Select Apply sdcard: update.zip, and press the Home Key to confirm. The prompt is:
Signature Verification Failed

Apparently, root failed again! To solve this signature authentication failure, it seems that the kernel needs to be refreshed.
Downgrade Android Recovery System to 2E.


3. Use superoneclick

We had to try superoneclick again when we hit the wall twice. At first, we didn't know the details of superoneclick.
What is the principle. Just follow the method of previous netizens:

I9000 2.2 jpd/jpe simple root tutorial
Http://www.angeeks.com/thread-550165-1-1.html

Note: in the previous article, select <run superoneclick.exe In the compressed package "shell root"> change
Select "root" "!

Run superoneclick.exe and click the root button on the graphical interface. The complete prompt is as follows:

Killing ADB server...
OK
Starting ADB server...
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 kb/s (0 bytes in 5392.000 S)
OK
Chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
*** If it keeps looping, try disabling USB debugging now ***
Killing ADB server...
OK
Starting ADB server...
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
Rooted
Getting Mount path...
/Dev/block/stl6
OK
Remounting system with read-write access...
OK
Pushing su...
Failed to copy Su to '/system/bin/Su': no space left on Device
OK
Chmod su...
Unable to chmod/system/bin/su: no such file or directory
OK
Pushing superuser.apk...
204 KB/s (0 bytes in 196521.000 S)
OK
Remounting system with read-only access...
OK
Running a su test...

Note: The system prompts no space left on device. Obviously, the/system directory is full. Use
Super Terminal (better terminal emulator pro v3.37), enter DF (
By the way, the default Chinese keyboard input method has poor compatibility with the Super Terminal and is often unavailable.
If this problem occurs, you can switch to the swype, Samsung keyboard, or sogou Input Method ):
$ DF
DF
/Dev: 155672 k total, 0 K used, 155672 K available (Block Size 4096)
/Mnt/. LFS: function not implemented
/Mnt/ASEC: 155672 k total, 0 K used, 155672 K available (Block Size 4096)
/System: 282432 k total, 282432 K used, 0 K available (Block Size 4096)
...

System has no available space, and Su cannot be copied. Therefore, root cannot be obtained!


Iv. Dark flowers

All three methods to obtain the root account have been tried, and all failed. It seems that only one method is available. However
In terms of the software version, there is no need to brush the machine! The most reliable superoneclick is due to/System
The directory has no space. /System is read-only by default. to remount to read and write, you still need
Root permission. Isn't it a conflict of restrictions?

View the superoneclick file directory and find the following files:

F:/own/phone/Samsung/tools/superoneclick directory

2010/10/16 577,335 adb.exe
2010/10/18 339,885 adblinux
2010/10/18 171,656 adbmac
2010/10/16 96,256 adbwinapi. dll
2010/10/16 60,928 adbwinusbapi. dll
2010/10/16 1,062,992 busybox
2010/10/16 5,392 rageagainstthecage
2010/10/16 24,120 sqlite3
2010/10/16 26,264 Su
2010/11/04 379,392 superoneclick.exe
2010/10/16 196,521 superuser.apk

Suand rageagainstthecageare copied to the mobile phone for operation, and adb.exe is the core!
Not only the Windows version, but also the adblinux version ),
Adbmac (Mac version ). Then, upload the pea directory to find files like adb.exe.
Finally, I realized the key to the problem!

In the command line (start and run cmd.exe), locate the directory where ADB is located and run:

C:/users/Administrator> D:
D:/> Cd D:/greensoft/wandoujia
D:/greensoft/wandoujia> ADB

Android debug bridge version 1.0.26
... (Some content is omitted due to excessive content)

Devices-list all connected devices
Connect Disconnect
Device commands:
ADB push <local> <remote>-copy file/DIR to Device
ADB pull <remote> [<local>]-copy file/DIR from Device
ADB sync [<directory>]-copy host-> device only if changed
(See 'adb help all ')
ADB shell-run remote shell interactively
ADB shell <command>-run remote shell command
Adb emu <command>-run emulator Console Command
ADB logcat [<filter-spec>]-view device log
...
ADB install [-L] [-R] [-S] <File> -...
ADB uninstall [-K] <package> -...
ADB bugreport-return all information from the device
That shoshould be added in a bug report.

ADB help-show this help message
ADB version-show version num
...
Scripting:
ADB wait-for-device-block until device is online
ADB start-server-ensure that there is a server running
ADB kill-server-kill the server if it is running
ADB get-state-prints: offline | bootloader | Device
ADB get-serialno-prints: <serial-number>
ADB status-window-continuously print device status for a specified device
ADB remount-remounts the/system partition on the device read-write
ADB reboot [bootloader | recovery]-reboots the device, optionally into the bootloader or recovery program
ADB reboot-bootloader-reboots the device into the bootloader
ADB root-restarts the adbd daemon with root permissions
Adb usb-restarts the adbd daemon listening on USB
Adb tcpip <port>-restarts the adbd daemon listening on TCP on the specified port
...

The function is very comprehensive. Take a closer look at ADB root and ADB remount. But rest assured that these
It must have been restricted and cannot be used! Otherwise, the foreign cool won't spend so much effort to crack the program!
Superoneclick actually uses the debugging interface ADB. Let's take a closer look at the superoneclick above.
The failure log contains the following content:

Running rageagainstthecage...
Rooted

This indicates that the root permission has been obtained, but an error occurred while copying the Su. While rageagainstthecage is
Key Permission extraction procedures. After obtaining the root, superoneclick Remount the/system:

Remounting system with read-write access...
OK

Once again, after executing rageagainstthecage, you can check the log to determine that the root user is successfully obtained.
Permission! When I tried z4root at the time, I suspected that the root failure was also caused by the full disk space problem.

5. Complete steps for obtaining root permissions, which are written at the end

After "3. Get root permissions 3. Use superoneclick" (do not restart your phone or unplug it.
USB connection, otherwise you need to re-run the superoneclick point root button), and then enter from the command line
ADB shell. The following message is displayed:

F:/own/phone/Samsung/tools/superoneclick> ADB Shell
#

This "#" is critical, indicating that the current root permission is already in use! If it is "$", superoneclick executes
Unsuccessful (It is also said that the rageagainstthecageexecution was not successful, and then superoneclick.exe was run again)
Click root. Until you enter ADB shell, the # is displayed!

Run the following command:

1) Modify/system to read/write
# Mount-O remount RW/System
2) enter the built-in application directory
# Cd/system/APP
3) Delete the weather clock that comes with Samsung, so that/system has some space available. Of course, you can also delete the clock before it is deleted.
Copy one copy to the SD card (command: CP/system/APP/samsungwidget_weatherclock.apk/mnt/sdcard /.)
# Rm samsungwidget_weatherclock.apk

After completing the preceding three steps, run superoneclick.exe and click root!
Then restart the mobile phone, and the mobile app will have one more authorization management (dedicated management of applications that require the root permission, in fact
Is the superuser.apk in superoneclick, which can be manually installed ).

Then, run root explorer on your phone, and you will be prompted if you want to grant root permissions to the current application! If
Then, the root Explorer will run in the highest permission mode, and the contents of all directories can be seen! Ning waihui
You can also see that root explorer is granted root permissions.

The complete superoneclick log for root success is attached:

Killing ADB server...
OK
Starting ADB server...
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
337 kb/s (0 bytes in 5392.000 S)
OK
Chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
*** If it keeps looping, try disabling USB debugging now ***
Killing ADB server...
OK
Starting ADB server...
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
Rooted
Getting Mount path...
/Dev/block/stl6
OK
Remounting system with read-write access...
OK
Pushing su...
96 kb/s (0 bytes in 26264.000 S)
OK
Chmod su...
OK
Pushing superuser.apk...
204 KB/s (0 bytes in 196521.000 S)
OK
Remounting system with read-only access...
OK
Running a su test...