Updated The Ultimate Rooting Guide (markdown)
parent
55b2d33947
commit
b10ad0b392
|
|
@ -61,31 +61,33 @@ Note: In any case you find the printed message is weird, or errors happen that y
|
|||
|
||||
Note2: Absolute do NOT try to decompile the PKG on your computer via the unpack tool in the script.
|
||||
|
||||
### 0x3 Obtain Android ADB Access (Optional, Subject to Change)
|
||||
### 0x3 Obtain Android ADB (Root) Access
|
||||
|
||||
If you want to install customized apps on your own, proceed. Otherwise you can stop here, and wait for flash-able PKGs coming out.
|
||||
Required system version:
|
||||
* `1.4.01.16100` (for RP1)
|
||||
* `1.4.02.09061` (for CP1)
|
||||
If not, request it in [Issues](https://github.com/HappyZ/dpt-tools/issues) and wait for your modifications out.
|
||||
|
||||
Make sure your system version is `1.4.01.16100` (for RP1) or `1.4.02.09061` (for CP1). If not, wait for corresponding modifications out.
|
||||
|
||||
You will need to modify your Android boot partition. Flashing the modded `boot.img` ***may*** disable the DPA connection via USB cable (but wireless still works with DPA). After making all changes to the system, you can restore your original `boot.img` if you want USB connection working again, but losing mass storage and ADB.
|
||||
The modification will change your Android boot partition.
|
||||
|
||||
Download `FwUpdater.pkg` from this [example](https://github.com/HappyZ/dpt-tools/tree/master/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img).
|
||||
|
||||
Boot into normal system, type `fw` in the tool (`python dpt-tools.py -ip xxx`) to update **with the downloaded PKG***. After update, it will say `update failure`, but it is actually flashed.
|
||||
In the interactive shell, type `fw` and press Enter key.
|
||||
|
||||
And you can run `adb devices` on your computer to see if your DPT appears. To address "unauthorized" issue, do the following. On your laptop/desktop, (Mac or Linux):
|
||||
```
|
||||
mv ~/.android/adbkey ~/.android/adbkey_bak
|
||||
cp python_api/assets/adbkey ~/.android/adbkey
|
||||
adb kill-server
|
||||
adb devices
|
||||
```
|
||||
(Windows should do similar thing but at `C:\Users\<user profile>\.android\`)
|
||||
It'll ask the file path of the downloaded PKG. Type the full file path, or drag the file into terminal.
|
||||
|
||||
It'll ask you to confirm it is the correct file. Type `yes` and press Enter key.
|
||||
|
||||
Your DPT will say `preparing for the update...` and then the DPT will restart and show update is in progress.
|
||||
|
||||
After update, it will say `update failure`, but it is actually flashed.
|
||||
|
||||
And you can run `adb devices` on your computer to see if your DPT appears.
|
||||
|
||||
Note: we are still unclear about [the issue DPA cannot be connected](https://github.com/HappyZ/dpt-tools/issues/58).
|
||||
|
||||
### 0x4 Obtain Android Root Access (Optional, Subject to Change)
|
||||
|
||||
Download `FwUpdater.pkg` from this [example](https://github.com/HappyZ/dpt-tools/blob/master/fw_updater_packer_unpacker/pkg_example/flashable_supersu/).
|
||||
|
||||
Boot into normal system, use `fw` in the tool to update **with the downloaded PKG***. After update, it will say `update failure`, but it is actually flashed.
|
||||
|
||||
After then, you can do `adb shell` and then type `su` to verify if you have obtained the sudo access. You can now use `adb install` to install any packages. However, it does appear that all third party apps have super small font.
|
||||
Boot into normal system, use `fw` in the tool.
|
||||
Loading…
Reference in New Issue