Open QGB opened 2 years ago
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb fastboot flash boot C:\Android\SDK\skins\nexus_6p\magisk_patched-24300_64n97.img
adb.exe: unknown command fastboot
C:\Android\SDK\platform-tools>fastboot flash boot C:\Android\SDK\skins\nexus_6p\magisk_patched-24300_64n97.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 12891432).
Sending 'boot' (12589 KB) OKAY [ 0.297s]
Writing 'boot' OKAY [ 0.196s]
Finished. Total time: 0.598s
C:\Android\SDK\platform-tools>
Microsoft Windows [版本 10.0.18363.1316]
(c) 2019 Microsoft Corporation。保留所有权利。
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
failed to authenticate to 192.168.1.10:5555
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
already connected to 192.168.1.10:5555
C:\Android\SDK\platform-tools>adb devices
List of devices attached
192.168.1.10:5555 device
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
cannot connect to 192.168.1.10:5555: 由于目标计算机积极拒绝,无法连接。 (10061)
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
cannot connect to 192.168.1.10:5555: 由于目标计算机积极拒绝,无法连接。 (10061)
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
cannot connect to 192.168.1.10:5555: 由于目标计算机积极拒绝,无法连接。 (10061)
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
connected to 192.168.1.10:5555
C:\Android\SDK\platform-tools>adb devices
List of devices attached
192.168.1.10:5555 device
C:\Android\SDK\platform-tools>adb logcat
- waiting for device -
^C
C:\Android\SDK\platform-tools>adb devices
List of devices attached
84B7N18130000155 recovery
C:\Android\SDK\platform-tools>adb devices
List of devices attached
84B7N18130000155 recovery
C:\Android\SDK\platform-tools>adb sideload
adb.exe: sideload requires an argument
C:\Android\SDK\platform-tools>adb sideload C:\angler-ota-opm7.181205.001-abb36a2f.zip
Total xfer: 1.01x
C:\Android\SDK\platform-tools>adb shell
adb.exe: no devices/emulators found
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
84B7N18130000155 device
C:\Android\SDK\platform-tools>adb shell
angler:/ $ su
/system/bin/sh: su: not found
127|angler:/ $ exit
C:\Android\SDK\platform-tools>adb reboot recovery
C:\Android\SDK\platform-tools>
C:\Android\SDK\platform-tools>adb devices
List of devices attached
84B7N18130000155 device
C:\Android\SDK\platform-tools>adb reboot fastboot
C:\Android\SDK\platform-tools>adb devices
List of devices attached
84B7N18130000155 device
C:\Android\SDK\platform-tools>adb reboot fastboot
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>adb fastboot flash boot C:\Android\SDK\skins\nexus_6p\magisk_patched-24300_64n97.img
adb.exe: unknown command fastboot
C:\Android\SDK\platform-tools>fastboot flash boot C:\Android\SDK\skins\nexus_6p\magisk_patched-24300_64n97.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 12891432).
Sending 'boot' (12589 KB) OKAY [ 0.297s]
Writing 'boot' OKAY [ 0.196s]
Finished. Total time: 0.598s
C:\Android\SDK\platform-tools>fastboot flash boot C:\Android\SDK\skins\nexus_6p\angler-ota-opm7.181205.001-abb36a2f\boot.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 12383462).
Sending 'boot' (12093 KB) OKAY [ 0.323s]
Writing 'boot' OKAY [ 0.190s]
Finished. Total time: 0.613s
C:\Android\SDK\platform-tools>fastboot devices
84B7N18130000155 fastboot
C:\Android\SDK\platform-tools>fastboot flash recovery C:\Android\SDK\skins\nexus_6p\twrp-3.6.1_9-0-angler.img
Sending 'recovery' (18412 KB) OKAY [ 0.436s]
Writing 'recovery' OKAY [ 0.285s]
Finished. Total time: 0.774s
C:\Android\SDK\platform-tools>
C:\Android\SDK\platform-tools>
C:\Android\SDK\platform-tools>adb devices
List of devices attached
C:\Android\SDK\platform-tools>fastboot devices
84B7N18130000155 fastboot
C:\Android\SDK\platform-tools>fastboot flash recovery C:\Android\SDK\skins\nexus_6p\twrp-3.6.1_9-0-angler.img
Sending 'recovery' (18412 KB) OKAY [ 0.436s]
Writing 'recovery' OKAY [ 0.283s]
Finished. Total time: 0.775s
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
cannot connect to 192.168.1.10:5555: 由于目标计算机积极拒绝,无法连接。 (10061)
C:\Android\SDK\platform-tools>adb connect 192.168.1.10
connected to 192.168.1.10:5555
C:\Android\SDK\platform-tools>recovery又神奇的恢复到了官方原版的recovery了。为什么会出现这样的情况呢?我们最 简单的理解 为,手机每次开机启动都会检验boot和系统文件,当系统文件和boot都是原厂 文件后,就会自动合成恢复到官方recovery ,修改下boot或者系统文件即可。到底怎么去修 改boot和系统文件呢?目前最常见的就是刷入magisk.apk.zip面具授权卡刷包,等待面具root刷完, 就彻底的固定住了TWRP_recovery了,无论怎么重启,都不会还原了
adb reboot fastboot #无效