Updated The Ultimate Rooting Guide (markdown)

HappyZ 2019-07-31 16:22:26 -05:00
parent ec6b9e1a55
commit efba0ff634
1 changed files with 8 additions and 10 deletions

@ -86,7 +86,7 @@ Note2: Absolute do NOT try to decompile the PKG on your computer via the unpack
### 0x3 Obtain Android ADB (Root) Access
The modification will change your Android boot partition.
The modification will change your Android boot partition. If you are not sure what ADB is, please read [this xda page](https://www.xda-developers.com/install-adb-windows-macos-linux/).
Download corresponding PKG for your system version:
* `1.4.01.16100` (for RP1) [download](https://github.com/HappyZ/dpt-tools/blob/6e8e30c0062ac51410caa9ddf5adb959d84ab038/fw_updater_packer_unpacker/pkg_example/flashable_mod_boot_img_no_mass_storage/FwUpdater.pkg)
@ -96,17 +96,15 @@ Download corresponding PKG for your system version:
If not found, request it in [Issues](https://github.com/HappyZ/dpt-tools/issues) and wait for your modifications out. Don't proceed with a different version.
In the interactive shell, type `fw` and press Enter key.
In the interactive shell, type `fw` and press Enter key. It'll ask the file path of the downloaded PKG. Type the full file path, or drag the file into terminal.
It'll ask the file path of the downloaded PKG. Type the full file path, or drag the file into terminal.
Then it'll ask you to confirm it is the correct file. Type `yes` and press Enter key. Your DPT will now say `preparing for the update...` and then the DPT will restart and show update is in progress. After update, it will show an error message saying `update failure`, but it is actually flashed.
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 (it may take a while to boot ADBD after DPT boots up, if you have waited for >1min, try to unplug and plug back in the cable, and do `adb kill-server && adb devices` several times, it eventually will come up! Fully tested).
To validate, in your computer, quit `dpt-tool` and in terminal run `adb devices` to see if your device appears. If it didn't show up:
* Check your cable
* Try `adb kill-server && adb devices`
* If you are using MacOS, log off and log back in (or reboot)
* If you are using Windows, you should use `<path/to/adb>/adb.exe devices` instead (you can download it according to [this xda page](https://www.xda-developers.com/install-adb-windows-macos-linux/))
### 0x4 Obtain Android Root Access (Optional, Subject to Change)