ジャンクPixel #2
前回ファクトリーイメージ焼いてといったけど、よくよく考えたらログを確認してない…
ということで確認をしてみた
Sending 'bootloader_a' (32424 KB) OKAY [ 0.790s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.005s]
Finished. Total time: 3.106s
Rebooting into bootloader OKAY [ 0.007s]
Finished. Total time: 0.011s
Sending 'radio_a' (57140 KB) OKAY [ 1.386s]
Writing 'radio_a' OKAY [ 0.492s]
Finished. Total time: 2.404s
Rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.010s
--------------------------------------------
Bootloader Version...: 8996-012001-1812132253
Baseband Version.....: 8996-130181-1811270246
Serial Number........: xxxxxxxxxxxxxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.045s]
Checking 'version-bootloader' OKAY [ 0.037s]
Checking 'version-baseband' OKAY [ 0.007s]
Setting current slot to 'a' OKAY [ 0.099s]
extracting boot.img (29 MB) to disk... took 0.340s
archive does not contain 'boot.sig'
Sending 'boot_a' (29757 KB) OKAY [ 0.789s]
Writing 'boot_a' OKAY [ 0.257s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product_services.img'
extracting system.img (1944 MB) to disk... took 46.994s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 12.339s]
Writing 'system_a' OKAY [ 3.500s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 12.401s]
Writing 'system_a' OKAY [ 3.484s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 12.353s]
Writing 'system_a' OKAY [ 3.456s]
Sending sparse 'system_a' 4/4 (418288 KB) OKAY [ 10.147s]
Writing 'system_a' OKAY [ 2.839s]
extracting system_other.img (312 MB) to disk... took 2.764s
archive does not contain 'system.sig'
Sending 'system_b' (319664 KB) OKAY [ 7.510s]
Writing 'system_b' OKAY [ 2.197s]
extracting vendor.img (259 MB) to disk... took 2.069s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (265784 KB) OKAY [ 6.215s]
Writing 'vendor_a' OKAY [ 1.849s]
archive does not contain 'vendor_other.img'
Erasing 'userdata' OKAY [ 1.801s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 1c480b68-5bb4-11e9-b71c-1d7797563276
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4272 KB) OKAY [ 0.146s]
Writing 'userdata' OKAY [ 0.103s]
Rebooting OKAY [ 0.048s]
Finished. Total time: 145.063s
Press any key to exit...
あれ？
bootコケてない…？
と思いましたのでFlash-allを書き換えて手動インストールに変えました
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-sailfish-8996-012001-1812132253.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-sailfish-8996-130181-1811270246.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-sailfish-pq2a.190405.003.zip
↓
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-sailfish-8996-012001-1812132253.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-sailfish-8996-130181-1811270246.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
:: fastboot -w update image-sailfish-pq2a.190405.003.zip
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
:: fastboot flash modem modem.img
modem.imgは焼くかわからないのでコメントアウトにしてます
これでイメージ焼いたらGoogleロゴから進んだので可能性を感じたのですが、途中で落ちました
VerizonモデルのBootloader unlockツールを使うとどうとかと見たのですがそれを使って壊れてるのか？と考えたりもしたのですが、さてどうなってるのか
いろいろ検索してLPDDR4が死んでたらBootloaderのアンロックがうまくできないという情報を得たのでおそらくLPDDR4は死んでない
イメージで焼けてない部分のところで異常なデータになってロックされた……？
という状態なのかなといった現状みたいですね…
