Invalid command resize-logical-partition:system_a:1373093888 #252
Comments
|
Have you tried GrapheneOS without using avbroot before to see if it actually works? This doesn't seem like a problem caused by avbroot to me. Also what fastboot version are you using? Have you tried the standalone version as described in the GrapheneOS CLI Install guide? |
|
Oops, I overlooked this when updating the documentation after avbroot started patching The problem is that recent Android versions have 2 fastboot modes:
So the procedure should be:
I need to find a good way to document that in the README without turning this step into a big script. |
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
|
Wow, it definitely should be in README ;) 3 day of attempts... |
I seen your commit, but I don't see this step anywhere in readme.md. I see you added this step though:
Is this supposed to be equivalent to steps above? |
|
The instructions in the new commit (https://github.com/chenxiaolong/avbroot/pull/253/files?short_path=b335630#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5) are an easier way to accomplish the same thing. I haven't merged the changes yet because although I'm pretty confident it'll work, I haven't had the time to factory reset my device and test it myself. |
|
Where is the |
EDIT: Hmm, no, looks like more stuff is needed. I'll have to investigate. |
|
For now you can extract
|
|
You might also need |
|
For now, I've updated Once I figure out exactly what is needed to get the |
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. This is a bit slower than the old method of only flashing the partition images that were modified, but is much less accident-prone and is a well supported and tested feature of fastboot. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
`fastboot flashall` is identical to the `fastboot update` command used by the Pixel factory images, except it reads from a directory instead of a zip file. It knows how to flip between the fastboot and fastbootd modes without user intervention. Fixes: #252 Signed-off-by: Andrew Gunnerson <[email protected]>
After flashing both partitions with the factory grapheneOS images. I can only get to this step.
~/Desktop/avbroot/extracted$ for image in *.img; do
partition=$(basename "${image}")
partition=${partition%.img}
fastboot flash "${partition}" "${image}"
done
Sending 'boot_a' (65536 KB) OKAY [ 1.847s]
Writing 'boot_a' OKAY [ 0.245s]
Finished. Total time: 2.096s
Sending 'init_boot_a' (8192 KB) OKAY [ 0.246s]
Writing 'init_boot_a' OKAY [ 0.033s]
Finished. Total time: 0.283s
Resizing 'system_a' FAILED (remote: 'Invalid command resize-logical-partition:system_a:1373093888')
fastboot: error: Command failed
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.037s]
Finished. Total time: 0.039s
Sending 'vendor_boot_a' (65536 KB) OKAY [ 1.876s]
Writing 'vendor_boot_a' OKAY [ 0.238s]
Finished. Total time: 2.116s
Luckily I have the other partition so no issues.
The text was updated successfully, but these errors were encountered: